What version of RP are you using?

4.0.SP1

Detach RPA1 from the VMAX 40K cluster via boxmgmt. Stayed logged in as boxmgmt then format a repository volume on RPA1 by selecting a masked volume from the VMAX 40K. A 3GB volume is a sufficient size (minimum requirement is 2.86GB). Note that you will need to mask this volume to all RPAs in the VMXA 40K cluster prior to this activity and run a rescan_san from admin or a SAN Diagnostics check from boxmgmt to ensure visibility of the volume. Reattach RPA1 to its cluster and wait for it to reboot.

Then select (not format) the newly formatted repository volume from each of the other RPA's in the VMAX 40K cluster from 2 - 6. Note that you will have detach and re-attach as per RPA1. Perform this action one RPA at a time.

Once you have completed this, log into the Unisphere for RecoverPoint UI and you should see a settings conflict message in the Dashboard informing you that no config exists on the repository volume for the VMAX 40K cluster. Choose the option to import the settings from the VMAX 20K. This will reconcile any differences in the settings between the clusters. If you don't see the option from the UI in the Dashboard you can use the CLI 'resolve_settings' command.

Unfortunately this process will cause a fulll sweep on all of your CGs.

Let me know how it goes.

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

Data Protection & Availability Division

Thank you for your help on this Rich.  I was able to add the repository volume successfully.  I found you must select the repository volume before you reattach the RPA.

Once again thank you so much for your help.

Kevin Simon

I'll use this process tomorrow, please let me know if you think there is something that I should be aware about. It looks pretty simple. Any hints or anything outstanding that I need to be aware would be greatly appreciate it.

Alternatively if it's a case of repository migration then refer to KB 303715 on EMC Online Support.

Regards,

Rich