Notes For Implementing RecoverPoint 3.2 SP1 with SRM 1.1

Note: Finally upgraded to version 3.2 SP1 after my complaining about the snapshot consolidation bug…

First, the admin account has been stripped of some privileges.  This account no longer has the ability to manage bookmarking or image access.  I personally see that as a good thing, now I can change the passwords my UNIX admins have and lock down some access.  Account management for SRM was handled by;

  1. Create a new role with Target Image, Failover, Group Configuration and Data Transfer roles
  2. Create an user for SRM, assign the new role

Obviously, the array pairing will need to be reconfigured with the new credentials.  From the production source;

  1. Reconfigure Array Managers
  2. Edit Protection Site Array Manager with new credentials
    1. Select Connect to test connectivity
    2. Replicated Array Pairs should show proper LUN count
  3. Edit Recovery Site Array Manager with new credentials
    1. Connect
    2. LUN count was 0 for me
  4. Rescan Arrays, verify LUN

Edit RecoverPoint configuration settings for SRM on each Consistency Group

  1. Select Policy tab on each Consistency Group to be managed by SRM
  2. Select the “Stretch Cluster/VMware SRM Support” configuration section
  3. Set “Use VMware Site Recovery Manager”
  4. Set “Group is managed by SRM…”
    1. If you don’t know what Cluster Enabler is, check it out.  Very cool Windows clustering tool.

To perform reconfiguration of most sections of the Consistency Group option for “Group is managed by SRM…” will need to be reset to “Group is in maintenance mode…”.

Next is the upgrade to SRM 4.0!