Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Clustering with Database Mirroring Question...? Expand / Collapse
Author
Message
Posted Monday, July 2, 2012 9:55 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, September 26, 2013 3:42 AM
Points: 72, Visits: 43
I'm looking to setup high availability with Clustering and Database Mirroring on my SQL 2008 R2 Server with log shipping offsite for Disaster Recovery(Not sure if this is the best way for High availability? What is everyone else using? Third party? Or MS built-in tools?);

Current Environment;
Single server, windows 2008 R2, SQL 2008 R2 Ent. with Direct attached storage.

New Envrionment;

Two servers, windows 2008 R2, SQL 2008 R2 Ent. Connected to an EqualLogic iSCSI SAN with 1 SQL server off site connected to Equallogic iSCSI SAN.

Here are my questions;

1. Does the Cluster share a singe IP Address?
2. With Database mirroring can you failover and perform maintenance on the primary then fail back when the primary is back online?
3. If you bring the primary down for a day, the database will be out of sync, Can you switch back and forth on the fly?...Do you need the DB's to sync first in order to failback? or can it come on line and still be syncing??
4. When Mirroring are both Databases online?
5. Has anyone had success setting up Database mirroring to an offsite server with Syncronous Saftey mode without affecting performance?
6. Has anyone had more downtime with Clustering and Database mirroring then without?

Thanks in advance for your posts!
Cheers,
Greg




Post #1324119
Posted Tuesday, July 3, 2012 2:47 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 10:52 AM
Points: 6,291, Visits: 13,552
From reading your post it sounds very much like you require AlwaysOn in SQL Server 2012, are you not able to make the upgrade and utilise the newer technology?

Aside that I'll answer what i can

gregtm (7/2/2012)
1. Does the Cluster share a singe IP Address?

Yes that's the whole point of clustering resources are shared among nodes although only one can own the resource(s) at a time.


gregtm (7/2/2012)
2. With Database mirroring can you failover and perform maintenance on the primary then fail back when the primary is back online?

no, for the same reason as in q4


gregtm (7/2/2012)
3. If you bring the primary down for a day, the database will be out of sync, Can you switch back and forth on the fly?...Do you need the DB's to sync first in order to failback? or can it come on line and still be syncing??



[quote]gregtm (7/2/2012)
4. When Mirroring are both Databases online?

No, one database is in restoring state as transactions are continuously fed between the 2 endpoints. You can use snapshots if you have Enterprise edition of sql server.



gregtm (7/2/2012)
5. Has anyone had success setting up Database mirroring to an offsite server with Syncronous Saftey mode without affecting performance?

Never done it myself, but with synchrounous mirroring over WANs you have to test and get it right otherwise unexpected failovers can occur due to network latency.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1324203
Posted Tuesday, August 21, 2012 8:50 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Friday, September 21, 2012 1:52 PM
Points: 696, Visits: 743
Perry,

I think your answer to number 2 is incomplete. Once the original principal database has caught up, you can failover and 'return' the original principal to being the principal server. We do this every month when we apply Microsoft patches. Fortunately, we have low transaction volume, so the catch-up period is mercifully brief. Can't say what would happen in high volume environment - could end up always playing catchup and never resynchronize?

Steve
Post #1347837
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse