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
Best practices for backing up data
Consider the following best practices before you define and run your first backup.
For optimum protection, you should define a drive-based backup and run it on a regular basis. A drive-based backup backs up and recovers your computer's system drive. Typically, it is the C drive, which includes your operating system. You can also use a drive-based backup to back up and recover a specific hard drive, such as a secondary drive, or to recover lost or damaged files or folders from a specific point in time.
To protect your personal files, such as photographs, music, or documents, you should define a file and folder backup and select the specific files and folders that you want to protect.
Table: Best practices for backing up data
Best Practice | Description |
---|---|
Schedule backups at a time when you know your computer is on. | Your computer must be turned on and Windows must be running at the time a backup occurs. If not, any scheduled backups are skipped until the computer is turned on again. You then are prompted to run the missed backup. Note: Veritas recommends that you do not back up volumes while deduplication is running on them. Schedule backups such that deduplication and backup do not run at the same time. |
Use a secondary hard disk as your backup destination. | You should store recovery points on a hard disk other than your primary hard disk (C). It helps ensure that you can recover your system in the event that your primary hard disk fails. |
Consider using external drives as your backup destination. | Using an external drive makes your backup data more portable. Should you need to remove your critical data from a particular location, you can quickly grab an external drive on your way out the door. |
Give unique names to your external drives to help you easily identify them. | You can assign a unique name to each external drive. A unique name helps you to keep a track of where your backup data is stored for each computer you back up. It is more useful in situations when the drive letters change each time you unplug and plug an external drive into your computer. A unique name ensures that you always know which drive is used when you are running Veritas System Recovery. Using a unique name does not change the volume label of a drive. A unique name helps you to identify the drive when you use Veritas System Recovery. Once a unique name is assigned, it stays with the drive. If you plug the drive into a second computer running another copy of Veritas System Recovery, the unique name appears. Note: You might also consider placing a sticky label on each drive that matches the unique name that you have assigned. |
Use Offsite Copy | Use Offsite Copy to copy your latest recovery points to either a portable storage device or a remote server. By copying recovery points to a portable hard disk, you can then take a copy of your data with you when you leave the office. |
Run backups frequently on a regular basis. | When you define your backups, schedule them to run frequently so that you have recovery points that span at least the last two months. |
Keep personal data on a separate drive than the drive on which Windows and your software programs are installed. | You should keep your operating system and software programs separate from your own data. It speeds the creation of recovery points and reduces the amount of information that needs to be restored. For example, use the C drive to run Windows and to install and run software programs. Use the D drive to create, edit, and store personal files and folders. For other drive management solutions, go to the Veritas website at the following URL: https://www.veritas.com/ |
Verify the recovery point after you create it to ensure that it is stable. | While defining a backup, select the option to verify that the recovery point is stable and can be used to recover lost data. |
Delete the corrupt images. | When the backup destination is a network location, all backup images in the destination folder are appended with a .tmp extension during the backup. If the backup is successful, the images are automatically renamed with .v2i (base) and .iv2i (incremental) extensions. If a network connection to the destination fails, the backup is unsuccessful. The corrupt images with the .tmp extension are retained. These files are not tracked by Veritas System Recovery 21 and can be deleted safely. |
When a backup starts to run on your computer, you might notice that the performance of your computer slows down. Veritas System Recovery requires significant system resources to run a backup. If slowing occurs, you can reduce the speed of the backup to improve computer performance until you are finished working.