OK, there is a mistake in my question.
Better is: how to change nodes between two failover servers (Primary/Secundary to Secundary/Primary).
Is it possible without disconect virtual IP addresses?
OK, there is a mistake in my question.
Better is: how to change nodes between two failover servers (Primary/Secundary to Secundary/Primary).
Is it possible without disconect virtual IP addresses?
For this to happen you will need o stop the Failover Service and stop the Volume Replication tasks and switch them there positions from Source to Destination and Destination to Source then proceed with the Failover service to set there positions.
So, my VM hosts are connected to DSS, using RoundRobin and virtual IPs. They are and should be in production all the time (this in my target in this debate!).
Before stop the Failover Service, physical IPs of primary DSS must be added on hosts to connect iSCSI targets. In this short time, all paths are active (I/O). It is not safe to configure paths using Virtual and Physical addresses together for longer period, but for this short time, I think, it is “usable”?
After stop the Failover Service, virtual IP addresses are not active, so targets are connected via physical IPs.
If I understand Volume Replication, there is "the very identical" data on Source and Destination Volumes, if they are consistent, of course.
If it is true, physical IPs addresses of Secondary DSS can be added on hosts to connect iSCSI targets. "When running Volume Replication the destination volumes are not available while they are selected as destination volume, so forget all this"
After all paths are active (I/O), paths of the Primary DSS must be removed, ASAP. Hosts are connected only to Secondary DSS, now.
Only now we can switch the Volume Replication tasks off.
Old Secondary DSS “becomes to New Primary” and it is active and connected to VM hosts.
Is there something that I have missed?
Now follows a new Volume Replication and Failover setup.
Must I “clear metadata” on NewPrimary after switch positions from Destination to Source?
Last edited by Toni Bizjak; 02-16-2012 at 03:29 PM.
For clearing the metadata, and changing secondary to be primary, please find the following Forum post that can help you:
http://forum.open-e.com/showthread.php?t=1493
So, there is the problem in "my procedure".
http://kb.open-e.com/entry/147/
When running Volume Replication the destination volumes are not available while they are selected as destination volume.
Before stoping Volume Replication tasks, only paths of source Volumes are active(I/O) and VM hosts can't use (manually entereed) paths to destination Volumes.
I suppose, I'm not fast enought to make switchig procedure and reconnect paths between nodes.
Idea Nr. n+1:
After Manual Failover, Secondary DSS is active. Paths using Virtual IPs are still active (I/O). Can we add paths using Physical addresses of Secondary Node, now?
Better, I try to realise all this on two test DSS servers.
Less damage ...
Last edited by Toni Bizjak; 02-16-2012 at 03:30 PM.
Butler 1.5??? Huh?Originally Posted by Toni Bizjak