Skip to main content
Sign Out

Welcome to Dell

My Account
  • 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.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC PowerProtect DDVE on Google Cloud Platform 7.9 Installation and Administration Guide

PDF

Recovering DDVE using system headswap

A system headswap recovers a DDVE instance from a head unit failure. The head unit refers to 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

Use this procedure only to recover DDVE with a head unit (root disk) failure.
NOTE The failed instance is referred to as instance A. The new instance is instance B.

Steps

  1. Create instance B with Head Unit (root disk only) with the same instance type as the original one.
    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. Detach the vNVRAM and metadata disks from the failed head unit (instance A).
  3. Attach the vNVRAM and metadata disks that were detached from instance A to instance B
  4. 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.
  5. 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 with system B.
  6. Run the system headswap command on instance B.
    NOTE The system will reboot 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 (Fri May 25 07:12:35 2018):
The system is going down for reboot NOW!
  7. Verify the file system status after the headswap process completes. 
    # filesys status
The filesystem is enabled and running.
    NOTE
    • You might need to re-activate one or more licenses on the new instance if an unserved-mode license is used.
    • Use the CLI elicense checkout and elicense checkin to obtain licenses from DDVE
      • If an invalid key magic error occurs after a headswap, set the passphrase on the new DDVE, and then perform the headswap using ddboost user revoke token-access sysadmin.
      • If DDVE was attached to an AV-server and a certificate authentication error occurs 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: <>()\