For some protection policy types, you can add a
Cloud Tierobjective to a protection policy in order to move local full backups to
Cloud Tier after a predefined number of days.
Prerequisites
Ensure that a
protection storage system is set up for
Cloud Tiering, with the system passphrase set.
Cloud storage units must be pre-configured on the
protection storage system before they are configured for
Cloud Tier in the
PowerProtect Data Manager UI.
A data movement schedule must be configured and running on the cloud storage unit.
The
Cloud Tierobjective can be added to the
Primary Backup and
Replicateobjectives. The
Primary Backup and
Replicateobjectives should be using the
protection storage system that is set up for
Cloud Tiering
About this task
Cloud Tiering happens at 00:00 UTC each day. Depending on your time zone, this time may be within business hours and thus
Cloud Tiering may impact available network bandwidth.
Cloud Tiering applies to both centralized and self-service protection policies.
Steps
Log in to the
PowerProtect Data Manager user interface as a user with the
Administrator role.
From the
PowerProtect Data Manager UI, select
Protection > Protection Policies, and then click
Add.
The
Add Policy wizard appears.
On the
Type page, enter a name and description, select the type of system to back up, and click
Next.
The following protection policy types support
Cloud Tiering:
Virtual machine
Microsoft SQL Server
Microsoft Exchange Server
Network Attached Storage (NAS)
Oracle
SAP HANA
File System
Kubernetes
Block volume
On the
Purpose page, select from the available options to indicate the purpose of the new protection policy, and then click
Next.
On the
Assets page, select the assets that you want to protect with this policy, and then click
Next.
On the
Objectives page, click
Add under
Primary Backup if the primary backup
objective is not already created, and fill out the fields in the Target and Schedules panes on the
Add Primary Backup dialog.
NOTE:There is no minimum recurrence required for the Cloud
objective, however, the
Cloud Tierobjective requires a minimum retention period of 14 days in the
Retain for field.
Click
Cloud Tier next to
Primary Backup or, if adding a Cloud
objective for a replication
objective that you have added, click
Cloud Tier under
Replicate.
An entry for
Cloud Tier is created to the right of the primary backup
objective, or below the replication
objective.
Under the entry for
Cloud Tier, click
Add.
The
Add Cloud Tier Backup dialog appears, with summary information for the parent node. This information indicates whether you are adding this
Cloud Tierobjective for the primary backup
objective or the replication
objective.
In the
Add Cloud Tier Backup dialog box, set the following parameters and then click
Save:
Select one or more of the upstream full backups.
Select the appropriate Cloud Unit from the
Cloud Target list.
For
Tier After, set a time of 14 days or more.
The protection policy is now enabled with
Cloud Tiering.
NOTE:If the retention period of a copy is less than the time specified in the
Tier After field, and you do not edit the
Retain for value of this schedule or its copy to a value greater than the
Tier After field before the retention period of the copy expires, the copy will not be cloud tiered.
Click
Next to proceed with the remaining pages of the
Add Policy wizard, verify the information, and then click
Finish.
A new job is created, which you can view under the
Jobs tab after the job completes.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\