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
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC PowerProtect DDVE in VMware Cloud 7.8 Installation and Administration Guide

Recovering the DDVE system

The system recovery procedure recovers a DDVE instance from failure of the head unit, NVRAM disk, metadata disks, or any combinations of these components. The head unit is the DDVE root disk.

Prerequisites

System recovery between the same DDOS versions is recommended. When the same DDOS version is not available, system recovery can be done with a later DDOS version. The DDOS version compatibility rules are the same as the RPM upgrade.

About this task

Follow these steps only to recover DDVE when metadata disks or NVRAM disks are not available or failed. If both NVRAM and metadata disks are available, then use Recovering DDVE with system headswap.

Steps

  1. Create instance B with the same configuration as instance A. It must include the same memory size, maximum capacity, and metadata disk capacity. The instance type can be a new generation type that the DDOS version supports.
  2. Enable object-store.
    # storage object-store enable
    Object-store is enabled.
    
  3. Set object-store profile:
    1. Set the passphrase to match the system A passphrase. Otherwise, the recovery fails.
    2. Set the S3 bucket name the same as system A.
      # storage object-store profile set
      A passphrase needs to be set on the system.
      Enter new passphrase: <enter-passphrase-string-meeting-requirements>
      Re-enter new passphrase: <re-enter-passphrase-string>
      Passphrases matched.
      The passphrase is set
      DDVE is running in AWS. Role-based access will be used to access s3.
              Enter the bucket name: <name-of-the-bucket>
              Object-store endpoint needs the Baltimore CyberTrust Root certificate to be imported.
              Do you want to import that certificate with below fingerprint?
              D4:DE:20:D0:5E:66:FC:53:FE:1A:50:88:2C:78:DB:28:52:CA:E4:74  (yes|no) [yes]:
      
              Profile is set.
      
    3. Follow the remaining CLI prompts.
  4. Add metadata disks to the active tier to match or exceed the capacity of system A.
    # storage add dev3
    Checking storage requirements...done
    Adding dev3 to the active tier...done
    Updating system information...done
    dev3 successfully added to the active tier.
    
  5. Run system recovery precheck.
    # system recovery precheck from object-store
    Recovery precheck passed. Use start command to start the recovery.
    
  6. Run the recovery.
    # system recovery start from object-store
    System recovery has started. Use status command to check the status.
    
  7. Check the recovery status.
    # system recovery status
    System recovery is running: stage 2 of 6 (attaching object-store)
    NOTE The system reboots during the recovery process.
  8. After the recovery process finishes, check the status of the file system.
    # filesys status
    The filesystem is enabled and running.
    

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: <>()\