Cloud Snapshots contain a backup of everything in a system, including all tenants, VMs, NAS volumes, networks, and settings. A cloud snapshot can be used to restore an entire system. Additionally, the following can be imported and restored from a cloud snapshot:
*VM snapshots contained within a cloud snapshot are crash-consistent. Individual VM snapshots allow a quiesce option (guest agent required). See VM Snapshots and Restores for VM-level snapshot instructions.
By default cloud snapshots run according to the included Cloud Snapshots profile. The cloud snapshot schedule can be changed by modifying this default profile or assigning a different profile.
A manual snapshot can be taken at any time.
In the Expiration Type field, "Never Expire" can be selected, however, it is important to consider vSAN space utilization. Initially source and snapshot are the same and thus there is no impact on storage; but, as source data diverges more from the snapshot data, there is less deduplication between the two and thus more vSAN usage. It is typically not recommended to use the Never Expire option unless necessary.
The following directions are applicable to systems that are tenants themselves. If provider has allowed it, a tenant can access a snapshot of their own cloud from the provider's cloud snapshots. Once requested from the provider, the snapshot is then available to use for restoring individual VMs or entire cloud.1. From the main dashboard, Select System from the left menu.
From the main dashboard, Select System from the left menu.
Select Cloud Snapshots from the left menu.
A listing of available snapshots is displayed; those displayed with a type of Provider are snapshots taken by the host. Click to select the desired provider snapshots (selected snapshots will show a checkmark).
Click Request From Provider on the left menu.
A Confirmation dialog appears. Click Yes to continue pulling down the selected snapshots.
After the process is confirmed, transferring a snapshot down from the host can take 15 or more seconds. Once transferred the snapshot will now display with a type of Local with a green indicator; at this point it can be used for cloud, tenant, VM and volume restores from cloud snapshots as described below.
After a snapshot is requested from provider, and displays as type=Local, the snapshot can be edited to modify description and expiration. When changing expiration to a longer period it is important to consider effects on storage; long-term snapshots can substantially increase storage usage as data divergence between snapshot and live data increases over time.
Restoring an entire cloud reverts everything within the system, including all VMs, tenants, NAS data, and settings.
Restoring entire cloud requires rebooting of all nodes; rebooting nodes can be done without system outages provided there are adequate system resources.
Reboot of all nodes is necessary to complete the cloud restore.
Need more Help? Email support@verge.io or call us at (855) 855-8300