I was thinking of that. Current TTL is 900s, we can probably lower it on a temporary basis to facilitate the change. I wasn't aware about the AD object, no... I presume the existing object will simply be updated when the new cluster joins, which in turn will trigger a replication of it anyway?
Thanks Richard -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Buzzard Sent: 20 July 2016 16:16 To: [email protected] Subject: Re: [gpfsug-discuss] Migrating to CES from CTDB On Wed, 2016-07-20 at 14:42 +0000, Sobey, Richard A wrote: [SNIP] > > The downtime option involves shutting down the CTDB cluster, deleting > the AD object, renaming the new cluster and starting CES SMB to allow > it to join AD with the same name. This takes about 15 minutes while > allowing for AD replication and the TTL on the DNS. This then has to > be repeated when the original CTDB nodes have been reinstalled. > Can you not reduce the TTL on the DNS to as low as possible prior to the changeover to reduce the required downtime for the switch over? You are also aware that you can force the AD replication so no need to wait for that, other than the replication time, which should be pretty quick? I also believe that it is not necessary to delete the AD object. Just leave it as is, and it will be overwritten when you join the new CES cluster. Saves you a step. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
