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 on Google Cloud Platform 7.9 Installation and Administration Guide

PDF

Recovering the DDVE instance

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 refers to the DDVE root disk.

Prerequisites

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

A static IP address that is configured using DDVE interfaces (CLI or UI) is not recommended. If a static IP address is configured on the network interface in the original DDVE, the same configuration is restored on the new head. This scenario might cause a network disconnection.

Generally, instead of configuring a static IP address using DDVE interfaces, configure it in the cloud provider environment. The DDVE uses DHCP to obtain the static IP address that you configure in the cloud environment.

If you are already using a static IP address that is configured within DDVE, and a disconnection occurs after following these steps, power off the DDVE. Then add an additional network interface to the new DDVE, and login using the IP address of this interface. Finally, enable or reconfigure the primary network interface on the new head, preferably using DHCP.

About this task

Use this procedure only to recover DDVE when metadata disks or NVRAM disks are unavailable or failed. If both NVRAM and metadata disks are available, use Recovering DDVE using 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 is supported by the DDOS version.
  2. Use the following command to enable the object-store:
    # storage object-store enable
    Object-store is enabled.
    
    
  3. Set the object-store profile.
    Ensure that:
    • The passphrase on system B matches that of system A (otherwise, the recovery fails).
    • The bucket name for both systems is the same.
    • When creating the profile on system B, select the same authentication method (OAuth 2.0 or HMAC) and the same access key (HMAC) as system A.
  4. Run the command to verify the disks that are attached to the DDVE: # disk show hardware.
  5. Add disks to the active tier: # storage add tier active dev<n>
    NOTE Add disks with at least the same capacity as system A.
  6. Run system recovery precheck:
    # system recovery precheck from object-store
    Recovery precheck passed. Use start command to start the recovery.
    
  7. Run the recovery:
    NOTE Ensure that instance A is shut down before running the recovery.
    # system recovery start from object-store
    System recovery has started. Use status command to check the status.
    
  8. Check the recovery status.
    The system reboots during the recovery process.
       
    # system recovery status
    System recovery is running: stage 2 of 6 (attaching object-store).
    
  9. After the recovery process is complete, check the file system status.
    # 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: <>()\