Page History

...

1. Hypervisor Type
2. Template ID or ISO ID
3. Service Offering UUID
4. UUIDs of the Networks to attach
5. IP and MAC Address configurations for each network
6. Disk Offering ID, Volume Sizes, Min IOPS, Max IOPS for all data volumes

• Hypervisor and Template/ISO are retrieved directly from the original instance
• Service Offering and Network details (including IP/MAC configurations stored in a comma separated format for each network) are stored in the backup_details table
• Volume information is already stored in the backed_volumevolumes column in the backup table. It has details like Disk Offering UUID, size and type. It is enhanced to also store deviceId, minIOPS and maxIOPS. This information is stored for all the volumes.

...

Some properties are not fetched from backup but still needs special handling.

• ISO : ISO is attached  while creating the instance and detached  before restore, so that the new instance doesn't boot with ISO, but still has the metadata that it was created using that ISO.
• SSHKeys : SSH key if given by the user is set after restore so that it doesn't get overwritten during restore.
• User data : User data is not re-applied when restoring from a backup.  Backups are expected to capture the full VM state after user data (cloud-init) has been applied. Therefore, user data is considered already baked into the disk image.

...