For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginGet Started
DocsAPI ReferenceChangelog
DocsAPI ReferenceChangelog
    • Home
  • Getting Started
  • Infrastructure
    • GPU VMs
    • Cloud VMs
    • Object Storage
    • Block Storage
  • Network & Security
    • Load Balancer
    • DNS
    • CDN
    • Firewalls
    • SSL Certificates
  • Tools
    • Backups
      • Enable backups
      • Restore from backup
      • Backup pricing
    • Snapshots
    • ISOs
    • SSH Keys
    • API Tokens
    • Secret Manager
    • Container Registry
  • Platform Fundamentals
    • Projects and tenancy model
    • IAM
    • Networking overview
    • Billing and usage
    • Limits and quotas
    • SLA and reliability
  • Tutorials
    • Deploy a web app
    • Host a static website with object storage
    • Run an AI model on a GPU VM
    • Set up a load-balanced architecture
    • Backup and disaster recovery
    • Multi-region deployment
  • Migration Guides
    • Migrate from AWS
    • Migrate from GCP
    • Migrate from Vultr and Linode
    • Move S3 workloads to IBEE Object Storage
    • VM image migration
  • Reference
    • Pricing
    • Regions
    • Limits
    • Error codes
    • Service level agreement
  • Support
    • Contact Support
    • Create a request
    • Troubleshooting guides
    • Visit ibee.ai
LogoLogo
LoginGet Started
On this page
  • Steps
  • Verify the schedule
  • Disable backups
  • What gets captured
  • Best practices
  • Related pages
ToolsBackups

Enable backups

Was this page helpful?
Edit this page
Previous

Restore from backup

Next
Built with

Automated backups capture the root disk and all attached persistent data volumes on a schedule. Once enabled, recovery points appear in the Backup Recovery Points list and can be restored in place, used to create a new VM, or rolled back per-disk.

Steps

1

1. Open Backups

On the server detail page, open the Backups tab.

2

2. Enable Automated Backups

Toggle Automated Backups to Enabled. The schedule controls become editable.

3

3. Pick a frequency

Use the Schedule backups dropdown:

  • Daily — runs every day at the chosen time.
  • Weekly — runs once per week on the chosen day.
4

4. Pick the day (Weekly only)

If you chose Weekly, pick a day under On: Sunday through Saturday.

5

5. Pick the time

Use the At dropdown to choose an hourly UTC slot — 00:00, 01:00, … 23:00.

Pick a window of low workload activity. Backups run online (the VM stays up) but I/O is briefly busier; pick a time outside peak hours.

6

6. Wait for save

Schedule changes save automatically. A Saving… indicator confirms the change has been persisted; once it returns to idle, the schedule is active.

Verify the schedule

The fields you saved remain visible at the top of the Backups tab. The next backup runs at the next matching slot — for example, a Weekly + Sunday + 12:00 UTC schedule saved on Tuesday will first run the following Sunday at 12:00 UTC.

The first run produces a recovery point in Backup Recovery Points:

  • Name like srp-20260509T162709Z
  • Disks: Root + N data disk(s)
  • Storage: total recovery footprint (for example 60 GB)

Disable backups

To stop scheduled backups for a VM, toggle Automated Backups to Disabled. Existing recovery points are retained according to the retention policy and can still be restored — only the schedule is paused.

What gets captured

Backups always capture:

  • The root disk.
  • Every persistent data volume attached at the time the schedule runs.

If you attach a new volume midway through a week, it’s included starting from the next scheduled run. If you detach a volume before a run, that volume is not in subsequent recovery points.

Best practices

  • Pick a low-traffic window. UTC schedules; convert from your local time before choosing.
  • Use weekly + selective snapshots if daily storage cost is a concern — cover routine protection with weekly backups, take manual snapshots before risky changes.
  • Test restore before you need it. Use Create New VM restore mode periodically to confirm your recovery points are usable.
  • Keep separate copies of critical data. Automated backups protect a single VM; for cross-region resilience, also use Cross-region snapshots or replicate to Object Storage.

Related pages

  • VM backups overview
  • Restore from backup
  • Backup pricing
  • Snapshots