Backup options new and view/modify buttons

The following fields display when the New or View/Modify buttons are clicked on the Backup Options tab.

Item

Description

Options Name

Enter a unique name for the option.

Clock icon [Show all scheduled references]

File-level_Backups00005.bmp

Click the clock icon to see the schedule references on the Schedules References window.

Options Description

Enter a description of the option.

Operating System Family

Operating system to which this option can be applied. If you will be using the option for multiple OS families, select Any. The system only allows the option to be applied to clients belonging to the OS family you select here.

For example, if the options will be used with Windows systems only, select Windows in the list.

Most options lists can be applied to any OS family. If you are using different disk devices or verify levels for specific operating systems, select the appropriate OS family.

Various Options

 

- Directory Depth

A value greater than zero will not back up files below n directories deep. (Zero, full depth, is the default.)

- Read Locking Level

Select this toggle button to specify how read locking is performed on files prior to backing them up. Before a file is backed up, the backup attempts to get a read lock on the file, which allows the file to be read without any other process accessing the file.

There are three read-locking states:

     None - No read locking.

     Do Not Wait - Do Not Wait (not forced) read locking attempts to lock the file, but if the lock cannot be gained, continues to back up the file without the lock.

     Wait Forever - Wait Forever (enforced) read locking stops the backup until the lock can be set. This could potentially take forever.

- Verify Level

Select one of the following:

     None – Do not verify the files in the backup.

     File Level – Files exist. Verify that the list of files sent by the client matches the list received by the backup system. The verify runs once the backup completes, as a dependent task.

     Bit Level – Files exist and contents match. Compare, bit by bit, the contents of the files received by the backup system with the source files on the client. The verify runs once the backup completes, as a dependent task. A bit-level verify often fails when backing up C:\windows due to the some Microsoft processes failing to update modification dates on logs and other files in this folder.

     Inline – Run a file-level verify during the backup by creating and comparing rolling check sums on the client and backup system.

 - Create Catalog Entry? [checkbox]

Creates a catalog of files backed up and places it on the client. If space is limited on the client, this option can be unchecked.

- Speed Option? [checkbox]

Check to enable the backup double-buffering scheme to increase the speed of the backup. This uses more backup system resources and might affect performance of other running processes.

Available Devices

Click the disk device to define the target device where backups are written.

Backup Description

Enter a description of the backups to which this option will be assigned.

Pre-Backup Commands

Use this field to specify commands or scripts to run before the backup (any system command or user script). For example, enter the command to shut down the database before a backup. The output from the command is directed to the backup summary.

Note: For Linux clients, running long pre-backup commands can cause backups to fail. To prevent this, adjust the timeouts in the client’s full .ini file as described in KB 1245.

To specify a pre-backup command, enter the full path to the command in the Pre-Backup Commands field. For example, C:\Data\script.bat or /usr/jsmith/script.sh.

Execute Pre-Backup Command on System [checkbox]

To run the pre-backup command from the Unitrends system, enter its full path and check the Execute Pre-Backup Command on System box. To run a command from the client, leave this box unchecked.

Post-Backup Commands

Use this field to specify commands or scripts to run after the backup (any system command or user script). For example, enter the command to restart a database after a backup completes. The output from the command is directed to the backup summary.

Note: For Linux clients, running long post-backup commands can cause backups to fail. To prevent this, adjust the timeouts in the client’s full.ini file as described in KB 1245.

To specify a post- backup command, enter the full path to the command in the Post-Backup Commands field. For example, C:\Data\script.bat or /usr/jsmith/script.sh.

Execute Post-Backup Commands on System [checkbox]

To run the command from the Unitrends system, enter its full path and check the Execute Post-Backup Command on System box. To run a command from the client, leave this box unchecked.

Save

Click to save your entries.

Cancel

Click to exit the Options tab without saving changes.