> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.ai/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.ai/docs/_mcp/server.

# Cross-region snapshots

> Copy snapshots across IBEE regions for disaster recovery and cross-region cloning.

Cross-region snapshots let you keep a copy of a Cloud VM's recovery point in a region other than where the source VM lives. The primary use case is disaster recovery — if a region is unavailable, you can spin up a new VM in another region from the copied recovery point.

## When to use this

* **Disaster recovery (DR)** — keep a recent recovery point off-region so a regional incident doesn't take your data with it.
* **Region migration** — move a VM from one region to another by copying a snapshot, restoring as a new VM, then decommissioning the original.
* **Latency-driven cloning** — stand up a clone closer to a different user base.

For routine, in-region protection, regular [snapshots](/docs/tools/snapshots/create-a-snapshot) and [scheduled backups](/docs/tools/backups) are sufficient.

## Available regions

Cloud VMs are currently available in the **Asia** region across these locations:

| Region | Location         | Code |
| ------ | ---------------- | ---- |
| Asia   | Amaravati, India | AVR  |
| Asia   | Hyderabad, India | HYD1 |

A multi-region (cross-continent) layout is on the roadmap. Until then, "cross-region" snapshot copy applies between locations within Asia.

## Workflow

The high-level pattern, regardless of which UI controls are surfaced for copy:

### 1. Take a snapshot in the source region

In the source VM's **Snapshots** tab, create a recovery point with the Capture Mode that matches your DR plan ([Create a snapshot](/docs/tools/snapshots/create-a-snapshot)). For DR, **All attached volumes** is the safest default.

### 2. Copy to the target region

From the recovery point's **Details** view, copy the snapshot to the target region. The platform replicates root and captured data disks to the destination region's storage and produces a recovery point there.

The copy operation runs as an activity event you can track via the [Activity feed](/docs/infrastructure/cloud-vms/monitoring#activity-feed).

### 3. Restore in the target region

In the target region, open the copied recovery point and use **Create New VM** to provision a new VM from it. Pick a plan available in the target region.

### 4. Cut over

Update DNS, callers, or load balancer backends to point at the new VM. Verify, then decommission the original VM if you're migrating rather than running active-passive DR.

## What's copied

Cross-region snapshots replicate the same content as in-region snapshots:

* The **root disk**.
* Any **captured data volumes** (per the Capture Mode used at snapshot time).

Mount instructions for data volumes remain available on the copied recovery point — they're identical to the source because device paths inside the guest don't depend on region.

## Considerations

* **Transfer time** scales with recovery storage. A 60 GB recovery point will take longer to copy than a 10 GB one.
* **Cost** — cross-region snapshots are billed for storage at both ends until you delete one. See [Backup pricing](/docs/tools/backups/backup-pricing); cross-region copy may have an additional transfer component.
* **Eventual consistency** — copying is asynchronous; don't restore from the destination until the copy event reports succeeded.
* **Plans available in the target region** — the **Available Upgrades** dropdown only shows plans the target region offers. Pick a plan equal to or larger than the source VM's plan to avoid disk shrink issues.

## DR drill checklist

Test your DR plan periodically — a snapshot you've never restored is just hope.

1. Take a fresh snapshot in the source region.
2. Copy it to the target region.
3. Restore as a **new VM** in the target region.
4. Verify the application boots, the data is intact, and external dependencies (DNS, DBs, queues) are reachable.
5. Document any guest-level steps (mount commands, service start order) that aren't part of the platform restore.
6. Delete the test VM and copied recovery point if you don't need to keep them.

## Related pages

* [VM snapshots overview](/docs/tools/snapshots)
* [Create a snapshot](/docs/tools/snapshots/create-a-snapshot)
* [Restore a snapshot](/docs/tools/snapshots/restore-a-snapshot)
* [VM backups](/docs/tools/backups)
* [Regions and locations](/docs/getting-started/overview/regions-and-locations)