In August of 2007 there was a discussion on CDP about software mirroring
of D3/NT. From the discussion at that time it seemed that there was a
problem mirroring D3/NT using standard Windows software. The only viable
solution stated then was Ross Ferris' product Visage.DRS. I'm wondering
if anyone has anything further to add since the August discussion.
What we are trying to do, is to have a backup machine ready to go if our
regular system should crash - just pull out the wires from the crashed
system, put them into the backup system, change the IP address, start
the D3 services, and we're ready to go. Sounds great theoretically, but
not working realistically at all.
To test this concept we are using a mirroring product called
MirrorFolder. What we did was set up D3 on the backup system and load
data from an old file-save. We then stopped the D3 services on both
systems and did a mirror of the live D3 system to the backup. In
explorer, we checked the file dates, and they matched.
We then started the services on the backup system, and all hell broke
loose. First we got "*** Remote File System Error ***" errors, which
surprised me, since the files are mirrored. Then we got "Cannot Bind
Remote Connection" errors, which I don't know what it means.
Anyway, I let the startup continue even with all the error messages just
to see what would happen. I then tried to log in - and lo and behold, I
was able to get it and run programs. I then checked to see which version
of the programs I was running (I had made a change to a program an hour
before doing this test) and I was running old software. Huh? I had just
mirrored the drives and the dates show it!
Does anyone know what's going on here?
Has anyone had any success with software mirroring? Should I give up on
it and just stick with hardware mirroring?
Sholom
|
