Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

thadley1

1 Message

8437

April 1st, 2011 14:00

Re: RecoverPoint - changing the default WAN gateway

Does anyone know the procedure and impact of changing the WAN default gateway in RecoverPoint 3.3?  My understanding is to change the settings on the cluster you log in with boxmgmt and choose setup-> Modify settings -> Enter site 1 details then enter the current and new settings.  After the changes are applied all the rpa's will have to be detached and reattached which will cause a full sweep of all the consistency groups.

schaats

40 Posts

April 4th, 2011 01:00

Hi,

IMHO, your procedure is correct.

Log into site1_box1 with boxmgmt -> detach from cluster -> change gateway -> apply -> attach cluster.

After site1_box1 is attached to cluster successfully, log into site1_box2 -> 'get remote settings' from site1_box1 -> apply -> attach cluster.

And you must do same procedure to your remote site rpa's if you have CRR or CLR configuration.

                                      Oh, Min-Seok

SureshThirumala

60 Posts

May 4th, 2011 05:00

Hello,


Greeting for the day. Please find the details steps to modify your site parameter settings:


1.    Ensure all RPAs are working correctly:

     a.   In the RPA tab of the Management Application GUI, ensure that all RPAs have green check marks in the RPA Status column.

     b.   If any error conditions exist, correct them before continuing.

2.    In the Policy tab of each consistency group in the Management Application GUI, record the value of the Preferred RPA for that group. This value will be used to restore the RPA values at the end of this procedure.5

Use the following table to record your Preferred RPAs.

Consistency    Group

Preferred RPA

Note:                

The following steps can be modified slightly if your configuration consists of more than 2 RPAs.  In that case, balance the consistency groups across all other RPAs except for the one that you are going to initially make the parameters change on.

3.    Ensure that Preferred RPA=RPA 1 for each consistency group. Click Apply for any Preferred RPA that you change.

4.    In the Management Application GUI, for each enabled group, verify that the title of the Status tab includes “Running on RPA 1.” If the group is not enabled, check in the Policy tab that the Preferred RPA = RPA 1.

5.    In the Installation Manager, log in as user boxmgmt using the IP address of RPA 2 at site 1.6

6.    Detach RPA 2 at site 1 from the RPA cluster by selecting Cluster Operations > Detach from cluster.

7.    Select Setup > Modify, and then select and modify the parameters you want to modify.

8.    Apply the changes by selecting Setup > Apply.

9.    Reattach RPA 2 at site 1 by selecting Cluster Operations > Attach to Cluster.

The RPA restarts.

10.  Log in again to the Management Application GUI. In the RPA tabs, ensure that all RPAs have green check marks in the RPA Status column.6

11.  In the Installation Manager, log in as user boxmgmt using the IP address of RPA 2 at site 2.6

12.  Detach RPA 2 at site 2 from the RPA cluster by selecting Cluster Operations > Detach from cluster.

13.  Copy the installation parameters from RPA 2 at site 1 by selecting Setup > Get remote settings, and follow the instructions on screen.

14.  Apply the changes by selecting Setup > Apply.

15.  Reattach RPA 2 at site 2 by selecting Cluster Operations > Attach to Cluster.

The RPA restarts.

16.  Log in again to the Management Application GUI. In the RPA tabs ensure that all RPAs have green check marks in the RPA Status column.6

17.  For all enabled consistency groups, set Preferred RPA value to RPA 2.

No user action is required if consistency groups continue to run on RPA 1.

18.  Repeat steps 11–16 for RPA 1 at site 1.

19.  Repeat steps 11–16 for RPA 1 at site 2.

20.  In the Management Application GUI, restore the RPA values to their previous settings.

On the Policy tab of each consistency group, set Preferred RPA to the value you recorded in step 2.7

I hope, it will help you more. Let me know in case of any queries/issues. Thank you.

Suresh Thirumalaisamy

Technical Support Engineer

Worldwide Technical Support - IMG RecoverPoint

Office Hours: Sun-Thur, 20:00 to 05:00 hrs EST

Phone            : (US Tollfree)1-800-782-4362 || Extn 25083

Email               : Suresh_Thirumalaisamy@emc.com

Please let us know what you think of the level of service provided by sending an email to my manager,

Vashisht, Mohit @ (Mohit.Vashisht@emc.com)

Roberto Nunin

1 Message

September 16th, 2011 06:00

Hello

I know I'm posting a new question instead posting a reply to the main topic, but my situation is similar to the main scenario exposed:

We have a CLR/CRR installation, with two RPA for each site. We must change all IP addresses, both management and WAN addresses.

Currently, he have 5 CLR replicas and 2 CLR/CRR replicas.

We can suspend (hopefully !) or stop all of them.

Which is the correct procedure to do this job ? I've found some instructions, but I'm not sure are completely explained.

Can someone help me about ?

Here are instructions found:

Scenario 3:  Change IP addresses on all the sites

1.  Login to each RPA node on each site and detach them from the cluster.

2.  Modify the IP settings on RPA 1 at site 1. Apply the changes and reattach it to the cluster.  After the RPA 1 site 1 reboot, the site 1 management IP address should be accessible.

3.  Using Setup -> Get remote settings from RPA 1 site 1, apply the changes and reattach them back to the clusters.

Thanks in advance for any help

Best Regards

Roberto

Was this post helpful?

View All

No Events found!

Top