Requirements and recommendations
Please ensure that the following requirements are met by the Hyper-V server:
1. ServosityPro version 6.21 or above is installed on the Hyper-V server.
2. The Hyper-V management tools are installed on the Hyper-V server.
3. It is recommended that the temporary directory have disk space of at least 50% of the largest sized virtual machine to be backed up.
4. For backup of virtual machine with snapshot, backup of the whole VM instead of individual disk is highly recommended.
5. The current virtual hard disk specification limits the size of a virtual hard disk to be 2040 GB (2 TB), which can fit a volume of size 2040 GB minus 2 MB.
For details, please refer to:
Limitations - The following are limitations of the MS VM backup module:
1. Virtual machine backed up with the MS VM backup module can only be restored to the original Hyper-V server.
2. Backup of virtual machine with pass through disk (directly attached physical disk) is not supported.
3. For virtual machine with snapshot, the restoration process for individual virtual disk requires manual editing of VM configuration files.
In-depth knowledge on Hyper-V is required.
4. The virtual machine cannot start up if the guest operating system virtual disk is not restored.
5. Restore of individual virtual disk to a different virtual machine is only supported for virtual disk with no snapshot.
6. For backup of individual virtual disk, the restored virtual machine does not support the reversion of previous snapshots, if the snapshot contains disks which are not previously backed up by ServosityPro.
The following steps are performed during a backup job:
1. Connection from the backup client to the backup server is established.
2. Download the server file list from the backup server.
3. Commands are issued to the hypervisor to create snapshot (memory dump) of the virtual machine with Volume Shadow Copy.
Important: The corresponding virtual machine will be paused during the snapshot process, and resume when the snapshot is completed.
Do not attempt to start the virtual machine while it is in the saving state. The snapshot created may be invalid.
Furthermore, the corresponding virtual machine uptime will also be reset to 00:00:00 in the Hyper-V Manager.
4. After generating all files, the files are copied to the temporary spool path and upload to Servosity Backup Servers.
5. Commands are issued to the hypervisor to remove the Volume Shadow Copy snapshot created.
6. Backup completed successfully.