About running command files during a backup
|Article:HOWTO21403|||||Created: 2009-01-29|||||Updated: 2013-10-17|||||Article URL http://www.symantec.com/docs/HOWTO21403|
You can use command files (.exe, .cmd, .bat) during a backup. You can use command files to integrate Backup Exec System Recovery with other backup routines that you might be running on the computer. You can also use command files to integrate with other applications that use a drive on the computer.
You cannot run command files that include a graphical user interface, such as notepad.exe. Running such command files will cause the backup job to fail.
You can run a command file during any of the following stages during the creation of a recovery point:
You can specify the location of command files if you want them to be located in a place other than the default location. You can also specify a location on a per-job basis, as well as specify a location that can be shared among several computers. If you specify a network location, you will be asked for network credentials.
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:
The command files cannot depend on any user interaction or have a visible user interface. You should test all command files independently of Backup Exec System Recovery before you use them during a backup.
When the backup begins, the command file is run during the specified stage. If an error occurs while a command file is running or the command file does not finish in the time you specified (regardless of the stage), the backup is stopped, the command file is terminated (if necessary), and the error information is logged and displayed.
Table: Recovery point creation stages
Article URL http://www.symantec.com/docs/HOWTO21403