Creating an Agentless VMware Archive Job
A separate archive backup job must be created for the archive job to be run. For VMware Agentless backup, Archive jobs are created by scheduling their instances from within the VMware backup job creation process.
The typical scenario for archive jobs is that they are scheduled to run soon after the backup job is completed, ensuring the most recent recovery point is archived.
Note. If the Archive job is attempted to run a second time on the same recovery point, an error will be thrown and the archive job will fail due to no new recovery point detected.
Go to Job Manager in the sidebar.
Click the New Backup Job button to start creating a new VMware backup job, or select an existing VMware backup job from the Jobs list.
Go to the Archive section (scroll down if necessary) and click Add Archive.
Set Options as desired. See the full options description at the bottom of this page.
Schedule your archive job. Select Base, Incremental or Differential Archive.
See also. For discussion on differences between incremental and differential backups, see Differential and Incremental Backups.
Specify the schedule frequency, start time and date, and Archive retention period. Click Add in the Schedule area. Multiple schedules may be added.
See also. For details concerning scheduling jobs, see Scheduling a VMware Backup Job.
The added Archive schedule will be shown in the Schedule area. To add another schedule, click Add Another Schedule.
Important. When scheduling an Archive job, ensure the relevant Backup job is completed before the Archive job starts. Otherwise, the Archive job will fail.
When all schedules are set, click Add at the bottom of the Add Archive dialog. The dialog will close, and the newly added Archive schedules will be shown in the Add Schedule pane.
Click Save or Save as…. The Run Job prompt will be shown, where you may determine the retention period (default: 90 days) and choose whether to run the job immediately. Either way, the job will be available in the Job Manager section.
Important. The Archive job will run according to the schedule even when the VMware agentless backup is not completed. We strongly suggest monitoring the completion of both jobs to ensure proper backup archiving.
Options
Mark original offsite
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Toggle on | Indicates in the Catalog that the tape is stored offsite. |
Toggle off | Indicates in the Catalog that the tape is stored onsite. |
Append offsite
Determines if a backup tape with the status Offsite can be appended to.
Toggle on | Tapes in the library with status Offsite can be appended to. The Append Offsite field in the Edit Media Pool dialog must also be set to Yes. |
Toggle off | Tapes in the library with status Offsite cannot be appended to. |
The Offsite status of a tape can be viewed through the Operate Tape Library function, the Configure Media function, or in the media volume report. Note that when you use the Operate Tape Library function to import a tape with the status Offsite, the Offsite status is cleared and the tape becomes available for use.
Max Devices
Limits the number of storage devices valid for use with this job. Use this option if you want to stop DPX from using all the drives in the selected device cluster so that some drives will be available for other purposes.
Alternate Secondary
When this toggle is on, two additional fields appear, where the user needs to select the node and volume within the node where a secondary copy of the backup is stored. Data can be restored from an alternate secondary data source directly from the management console.
Last updated