2011 (Windows)

Table Of Contents
Note: You cannot run command files that include a graphical user interface, such
as notepad.exe. Running such command files causes the backup job to fail.
You can run a command file during any of the following stages during the creation
of a recovery point:
Run before snapshot creation
Run after snapshot creation
Run after recovery point creation
See
Command files options on page 84.
The most common use for running command files is to stop and restart
non-VSS-aware databases that you want to back up.
To use a Visual Basic script file (.vbs) during a backup, you can create a batch file
(.bat) to run the script. For example, you can create a batch file called Stop.bat
that contains the following syntax:
Cscript script_filename.vbs
Make sure that Cscript precedes the file name of the Visual Basic script.
Warning: The command files cannot depend on any user interaction or have a
visible user interface. You should test all command files independently of Symantec
System Recovery before you use them during a backup.
When the backup begins, the command file is run during the specified stage. The
backup is stopped if an error occurs while a command file is running. Or, the
backup is stopped if the command file does not finish in the time you specified
(regardless of the stage). In either case, the command file is terminated (if
necessary), and the error information is logged and displayed.
See
Defining a drive-based backup on page 74.
See Running a one-time backup from Symantec System Recovery on page 93.
Command files options
The following table describes the options that are available in the Command file
panel.
Backing up entire drives
Defining a drive-based backup
84