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 backup policies
You can create backup policies to automate the creation of recovery points by using a daily, weekly, or monthly schedule. This method is useful if you want to create recovery points of managed client computers during off-hours when you are not present. Or, if you want to create a recovery point set without interrupting the normal flow of work. If you create a recovery point set, you can also specify that certain events, like logging on or off of a computer, create incremental recovery points
By default, file names for scheduled independent recovery points or recovery point sets are appended with 001.v2i, 002.v2i, and so forth. File names for incremental recovery points within a recovery point set are appended with _i001.iv2i, _i002.iv2i, and so forth. For example, if your base recovery point were called C_Drive001.v2i, the first incremental recovery point would be called C_Drive001_i001.iv2i.
The name of the computer (where the backup occurs) is always appended to the recovery point file name.
Each backup policy that you create is added to the Backup Policies tree of the product.
You implement a backup policy by doing the following:
Create a backup policy.
You specify what to back up, the backup destination where the resulting recovery points are stored, and when to run the backup (scheduled or manually).
Deploy a backup policy to one or more computer collections.
You can also specify the compression levels of recovery points, enable encryption and password protection. Many other options are available that let you customize each backup according to your business needs.
The client computer must be turned on to create a recovery point at the scheduled time. However, Symantec Management Console does not need to be open for the backup to take place. Also, a remote user does not need to be logged on to the managed client computer. However, Windows must be started on the computer.
To verify that a backup completed as scheduled, you can use the Veritas System Recovery 18 Management Solution portal page to check backup status information. Or, you can review the Recovery Points report in the Reports folder of the Veritas System Recovery 18 Management Solution tree.
Note:
Veritas System Recovery 18 Management Solution supports the recovery point files that are saved directly to a network hard disk or to a local hard disk on the client computer (including USB or FireWire drives). Veritas System Recovery 18 Management Solution does not support saving recovery point files directly to CD or DVD.
See Creating a basic backup policy.
You can also set advanced backup options for an existing backup policy. For example, you can specify the compression level of recovery points or run command files when a backup policy begins on client computers.
See Creating an advanced backup policy.
You can back up databases.
See About backing up VSS-aware databases.
See About backing up non-VSS-aware databases.
See Recovery point sets and independent recovery points in backup policies.