Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In File backup, DPX backs up data logically file by file. File backup is what you normally think of when you think of backups.
In this backup type, you back up information at the node group, node, disk, directory, or file level. The following list describes each level:
Temporary space is required on the backup source node(s) for File backup. A rule of thumb for approximating the temporary space (in bytes) is 150–200 times the number of files being backed up. The temporary file, created in the directory where DPX was installed, is deleted after the backup.
Files or directories included in the backup definition will not be backed up if they are excluded through a Windows registry entry. The Windows registry excludes some files by default. If you want to back up these files, remove the exclusions in the registry.
To check for exclusions in the Windows registry, run Microsoft Registry Editor (regedit) and drill down to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup. Remove any undesired exclusions.
Warning! Changes to registries or environmental variables should be done only by qualified administrators. If done incorrectly, such changes can adversely affect applications or operating systems. Contact the Catalogic Software Data Protection Technical Support if you need assistance.
To add exclusions, use DPX rather than the Windows registry.
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 Encryption options section controls how and when a job is encrypted.
To access the job encryption options, do the following:
Go to Job Manager in the sidebar.
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.
Go to the Advanced Options section at the bottom (scroll down if necessary) and expand it. Click the Encryption options header to expand it. Each field and the available choices are explained below.
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 Notification Options section controls who receives messages pertaining to the current job when it is run.
To access the job notification options, do the following:
Go to Job Manager in the sidebar.
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.
Go to the Advanced Options section at the bottom (scroll down if necessary) and expand it. Click the Notification options header to expand it. Each field and the available choices are explained below.
The Notification options consist of a radio button selection with three possible options.
No notifications
No e-mail notifications will be sent.
Default e-mail notifications
Custom e-mail notifications
If the Custom e-mail notifications option is selected, Four additional entry fields appear:
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 '.
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 Configuring Enterprise Information.
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 about 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:
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.
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.
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.
Open the Assign File Exclusion Rule dialog box by doing one of the following:
Right-click on the Enterprise name or icon (in the SOURCES pane) to display the context menu. Then select Edit File Exclusion Rule.
From the menu bar, select Backup > Edit File Exclusion Rule.
On the task panel, click Edit File Exclusion Rule under the Other Tasks section.
The Edit File Exclusion Rules dialog box appears.
In the New Rule Name field, enter the name of your new rule. Click the Add button next to it.
Add an exclusion pattern to that rule:
In the New Exclusion Patterns field, enter the file name or file pattern that describes the files you want to exclude.
Select Add from the task menu at the lower left of the dialog box. The new exclusion pattern is added to the Exclusion Patterns For list.
Repeat Steps 3.1 and 3.2 for each additional exclusion pattern you want to add.
See also. For more information about the exclusion pattern syntax, see Guidelines for setting exclusion patterns.
Click OK. The new file exclusion rule is created and appears in the Rule Names list.
Note. The rules are now created and globally available for various jobs, but they are not assigned to any specific job yet.
Assign the file exclusion rule to a job definition by following the steps in the Assign File Exclusion Rule section below.
To assign an existing file exclusion rule to the current job definition:
Open the Assign File Exclusion Rule dialog box by doing one of the following:
Right-click on the enterprise name or icon to display a context menu. Then select Assign File Exclusion Rule.
From the menu bar, select Backup > Assign File Exclusion Rule.
On the task panel, click Assign File Exclusion Rule.
The Assign File Exclusion Rule dialog box appears.
From the Rule Names list, select the rule to assign to this backup job definition. If you want no file exclusion rule to apply, select None from the list.
Click OK.
Note. File exclusion rules apply to base, incremental, and differential components of the backup job.
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 destination options, do the following:
Go to Job Manager in the sidebar.
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.
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 source options which are discussed in a separate section for the sake of clarity. See Job Source Options for File Backup.
Note. All three sections, i.e. Base, Incremental and Differential Backup Job Destination Options, feature exactly the same options, only referring to different backup types. For more information, see Differential and Incremental Backups.
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.
Enables the twinning option. The twinning option creates two sets of backups simultaneously, eliminating the need for separate tape duplication for off-site vaulting.
Indicates in the Catalog the location of twinned tapes, if twinning is on.
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.
Checksum Files
Generates a checksum value for each file that is backed up. The checksum value is written to the SIDF header.
Indicates the desired performance option. This option helps control the number of tasks running concurrently within a backup job. The appropriateness of each selection depends upon the backup you are running.
Sets a threshold for file splitting. File splitting is the ability to split a file into smaller pieces and back up those pieces simultaneously. File splitting is designed for large files or raw partitions. If Split Large Files/Partitions is selected in Performance Options and the file exceeds the size entered here, the file splits automatically. If the file does not exceed the size entered here, the file does not split. Keep the threshold large enough (2 GB) so that file splitting is reserved for truly large files.
Note. This option applies only to UNIX systems. It is not available for Windows.
Sets the maximum number of tasks that can have files backed up to a single device. The default is 1.
Note. Increasing concurrency to values >1 during backups slows restore performance and requires more memory on the master server during restore.
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.
Holds tasks within a job until the number of drives specified are available for each task to use.
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.
Controls tape drive usage.
To access the job destination 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 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.
Enables the twinning option. The twinning option creates two sets of backups simultaneously, eliminating the need for separate tape duplication for off-site vaulting.
Indicates in the Catalog the location of twinned tapes, if twinning is on.
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.
Checksum Files
Generates a checksum value for each file that is backed up. The checksum value is written to the SIDF header.
Indicates the desired performance option. This option helps control the number of tasks running concurrently within a backup job. The appropriateness of each selection depends upon the backup you are running.
Sets a threshold for file splitting. File splitting is the ability to split a file into smaller pieces and back up those pieces simultaneously. File splitting is designed for large files or raw partitions. If Split Large Files/Partitions is selected in Performance Options and the file exceeds the size entered here, the file splits automatically. If the file does not exceed the size entered here, the file does not split. Keep the threshold large enough (2 GB) so that file splitting is reserved for truly large files.
Note. This option applies only to UNIX systems. It is not available for Windows.
Sets the maximum number of tasks that can have files backed up to a single device. The default is 1.
Note. Increasing concurrency to values >1 during backups slows restore performance and requires more memory on the master server during restore.
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.
Holds tasks within a job until the number of drives specified are available for each task to use.
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.
Controls tape drive usage.
Editing a File backup job allows you to change some parameters of an already defined job (Save), or to create a new job based on the definition of an existing one (Save as…). The procedure is similar to creating a backup job from scratch.
In the main web interface view, go to Job Manager in the sidebar. Then select the file backup job you want to edit from the list.
Tip. You can control this view by ordering items by Job Name, Type, Created Date, Description, or Job Folder. Just click the column header to enable ascending/descending ordering.
Note also the Items per page value and navigation buttons at the bottom of the list, which can be useful when managing the display of many jobs.
Make all required changes to the job definition. The workflow is the same as in Creating a File Backup Job.
Save the job by clicking Save (the changes will be saved under the current job’s name, overwriting previous settings), or Save As (you will be prompted to provide a new name for the job).
Restrictions. The new job name must be unique throughout the entire DPX, regardless of the folder the job is stored in.
In the main desktop interface window, go to the Backup tab, and from the Backup Modes section in the task panel, choose File.
Under Job Tasks in the side panel, select Open Backup Job. The Open Job dialog will appear.
Note. The Job List includes all File backup job names, regardless of the folders they are stored in. The Folder field indicates the actual folder where the selected job is stored.
Select the job you want to edit from the list. Click OK. The Open Job dialog will close and the settings of the selected job will be loaded to the main window view.
Proceed with editing the job. See Creating a File Backup Job for more details.
When finished, 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. If you choose the same name, you will be prompted to confirm the replacement of an already existing job. Select Yes to change the job definition, or No to return to the previous step and specify another name for the job.
If you want to run certain backup jobs on a regular basis, it is best to create a schedule for them.
You may add a schedule to an existing job and save it, add a schedule to an existing job and save it under another name (thus creating a new job without affecting the job you have made edits to), or create a completely new job, adding a schedule to it.
To add a schedule to a File backup job, create a new job or open an existing one from the Job Manager.
In the job creation/editing view, scroll down to the SCHEDULES pane and click Add Schedule. The Schedule dialog will open. Depending on the selected frequency, the dialog will display slightly different parameters to select. Below, the Weekly schedule view is shown.
Select all required parameters, such as the schedule starting time and date, day of the week (if applicable), repetition period, backup retention time, etc.
Click Add.
Important. The schedule is now added to the job, but the job is not saved yet. Continue with the procedure to save the job.
Save the job. If you have added the schedule by modifying an existing job, two options will be available.
Click Save to apply changes to the existing job; or
Click Save As to create a copy of the modified job, with the schedule added, under a new name.
Restrictions. The new job name must be unique throughout the entire DPX, regardless of the folder the job is stored in.
To add a schedule to a File backup job, start creating a new job or open a saved job to edit it.
Go to the Backup tab and from the Backup Modes section in the task panel, choose File.
Under the Job Tasks section, select Schedule Backup Job. The Job Schedule dialog will open.
The Schedule tab allows you to define the dates and times you want the current job to run.
The Exceptions tab allows you to list any exceptions to that schedule.
The Preview tab allows you to view all jobs scheduled for a specified future date.
Note. For File, Image, and NDMP backup jobs only, you can use the scheduler to define a Migrate operation. See Specifying an Automatic Migrate Operation in the DPX 4.9.x Reference Guide.
Select the Schedule tab. Using the Schedule window, you systematically define the schedule for the particular job you are defining. A single schedule definition for a single job can include many schedule description items or job schedule elements, which can be for different frequencies and different backup types. The following illustrates a schedule definition that contains three job schedule elements. Note that after defining the schedule, you will have an opportunity to exclude particular events by using the Exceptions tab.
Add job schedule elements one by one. To do so:
Click New.
In the New Schedule box, select a frequency. The following list describes your choices:\
Fill in the relevant details. The following table provides an overview of the field definitions. The field definitions may vary depending on the frequency you selected.
Click Apply. The job schedule element is added to the “Schedule Description” list at the top of the window.
Repeat steps 4.1 through 4.4 as needed to define the schedule for the particular job you are defining.
Select the Exceptions tab if exclusions are desired. This window allows you to exclude any future scheduled runs of the job. Add exclusion description items one by one. To do so:
Click New.
In the New Exclusion box, select from the display calendar the date of your desired exclusion. In the display calendar, the dates for which the current job is scheduled are denoted in purple. The job elements scheduled for that date appear in the box.
To exclude certain job elements scheduled for that date, click Select one or more entries to exclude, then select the desired jobs from the entries listed in the box. To exclude all job elements scheduled for your selected date, click Exclude whole day.
Click Apply. The exclusion description item is added to the Schedule Description list at the top of the window.
Repeat steps 5.1 through 5.4 as needed to define the exceptions for the particular job you are defining.
You can also indicate whether or not scheduled jobs should be skipped on holidays by clicking to select or unselect Skip Run if Holiday.
Click OK. The schedule and exceptions you just defined are associated with the job you are defining.
Tip. Remember to save the job definition after you specify a job schedule.
Before running a file backup, you need to create a File Backup Job. To do this, use either of the DPX interfaces.
In the main web interface view, go to Job Manager in the sidebar. Then select the New Backup Job button in the upper right corner.
Specify the Job Name. You can also add an optional description (both fields may contain up to 48 characters).
Select Job Type – File and the Job Folder to store the job in (see the Job Manager section for more information). By default, all jobs are stored in the SS_DEFAULT job folder.
Click Add Source in the SOURCES pane to specify which volumes you want to back up. The Source selection dialog will appear. Select the desired volumes and click Select.
See also. For more information about backup source options, see Job Source Options for File Backup.
Tip. You may view your current selection at any moment, using the Selected Items button next to the search field.
You can clear each item using the “X” symbol next to the item, or clear all items at once using the Clear All button.
Optionally, set exclusion rules for files of a certain type. Click Assign Exclusion Rule in the EXCLUSIONS pane to select one of the already existing exclusion rules.
See also. For more information about file exclusion rules and how to define them, see File Exclusion Rules.
In the BASE BACKUP DESTINATION pane, click Set Destination to choose the destination for the base backup.
The INCREMENTAL BACKUP DESTINATION and DIFFERENTIAL BACKUP DESTINATION panes are pre-populated as per the base backup destination. You may change that by clicking Set Destination in respective panes. Note that both these destinations are required for saving the job.
See also. To learn more about incremental and differential backups, see Differential and Incremental Backups.
You may also add a schedule in the SCHEDULES pane for the backup to be run on a regular basis. See Scheduling a File Backup Job.
Set advanced options as desired, selecting them from the Advanced Options drop-down at the bottom of the screen (scroll down if necessary).
See also. For more information about file backup job options, see the following sections:
Click Save. The job can now be viewed, run, edited or deleted from the Job Manager section.
In the main desktop interface window, go to the Backup tab, and from the Backup Modes section in the task panel, choose File.
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 File 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 File 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 file backup job options, see the following sections:
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.
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:
Go to Job Manager in the sidebar.
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.
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.
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).
Compresses data prior to network transmission.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
Tells DPX whether to expand compressed data. This applies only to supported versions of NetWare.
Controls whether Exchange backup occurs at the database or individual message level.
Controls the routing of NDMP server-generated log messages to the job log file.
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.
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>
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see Pre-Scripts and Post-Scripts.
To access the job source options for File backup, do the following:
Go to the Backup tab.
In the Backup Modes section, select File.
Open an already existing backup job by selecting Open Backup Job in the Job Tasks section. 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.
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 feature is set to Yes in Set Job Destination Options. The tape and SIDF headers are also read and verified (levels 1 and 2).
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.
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 not to back up NFS volumes or drives that are mapped to the Microsoft Windows nodes.
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.
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.
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.
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.
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 set to Yes, and if you select both a volume mount point and the drive itself, duplicate backups might occur.
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.
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
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.
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.
Controls whether Exchange backup occurs at the database or individual message level.
Tells DPX whether to expand compressed data. This applies only for supported versions of NetWare.
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.
See also. Generic NDMP Restore with File History Processing in the DPX 4.9.x Reference Guide
Controls the routing of NDMP server-generated log messages to the job log file.
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.
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>
See also. For detailed information about pre- and post-job scripts, including all valid definitions, see Pre-Scripts and Post-Scripts.
E-mail notifications will be sent to the e-mail account specified in the Administrator E-mail Settings tab on the ENTERPRISE INFORMATION page under on the top menu bar. See Administrator E-mail Settings.
This dialog box contains three tabs along the top: Schedule, Exceptions, and Preview.
| Freq | Description |
|---|---|
| Freq | Field | Definition |
|---|---|---|
Node Group
Set of nodes that have been explicitly organized into a named group by the System Administrator.
Node
A single machine such as a PC, a workstation, or a server.
Disk
A logical disk or file system such as C: or D: on a node running Windows, / on UNIX or Linux.
Directory
A UNIX or Linux directory or a Windows folder.
File
Any file.
Toggle on
Enables encrypted data transfer.
Toggle off
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.
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.
Toggle on
Indicates in the Catalog that the tape is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
Toggle on
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.
Toggle off
Tapes in the library with status Offsite cannot be appended to.
Toggle on
Backs up data simultaneously to two tapes.
Toggle off
Disables twinning.
Toggle on
Indicates that the twinned tape (second tape) is stored offsite.
Toggle off
Indicates in the Catalog that the tape is stored onsite.
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.
Toggle on
Generates a checksum value for backed-up files.
Toggle off
Turns off checksum generation. If you turn checksum generation off, level 3 verification cannot be performed. For more information on level 3 verification, see the source option Verify Backup.
Standard
Backs up UNIX nodes and Windows disks concurrently. Use this option when memory on the master or device server(s) is limited or when you will not derive benefit from any of the other choices.
Split Job by Partitions
Backs up UNIX partitions (mount points) and Windows disks concurrently. Use this option when backing up multiple partitions and there are no device or memory limitations.
Split Job by Files
Use this option when backing up single partitions (disks or volumes) that contain many files. This selection will create a task for every available tape drive in this job. Note. This option is not supported for Linux OES.
Split Large Files/Partitions
Splits files that exceed the Split Size threshold. Each part of the split file is backed up concurrently. Use this with large raw partition backups or when you are backing up very large files and the number of files or partitions is less than the number of devices.
Toggle on
The tape drive is released after the current task with a tape drive finishes so that the next job can use the same tape drive before completing the entire job.
Toggle off
The tape drive is not made available for the next job until the entire job is completed.
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.
Yes
Backs up data simultaneously to two tapes.
No
Disables twinning.
Yes
Indicates that the twinned tape (second tape) is stored offsite.
No
Indicates in the Catalog that the tape is stored onsite.
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.
Yes
Generates a checksum value for backed-up files.
No
Turns off checksum generation. If you turn checksum generation off, level 3 verification cannot be performed. For more information on level 3 verification, see the source option Verify Backup.
Standard
Backs up UNIX nodes and Windows disks concurrently. Use this option when memory on the master or device server(s) is limited or when you will not derive benefit from any of the other choices.
Split Job by Partitions
Backs up UNIX partitions (mount points) and Windows disks concurrently. Use this option when backing up multiple partitions and there are no device or memory limitations.
Split Job by Files
Use this option when backing up single partitions (disks or volumes) that contain many files. This selection will create a task for every available tape drive in this job. Note. This option is not supported for Linux OES.
Split Large Files/Partitions
Splits files that exceed the Split Size threshold. Each part of the split file is backed up concurrently. Use this with large raw partition backups or when you are backing up very large files and the number of files or partitions is less than the number of devices.
Yes
The tape drive is released after the current task with a tape drive finishes so that the next job can use the same tape drive before completing the entire job.
No
The tape drive is not made available for the next job until the entire job is completed.
Once
To schedule a job to run once, on a particular date and at a particular time in the future.
Daily
To schedule a job to run every day at a particular time.
Weekly
To schedule a job to run weekly on a particular day of the week, or to schedule a job to run in a particular week of each month.
Monthly
To schedule a job to run monthly on a particular day of the month.
Scheme
To schedule rudimentary base/incremental or base/differential schemes. These are weekly schedules that run a Base backup once a week and Incremental or Differential backups on the remaining days. This option is not available for Block backup jobs.
Once
Run [Backup Type]
Select the backup type (base, differential, or incremental) for this job element. See Backup Types. For File, Image and NDMP, you can also select Migrate.
Backup at [Time]
Enter the time of day you want this job element to commence.
On [Date]
Select from the display calendar the date you want this job element to run.
Retention
Enter the number of days you would like the backed-up data for this element of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
Daily
Run [Backup Type]
Select the backup type (base, differential, or incremental) for this job element. See Backup Types. For File, Image and NDMP, you can also select Migrate.
Backup at [Time]
Enter the time of day you want this job element to commence.
On [Date]
Select from the display calendar the first date you want this job element to run.
Repeat every [Days]
Select the repeat frequency in days.
Retention
Enter the number of days you would like the backed up data for this element of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
End Date
This field is optional. To enable this field, select the check box, then select from the display calendar the final date you want this job element to run.
Weekly
Run [Backup Type]
Select the backup type (base, differential, or incremental) for this job element. For more information, see Backup Types. For File, Image and NDMP, you can also select Migrate.
Backup at [Time]
Enter the time of day you want this job element to commence.
On [Day of Week]
Select the day of the week you want this job element to run. You can select more than one day.
Repeat
Choose either Select Weeks or Week Day in Month.
Every
With the Select Weeks option selected in the Repeat field, select the frequency of weeks that this job should repeat.
The
With the Week Day in Month option selected in the Repeat field, select the week in each month that you would like this job element to run. You can select more than one week. Note that Week Day in Month refers to the set of 7 days starting from the first day in the month, not the calendar week containing the first day of the month.
Retention
Enter the number of days you would like the backed up data for this element of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
Start Date
This field is optional. To enable this field, select the check box, then select from the display calendar the first date you want this job element to run.
End Date
This field is optional. To enable this field, select the check box, then select from the display calendar the final date you want this job element to run.
Monthly
Run [Backup Type]
Select the backup type (base, differential, or incremental) for this job element. See Backup Types. For File, Image and NDMP, you can also select Migrate.
Backup at [Time]
Enter the time of day you want this job element to commence.
On [Day of Month]
Select the numeric day of the month you want this job element to run. You can also choose last day of month.
Repeat every [Months]
Select the repeat frequency in months.
Retention
Enter the number of days, months, or years that you would like the backed up data for this element of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
Start Date
This field is optional. To enable this field, select the check box, then select from the display calendar the first date you want this job element to run.
End Date
This field is optional. To enable this field, select the check box, then select from the display calendar the final date you want this job element to run.
Scheme
Run [Backup Type]
Select the backup type Base. See Backup Types.
Backup at [Time]
Enter the time of day you want the base backup of this job to commence.
On [Day of Week]
Select the day of the week you want the base backup of this job to run.
Retention
Enter the number of days you would like the backed-up data for the base backups of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
Run [Backup Type]
Select either Differential or Incremental. See Backup Types.
Backup at [Time]
Enter the time of day you want the differential or incremental backups of this job to commence.
On [Scheme]
Select the scheme for the differential and incremental runs of this job. Your choices are displayed on the drop down list.
Retention
Enter the number of days you would like the backed up data for the differential or incremental backups of this job to be saved in the Catalog. See Tape Retention in the DPX 4.9.x Reference Guide.
Toggle on
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. The setting minimizes the impact of data transmission on data lines.
Toggle off
Disable data compression.
Toggle on
Back up NFS volumes and drives mapped to the Microsoft Windows nodes.
Toggle off
Do not back up NFS volumes or drives mapped to the Microsoft Windows nodes.
Toggle on
Catalog the backed-up file if detected that the file has been modified during the backup process and the number specified in the Open File Retries field has been reached. 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.
Toggle off
Do not 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.
Toggle on
Data on a mounted drive is backed up through a volume mount point.
Toggle off
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.
Toggle on
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.
Toggle off
Files on remote storage are not backed up. DPX backs up their links.
Toggle on
System-protected files are backed up as part of System State.
Toggle off
System-protected files are not backed up as part of System State.
Toggle on
Take a snapshot of the current data condition, then back up the snapshot.
Toggle off
Do not take a snapshot first.
Toggle on
Performs the consistency check.
Toggle off
Does not perform the consistency check.
Toggle on
Expand compressed data when performing the backup. Select this option if you want to restore to an uncompressed volume. DPX cannot restore compressed data to an uncompressed volume.
Toggle off
Do not expand the compressed data. If you choose this option, you can restore this data only to a compressed volume.
Database Level Backup
EXCHANGE and EXCH2000 disks appear on the Backup File definition screen; EXCHANGEFS and EXCH2000FS disks do not appear. If you back up an entire server, database level backups are performed; folder level backups are not. Database Level Backup is the default.
Folder Level Backup
EXCHANGEFS and EXCH2000FS disks appear on the Backup File definition screen; EXCHANGE and EXCH2000 disks do not appear. If you back up an entire server, folder level backups are performed; database level backups are not.
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.
Toggle on
All NDMP server log messages will be routed to the master server’s job log file. Yes is the default.
Toggle off
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.
Yes
Data on a mounted drive is backed up through a volume mount point.
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
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.
No
Files on remote storage are not backed up. DPX backs up their links.
Yes
System protected files are backed up as part of System State. Yes is the default.
No
System protected files are not backed up as part of System State.
Yes
Take a snapshot of the current data condition, then back up the snapshot.
No
Do not take a snapshot first.
Yes
Performs the consistency check.
No
Does not perform the consistency check.
Database Level Backup
EXCHANGE and EXCH2000 disks appear on the Backup File definition screen; EXCHANGEFS and EXCH2000FS disks do not appear. If you back up an entire server, database level backups are performed; folder level backups are not. Database Level Backup is the default.
Folder Level Backup
EXCHANGEFS and EXCH2000FS disks appear on the Backup File definition screen; EXCHANGE and EXCH2000 disks do not appear. If you back up an entire server, folder level backups are performed; database level backups are not.
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.
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.
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.
