System Snapshots

overview system snapshots contain a backup of everything in a system, including all tenants, vms, nas volumes, networks, and settings a system snapshot can be used to restore an entire system additionally, the following can be imported and restored from a system snapshot individual tenants individual nas volumes individual vms automated system snapshots by default, system snapshots run according to the included system snapshots profile the system snapshot schedule can be changed by modifying this default profile or assigning a different profile assign different automated schedule from the top menu , click system > system snapshots from the left menu, click edit snapshot profile select the desired snapshot profile click submit add period to system snapshot profile from the top menu , click system > system snapshots from the left menu, click view snapshot profile from the left menu, click profile periods from the left menu, click new configure fields as desired click submit modify system snapshot profile from the top menu , click system > system snapshots from the left menu, click view snapshot profile from the left menu, click profile periods select the desired profile from the left menu, click edit modify fields as desired click submit remove period from system snapshot profile from the top menu , click system > system snapshots from the left menu, click view snapshot profile from the left menu, click profile periods select the desired profile from the left menu, click delete click yes to confirm manual system snapshots a manual snapshot can be taken at any time take a manual snapshot of entire system from the top menu , click system > system snapshots from the left menu, click new enter a name for the snapshot (optional), enter a description set expiration type set date allows you to configure a custom date/time never expire sets snapshot to never expire always consider vsan usage when setting snapshots to never expire as source data diverges more from the snapshot data, vsan usage will grow using the never expire option is generally not recommended in the expires field, select a data and time for expiration this field is only visible if expiration type is set to set date the private checkbox can be deselected to allow tenants access to their own data within the snapshot click submit restores from system snapshots korgrid provides several platform level snapshots as part of the service, available to you as a built in benefit if you need recovery points outside of korgrid’s standard snapshot cadence, you can also configure your own system level snapshots and define schedules that best fit your operational needs access system snapshots from the top menu , click system > system snapshots select the desired provider snapshot from the left menu , click request from provider click yes to confirm after the process is confirmed, tranferring the snapshot to your tenant can take up to a minute (depending on the size delta of the snapshot) once transferred the snapshot will display as a local snapshot and can be used for system, vm, and volume restores after a snapshot has been requested from korgrid, and displays as a local snapshot, it can be edited to modify description and expiration when changing the expiration date it's important to consider effects on your vsan usage long term snapshots can substantially increase storage usage as data divergence between the snapshot and live data increases over time restore entire system full system restoration is only supported on the local cluster where the snapshot was taken this operation can't be used to restore one site over another for example, you can't restore central2 with a system snapshot from west1 in addition, a full system restoration will require a reboot of all nodes a full system restoration will revert all system components, including virtual machines tenant configurations nas data system settings this is a full restoration that can't be selectively applied to specific components first, request a system snapshot using the docid 5zmc9 ffyr8snfazak5iu instructions select the desired provider snapshot from the left menu , click restore recommended , leave the option checked to take a snapshot of the system prior to the restoration this allows for reverting the system back, if needed be default, the topion to reboot all nodes after the restore is enabled this will let the system handle the node reboots for you a reboot of all nodes is necessary to complete the system level restore click proceed click yes , to confirm to cancel the operation, the cancel button must be clicked within 60 seconds; otherwise, the restore operation will continue restore select tenants first, request a system snapshot using the docid 5zmc9 ffyr8snfazak5iu instructions select the desired provider snapshot from the left menu , click view tenants select the desired tenant(s) to restore from the left menu , click recover click yes to confirm the snapshot tenant listing will display a checkmark and complete message next to each tenant by default, tenant restorations are restored as a new tenant instance if you wish to overwrite the tenant during restoration, follow the docid 5zmc9 ffyr8snfazak5iu instructions below restore tenant (overwrite) from the top menu , click tenants > tenant nodes select the desired tenant nodes from the left menu , click power off from the top menu , click tenants > list select the tenant whose nodes have been powered off from the left menu , click view from the left menu , click snapshots select the desired snapshot from the left menu , click restore click procreed the changes will take effect when the tenant is powered on again restore select vms first, request a system snapshot using the docid 5zmc9 ffyr8snfazak5iu instructions select the desired provider snapshot from the left menu , click view vms select the desired virtual machine(s) from the left menu , click recover click yes to confirm the snapshot vm listing will display a checkmark and complete message next to each vm by default, vm restorations are restored as a new vm instance if you wish to overwrite the vm during restoration, follow the docid\ dd3o9ejgxtw6geat0vejp instructions