Veritas™ System Recovery 23 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
- Managing and Monitoring the backup status of remote computers using Veritas System Recovery Manager
- Adding a remote computer to All Computers
- About Backup Tasks
- 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 23 and Windows Server Core
Tips for creating recovery points
The following information may help when you create recovery points:
Veritas System Recovery Manager does not need to be open for a scheduled backup to start or run. Therefore, after you create a backup jobs and assign it to resource targets, you can exit the console. The client computer that you manage, however, must be turned on and Windows must be started.
All backup jobs are saved in the Veritas System Recovery Manager console so that you can edit or apply to the target later.
Store recovery points to a network share or to a local drive on the managed client computer other than the primary hard disk C. This practice helps ensure that you can recover the system in the event that the client's primary hard disk fails.
Avoid the need to run a disk defragmentation program on the managed client computer during the creation of recovery points. Doing so significantly increases the time it takes to create the recovery point, and it may cause unexpected system resource issues on the client computer.
If you have two or more drives that are dependent on each other, or they are used as a group by a program like a database service, include both drives in the same backup jobs. Back up multiple drives simultaneously by selecting two or more drives in the Create Backup Job window.
Include multiple drives in the same backup jobs to reduce the total number of backups that must be run.
Avoid storing recovery points on the Veritas System Recovery computer. As the number or size of recovery points grows, you have less disk space available for regular server use. When you save recovery points to a separate drive or a network location, this problem is eliminated. Also, if you decide to store recovery points on the client computer, store them to a secondary hard disk. Avoid storing them on the primary hard disk C. This practice helps ensure that you can recover the system in the event that the client's primary hard disk fails.