It may be beneficial to read about backup policies on Katapult.
A virtual machine backup policy effectively defines a single backup policy for all system disks associated with it and so setting a once per day policy at 12am will see all disks on the machine backed up at 12am. It is also possible for you to define backup policies at the disk level too should you wish to backup a single disk more frequently - see System Disk Backup Policies for more information.
The virtual machine level disk backup policy will now be created. Note that this type of backup policy does not include Shared Disks. To backup a shared disk you must specify a backup policy on that disk separately. See Shared Disk Backup Policies for more information.
The changes will apply on the next backup run.
The backup policy and associated backup data will then be moved to the deleted items within Katapult. It will be removed automatically after 48 hours. It can also be reinstated during that time if needs be.
To create an ad-hoc backup of all disks in your virtual machine, follow these steps:
The backup will then initiate.
As virtual machine level backups backs up each disk individually you are able to restore any one of those individual disks into a new disk. You can then do with this new disk as you wish, i.e. mount it to retrieve lost data, or alternatively use it as a replacement for a disk to effectively roll the disk state back in time. The choice is yours. To learn how to restore a disk backup into a new disk see our Backup Restoration how-to guide.