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.

PowerProtect Data Manager 19.11 Storage Direct User Guide

Restore backup copies from replication DD when source Storage Direct agent host, PowerProtect Data Manager server, and VMAX are unavailable

When the source Storage Direct agent host, source PowerProtect Data Manager server, and source VMAX are unavailable, you can use the CLI to perform a restore from the replication DD system.

Prerequisites

Ensure that the following requirements are met:
  • The alternate Storage Direct agent is zoned with the replication (or secondary) DD system and alternate VMAX storage array.
  • Storage groups from the alternate VMAX have the same geometry as the source storage groups are mapped to the alternate Storage Direct agent host.
  • The configuration files that are used for performing the backup are copied to an alternate location.
  • Create a DD support ticket and obtain the password of the vDisk and Boost users who are specified in the configuration file.
  • The Storage Direct agent software is installed on the alternate host.

Steps

  1. Restore the configuration file that you copied to an alternate location, and copy this file to the alternate Storage Direct agent host.
  2. Obtain login details for the replication (or secondary) DD system from the configuration file.
  3. Log in to the replication DD system and perform the following:
    • For an existing configuration, create a vDisk pool, vDisk group, and vDisk devices using the same user specified in the configuration file.
    • For a new configuration:
    1. Create FAST.X restore devices in the same vDisk pool and device group that was created for restore during the protection policy creation. This vDisk pool is the pool that was created to restore FAST.X devices and export to the original VMAX. For example:
      :sysadmin@blrv027a046# vdisk device create count 1 capacity 1 GiB device-group RShivam_SG1_154-0638 pool QR2-Shivam-blrv209a226-c9490-Rec  where RShivam_SG1_154-0638  
      Created VDISK device: vdisk-dev69 WWN: 60:02:18:80:00:36:60:30:bc:05:f7:1b:e6:90:12:a6
      1 VDISK devices created
      device group and QR2-Shivam-blrv209a226-c9490-Rec created during the greenfield protection policy configuration. Count and capacity should be matching the geometry of the source storage group.
      
    2. Export these devices to the alternate VMAX array. For example:
      sysadmin@blrv027a046# scsitarget group show list
      Group Name     Service   # Initiators   # Devices
      ------------   -------   ------------   ---------
      FTS_VMAX_476     VDisk              8          60      Original VMAX
      FTS_VMAX_638     VDisk              8          64       Alternate VMAX
      ------------   -------   ------------   ---------
      sysadmin@blrv027a046# scsitarget group add FTS_VMAX_638 device vdisk-dev69
      
  4. Encapsulate the newly added devices. From the alternate Storage Direct agent host or any of the hosts where the Solutions Enabler is installed, perform the following steps to encapsulate the newly added FAST.X devices into the alternate host:
    1. Create a file with the following format:
      ADD EXTERNAL_DISK WWN=wwn ENCAPSULATE_DATA=YES
      Where wwn is the World Wide Name of the newly created FAST.X LUN.
    2. Run the command for encapsulation:
      symconfigure -sid 638 -file /a commit -n
  5. Create a storage group in the alternate VMAX, for example, QR_SG2, and then add the newly encapsulated FAST.X device to this storage group:
    symsg create QR_SG2 -sid 638
    symsg -sg QR_SG2 add dev 00334 -sid 638
    Where 00334 is the symdev ID provided to the FAST.X device after encapsulation.
  6. Edit the configuration file to add the details for the VMAX_FASTX_RESTORE_SG storage group on the alternate storage. For example:
    [SECONDARY_SYSTEM]
    DDBOOST_USER = QR2-Shivam-blrv209a226-c9490
    DEVICE_HOST = blrv027a046.lss.emc.com
    DEVICE_PATH = QR2-Shivam-blrv209a226-c9490-SU
    DDVDISK_USER = QR2-Shivam-blrv209a226-c9490
    # DEVICE_POOL =
    #RESTORE_DEVICE_POOL = QR2-Shivam-blrv209a226-c9490-Rec
    #RESTORE_DEVICE_GROUP = R-Rep-Shivam_SG1_154-0476
    #RESTORE_DEVICE_GROUP = R-Rep-Shivam_SG2_154-0476
    # DD_BOOST_FC =
    # DD_PORT =
    VMAX_FASTX_RESTORE_SG = QR_SG2  this is the SG created in step 5.
    [ROLLBACK_TARGET_DEVICES]
    SRC_GROUP1 = 000196700638:25AUG2019_SG5   this is the storage group created in the alternate VMAX with the same geometry of source device
    
  7. From the alternate storage, create a lockbox entry for the user who is specified in the configuration file by running the following commands:
    protectpoint security add dd-credentials dd-system secondary vdisk config-file config file location
    protectpoint security add dd-credentials dd-system secondary ddboost config-file config file location
    NOTE These commands prompt you for the passwords that you obtained from DD support for the users who are specified in the configuration file.
  8. Run the following command to ensure that all the restore copy details are obtained using the newly created lockbox:
    Protectpoint backup show list dd-system secondary ddboost config-file config file location
  9. Select one of the backup IDs to restore, and run the following command:
    protectpoint rollback backup-id <backup-id>client source agent hostname dd-system secondary config-file config file location

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