Data Protector Express User Guide (TC330-96005, September 2011)

Log will be saved to this file
Data Protector Express lets you select a file in which to store the job logs. Click the Browse button
to select a file. Data Protector Express always saves a copy of the log in the catalog in addition
to the settings you choose here.
E-mail log
Log Format
Choose a format from the drop down list.
Log will be sent to...
Data Protector Express lets you e-mail logs to one or more recipients. Enter a list of recipients
separated by semicolons.
Auditing
In some cases, you may want positive confirmation that an object — such as a database — was
backed up but you don't want to examine the compete log file generated by selecting Log All. You
can accomplish this by setting the Audit property on the object when you select if for backup.
Simply locate the object in the Selection page of the job properties, right-click on the object and
select Properties, and check the Enable Audit box on the property page. By default, all Exchange
and SQL databases are audited.
Job Pre-Post Execution Commands
You can define commands to be executed before the backup job runs and after the backup job
runs. They are often used to perform custom OS-specific or application-specific tasks, such as to
stop/start a database. Commands are defined on the Execution page of a backup job.
Pre Execution Commands
The pre execution tab on jobs controls the command to be executed before the job is run, either
on multiple hosts, or just the Domain Server. In addition there are options to control whether the
job should stop, or whether the job should continue based on the outcome of the command.
Command path
Specifies a full path or relative path, to a shell command, including command parameters. For
instance cmd.exe /c explorer.exe, or c:\windows\explorer.exe. A macro syntax is
also supported in this field, for many different uses. See the Data Protector Express Technical
Reference Guide for more information.
Run command on all hosts selected in job, as well as the Domain Server
When checked, processes the command on all machines selected in job. When unchecked, only
runs the command on the Domain Server.
Number of minutes to wait for command completion
This value in minutes specifies how long the application should wait for the command to return.
By default, it is set to Forever, meaning the application will wait for as long as possible for the
command to complete. If set to something other then Forever, the application will terminate the
command forcefully if it does not return in time.
Stop job if command fails to be executed
When checked, causes the job to be stopped if the pre command is fails to be executed, such as
if the command does not exist or the operating system cannot property determine how to execute
the command.
Stop job if command returns error code
When checked, causes the job to be stopped if the pre command executes but returns a non-zero
code. When checked, enables the additional options beneath it.
76 Advanced Job Options