• |
Level 0 or Full Backup: A Full Backup provides a backup of all the data in the selected path. |
• |
Level 1 through 9 or Incremental Backup: The Incremental Backups base themselves on the most recent lower‑level Incremental Backup, and include any data that has changed or is new since the last Full or Incremental Backup. |
NOTE: Clustered Data ONTAP 8.3 supports 32 (0 to 31) levels of Incremental Backups (Level 0 is a Full Backup and Level 1 through Level 31 are Incremental Backups). For more information, see the Clustered Data ONTAP 8.3 Data Protection Tape Backup and Recovery Guide. |
1 |
In the Navigation pane, click Create Backup Job. |
2 |
In Job Name, specify a name for the job. |
3 |
In the Selections list, select an existing Backup Selection Set, or complete the following steps to create a set. |
a |
b |
• |
• |
Back up all volumes: Select the Volumes node. |
• |
Back up individual volumes: Open the Volumes node, and select the volumes that you want to back up. |
• |
Back up individual files and directories: Open the Volumes node, and then open the target volume. Select the files and directories that you want to back up. |
• |
Back up snapshots: To list all volumes, open the Snapshots node, and then open the applicable volume to list directories that have any snapshots available for a backup. Open the applicable directory, and select the snapshot that you want to back up. You can only select a single snapshot. |
e |
f |
4 |
In the Plugin Options list, select an existing Backup Options Set, or complete the following steps to create a set. |
a |
b |
Under NDMP Backup Options, configure the following settings. |
The file “/etc/dumpdates” keeps a record of the backup, including the backup name, backup level, and snapshot time. | |||||
Leave this check box selected to back up ACLs associated with the selected files. | |||||
To use this feature, do the following:
| |||||
You can use up to two wildcard characters per file. Wildcard characters can only be used at the first or the last place in the filename. For example, if you enter “/dir1/tmp*, *.o” in Exclude, the plug-in excludes the following items:
Filenames are case-sensitive for NFS shares and case-insensitive for CIFS shares. |
c |
Under Volume Backup Options, configure the following settings. |
| |||
It eliminates the need to select individual qtrees. You can select the volume node, and then select this check box to back up qtree data and exclude non-qtree data. You must use this option with the Backup Subvolumes Individually option. | |||
You can use this option to back up only the non-qtree data while excluding the qtree data. It eliminates the need to select individual files and directories. You can select the volume node, and then select this check box to back up all non‑qtree data and exclude the qtree data. This option cannot be used if the Backup Subvolumes Individually check box is selected. |
d |
Under Sub Jobs, configure the following settings. |
To achieve the required result, set the same value for each job. | |
The plug-in creates individual subjobs for each volume included in a backup. If this check box is not selected, all subjobs are listed on the Job Status page. This display can create confusion when you try to view the details of the parent job. To include only a single entry for the parent job, leave this check box selected. |
f |
g |
5 |
Select or create the Schedule Set, Target Set, and Advanced Options Set. For more information about these sets, see the Quest 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. |
• |
BRE may fail if you restart the filer. Certain circumstances may prevent the filer from correctly continuing a backup restart. When this error occurs, the message “Node Data Missing for File <Filename>” is written to the NetVault Backup logs during the index building stage. If this message is displayed in the log, it implies that the restart has failed and the job cannot be resumed. |
• |
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center