If you want to run certain backup jobs on a regular basis, it is best to create a schedule for them.
You may add a schedule to an existing job and save it, add a schedule to an existing job and save it under another name (thus creating a new job without affecting the job you have made edits to), or create a completely new job, adding a schedule to it.
To add a schedule to an Agentless VMware backup job, create a new job or open an existing one from the Job Manager.
In the job creation/editing view, scroll down to the SCHEDULES pane and click Add Schedule. The Schedule dialog will open. Depending on the selected frequency, the dialog will display slightly different parameters to select. Below, the Monthly schedule view is shown.
Select all required parameters, such as the schedule starting time and date, day of the week (if applicable), repetition period, backup retention time, etc.
Click Save.
Important. The schedule is now added to the job, but the job is not saved yet. Continue with the procedure to save the job.
Save the job. If you have added the schedule by modifying an existing job, two options will be available.
Click Save to apply changes to the existing job; or
Click Save As to create a copy of the modified job, with the schedule added, under a new name.
Restrictions. The new job name must be unique throughout the entire DPX, regardless of the folder the job is stored in.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name. For Hyper-V Backup, this field may contain no more than 64 characters. You can also add an optional description (up to 48 characters).
Select Job Type – Hyper-V and the Job Folder to store the job in (see the Job Manager section for more information). By default, all jobs are stored in the SS_DEFAULT job folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. The Source selection dialog will appear.
Tip. You may select an entire Hyper-V node or individual virtual machines within the node.
Tip. Powered-on machines are displayed with green icons, and powered-off machines are displayed with grey icons.
Hyper-V backup is possible even when the virtual machine is powered off.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
You can clear each item using the “X” symbol next to the item, or clear all items at once using the Clear All button.
To close the Selected Items pane, click anywhere outside of it.
Use the EXCLUSIONS pane to exclude certain machines within a Hyper-V node. You may exclude individual machines by selecting them within the tree view in the Exclusions dialog or use exclusion patterns for a series of machines within an entire Hyper-V node selected as a Source.
In the DESTINATION pane, specify the destination for the Hyper-V backup.
You may also add a schedule in the SCHEDULES pane for the backup to be run on a regular basis. See Scheduling a Hyper-V Backup Job.
Specify the retention period for the backup. The default value is 90 days.
Click Save. The job can now be viewed, run, edited or deleted from the Job Manager section.
Editing a Hyper-V backup job allows you to change some parameters of an already defined job (Save), or to create a new job based on the definition of an existing one (Save as…). The procedure is similar to creating a backup job from scratch.
In the main web interface view, go to Job Manager in the sidebar. Then select the file backup job you want to edit from the list.
Tip. You can control this view by ordering items by Job Name, Type, Created Date, Description, or Job Folder. Just click the column header to enable ascending/descending ordering.
Note also the Items per page value and navigation buttons at the bottom of the list, which can be useful when managing the display of many jobs.
Make all required changes to the job definition. The workflow is the same as in Creating a Hyper-V Backup Job.
Save the job by clicking Save (the changes will be saved under the current job’s name, overwriting previous settings), or Save As (you will be prompted to provide a new name for the job).
Restrictions. The new job name must be unique throughout the entire DPX, regardless of the folder the job is stored in.
To use the Agentless Backup for Microsoft Hyper-V, you must install Catalogic DPX Backup Agent for Microsoft Hyper-V on your Microsoft Hyper-V host. The agent handles Hyper-V snapshot processing and communicates with the storage destination and master server. Agentless Hyper-V Backup supports auto-discovery and protection of new and modified VMs. Moreover, it supports crash-consistent backup of all guest operating systems supported by Microsoft Windows 2016 and later.
Restrictions. Microsoft Hyper-V backup and restore are only accessible through the web interface.
You can use the Catalogic DPX Agentless Backup with the following Microsoft Hyper-V environments:
Microsoft Hyper-V for Windows Server 2022
Microsoft Hyper-V for Windows Server 2016
Microsoft Hyper-V for Windows Server 2019
The VMs you want to protect must have the Microsoft Hyper-V virtual machine configuration versions of 8.0 or later. To check the configuration version of a VM, click the VM in the main window of Microsoft Hyper-V Management Console and see the Configuration Version value in the summary tab.
Or, you can get the configuration versions of all or specific VMs by using Microsoft Hyper-V Module for Microsoft Windows PowerShell or Microsoft PowerShell. In the Microsoft Windows Server system, launch Microsoft Windows PowerShell or Microsoft PowerShell with the administrator privilege. Use the following command:
The command prompts the output that is structured as shown:
In this example, you have to upgrade the configuration version of sales-vm
before DPX protects this VM.
See also. For more information about virtual machine configuration versions in Microsoft Hyper-V, see the following document:
In addition, you must install Catalogic DPX Backup Agent for Microsoft Hyper-V on the Microsoft Hyper-V host system.
Microsoft Docs: .