Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

Dell PowerProtect Data Manager Appliance 5.13.0.0 Administrator Guide for DM5500

PDF

Add a Cloud Tier objective to a protection policy

For some protection policy types, you can add a Cloud Tier objective to a protection policy in order to perform backups to Cloud Tier.

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 Appliance UI.
  • A data movement schedule must be configured and running on the cloud storage unit.
  • The Cloud Tier objective can be added to the Primary Backup and Replicate objectives. The Primary Backup and Replicate objectives should be using the protection storage system that is set up for Cloud Tiering

About this task

You can create the Cloud Tier objective from Primary Backup, Replicate, and Extend Retention objectives. Objectives must have a retention time of 14 days or more.

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

  1. Log in to the PowerProtect Data Manager Appliance user interface as a user with the Administrator role.
  2. From the PowerProtect Data Manager Appliance UI, select Protection > Protection Policies, and then click Add.
    The Add Policy wizard appears.
  3. 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
  4. On the Purpose page, select from the available options to indicate the purpose of the new protection policy, and then click Next.
  5. On the Assets page, select the assets that you want to protect with this policy, and then click Next.
  6. 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 Tier objective requires a minimum retention period of 14 days in the Retain for field.
  7. Click Cloud Tier next to Primary Backup or Extend Retention 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 or extended retention objective, or below the replication objective.
  8. 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 Tier objective for the primary backup objective, the extended retention objective, or the replication objective.
  9. In the Add Cloud Tier Backup dialog box, set the following parameters and then click Save:
    • Select the appropriate storage 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.
  10. 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.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\