Deployment KBA: VPLEX: Procedure to move VPLEX Metadata from one Storage to another for redundancy or after adding second storage

Summary: When adding a new array behind a VPLEX, it is required to reconfigure VPLEX metadata volumes so they can benefit from highest availability using both arrays for best practice redundancy. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Goals

Reconfigure VPLEX metadata volumes to meet Best Practices after a Storage Tech Extension.

Facts

It is required that metadata and metadata backups are configured across arrays when more than one array at the local site if more than one array is present.

If the site were built originally with a single array, and another array were to be added at a later time, then it is required to move one leg of the metadata volume and one backup to the new array.

​Unless only one back-end array is available, the meta volume and its backup volume must be on separate arrays and should be in separate failure domains. This requirement also applies to the mirror volume and its backup volume.

Solution

Metadata Reconfiguration:
Before reconfiguration, review current system volume configuration and status.
 

Example: 
VPlexcli:/clusters/cluster-1/system-volumes> ls -al
Name                             Volume Type     Operational  Health  Active  Ready  Geometry  Component  Block     Block  Capacity  Slots
-------------------------------  --------------  Status       State   ------  -----  --------  Count      Count     Size   --------  -----
-------------------------------  --------------  -----------  ------  ------  -----  --------  ---------  --------  -----  --------  -----
C1_Log_vol                       logging-volume  ok           ok      -       -      raid-0    1          2621440   4K     10G       -
C1_Meta                          meta-volume     ok           ok      true    true   raid-1    3          20971264  4K     80G       64000
C1_Meta_backup_2022Aug01_160020  meta-volume     ok           ok      false   true   raid-1    1          20971264  4K     80G       64000
C1_Meta_backup_2022Jul31_160019  meta-volume     ok           ok      false   true   raid-1    1          20971264  4K     80G       64000

Identify current legs of the meta-data mirror and record the VPD ID:
  
VPlexcli:/clusters/cluster-1/system-volumes/ ll <metaname>/components
/clusters/cluster-1/system-volumes/C1_Meta/components:
Name                                      Slot    Type            Operational  Health  Capacity
----------------------------------------  Number  --------------  Status       State   --------
----------------------------------------  ------  --------------  -----------  ------  --------
VPD83T3:600601602cf05500f9b58f62ecc07ae6  0       storage-volume  ok           ok      80G
VPD83T3:68ccf09800371feb2068bb5e40248aaa  1       storage-volume  ok           ok      80G
VPD83T3:68ccf098008daf130e2789948fbd6994  2       storage-volume  ok           ok      80G
 

Steps to create new meta volumes

 

  1. Claim two (2) new storage volumes on the array with the same size (use block size) as the current metadata volume. The meta-volume’s backup size should be equal to or greater than 78G. One new storage volume will be used for active metadata, the other one for metadata backup.

  2. This can be done to ensure the new volumes are clean all any older data on the storage volumes; example of how to clean all data from the given disk:

    • Expose disk that will be used for metadata to the Linux host

    • Write zeros to the disk using the following command
       

      CAUTION: This host command will erase all data on the disk. 
      # dd if=/dev/zero of=device name conv=notrunc



      example: 

      host#: dd if=/dev/zero of=/dev/sdbg conv=notrunc

       

  3. From the array mask the new storage volumes with the VPLEX.
     

  4. Ensure the new volumes are properly discovered and ready to be added as a system volume, record VPD ID.

    Example:

    VPlexcli:/> configuration show-meta-volume-candidates

     

  5. Remove one of the two (2) legs identified previously on the metadata.

    Example:

    VPlexcli:/> meta-volume detach-mirror --storage-volume <VPD_to_remove> --meta-volume <metaname>

     

  6. Add one (1) of the new storage volumes to the metadata.

    Example:

    VPlexcli:/> meta-volume attach-mirror --storage-volume <VPD_to_add> --meta-volume <metaname>

     

  7. Wait for the current metadata volume leg and the new metadata volume leg sync to complete, then review the current system volume configuration and status,

    Example:

    VPlexcli:/clusters/cluster-1/system-volumes> ls -al

     

  8. Reconfigure the metadata backup with the other new storage volume and an existing one using the command shown below. The command selects the volumes to use as backup volumes and creates the initial backup of both volumes.

    Example:

    VPlexcli:/> configuration metadata-backup

    Refer to the VPLEX GeoSynchrony version running CLI Guide for more details on this command. Available on Dell eSupport.
     

  9. Run a health-check and confirm there are no errors related to system volumes.

    Example:

    VPlexcli:/> health-check

     

  10. When done you will need to remove the unused volume from the VPLEX, to do this refer to the SolVe procedure, "Remove disk or array from VPLEX". This procedure is available from SolVe Desktop or SolVe Online under Reference Material > Admin > Admin Procedures > Manage near the bottom of the selection list. 

  11. Repeat steps 1 through 10 for the second cluster if a Metro configuration.

Affected Products

VPLEX, VPLEX GeoSynchrony
Article Properties
Article Number: 000205697
Article Type: How To
Last Modified: 01 Aug 2023
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.