Apologies if this appears twice as something odd happened before.
I have been tasked with creating mirrors for a server with a critical notes database on it. I thought that it was just a case of replicating to another server but have been told it isn’t as simple as doing a replication.
Can anyone shed some light on this?
Thanks in anticipation.
Subject: mirroring databases for disaster recovery
Perhaps you ought to be looking at clustering with transactional logging enabled; clustering to ensure that:
a)failover to the drp server happens immeadiately and seemlessly to the user in the event of failure (at least thats how it’s supposed to work!)
b)the alternate database is updated as soon as possible rather than waiting on the replication schedule
and transactional logging to ensure that in the event of failure as much possible data is retained and that any restart of the (failed) server is as quick as possible.
Good Luck
Chris Stoneley