Moving a DCO DR node to a different subnet

[DCIM_Support]

This question was originally posted on DCIM Support by Jim Davis on 2018-05-07

---

I have a customer who will be moving an existing DCO DR node from one site to another. There existing infrastructure consists of a DCO server with an attached DR node in the same rack. They also have a spare server of the same type which they wish to build as a standalone DCO server, relocate it interstate then have it assume the role of the DR node. They wish to minimize the time that they are without a DR node. They have 2 HA licences FYI...

Questions:-

1. Can they just add the new DR IP address to the DCO server then attach the second DR node? (is this supported? i.e. can DCO support 2 DR nodes?)
   
   
2. Should they just shut down the existing DR node then add the interstate DR node as per normal procedure? (will this cause any conflict with the original DR entry that the DCO server already knows about?)

I would appreciate any thoughts on the best way to "migrate" the DR node interstate.

Regards

Jim Davis - NIE Melbourne/AU

(CID:130683435)

[DCIM_Support · Accepted solution]

This answer was originally posted on DCIM Support by Jef Faridi on 2018-05-08

---

Hi Jim,

1. The new server (as second DR) cannot be added to an exiting setup "Standalone + DR". Setup will allow only 1 DR node!
2.  Shutting down the existing DR node would not help, but it may help if it is promoted. Then it can be off-lined, if you wish. After promoting the existing DR node (via Webmin interface > StruxureWare DC Operation > Disaster Recovery > "Promote disaster recovery node"), then you would be able to add the new server as DR node.

Kind regards

(CID:131336255)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jim Davis on 2018-07-18

---

After working with the customer today we identified the following error during the DR attachment process:-

The cluster time is 36080 seconds off from our time. Please correct the time.

36080 works out to 10 hours so we established that the server they were attempting to attach as a DR node had its system time out by 10 hours. Once a valid NTP server was configured and both servers times were closely matched, the DR attachment was successful.

Even though these are both standalone DCO servers, the reference to cluster time does not just refer to a DCO clustered environment.

(CID:132666154)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.