Passive mirror is invalid

[kingmetal]

I'm trying to run a replication mirror across two nodes and I'm getting the following error message when I try to check and synchronize:

Command failed: passive mirror is invalid.
Mirror reopening failed.

My setup is two Windows Server 2008 machines running 3.5.3 build 20080229

the mirror host's properties are as follows:

Device: Mirror0
Image file name: Mirror Volumes\C\twinhearts.mir
Total size: 1328 MB
First image path: B:\heartone.img (active)
First image state: Valid
Second image path: #iscsi:192.168.1.13:3260|TargetName=sharedheart|InitiatorName=2BF122E0B102CB41B6BD80F9095BA931
Second image state: Invalid
Read-only: No
Clustered: Yes
Persistent reservation: Yes
Mirror need to be checked and synchronized

The replication host's properties are as follows:

Device: ImageFile0
Image file name: My Computer\B\sharedheart2.img
Total size: 30000 MB
Asynchronous: Yes
Read-only: No
Clustered: Yes
Persistent reservation: Yes

The targets appear to be able to talk to each other, since I can manage them from each other. Is this some sort of file permission error?

Thanks!

[anton (staff)]

Please start with upgrading to the most recent StarWind build. Then if the problem will be still there catch and send us back both target's logs. It will definitely put a bit more light on this issue Thanks!

[kingmetal]

Please start with upgrading to the most recent StarWind build. Then if the problem will be still there catch and send us back both target's logs. It will definitely put a bit more light on this issue Thanks!

I just tried the latest build and I get the same issue. Any clues as to what this error message is telling me?

Thanks for your quick response! Greatly appreciated!

[anton (staff)]

No. That's general error. That's why I was asking for the log.

Please start with upgrading to the most recent StarWind build. Then if the problem will be still there catch and send us back both target's logs. It will definitely put a bit more light on this issue Thanks!

I just tried the latest build and I get the same issue. Any clues as to what this error message is telling me?

Thanks for your quick response! Greatly appreciated!

[kingmetal]

Thanks for your time but I JUST figured it out! I was using the DNS name of the remote target and I needed to use the ip address. Bone-headed mistake, but one I just kept making.

It works GREAT now! I'm battle testing it at the moment. I will have many more questions shortly, I'm sure.

Thanks so much for your help!

[kingmetal]

So far so good! This weekend I'm going to start doing some really serious testing to see if I can break it - but so far everything is operating fantastically. SQL 2005 is using the drive as a shared-drive and the replication seems to be working perfectly. Restarting the primary node doesn't seem to break anything, and once the node comes back all the services reconnect to the shared drive like I would expect them to. I'm pleased!

Of course, now I'm going to just start dreaming up a hundred products to use Starwind for!

[anton (staff)]

Very good! Please drop us an e-mail to support@starwind.com with your ideas about StarWind usage scenarios. We'll be happy to discuss them! Thank you!