On Tue, 31 Jul 2012 10:57:47 +0200<br>Dirk Bonenkamp - ProActive <<a href="mailto:dirk@proactive.nl">dirk@proactive.nl</a>> wrote:<br><br>> <br>> Since the problem is on the slave, I wouldn't worry to much.<br>
> Fix the IP on the slave and issue the 'drdbadm connect all' on<br>> the slave. If it has been the slave all the time, it should<br>> connect and synchronise without complaining.<br>> <br>> And... just to be sure: Make a backup of the data on the master<br>
> node...<br>> <br><br>Thanks, Dirk!<br><br>Unfortunately I can't back up the master node's data. It consists of<br>running VM disk images, and most of them can't be shut down in the<br>foreseeable future.<br>
<br>The "troublesome" node is configured to be the official slave, so it<br>sounds as though it won't affect the master's view of the data.<br><br>I'm guessing the sync operation will take quite a long time and cause<br>
a performance hit on those VMs, so I'll have to do it out of hours.<br><br>James<br>