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
Manually validating recovery points
You can validate the recovery points by identifying if any of the recovery points are corrupted. You can verify both base and incremental images.
This validation is independent of your backup jobs. At any given point you can validate the older recovery points. You can verify recovery points located on a local or network location.
At a time you can specify one recovery point for validation. After the validation is complete, a list of corrupted recovery points is displayed.
A PowerShell script is used for this validation of recovery points. This script is available in the Veritas System Recovery media. <media path>\Docs\Automation\PowerShellscripts
This feature is not available from the Veritas System Recovery user interface and only available using the Powershell script.
If you give the path of the first incremental, the script validates the first incremental and then the base recovery point and not the second incremental.
For example, in case of a full backup (.v2i) and its incremental backups (.iv2i), if you have one full backup and two incremental images, and you give the path of the second incremental for validation, the script validates the second incremental and then proceeds to the base recovery point.
To manually validate recovery points
- Launch the PowerShell command line.
- Change the directory to where the PowerShell script is available and enter \\VERIFYIMAGE.psl and the location of the recovery point (local or network).
Note:
You can also give the path of the PowerShell script and the location of the recovery point without changing the directory.
If you have specified a network location, provide the username and password after the network location.
The script verifies the backup image and lists corrupted images, if any. If none of the backups are corrupt, a message is displayed that the backups are validated successfully.