Veritas™ System Recovery 18 Service Pack 3 Management Solution Administrator's Guide

The following information may help when you create recovery points:

• Because Notification Server works with a database, you should back up the server on a regular basis.

• Symantec Management Console does not need to be open for a scheduled backup to start or run. Therefore, after you create a backup policy and assign it to resource targets, you can exit the console. The client computer that you manage, however, must be turned on and Windows must be started. To verify that the creation of a recovery point is in progress, check the Status tab of a selected backup policy. To verify that a recovery point was made, you can review the information on the Veritas System Recovery 18 Management Solution portal page.

• All backup policies are saved in the Veritas System Recovery 18 Management Solution database so that you can edit or run them later.

• Store recovery points to a network share or to a hard disk on the managed client computer other than the primary hard disk C. This practice helps ensure that you can recover the system in the event that the client's primary hard disk fails.

• Avoid the need to run a disk defragmentation program on the managed client computer during the creation of recovery points. Doing so significantly increases the time it takes to create the recovery point, and it may cause unexpected system resource issues on the client computer.

• If you have two or more drives that are dependent on each other, or they are used as a group by a program like a database service, include both drives in the same backup policy. Back up multiple drives simultaneously by selecting two or more drives in the Create New Backup Policy Web page.

• Include multiple drives in the same backup policy to reduce the total number of backups that must be run.

• Avoid storing recovery points on the Veritas System Recovery 18 Management Solution computer. As the number or size of recovery points grows, you have less disk space available for regular server use. When you save recovery points to a separate drive or a network location, this problem is eliminated. Also, if you decide to store recovery points on the client computer, store them to a secondary hard disk. Avoid storing them on the primary hard disk C. This practice helps ensure that you can recover the system in the event that the client's primary hard disk fails.