Dell PowerProtect DD Cloud Tier With Wasabi
    • 25 Jun 2024
    • 5 Minutes to read
    • PDF

    Dell PowerProtect DD Cloud Tier With Wasabi

    • PDF

    Article summary

    How do I use Dell PowerProtect DD Cloud Tier With Wasabi?

    Dell Technologies PowerProtect DD Cloud Tier backup and de-duplication storage software is validated for use with Wasabi. Wasabi is now on the Dell validated list of cloud providers. Data Domain's (DD) Cloud Tier enables object storage from Wasabi to be added for long term retention of your data in the Wasabi cloud.

    This article describes the procedure to integrate Wasabi cloud storage with PowerProtect DD Cloud Tier. The procedure outlined in this article applies to all PowerProtect DD appliances, such as DD3300, DD6400, DD6900, DD9400, DD9900 and PowerProtect DD Virtual Edition. The PowerProtect DD Virtual edition can be installed on a Dell PowerEdge R750 server.

    Prerequisites

    • Active Wasabi cloud storage account.

    • Data Domain Virtual Edition (DDVE) product suite with Cloud Tier feature. 

    • Cloud Tier license on Data Domain Virtual Edition.

    The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, Wasabi recommends that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty, or have application-specific inquiries.

    Architecture Diagram

    Wasabi fits into the Data Domain reference architecture, as shown in the diagram below.

    mceclip0.png

    Enabling Cloud Tier

    Cloud Tier storage is required for the DD system to support cloud-units. The Cloud Tier holds the metadata for the migrated files, while the actual data resides in the cloud. Before enabling Cloud Tier, the File System must be disabled. Below are the steps to disable the File System:

    1. Log in to the DD System Manager.

    2. Open the Data Management drop-down.

    3. Select File System.

    4. Click the SUMMARY tab.

    5. Click Disable.

    6. Open the Hardware drop-down.

    7. Click Storage.

    8. Expand the Cloud Tier drop-down. Click Configure.

    9. Select the checkbox for the shelf to be added from the Addable Storage selection.

    10. Click Add to Tier.

    11. Click Next to add the storage.

    12. Open the Data Management drop-down.

    13. Select File System.

    14. Click Enable Cloud Tier.

      Configure the cloud tier of the file system. To enable the cloud tier, you must meet the storage requirement for the licensed capacity.

       

    15. Click Enable File System from Bottom. When enabling the file system is complete, you should see the message below:

    16. Click Close.

    Importing a CA Certificate

    For more information on downloading the certificate, review Wasabi CA Certificate for https Support on Third-Party Applications.

    Download the "DigiCert Global Root G2" root certificate, which was used to sign the Wasabi vaults.

    To import the certificate:

    1. Open the Data Management drop-down.

    2. Select File System.

    3. Click Cloud Units

    4. Click Manage Certificates. The Manage Certificates for Cloud dialog is displayed. 

    5. Click Add to add the certificate.

    mceclip8.png

    Select one of the following options:

    • Uploading the Certificate as a .pem File

    • Copying and Pasting the Certificate Text

    Uploading the Certificate as a .pem File

    1. Click Choose File.

      mceclip9.png
    2. Browse to the Root CA file and select it.

      mceclip10.png

    Copying and Pasting the Certificate Text

    1. Copy the contents of the .pem file to your copy buffer. Paste the buffer into the dialog. 

    2. Click Add to add the certificate.

      mceclip11.png

      You will see the certificate listed in the certificate table.

      mceclip12.png

    Adding the Cloud Unit

    Follow the steps below to add the Wasabi bucket.

    Port 443 (HTTPS) and/or Port 80 (HTTP) must be open for bi-directional traffic toward the configured Wasabi endpoint URLs.

    1. Open the Data Management drop-down.

    2. Click File System.

    3. Click the CLOUD UNITS tab.

    4. Click Add.

    5. Enter your Wasabi account credentials.

      — Provide a name for the cloud unit.

      — Select Flexible Cloud Tier Provider Framework for S3 as the Cloud Provider.

      — Click Manage certificates and be sure that the imported certificate is checked.

      DDOS version prior to 7.9 did not have the option to add a bucket name.

      — Enter the name of the Wasabi bucket that you want to use.

      DDOS version prior to 7.9 did not have the option to add a bucket name.  

      — Enter "Wasabi" as the S3 Provider name.

      If you are running DDOS version 7.9 on the PowerProtect DD, use the fqdn of the endpoint as the S3 Provider name. For example, if using Wasabi's us-west-1 region the S3 Provider Name will be s3.us-west-1.wasabisys.com.

      — Enter your access key and secret key for your Wasabi account. For more detail, review How do I create a sub-user with Console access and Access and Secret Keys?

      — Enter the appropriate storage region and endpoint URL. For more detail, review Service URLs for Wasabi's Storage Regions.

      — Select standard for the Storage class.

    6. Click Verify to run the cloud provider verify tool before adding the cloud unit. This tool performs pre-check tests to ensure that all requirements are met before adding the actual cloud unit.

    7. Click Add to add the cloud unit.

    8. Click Close to close the status window.

      mceclip16.png

    The file system main window now displays summary information for the new cloud unit and a control for enabling and disabling the cloud unit.

    Adding Data Movement

    Data is moved from the active tier to the cloud tier as specified by the data movement policy. The policy is set on a per-MTree basis. Data movement can be initiated manually or automatically using a schedule.

    1. Open the Data Management drop-down.

    2. Select MTree. In the top panel, select the MTree to which you want to add a data movement policy.

    3. Click the SUMMARY tab.

    4. Under Data Movement Policy, click Add.

    5. Select the Cloud Unit added above as the Destination.

      mceclip20.png

    If you select Age Range, you can select a range of ages. For File Age in Days, set the file age threshold (Older than) and, optionally, the age range (Younger than).

    The minimum number of days for Older than is 14.

    Data movement can be triggered automatically to move data from Active Tier to Cloud Tier based on a schedule. To set a schedule:

    1. Open the Data Management drop-down.

    2. Select File System.

    3. Click Settings.

    4. Click the DATA MOVEMENT tab and set the Throttle and Schedule.

    5. Click Save.

      mceclip21.png

    Data movement can be started and stopped manually for any MTree that has a data movement policy.

    1. Open the Data Management drop-down.

    2. Select File System.

    3. Click the SUMMARY tab.

    4. Under Active Tier, click Start to start the data movement to the Cloud Tier.

    5. To stop data movement, click Stop when data movement is running.

    To view the statistics for Cloud Tier:

    1. Open the Data Management drop-down.

    2. Select File System.

    3. Click the SUMMARY tab.

      mceclip24.png

    To view the statistics for data stored in each of the Cloud Units:

    1. Open the Data Management drop-down.

    2. Select File System.

    3. Click the CLOUD UNITS tab.

      mceclip25.png

    Cloud Tier File Structure in Wasabi Storage

    The Data Domain Cloud Tier feature creates three directories in your Wasabi bucket when the Cloud Unit is added successfully. The directories are named 'd x', 'c x' and 'm x'. The d x directory is used for data segments. The directory named 'c x' is used for configuration data. The directory named 'm x' is used for storing metadata.    

    Prior to DDVE version 7.9, Cloud Tiering creates three buckets (c0, d0, and m0) on the Wasabi account to store configuration, data segments, and metadata respectively. 

    Currently, there is an issue resulting in data stored in the Wasabi bucket not being visible on Wasabi Console. You will need to use S3 Browser to view data in the Wasabi bucket.

    For any questions, submit a request.