Continuous Protection Server lets you back up data to a specific location on a specific Protection Server. This server and location are referred to as the backup destination. Before you can create backup jobs, you need to create one or more backup destinations where the backed up files are stored. The backup destination designates a specific Protection Server and volume where the data is stored.
Create a backup destination naming strategy that makes it easy to determine what kind of content is in each location. For example, if you plan to store marketing proposals, you might create a destination such as Marketing. If you have marketing departments in different locations, create a destination for each location by adding a prefix to the department name. For example, a destination for the West Coast Marketing department could be WCMarketing.
There are additional details for managing backup destinations such as the following:
-
Permissions for backup destination folders or permissions on objects within a backup destination should not be changed after backup jobs have been run.
-
If you are unable to delete some files from a backup destination, the task should be performed by a user with Administrator rights.
Additionally, Administrators may not be able to delete the folder tree when deleting backup destinations. In this case, local ownership must be assigned to the Domain Admin on the files and all related subfolders if they originate from another local system.
-
CPS cannot be used to back up a Protection Server’s data to a backup destination on the same Protection Server.
-
Backup destinations can only be created on servers that run Windows Server 2003/2008/2008 R2 operating systems and have a Continuous Protection Agent (CPA) installed. In addition, only one backup destination is allowed for each logical volume or drive letter.
-
Symantec recommends that CPS backup destinations be created on volumes separate from the Backup Exec backup-to-disk volumes to prevent redundant use of storage.