Veritas™ System Recovery 21 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 the Veritas System Recovery 21 Management Solution Home page
- Starting Veritas System Recovery 21 Management Solution
- Sending feedback to Veritas
- Preparing to manage the backups of client computers
- Discovering client computers on the network
- Installing the Symantec Management Agent on client computers
- Installing the Veritas System Recovery Plug-in on computers
- Uninstalling the Veritas System Recovery Plug-in on computers
- Installing Veritas System Recovery 21 and later or Veritas System Recovery 21 and later Linux Edition on client computers
- Installing Veritas System Recovery 18 or 16 on client computers
- Installing Veritas System Recovery 18 or 16 Linux Edition on client computers
- Uninstalling Veritas System Recovery-related products and components from client computers
- Generating the LightsOut Restore package in Veritas System Recovery 21 Management Solution
- Generating the LightsOut Restore 18 and 16 package
- Configuring and installing LightsOut Restore 21, 18, or 16 on client computers
- Uninstalling LightsOut Restore from client computers
- Updating the settings of a package
- Uninstalling Veritas System Recovery-related products from the Symantec Management Platform
- Adding or removing recovery point passwords
- About managing recovery point destinations
- Configuring a Dedicated Offsite Copy task
- About viewing filters
- About organizational views
- About managing Veritas System Recovery license policies
- Adding Veritas System Recovery license policies
- Deleting Veritas System Recovery license policies
- Assigning Veritas System Recovery licenses to client computers
- Unassigning Veritas System Recovery licenses from client computers
- Checking the license status of Veritas System Recovery on client computers
- Managing backups
- About backup policies
- Creating a basic backup policy
- Creating an advanced backup policy
- Creating an independent backup task
- Deploying a backup policy
- Deploying an existing backup policy as soon as possible
- Viewing the status of computers within a backup policy
- Editing a backup policy
- Editing the schedule of a backup policy
- Renaming a backup policy
- Disabling a backup policy
- Disabling a backup schedule
- Deleting a backup policy
- Viewing Veritas System Recovery details for a client computer
- 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
- Recovering a computer locally
- Starting a computer locally by using Veritas System Recovery Disk
- Checking a hard disk for errors
- Recovering a computer locally by using a Veritas System Recovery Disk
- About using Restore Anyware to recover locally to a computer with different hardware
- Recovering files and folders locally by using Veritas System Recovery Disk
- About using the networking tools in Veritas System Recovery Disk
- Viewing the properties of a recovery point
- Viewing the properties of a drive within a recovery point
- About the Support Utilities on 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 21 Management Solution and Windows Server 2008 Core
- Index
About backing up non-VSS-aware databases
With Veritas System Recovery, you can create cold recovery points manually, warm recovery points automatically, or hot recovery points of non-VSS-aware databases.
The Veritas System Recovery 21 Management Solution server includes a database, which should back up the server on a regular basis. You must stop the Altiris Notification Server services before backing up so you do not lose or corrupt data. To stop the server, you can use Veritas System Recovery through Veritas System Recovery 21 Management Solution to create a cold recovery point automatically.
A manual cold (or offline) recovery point ensures that all database transactions are committed to the hard disk. You can then use Veritas System Recovery to create the recovery point, and then restart the database.
See Creating the cold, warm, and hot recovery points.
When you automate the creation of a warm recovery point (non-VSS-aware database), you run a command file in the backup policy. The command file is run before data capture to stop the database and commit all transaction logs to the hard disk. Veritas System Recovery snaps a "virtual volume recovery point." A second command file is run in the backup to automatically restart the database while the recovery point is created from the virtual volume recovery point.
The virtual volume snapshot takes only a few seconds to create. The database is in the recovery point state momentarily; which results in a minimal number of created log files.
See “To create a warm recovery point automatically”.
If a cold or warm recovery point is not possible in your organization, to back up non-VSS-aware databases, you can create a hot (or online) recovery point. Veritas System Recovery takes a crash-consistent recovery point. Such a recovery point is equivalent to the state of a system that was running when the power failed. A database that can recover from this type of failure can be recovered from a crash-consistent recovery point.
See “To create a hot recovery point”.