Version 35 by Nata Ramanenka
on Feb 27, 2012 03:46.
<< Changes from 34 to 35
compared with
Current by Irina Gruzdilovich
on Mar 06, 2012 08:35.
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (11)

View Page History
Follow the instructions below to add a Data Protection [Policy|Policies] in CDP.

1. Open the Web browser connected to the CDP Server Web Interface and log in (See [CDP3:Accessing Standard Edition Web Interface], [Accessing Enterprise Edition Web Interface], and [CDP3:Accessing Advanced Edition Web Interface]).

!log.png!

21. Click on "Policy" in the Main Menu to open the "Policies" screen.
|| Standard Edition || Enterprise Edition || Advanced Edition ||
| !pol-st.png! | !main-menu-ent.png! | !main-menu-pola.png! |
32. In the Policy menu, click on "Create New Policy."

!create-new-policya.png!

43. The "Create New Policy" window will open. It contains the following tabs:
* *Policy Settings*
* *Data Retention*
...
{info:title=Note}Depending on the limits, defined for the Disk Safe to which the current Policy is assigned, some of the tabs might be disabled. See [CDP3:Creating Disk Safes#lim]
!az.png!
{info}54. Define the following settings specific to the new Policy:

----
...
On this tab, you can set the Recovery Points Limit for the Policy and create an Archiving Schedule. See [CDP3:Creating Archiving Policies].
!tab1.png!
{info:title=Note} The Recovery Point limit you set on this tab cannot be greater than the limit defined for the current Disk Safe. See [CDP3:Creating Disk Safes#lim].
{info}

...
* *Verify Checksums Server Side* \- Optionally enable this option to ensure that no data is lost during transporting. If this option is activated, then the Server side uncompresses, unencrypts if necessary and compares block packet MD5 with data sent from Agent. Verifying encrypted or unencrypted block checksums on the CDP Server allows you to triple check the integrity of a backup.
* *Exclude Known Disk Safes* ({color:#ff3300}{*}Standard and Advanced Editions{*}{color}) - Optionally check this option to exclude the known Disk Safes from the replication to avoid backing up the same data twice.
* *Specify Backing File Location* (Linux only) - Optionally define a path which the mount point of a device should use to store changed blocks. This option is useful to support backups of devices with low free space. By default, the Linux snapshot driver stores changed blocks (needed to maintain snapshots) in the the free space of the file system on which it is performing a snapshot. When using a server with multiple disks, storing snapshots on a separate dedicated disk can help reduce the load during backup. The disk must have a file system and must be mounted.
{info:title=Example}Linux system:
|| Mount Point || Disk ||
...
| {{/dev/sda3}} | {{/}} |
| {{/dev/sda4}} | {{/var}} |
When {{/boot}} or {{/var}} is 99.99% full, the backups fail because there is no free space to maintain the snapshot.
\\
Once the user inputs "{{/}}" into the "Backing File Location" field, the {{/dev/sda3}} path will be used as the changed block storage location for all file systems.
...
!pol.png!

65. Click on "Create" in the bottom of the window to add the Policy to the "Policies" list.

!policy-create.png!

76. You will receive a notification that the creation of the Policy was successful. Click OK.

!created-policy-notification.png!
{info:title=Tip}The Task results can be sent via email as a Report. See [Reporting].
{info}
87. The new Policy item appears in the "Policies" list. The properties are shown in the grid.
{info:title=Tip}Click on an item in the "Policies" list to see the Policy details in the bottom pane.
{info}
...