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 EMC PowerProtect DDVE on Amazon Web Services 7.9 Installation and Administration Guide

PDF

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 not available, 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 instance A.
    NOTE Do not enable object-store or set the profile on instance B. The object-store will be enabled and the profile will be set automatically after the headswap.
  2. Attach the same role to instance B as that of instance A.
  3. On instance A, make a note of the vNVRAM disk name (usually sdb). Use the same name when attaching the vNVRAM disk to instance B.
    headswap step 1.
  4. Detach the vNVRAM and metadata disks from the failed head unit.
  5. Attach the vNVRAM disk to instance B. While attaching the vNVRAM disk, ensure that the name of the disk on instance B is same as that on instance A.
    Headswap step 2.
    NOTE Ensure that the vNVRAM disk is attached before attaching the metadata disks.
  6. Attach the metadata disks to instance B.
  7. Set the system passphrase.
    NOTE Set the passphrase to match system A, otherwise, the headswap fails.
    # system passphrase set
    Enter new passphrase:
    Re-enter new passphrase:
    Passphrases matched.
    The passphrase is set.
    
  8. Before running the headswap command, ensure that system A is powered off. This step is required to detach the bucket from system A and make it available to be attached to system B.
  9. Run system headswap.
    NOTE The system reboots 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!
    
  10. After the headswap process completes, verify the file system status.
    # filesys status
           The filesystem is enabled and running.
    
    NOTE
    • If an unserved-mode license is used, you might be required to re-activate licenses on the new instance.
    • Use the elicense check-out and elicense check-in commands to obtain licenses from the DDVE.
      • If you experience an invalid key magic issue after a headswap, set the passphrase on the new DDVE system, and run the headswap ddboost user revoke token-access sysadmin command.
      • If the DDVE was attached to an AV-server and you experienced a certificate authentication issue after a headswap, detach and re-attach the DD from the AV-server. The AV-server regenerates the certificate and imports it to DD.

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