ASP R6.0.x used cloning for Virtual Machine Backup. Starting with ASP R7.x and onwards the cloning feature has been deprecated in favor of snapshot. Snapshot is the only virtual machine backup method supported with ASP R7.x.
Many Avaya products that are certified to deploy on Avaya Solutions Platform (for example, Avaya Aura® documentation) refer to snapshots at the application level for various procedures.
Reference application specific documentation for detailed instructions on how to utilize the Virtual Machine snapshot.
Note:
Use of the Virtual Machine snapshot requires that the virtual machine to be powered off. A maximum of three snapshots per virtual machine is supported by Avaya. It is critical to remove Virtual Machine snapshots as soon as possible, no later than 48 hours after they are created, and to always assess available disk space prior to performing a Virtual Machine snapshot.
Important:
Snapshot Deletion Order: qcow2 external snapshots form a dependent chain (01 → 02 → 03...). To prevent disk corruption, snapshots must be deleted in reverse order (newest to oldest). Libvirt will block deleting intermediate (non-leaf) snapshots until all newer child snapshots are removed first.
