Job Source Options for File Backup
The Set Job Source Options dialog allows you to set options related to backup sources. The options displayed depend on the backup mode. An explanation of each field in the dialog and the available choices is provided in this section.
The following fields are displayed in the Source tab:
Verify Backup
Controls the data verification technique for writing data to a media volume. The higher the verification level, the greater the safety and the longer a backup takes. Each verification level builds upon the preceding level. For example, level 3 performs level 1 and level 2 verification as well. Select one of the following options:
No Verification
Writes data to the media volume without verification. This is the fastest option and relies on the tape device for data verification.
Level 1
Reads the tape to ensure that it is readable.
Level 2
Reads the tape and ensures that the SIDF headers are present and contain the correct information.
Level 3 Ensures that the checksum of each file on the tape matches the one contained in the SIDF header for that file. This verification is only performed if the checksum feature is set to On in Set Job Destination Options. The tape and SIDF headers are also read and verified (levels 1 and 2).
Data Compression
Compresses data prior to network transmission.
Select Yes to compress data prior to transmission at the node being backed up. This setting is recommended if there is processing power available on the client nodes and network bandwidth is limited. This setting minimizes the impact of data transmission on data lines.
Or, select No to disable the data compression.
Skip NFS Volumes
Determines expected behavior when encountering an NFS (network file system) volume during a backup operation. NFS volumes are remotely mounted volumes owned by another node. This option also controls the backup behavior of drives that are mapped to the Microsoft Windows node (CIFS mount point).
Select No to back up NFS volumes and drives that are mapped to the Microsoft Windows nodes.
Or, select Yes so as no to back up NFS volumes or drives that are mapped to the Microsoft Windows nodes.
Open File Retries
If you are not using an open file manager, this option controls how many times DPX attempts to back up an open file. If you enter zero, DPX skips open files. If you enter a number, DPX waits until all the files on the node have been backed up then tries again to save the open files. DPX attempts this the number of times you enter here.
Down Node Retries
Controls how DPX behaves when it cannot establish contact with a node during a backup operation. If you enter zero, DPX skips unreachable nodes. If you enter a number, DPX waits until all the reachable nodes have been backed up and then retries the nodes that it could not back up on its first attempt. The number you enter determines how many times DPX tries to reach unreachable nodes.
Task Retry Intervals (Minutes)
Determines how long to wait before retrying failed tasks.
When a task fails (due to permission problems, open files, interim job changes, etc.), it waits the number of minutes specified in this field before attempting that task again. Because the same failure might occur if the task is retried too soon, it is better to allow some time for an error to be corrected before retrying the task. A task is only retried once. Failing tasks appear in error message lists in the Job Log. All tasks are subject to retry.
Catalog Open Files
If you are not using an open file manager, this option tells Catalogic DPX whether to catalog open files encountered on UNIX systems. On UNIX nodes, Catalogic DPX backs up the file and then checks to determine if it has been modified while the backup transpired. If it has, the file is considered open. Cataloging open files is not generally recommended.
Select No so as not to save the backed-up file if DPX detects that the file has been modified during the backup process and the number specified in the Open File Retries field has been reached.
Or, select Yes to catalog the backed-up file if it detects that the file has been modified during the backup process and the number specified in the Open File Retries field has been reached. Catalogic DPX catalogs its last attempt to back up an open file if it finds the file is still open. Note that cataloging a file that has been modified during the backup can compromise the integrity of the file when that file is restored.
Note. Do not configure this option but keep the default settings for Catalog Backup.
Back Up Content of Mounted Drive
Tells DPX whether to back up data on a mounted drive (volume). This field only applies to NTFS volume mount points on Windows 2000 and higher machines.
No | Data on a mounted drive is not backed up through a volume mount point. Whether the directory is restored as a volume mount point or not depends on the Set Job Destination Options. |
Yes | Data on a mounted drive is backed up through a volume mount point. |
Note. If set to Yes, and if you select both a volume mount point and the drive itself, duplicate backups might occur.
Back Up Data in Remote Storage
Remote Storage Service (RSS) is the Hierarchical Storage Management (HSM) system for Windows 2000 and higher, which automatically migrates files from disk to remote media, like tape. If the Windows administrator configures this service and disk space becomes low, files not modified for a specified period of time are sent to remote storage. A link (stub file) to the remote storage is kept in their place. Users can recall these stub files by accessing their links. This field determines whether DPX should back up links to these files or the files themselves.
No | Files on remote storage are not backed up. DPX backs up their links. |
Yes | Files on remote storage are backed up by DPX. In this case, files are backed up from tape to tape. At restore, files are restored to disk. However, because file dates are not affected by backup and restore, it is likely that the files will automatically be sent back to remote storage. |
Note. The tape devices and the media pool used by Windows for remote storage service cannot be shared with DPX.
Back Up System Protected Files
Tells DPX whether to back up System Protected Files as part of the System State Backup. This applies only to Windows 2000 and higher backups.
No | System protected files are not backed up as part of System State. |
Yes | System protected files are backed up as part of System State. Yes is the default. |
The following field only applies to 32-bit Windows XP or higher.
Take Snap Shot
If this option is selected, DPX first creates a snapshot of the current state of all data to be backed up. Then, DPX backs up the snapshot to the destination server. This enables DPX to back up open files.
Yes | Take a snapshot of the current data condition, then back up the snapshot. |
No | Do not take a snapshot first. |
The following fields are displayed on the Application tab:
MSSQL DB Consistency Check
Tells DPX to run a consistency check on SQL Server before backing up a SQL Server database. The check runs three utilities that Microsoft recommends before a backup: DBCC CHECKDB, DBCC CHECKALLOC, and DBCC CHECKCATALOG.
No | Does not perform the consistency check. |
Yes | Performs the consistency check. |
Default MS Exchange Handling
Controls whether Exchange backup occurs at the database or individual message level.
Database Level Backup |
|
Folder Level Backup |
|
Both Database and Folder Level Backup | All Exchange disks appear on the Backup File definition screen. If you back up an entire server, both database and folder level backups of Exchange disks are performed. |
Expand Netware Compressed Data
Tells DPX whether to expand compressed data. This applies only for supported versions of NetWare.
Yes | Expand compressed data when performing the backup. Select this option if you may want to restore to an uncompressed volume. DPX cannot restore compressed data to an uncompressed volume. |
No | Do not expand the compressed data. If you choose this option, you can restore this data only to a compressed volume. |
The following fields are displayed on the NDMP tab:
NDMP File History Handling
Controls file history generation for NDMP and Block backup tasks.
For Block backups, recovery through the use of Instant Access provides for granular file-level restore regardless of whether file history was generated or not. Instant Access allows Block backups to be run very frequently by eliminating the need to include file histories during backup. For information on using Instant Access for file-level restore, see Instant Access as a File History Alternative in the User’s Guide.
Disable File History | Disables NDMP server file history generation. |
Process File History on Local Client | Enables NDMP server file history generation and processes the file history data on the NDMP client node. This is the default. |
Process File History on Master Server Appliance | Enables NDMP server file history generation but transmits the file history data to the master server node for processing. |
Related Topics:
Enable NDMP Server Logging
Controls the routing of NDMP server-generated log messages to the job log file.
Yes | All NDMP server log messages will be routed to the master server’s job log file. Yes is the default. |
No | The NDMP server log messages will be logged locally in the NDMP client node log file instead of in the master server’s job log file. |
Additional NDMP Environment
This option allows you to introduce any additional NDMP environment variables that are necessary for the backup task. Specify your environment variables as an ASCII string with an environment variable name and value pairs using the following syntax:
Note that syntax validation is not performed on the specified value at job definition time, but rather at run time. Only valid entries are added to the NDMP operation environment.
Do not specify any of the following NDMP environment variables in your variable string because DPX controls these specifically:
BASE_DATE
DEBUG
DIRECT
DUMP_DATE
EXTRACT
FILES
FILESYSTEM
HIST
LEVEL
PREFIX
RECOVER_FILEHIST
SINCE_TIME
TYPE
UPDATE
VERBOSE
Specifying the variables above may cause unexpected results due to unpredictability of the order in which they are evaluated.
NDMP servers from different vendors may support different NDMP environment variables. Except for a few well-known environment variable names, there is currently no standardized set of such variables. This option allows you to add environmental variables specific to your NDMP server.
The following fields are displayed on the Script tab:
Pre-Job Script
Enter the name of a script to execute prior to the actual job.
If Job fails
The action to take if the Job fails to successfully complete.
Post-Job Script
Enter the name of a script to execute after the actual job.
See also. For more information about the Pre-Job Scripts and Post-Job Scripts, see Chapter 29: Pre-Scripts and Post-Scripts.
Ensures that the checksum of each file on the tape matches the one contained in the SIDF header for that file. This verification is only performed if the Checksum Files feature is set to Yes in Set Job Destination Options. The tape and SIDF headers are also read and verified (levels 1 and 2).
Last updated