Veritas™ System Recovery 18 Service Pack 3 Management Solution Administrator's Guide
- Introducing Veritas System Recovery Management Solution
- Installing Veritas System Recovery Management Solution
- Getting started with Veritas System Recovery Management Solution
- About managing recovery point destinations
- About viewing filters
- About organizational views
- About managing Veritas System Recovery license policies
- Managing backups
- About backup policies
- Creating a basic backup policy
- Creating an advanced backup policy
- Managing recovery points
- Managing the conversion of recovery points to virtual disks
- Managing Cloud Storage
- Remote recovery of drives and computers
- Local recovery of files, folders, drives, and computers
- About recovering lost data locally
- Starting a computer locally by using Veritas System Recovery Disk
- Recovering files and folders locally by using Veritas System Recovery Disk
- About using the networking tools in Veritas System Recovery Disk
- Monitoring computers and processes
- Appendix A. About backing up databases
- Appendix B. About Active Directory
- Appendix C. Backing up Microsoft virtual environments
- Appendix D. About Veritas System Recovery 18 Management Solution and Windows Server 2008 Core
About backing up VSS-aware databases
Veritas System Recovery 18 Management Solution can co-exist with Microsoft VSS (Volume Shadow-copy Service) to automate the process of backing up VSS-aware databases such as the following:
Exchange Server 2007 or later
SQL Server 2005 or later
Windows Server 2008-based domain controller or later
Note:
Licensing Veritas System Recovery on client computers does not give users any rights to use VSS. VSS must be licensed separately from Microsoft, and users must conform to any license agreement or documentation that accompanies VSS.
VSS-aware databases are auto-enabled and cannot be turned off. VSS lets IT administrators create a shadow copy backup of drives on a server. The shadow copy includes all files (including open files).
When a backup policy starts, Veritas System Recovery alerts the VSS that a recovery point is about to be created. VSS then communicates this information to the VSS-aware databases and puts them into a quiesced (sleep) state. (Veritas System Recovery always attempts to communicate with VSS if it is installed on a desktop or server and tries to provide VSS with information to quiesce databases.)
While in this quiesced state, the databases continue to write to transaction logs. Veritas System Recovery takes an instantaneous snapshot that also includes any open files. When a snapshot is complete, VSS is notified, the databases are activated, and the transaction logs continue writing to the database. (To verify that there are no errors and that VSS is running, you should check the Microsoft error logs.)
While the recovery point is created from the snapshot, the databases and the applications return to an active state and continue to write data. This kind of integration means that you can back up business-critical databases at anytime during the day without it affecting productivity.
Additional points for backing up and restoring VSS-aware databases include the following:
Veritas System Recovery 18 supports Exchange Server 2007 or later, which implements VSS technology. If the database load is heavy, the VSS request might be ignored.
Backups should run during the lightest load time.
Additional backup applications are not needed to run Veritas System Recovery with Exchange databases.
Make sure that you have installed the latest service packs for your given database.
Veritas System Recovery prevents the VSS snapshots from occurring during the time the Veritas System Recovery create a recovery point.
If a full System Restore is done from a recovery point, individual files can be restored from a VSS snapshot. However, the recommended restore process is to use Veritas System Recovery to mount the recovery point file as a virtual drive (using the Recovery Point Browser).
After a full System Restore from a Veritas System Recovery recovery point, a VSS snapshot that was taken before the date and time of the Veritas System Recovery snapshot cannot be used to restore the entire system.
Warning:
Database corruption may occur if the computer is low on hard disk space when you rebuild a database at the same time you run a backup. To avoid database corruption, you should quiesce the database before backing it up. You should also not rebuild or restore the database at the same time that you back it up. To avoid possible conflict Veritas System Recovery does not let you take VSS snapshots and Veritas System Recovery snapshots at the same time.