Introducing Managed Instance’s Data Volume Persistence

Data volume persistence maintains the data volumes during Spot instance replacement. All the data on the volumes that were attached at the time of the previous instance termination will be present on the new instance, using the same BlockDeviceMapping configuration upon instance replacement.

Configuring Data Volume Persistence

To configure data volume persistence head to the Managed Instance’s configuration, select “Persistent Resources”, check the “Persist Data Volumes” option, and then select a persistence method.

 

Managed Instances provide 2 different methods for data volume persistence:

  • Snapshot Backups: Periodic snapshots of any data volumes are taken while the instance is running. For each data volume, 3 snapshots are kept. Upon Spot instance replacement, a new EBS volume is created from the latest snapshot and is attached to the new instance upon launch by updating the it’s launch specification’s Block Device Mapping.
  • Reattach: Recommended for large data volumes. The same EBS volume is detached from the original instance and reattached to the newly launched instance. If the new instance is launched in a different AZ, a snapshot is used to create a new volume and attach it to the new instance (as volumes can’t be migrated between AZ’s). Initially, volumes can be created based on the AMI’s Block Device Mapping upon the Managed Instance’s first Resume, or attached via the AWS console. The same volumes are maintained as long as the instance is launched within the same Availability Zone.