1 |
In the Navigation pane, click Create Backup Job to start the configuration wizard. |
2 |
In Job Name, specify a name for the job. Assign a descriptive name that allows you to easily identify the job for monitoring its progress or restoring data. |
3 |
In the Selections list, select an existing Backup Selection Set, or complete the following steps to create a set. |
a |
|
• |
Back up all virtual machines within a container: Select the container node. Data selection is possible at all levels starting from the Datacenter node. |
• |
Back up individual virtual machines: Open the applicable container nodes (for example, Datacenter, Cluster, Resource Pool, and other nodes), and select the virtual machines that you want to back up. In the VMs and Templates view, open the folder node, and select the virtual machines that you want to back up. |
• |
Back up individual virtual disks: Open the virtual machine node, and select the disks that you want to back up. Note the following: |
e |
Click Save, and in the Create New Set dialog box, type a name for the set. Click Save to close the dialog box. |
4 |
In the Plugin Options list, select an existing Backup Options Set, or complete the following steps to create a set. |
a |
|
b |
Under Backup Type, select one of the following options. |
c |
Under VM disk selection options, select one of the following options. |
d |
Under Other Options, configure the following settings. |
| |||||
When you run a backup job, the plug-in creates a snapshot named “BKB_SNAP” on the virtual machine to back up the selected data. Regardless of whether the backup completes successfully or fails, the plug‑in removes the snapshot on job completion. The plug-in also removes the snapshot if the job is aborted or the parent or child processes are terminated for any reason. However, if a job exits abnormally, the cleanup process may fail to remove the snapshot. To address such cases, the plug‑in provides an option to delete the snapshot when you run the job next time.
You can select the Remove snapshots from previous backups check box to remove any existing snapshots when you run the current job. Only the snapshots named “BKB_SNAP” are removed from the virtual machines. This option does not remove any other snapshots that exist on the virtual machine. | |||||
For parallel backups, the plug-in generates a parent process that coordinates the overall backup and individual child processes that perform the actual task of backing up the virtual machines. The maximum child processes that can be generated for a backup job is equal to the Maximum Number of Parallel Streams configured for the job. The parent and the child processes are all created on the NetVault Backup Client on which the plug-in is running.
When configuring Maximum Number of Parallel Streams, consider the following:
| |||||
When a restartable backup completes with some failed virtual machines, the plug-in generates a backup index for the completed virtual machines and sets the job status to Job Stopped. The log messages and log context show which virtual machines have failed for the job. When you restart the job later, the plug-in runs an Incremental Backup job to back up the failed virtual machines.
You can restart a job from the Job Status page. For more information about this method, see Restarting a backup job. A restarted instance does not back up virtual machines that are added to the host after the initial job is run.
NOTE: If all virtual machines fail for a job, the job status is set to Backup Failed. You cannot restart a failed backup job. |
e |
5 |
Select or create the Schedule Set, Target Set, and Advanced Options Set. For more information about these sets, see the Dell NetVault Backup Administrator’s Guide. |
6 |
To submit the job for scheduling, click Save & Submit. You can monitor the job progress from the Job Status page and view the logs from the View Logs page. |
• |
To create the first Full Backup of a virtual machine with Changed Block Tracking enabled, the target virtual machine must be powered off to enable CBT. For more information, see http://kb.vmware.com/kb/1031873. The virtual machine can be restarted as soon as the backup starts transferring data. |
• |
• |
The re-configuration of Changed Block Tracking takes effect only after the virtual machine goes through a stun and unstun cycle, including power-on, resume after suspend, migrate, or snapshot create, delete, or revert operations. |
• |
During an Incremental or Differential Backup, the plug-in does not attempt to enable CBT for any virtual machine included in the backup, unless you have selected the Enable Change Block Tracking for VM check box. |
• |
Creates a non-CBT Full Backup, unless CBT is already enabled for the virtual machine or you have selected the Enable Change Block Tracking for VM check box for the Incremental or Differential Backup. |
• |
Once you enable CBT for a virtual machine, all subsequent Full, Incremental, and Differential Backups are performed as CBT-based backups for that virtual machine. You do not have to select the Enable Changed Block Tracking for VM check box for each job. |
• |
When using CBT for backups, virtual machine migration using Storage vMotion or VMware vSphere® Storage DRS™ is not recommended. For more information, see http://kb.vmware.com/kb/2048201. |
1 |
In the Navigation pane, click Job Status. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center