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
Tips for running defined backups
Consider the following tips when you run a defined backup:
Veritas System Recovery does not need to be running for a scheduled backup to start. After you define a backup, you can close Veritas System Recovery.
The computer that is backed up must be turned on and Windows must be started.
All defined backups are saved automatically so that you can edit them or run them later.
See Running an existing backup job immediately.
See Running a backup to create an alternate type of recovery point.
Do not run a disk defragmentation program during a backup. Doing so significantly increases the time that it takes to create the recovery point and might cause unexpected system resource issues.
If you have two or more drives that are dependent on each other, you should include both drives in the same backup. Including both the drives in the same backup provides the safest protection.
Include multiple drives in the same defined backup to reduce the total number of backups that must be run. Doing so minimizes interruptions while you work.
Use the Progress and Performance feature to reduce the effect of a backup on your computer's performance. For example, say a scheduled backup starts while you are in the middle of a presentation. You can slow down the backup to give more processing resources back to your presentation program.
The power management features on a computer can conflict with Veritas System Recovery during a backup.
For example, your computer might be configured to go into hibernation mode after a period of inactivity. You should consider turning off the power management features during a scheduled backup.
If a backup is interrupted, consider running it again.
If you experience problems while creating a backup, you may need to restart the computer.