I tested it on my servers here in the lab and works for me, is there some events that took place that you post? Is this a production server or test server, if test server I could take a look over a Netviewer session.
The servers are in production, but only server A serves out volumes at the moment. Ok so i went on to SAB B and disconnected the Host binding and it removed all the replication tasks on both servers. I then setup the remote ip address and it connected ok. I can now create replication tasks both ways, maybe the password or something became corrupt, not sure but seems ok now. Will know for sure once all the replication is in sync and i try again
It seems to be working ok now , i have carried a manual failover on a test vm and volume and seems to work correctly and allows the reverse sync to work as well. Must the admin password be the same on both DSS servers for the GUI, as I am not sure what could of caused the problem, we did have some power issues here a couple of weeks ago so maybe something happened then.
Administrator
, i have carried a manual failover on a test vm and volume and seems to work correctly and allows the reverse sync to work as well. Must the admin password be the same on both DSS servers for the GUI, as I am not sure what could of caused the problem, we did have some power issues here a couple of weeks ago so maybe something happened then.
Posting Permissions
Reply With Quote