Catalogic SoftwareKnowledge BaseMySupport

Job Source Options for File Backup

Catalogic DPX offers a variety of source options for File backup. All of them are available from both interfaces, but the access thereto may slightly differ. See details for each interface below.

To access the job source options, do the following:

  1. Go to Job Manager in the sidebar.

  2. Open an already existing backup job. Or create a new File backup job, by clicking the New Backup Job button in the upper right corner and then selecting Backup Type File.

  3. Go to the Advanced Options section at the bottom (scroll down if necessary) and expand it. Click any of the following section headers to expand it. Each field and the available choices are explained below.

Note. The Advanced Options section in the web interface also includes job destination options which are discussed in a separate section for the sake of clarity. See Job Destination Options for File Backup.

The Source Options section

Verify Backup drop-down

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 Files toggle is set to Enabled in the Job Destination Options section. The tape and SIDF headers are also read and verified (levels 1 and 2).

Data Compression toggle

Compresses data prior to network transmission.

Skip NFS Volumes toggle

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 mapped to the Microsoft Windows node (CIFS mount point).

Open File Retries entry field

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 entry field

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) entry field

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 toggle

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.

Back Up Content of Mounted Drive toggle

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.

Note. If the toggle is set to On, and if you select both a volume mount point and the drive itself, duplicate backups might occur.

Back Up Data in Remote Storage toggle

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.

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 toggle

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.

Take Snap Shot toggle

Restrictions. This option applies only to 32-bit Windows XP or higher.

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.

The Application Options section

MSSQL DB Consistency Check toggle

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.

Expand Netware Compressed Data toggle

Tells DPX whether to expand compressed data. This applies only to supported versions of NetWare.

Default MS Exchange Handling drop-down

Controls whether Exchange backup occurs at the database or individual message level.

The NDMP options section

Enable NDMP Server Logging toggle

Controls the routing of NDMP server-generated log messages to the job log file.

Additional NDMP Environment input field

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:

env1name=value,env2name=value,...

Note. 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.

Note. Alternative syntax, e.g. env1name value;env2name value;... (semicolon-delimited, no equal sign) or env1name valueenv2name value... (no delimiter, no equal sign) may be displayed in the interface. However, for the sake of clarity, the env1name=value,env2name=value,... version is strongly recommended.

Attention! 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 the 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 Script Options section

Pre-Job Script

Enter the name of a script to execute prior to the actual job.

Basic usage: <script>@<node_name> <argument_list>

If Pre-Script fails

The action be taken if the Pre-Job Script fails to successfully complete:

  • Run Job/Run Post-Job Script

  • Skip Job/Run Post-Job Script

  • Skip Job/Skip Post-Job Script

If Job fails

The action to be taken if the Job fails to successfully complete:

  • Run Post-Job Script

  • Skip Post-Job Script

Post-Job Script

Enter the name of a script to execute after the actual job.

Basic usage: <script>@<node_name> <argument_list>

See also. For detailed information about pre- and post-job scripts, including all valid definitions, see Pre-Scripts and Post-Scripts.

PreviousCreating a File Backup JobNextJob Destination Options for File Backup