On 4/8/2011 3:49 PM, Ziots, Edward wrote: > Why not have SQL Mirror the Database and have a pointer in the SQL > Native Client connections for the Primary and Secondary Server? You can > control the failover of the Mirror to the secondary server either via a > Witness server ( the 3rd server at another site) or manual failover. > > Or you can use software like Never-fail/Double-take etc etc to make a > mirror copy. > > I would suggest that the databases that need to be available at the DR > site be mirrored from the Primary Site, since you would be working from > your D/R Site in a disaster anyways, and should be transactionally > correct to the minute. > > What we are going to be doing with SQL 2008 here, mirroring the database > to D/R Site and TLog Shipping to another site ( Both can be utilized for > the D/R Experience, without having to do a Stretch ( Multi-Site Cluster)
He says he understands about mirroring the database, etc. It's not the mirroring off the db, but the routine maintenance. What he doesn't understand is the maintenance aspect - how can you reboot one node of the cluster, if the cluster requires an odd number of nodes. How do you do that? Once the cluster is set up with nodes in more than one site, how do you maintain it, when you need to do work on one of the nodes? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
