Yes, cool feature we're all waiting for such a loooong time ...
Question: Will auto-failover be an active-active Solution (load-balanced), or "only" fail-over?
regards,
Lukas
Yes, cool feature we're all waiting for such a loooong time ...
Question: Will auto-failover be an active-active Solution (load-balanced), or "only" fail-over?
regards,
Lukas
Our failover will be working in active/passive mode.Originally Posted by pfeifferl
Active-active has been added to our TO DO list but there is no ETA for it yet.
So there is no way to set up even a manual switchover to a replicated Open_E server? For example, I have two identical servers. Primary is online, the secondary is strictly a replication destination for the primary. Should there be a catastrophic failure of the Primary I want the secondary to take over as soon as possible.
The only way I can see to do it now is to manually reconfigure everything on the secondary server which could take days. Disabling replication or changing to source, set up all the shares, permissions etc.
There's no way to keep a copy of the pertinent config options and copy them over?
If you are using volume replication and the primary fails
Just change the destination server to source and clear the metadata click apply
CONFIGURATION -> volume manager -> Vol. replication -> Function: Volume replication mode.
then change the ipaddress of the destination to that of the source
After that you should be all set
Ok, I see that gets the former Destination set as the source for replication. What about all the other configuration information needed since the former destination is now serving the data? Shares, permissions etc? You cannot set that up in advance when a volume is a destination.Originally Posted by To-L
thanks
mmmm.....
When you set your replication, you create the shares, and set the permissions ahead.. so when failure happen you just set the source and the destination...
Originally Posted by SuperSAN
With Data replication this is possible. With Volume Replication the destination volumes don't appear in NAS Resources. I prefer the idea of one or two replicated volumes vs. a lot of data replication tasks.