Last updated
Was this helpful?
Last updated
Was this helpful?
Catalogic DPX offers a variety of job options for Block backup. All of them are available from both interfaces, but the access thereto may differ. See details for each interface below.
In the web interface, backup job options are defined in the Advanced Options section. To access them, do the following:
Go to Job Manager in the sidebar.
Open an already existing backup job. Or create a new Block backup job, by clicking the New Backup Job button in the upper right corner and then selecting Backup Type Block.
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.
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.
This option controls the truncation of SQL Server Transaction Logs during a Block backup. This option must be set to On in order to enable Point-in-Time restore.
This option controls the truncation of Microsoft Exchange Logs during a Block backup.
Determines whether DPX will back up Exchange DAG from a passive node or an active node.
For Oracle backups, this option determines whether to synchronize the RMAN catalog after the job is completed. Yes is the default.
This section includes the following radio button selection:
Disable File History
Process File History on Local Client (default selection)
Process File History on Master Server
This section includes the following options:
Task Data Retry Count (default: 5)
Task Retry Interval (default: 1)
Throttle (default: 0)
Resolution Auto Cancel Timeout [Minutes] (default: 180)
Resolution Retry Count (default: 3)
Wait Interval Between Replies [Minutes] (default: 1)
Data Transfer Auto Cancel Interval [Minutes] (default: 0)
And one toggle:
Backup IA Mapped Drives (default: disabled)
The Notification Options section controls who receives messages pertaining to the current job when it is run.
This section includes the Job e-mail notification toggle.
Subject
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.
To
The email address of the primary recipient of your message. Only one “To” address is permitted.
Cc
Carbon Copy. The email address(es) of the secondary recipient(s) of your message. Use a semicolon to delimit multiple email addresses.
Bcc
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.
Note. Note that the following characters are invalid in all fields: <
>
;
and '
.
Enter the name of a script to execute prior to the actual job.
Basic usage: <script>@<node_name> <argument_list>
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
The action to be taken if the Job fails to successfully complete:
Run Post-Job Script
Skip Post-Job Script
Enter the name of a script to execute after the actual job.
Basic usage: <script>@<node_name> <argument_list>
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 the section.
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see .
In the desktop interface, backup jobs are defined exclusively through the Block Backup Wizard. See . The last but one step of the Wizard, the Job Options screen contains five tabs. Each of them is explained below.
Enter a value in KB/s (kilobytes per second) to set the maximum transmission rate per backup task. The value 0, the default, allows the task to use the maximum bandwidth available. See in the DPX 4.9.x User’s Guide.
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 in the DPX 4.9.x User’s Guide.
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see .
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 .
Toggle on
Performs the consistency check.
Toggle off
Does not perform the consistency check.
Toggle on
SQL Server transaction logs are truncated on the source database server after the backup completes. To find the backed-up SQL logs, refer to the message “BACKUP LOG <database-instance> TO DISK...” in the Job Log or to Event 18265 in the Application Event Log.
Toggle off
SQL Server transaction logs are not truncated and will therefore continue to grow on the source database server. To truncate translation logs, run SQL Server maintenance on the source machine. No is the default.
Toggle on
After the backup is complete, DPX deletes the old Exchange logs. Yes is the default.
Toggle off
DPX does not delete any Exchange logs.
Toggle on
Default setting. Back up Exchange DAG from a passive node.
Toggle off
Back up Exchange DAG from an active node.
Toggle on
Synchronize the RMAN catalog after the job completes.
Toggle off
Do not synchronize the RMAN catalog after the job is completed. If you choose this option, the job is not cataloged in RMAN.
Toggle on
The notification is sent as specified below the toggle (additional fields will appear – see below).
Toggle off
The notification is sent to the default e-mail address configured in the Administrator E-mail Settings section.
No
Does not perform the consistency check.
Yes
Performs the consistency check.
Yes
SQL Server transaction logs are truncated on the source database server after the backup completes. To find the backed up SQL logs, refer to the message “BACKUP LOG <database-instance> TO DISK...” in the Job Log or to Event 18265 in the Application Event Log.
No
SQL Server transaction logs are not truncated and will therefore continue to grow on the source database server. To truncate translation logs, run SQL Server maintenance on the source machine. No is the default.
Yes
Default setting. Back up Exchange DAG from a passive node.
No
Back up Exchange DAG from an active node.
Yes
After the backup is complete, DPX deletes the old Exchange logs. Yes is the default.
No
DPX does not delete any Exchange logs.
Yes
Synchronize the RMAN catalog after the job completes.
No
Do not synchronize the RMAN catalog after the job is completed. If you choose this option, the job is not cataloged in RMAN.
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
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.
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.