To access the job source options, do the following:
Go to the Backup tab.
In the Backup Modes section, select File.
Open an already existing backup job. Or go directly to step 4 to set source options for the new job you will be defining directly afterward.
Go to the Other Tasks section in the task panel (scroll down if necessary) and select Set Source Options. The Set Job Source Options dialog will appear.
The Set Job Source Options dialog allows you to set options related to backup sources. This section provides an explanation of each field in the dialog and the available choices.
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.
NDMP File History Handling
Controls file history generation for NDMP and Block backup tasks.
For information on using Instant Access for file-level restore, see Instant Access as a File History Alternative in the DPX 4.9.x User’s Guide.
Enable NDMP Server Logging
Controls the routing of NDMP server-generated log messages to the 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. 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.
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.
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.
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.
DPX provides generic NDMP support that can back up and restore data for NDMP NAS appliances in several ways.
High-Speed Local Backup
The NAS appliance is directly connected to a SCSI-attached or fiber-attached storage device (typically a tape drive). The NAS appliance must be defined in DPX as a node that uses the NDMP access method. DPX documentation refers to these nodes as NDMP nodes. Data is backed up and restored directly via the local device.
Three-Way Backup
The NAS appliance sends data over the LAN to a storage device attached to a second NDMP appliance. Both NDMP devices (source and destination) must be defined in DPX as nodes that use the NDMP access method.
Appliance-to-Server Backup
The NAS appliance sends or receives data over the LAN to a DPX device server. The NAS appliance must be defined in DPX as a node that uses the NDMP access method. The DPX device server is defined in DPX as system type TCP/IP, though DPX device servers can exchange data with supported NDMP devices.
In the main desktop interface window, go to the Backup tab, and from the Backup Modes section in the task panel, choose NDMP.
Two additional panes will appear. You are already in the defining new file backup job view, so there is no need to click the Define New Backup Job button under Job Tasks in the task panel.
Specify the NDMP backup source in the middle pane. Expand the tree as necessary.
Empty checkboxes indicate a directory that will not be included. Checkboxes marked in red indicate a directory that will be fully included. Half-red checkboxes indicate that only some subdirectories/files of a given directory will be included.
Specify the NDMP backup destination in the right-hand side pane. Expand the tree as necessary.
Note. Before running a backup job, you need to save it. Once saved, a previously defined job can be modified, run, or deleted. If you try to leave the job creation view without saving the changes, you will be prompted to either save or discard changes before leaving.
If you select Define New Backup Job, all unsaved changes will be lost.
Set advanced options as desired, selecting appropriate items in the Other Tasks section of the side panel. Scroll down if necessary.
See also. For more information about NDMP backup job options, see the following sections:
Other Job Options for NDMP Backup (includes encryption and notification options)
Save the job by doing one of the following:
Select File > Save Job
Select Save Backup Job in the Job Tasks section of the side panel
Press [Ctrl + S]
The Save Job dialog will appear.
Restrictions. The new job name must be unique throughout the entire DPX, regardless of the folder the job is stored in.
Click OK. The job is now saved.
Apart from source and destination options, DPX offers some additional backup job options, such as Job Encryption options and Job Notification options. They are available from both interfaces as presented below.
The Set Job Encryption Options dialog controls how and when a job is encrypted.
To set backup encryption options:
Open the Set Job Encryption Options dialog box by doing one of the following:
Right-click the Enterprise name or icon to display a context menu. Then select Set Encryption Options.
From the menu bar, select Backup > Set Encryption Options.
On the task panel, click Set Encryption Options.
The Set Job Encryption Options dialog box appears.
Complete the Set Job Encryption Options dialog box as needed.
Encrypt data while transmitting it through networks to enhance security. Typically, the encrypted data transfer can lower the data transfer speed.
Specifies if the data written to tape is encrypted. This option does not relate to data transport. If network transport encryption is important, use the Network Encryption option.
The Set Job Notification Options dialog controls who receives messages pertaining to the current job when it is run.
To set backup job notification options:
Open the Set Job Notification Options dialog box by doing one of the following:
Right-click the Enterprise name or icon to display a context menu. Then select Set Notification Options.
From the menu bar, select Backup > Set Notification Options.
On the task panel, click Set Notification Options.
The Set Job Notification Options dialog box appears.
Complete the Set Job Notification Options dialog box as needed.
An explanation of each field and the available choices follows:
Two sets of mail information can be specified:
The email address of the primary recipient of your message. Only one “To” address is permitted.
Carbon Copy. The email address(es) of the secondary recipient(s) of your message. Use a semicolon to delimit multiple email addresses.
Blind Carbon Copy. The email address(es) of the secondary recipient(s) not identified to other recipients. Use a semi-colon to delimit multiple email addresses.
The subject of your message. The subject line usually contains a combination of straight text and variable elements. Variables, which must begin with %, are replaced with actual corresponding values. If you enclose variables in double quotation marks, those variables are treated as literal values. You can embed the following variables:
%JOBNAME
%JOBID
%JOBTYPE
%RC
Use %RC to include the return code in the message for this run of the job, when applicable.
Selecting this check box option temporarily disables notifications for the job without deleting the currently defined job notification data.
Note. Note that the following characters are invalid in all fields: < > ; and '.
Note. DPX emailing must be enabled when you first configure your Enterprise. At that time, you supply general system information, including SMTP Host Name and SMTP Port. See Editing an Enterprise Configuration.
To access the job destination options, do the following:
Go to the Backup tab.
In the Backup Modes section, select NDMP.
Open an already existing backup job. Or go directly to step 4 to set source options for the new job you will be defining directly afterward.
Go to the Other Tasks section in the task panel (scroll down if necessary) and select Set Destination Options. The Set Job Destination Options dialog will appear.
The Set Job Destination Options dialog allows you to set options related to backup destinations. This section provides an explanation of each field in the dialog and the available choices.
Note. All three tabs, i.e. Base, Incremental and Differential, feature exactly the same options, only referring to different backup types.
Determines whether or not to accept a tape with data on it.
Determines expected behavior when an unlabeled tape is found in the tape drive.
Determines whether a backup tape is stored offsite. DPX adds the Offsite status to the tape.
Determines if a backup tape with status Offsite can 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 status Offsite, the Offsite status is cleared and the tape becomes available for use.
Determines what to do with the tape when the backup job is complete.
Attention! In some cases, a backup job may fail if the Export option is used for the first job following a system restart, especially if the initial job is a File backup with the Export setting.
Max Devices (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.
The maximum number to check a tape in a standalone tape device.
The number of seconds to wait between checking the availability of a tape in a standalone tape device.
Amazon S3 Object Lock prevents your archive data in the cloud storage from being deleted or overwritten. Set S3 Object Lock to Yes to make your archive data the write-once-read-many (WORM) model. Beginning from Version 4.8.1, you can also use the legal hold for cataloged job instances that use the Amazon S3 Object Lock.
If Yes is selected, another radio button selection will appear.
Set S3 Lock Mode for the retention modes of Amazon S3 Object Lock to either Governance or Compliance.
Restrictions. Some features of Amazon S3 Object Lock are not available in Catalogic DPX. For example, you cannot use the default retention period in Amazon S3 instead of the backup or archive jobs that are defined in Catalogic DPX.
Yes
Enables encrypted data transfer.
No
Data transfer without encryption.
No data encryption
Data is not encrypted at the device server.
Encrypt data at the device server (primary and twin tape)
Data is encrypted at the device server of both the primary and twin tapes. Hardware compression does not matter if same tape model/media is used.
Encrypt data at the device server (primary tape only)
For the primary tape, data is encrypted at the device server. Hardware compression does not matter.
Encrypt data at the device server (twin tape only)
For the twin tape, data is encrypted at the device server. Hardware compression must be disabled during original backup job.
Output Email
Specifies that the subsequent fields apply to reports that are sent when a job has completed.
Operator Email
Specifies that the subsequent fields apply to mount requests, error messages, and informational messages that are sent during a job.
Use a new tape
Requires media with status New or Empty from the selected media pool. Media with status New will only be used if the option Unlabeled Tape Usage (defined below) is set to Allow unlabeled tapes and label them.
Attempt to append data to available tape
Accepts a backup tape from the selected media pool with data on it (status Appendable) and writes to the unused portion of the tape. The appended data can have a retention period that differs from the data preceding it on the tape.
Label unlabeled tapes
Label the unlabeled tape. This saves the step of labeling a tape beforehand.
Reject unlabeled tapes
Do not use the unlabeled tape.
Yes
Indicates in the Catalog that the tape is stored offsite.
No
Indicates in the Catalog that the tape is stored onsite.
Yes
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.
No
Tapes in the library with status Offsite cannot be appended to.
Rewind Tapes
For a standalone tape device, this option rewinds the tape and leaves it in the drive. For a tape library tape drive, this option rewinds, unloads, and returns the tape to its slot.
Unload Tapes
For a standalone tape device, this option rewinds the tape and ejects it from the drive. For a tape library tape drive, this option rewinds, unloads, and returns the tape to its slot.
For DiskDirectory, this option causes empty volsers to be used before new volsers.
Leave Tapes
In the case of standalone tape drives, the tape remains wound to the point where the job ended and stays in the drive. However, for tape library drives, the tape is always attempted to be returned to its slot after the backup operation is completed. The next job attempts to use the tape in the drive instead of mounting a new tape. In the case of standalone drive, if the currently mounted tape is unacceptable (for example, if the next backup requires a tape from a different media pool), the operator is prompted to mount another tape. In the case of a tape library, if the tape in the drive is rejected for any reason, it unloads the tape, returns it to its slot, and proceed to select another tape.
Export Tapes
Automates the export of tapes to an I/O port, eliminating manual processes and preparing tapes for their next destination. In environments with physical tape libraries, the availability of an empty I/O port is essential. The system will alert and will return an error code if no port is available, prompting user action. A rescan of ports is recommended to ensure availability.
