Veritas™ System Recovery 21 User's Guide
- Introducing Veritas System Recovery
- Installing Veritas System Recovery
- Installing Veritas System Recovery
- Ensuring the recovery of your computer
- Creating a new Veritas System Recovery Disk
- Creation Options
- Storage and Network Drivers Options
- Customizing an existing Veritas System Recovery Disk
- About restoring a computer from a remote location by using LightsOut Restore
- Creating a new Veritas System Recovery Disk
- Getting Started
- Setting up default general backup options
- File types and file extension
- Best practices for backing up your data
- Backing up entire drives
- Backing up files and folders
- Running and managing backup jobs
- Running an existing backup job immediately
- Backing up remote computers from your computer
- Monitoring the status of your backups
- About monitoring backups
- Monitoring the backup status of remote computers using Veritas System Recovery Monitor
- Adding a remote computer to the Computer List
- Exploring the contents of a recovery point
- Managing backup destinations
- About managing file and folder backup data
- Managing virtual conversions
- Managing cloud storage
- Direct to cloud
- About creation of Amazon Machine Image (AMI) in Amazon from Veritas System Recovery backups
- About S3-Compatible Cloud Storage
- About Veritas System Recovery supporting Veritas Access
- Recovering files, folders, or entire drives
- Recovering a computer
- Booting a computer by using the Veritas System Recovery Disk
- About using the networking tools in Veritas System Recovery Disk
- Copying a hard drive
- Using the Veritas System Recovery Granular Restore Option
- Best practices when you create recovery points for use with the Granular Restore Option
- Appendix A. Backing up databases using Veritas System Recovery
- Appendix B. Backing up Active Directory
- Appendix C. Backing up Microsoft virtual environments
- Appendix D. Using Veritas System Recovery 21 and Windows Server Core
Running command files during a backup
You can use command files (.exe, .cmd, .bat) during a backup. You can use command files to integrate Veritas 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.
Note:
You cannot run the 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
When you use command files (.exe, .cmd, .bat) during a backup, stop and then restart non-VSS-aware databases.
To use a Visual Basic script file (.vbs) during a backup, you can create a batch file (.bat) to run the script. Veritas System Recovery runs any script using a high privilege account. When the command files are to be located at a place other than the default location, the Command Files
folder specifies the location of these files.
Note:
Veritas recommends that only high privilege users or an administrator have the permission to modify a backup script and access the Command Files
folder.
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 Veritas 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.
Table: Command files options
Option | Description |
---|---|
Specifies 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 are prompted for network credentials. | |
Lets you browse to locate a folder for any command files that you want to use. | |
Specifies the user name to a command file folder that is located in a network path. | |
Specifies the password to a command file folder that is located in a network path. | |
Indicates that you can run a command file after a backup has started and before a recovery point is created. You can run a command during this stage to prepare for the recovery point creation process. For example, you can close any open applications that are using the drive. Note: If you use this option, be sure that the command file has an error recovery mechanism that is built into it. If the computer has one or more services that must be stopped at this stage, and the command file does not contain any form of error recovery, one or more of the stopped services may not be restarted. For example, stopping a non-VSS aware database or a resource-intensive application. An error in the command file can cause the recovery point creation process to stop immediately. No other command files can run. | |
Indicates that you can run a command file after a snapshot is created. Running a command during this stage is a safe point to allow services to resume on the drive while continuing the recovery point creation. Because the snapshot takes only a few seconds to create, the database is in the backup state momentarily. A minimal number of log files are created. | |
Indicates that you can run a command file after the recovery point file is created. You can run a command during this stage to act on the recovery point itself. For example, you can copy it to an offline location. | |
(applies to each stage) | Lets you specify the amount of time (in seconds) that a command file is allowed to run. |