Deployment Snapshots¶

What are Deployment Snapshots?¶

Deployment snapshots are manual snapshots of a deployment instance’s state that you can use for disaster recovery.

Key characteristics of deployment snapshots:

• Manual triggers: Create snapshots on-demand as part of your disaster recovery preparedness and runbooks.
• Cross-region disaster recovery: You can create snapshots in a different region than the source deployment. This ensures that your data remains available even in the event of a total regional cloud outage.
• Independent lifecycle: Unlike automated backups that will be cleaned up automatically, manual snapshots are persistent. They remain in your account until you explicitly delete them.

Deployment snapshots are most useful when you want a durable recovery artifact for disaster recovery that you control, separate from automated schedules and retention policies.

For automated backups and point-in-time recovery, see Backup and Point-in-time Restore (PITR).

Managing Deployment Snapshots¶

You can manage deployment snapshots through multiple interfaces:

• Operations Console UI: Access snapshot management from two distinct levels:
  • Use the Deployment Snapshots page to view snapshots across a service environment.
  • Use the Snapshots tab in a deployment instance details view to manage snapshots for that deployment instance.
• Customer Portal: If enabled, customers can create and manage snapshots from the Customer Portal.
• API/CLI: Use the API or CLI for automation and integration.

For operational visibility (including progress and troubleshooting), see Workflows.

Supported Operations¶

Deployment snapshots support the following operations:

• Create
• Copy
• Restore
• Delete

All snapshot operations (create, copy, restore, and delete) run as workflows, so use workflow details for progress and troubleshooting. In cross-region scenarios, both snapshot creation and snapshot copy can incur inter-region transfer and storage costs.

Create a snapshot¶

Create a snapshot when you want a durable recovery artifact for a deployment instance. You can create snapshots in the same region as the deployment instance or in a different region for cross-region disaster recovery. Snapshots remain available until you explicitly delete them.

Copy a snapshot¶

Copy a snapshot to make it available in another region. After copying, you can restore from the copied snapshot in the destination region.

Restore from a snapshot¶

Restore is the operation you use to recover a deployment instance to the state captured by a specific snapshot. Restore is only possible in the same region as the snapshot. If you need to restore in a different region than where the snapshot exists, copy the snapshot to that region first.

Delete a snapshot¶

Delete a snapshot when you no longer need it. Because snapshots are persistent by design, you should periodically review and delete snapshots you no longer need to reduce storage costs and operational clutter. Deletion is permanent. After you delete a snapshot, you can’t restore from it.