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 the Azure Cloud 7.8 Installation and Administration Guide

Recovering DDVE with system headswap

A system headswap recovers a DDVE instance from a head unit failure. The head unit is the DDVE root disk.

Prerequisites

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

Ensure that the vNVRAM disk and metadata disks from system A (original system) are available for attaching to the new instance B. If either the vNVRAM disk or any metadata disk is unavailable, use Recovering the DDVE instance.

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

Follow these steps only to recover DDVE with a head unit (root disk) failure.

Steps

  1. Create instance B with head unit (root disk only) with the same instance type as the original.
  2. Detach the vNVRAM and metadata storage from the broken head unit and attach them to the instance B head unit.
    Attach the vNVRAM and Meta-data storage above to instance B Head Unit
  3. Set the system passphrase.
    NOTE Set the passphrase to match system A, otherwise, headswap fails.
    # system passphrase set
    Enter new passphrase:
    Re-enter new passphrase:
    Passphrases matched.
    The passphrase is set.
    
  4. Ensure that system A is in Stopped (Deallocated) status.
    This step is required to detach the bucket from system A and make it available to be attached to system B.
  5. Run system headswap.
    NOTE The system restarts during the headswap process.
    # system headswap
    This command returns the system back to its prior operational
    conditions. The system will be rebooted before
    resuming normal operations.
     
    **   If system passphrase was set on the old head, you will
         need to do one of the following after headswap completes:
         - unlock the filesystem          if you have encrypted data, or
         - set the system passphrase      if you don't have encrypted data
    Are you sure? (yes|no) [no]: yes
     
    ok, proceeding.
     
    Please enter sysadmin password to confirm 'system headswap':
    Restoring the system configuration, do not power off / interrupt process ...
    Broadcast message from root (Mon Apr 30 13:44:10 2018):
     
    The system is going down for reboot NOW!
    
  6. Check filesys status after the headswap process is complete.
    # 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: <>()\