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 recovery points stored on a network destination
You can choose to store recovery points on a selected network destination. To do this, you need to specify the UNC path (\\server\share\folder) to the folder on the network where you want to store the recovery points.
Table: Recovery point options stored on a network destination
Option | Description |
|---|---|
Indicates the location where you want to store the recovery points, relative to the managed computers. | |
Lets you browse to locate a destination that you want to use, relative to the managed computers. You must have create, read, and write privileges at the specified location. If there is insufficient space at the destination where the recovery point is stored, the policy fails and an error is reported on the Veritas System Recovery 21 Management Solution Home tab. | |
Lets you specify the user name to a destination folder that is located in a network path. | |
Lets you specify the password to a destination that is located in a network path. | |
Lets you retype the password for confirmation. |
See About recovery points stored in a local folder on the client computer.
See Creating default recovery point destinations.
You also have the option to create a subfolder (selected by default) for each computer's recovery points at the network destination. If you clear this option, all recovery points for all computers that are assigned to the backup policy are stored at the root of the network destination.
See About managing recovery point destinations.
Recovery point file names are unique and include the name of the computer. You can use the same network storage location for multiple computers or for groups of computers that you have created in the console.
The user name that you enter needs a read or write access to the network folders where the recovery points are stored. The product uses this logon information to access the network when you create a recovery point.
Note:
You should avoid storing recovery points on the Veritas System Recovery 21 Management Solution computer. As the number or size of backups grows, you have less disk space available for regular server use. When you save recovery points to a separate drive or a network location, the problem is eliminated. Also, if you decide to store recovery points on the client computer, store them to a secondary hard disk and not on the C drive. This practice helps ensure that you can recover the system in the event that the client's primary hard disk fails.