Hyper-V virtual machine backup workflow



Phoenix backs up virtual machines based on the schedule defined in the backup policy, or if a backup is triggered from Phoenix Management Console. The backup workflow is explained below:
Virtual machine backup workflow
Step | Operation |
---|---|
Step 1 |
Virtual machine backup request is initiated based on:
Phoenix forwards the backup request to the agent. |
Step 2 |
Phoenix agent verifies that the VSS service is running. The Phoenix agent requests the VSS service to create a snapshot. If the VSS service is not running, Phoenix agent starts the VSS service and instructs VSS to create a snapshot. Druva recommends that you enable Backup (volume snapshot) under Hyper-V Integration Services. If the Backup (Volume snapshot) is enabled, the VSS service can create a snapshot without interrupting services on the virtual machine. Phoenix agent validates if snapshots are created successfully and initiates the backup job.
Note: Integration Services are available for virtual machines with Windows guest OS. However, Microsoft provides Integration Services for certain Linux distributions also. For more information, see: On Windows Server 2016 or later, the Phoenix agent can back up virtual machines using the Resilient Change Tracking (RCT) feature if:
The Phoenix agent can back up virtual machines using RCT on a Hyper-V host that meets the criteria above and:
|
Step 3 |
Phoenix determines the type of backup.
|
Step 4 |
Agent estimates the data for backup |
Step 5 |
Agent backs up the data based on the VSS provided snapshot |
Next steps
If you want to configure Phoenix for backup and restore, see:
To learn more, see: