April 6, 2010 at 11:10 am
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.
It is difficult to provide you with the assistance you need over a forum discussion.
April 6, 2010 at 11:14 am
Lynn Pettis (4/6/2010)
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.It is difficult to provide you with the assistance you need over a forum discussion.
I completely agree with Lynn. Find someone who has expertise and let him setup.
April 6, 2010 at 11:29 am
ps. (4/6/2010)
Lynn Pettis (4/6/2010)
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.It is difficult to provide you with the assistance you need over a forum discussion.
I completely agree with Lynn. Find someone who has expertise and let him setup.
Three for the money - get a consultant that has done this before.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 6, 2010 at 11:32 am
CirquedeSQLeil (4/6/2010)
ps. (4/6/2010)
Lynn Pettis (4/6/2010)
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.It is difficult to provide you with the assistance you need over a forum discussion.
I completely agree with Lynn. Find someone who has expertise and let him setup.
Three for the money - get a consultant that has done this before.
The difficulty is not SQL, it's NT, SAN, and Networking. So you are really looking at several consultants plus compliant hardware (not all SAN's can do it, even those that can will charge licensing fees for running the software that allows replication). Log-shipping and mirroring would be much easier for you to implement.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 6, 2010 at 12:01 pm
Thanks to all of you for your valuable suggestions...
After reading all your responses, this is what I've come up with... Please tell if this will work for me or not....
PR Site
Server 1 -Instance 1-----Active/Active Clustering----> - Server2 - Instance 1 (server 1 - instance 1 would have its failover on server 2 and Server 2 - Instance 1 would have its failover on Server 1)
LUN1 for -- Instance 1
LUN2 for -- Instance 2
SAN Replication would be set up between PR and DR Site.
DR Site - Server 1 (with the Same server and Instance name what I've at the PR Site) needs to be configured but would not be turned on untill and unless DR occurs (it will have static IP, I'm not sure though.. 🙁 ). This DR Server will look for the replicated LUN1 and LUN2.
AT the time of DR, Storage team will bring up the LUNs for me at the DR Site and I'll turn the SQL servers on. Now as it has the same name and Instance what my PR site's server had so the application which were hosted on it would not face any problem talking to it.
Rgds,
Pankaj
April 6, 2010 at 12:05 pm
Again, hire a consultant to work with you on this.
April 6, 2010 at 12:07 pm
GregoryF (4/6/2010)
CirquedeSQLeil (4/6/2010)
ps. (4/6/2010)
Lynn Pettis (4/6/2010)
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.It is difficult to provide you with the assistance you need over a forum discussion.
I completely agree with Lynn. Find someone who has expertise and let him setup.
Three for the money - get a consultant that has done this before.
The difficulty is not SQL, it's NT, SAN, and Networking. So you are really looking at several consultants plus compliant hardware (not all SAN's can do it, even those that can will charge licensing fees for running the software that allows replication). Log-shipping and mirroring would be much easier for you to implement.
Even with hiring a consultant(s) the consultants will most likely also be speaking with the hardware vendors. I ran a SAN for awhile and when it comes to something like this, being the expert, I had experts from the switch and routing manufacturers, my networking team, representatives from the company that made the SAN. People from the co-location company, people from the provider of the fiber equipment, people from the company who provided the fiber between the sites who used people .... and it goes on and on. this is a VERY complex process and takes a lot of skilled people.
---------------------------------------------------------------------
Use Full Links:
KB Article from Microsoft on how to ask a question on a Forum
April 6, 2010 at 12:07 pm
pankaj.baluni (4/6/2010)
Thanks to all of you for your valuable suggestions...After reading all your responses, this is what I've come up with... Please tell if this will work for me or not....
PR Site
Server 1 -Instance 1-----Active/Active Clustering----> - Server2 - Instance 1 (server 1 - instance 1 would have its failover on server 2 and Server 2 - Instance 1 would have its failover on Server 1)
LUN1 for -- Instance 1
LUN2 for -- Instance 2
SAN Replication would be set up between PR and DR Site.
DR Site - Server 1 (with the Same server and Instance name what I've at the PR Site) needs to be configured but would not be turned on untill and unless DR occurs (it will have static IP, I'm not sure though.. 🙁 ). This DR Server will look for the replicated LUN1 and LUN2.
AT the time of DR, Storage team will bring up the LUNs for me at the DR Site and I'll turn the SQL servers on. Now as it has the same name and Instance what my PR site's server had so the application which were hosted on it would not face any problem talking to it.
It is very unadvisable to name servers the same. How is DNS going to work? When the second server somes on, it will try to register with DNS, the DNS server will see a conflict. And the IP address will most certainly be different. Also, you will have a very hard time convincing the NT people to create to servers with the same NetBIOS name. It's just one of those things that's not ever done, regardless of who is pushing for it.
From the SQL Side, are you replicating master, msdb, or just user db's?
I really think you need to bring in some expert advice.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 6, 2010 at 12:11 pm
Trey Staker (4/6/2010)
GregoryF (4/6/2010)
CirquedeSQLeil (4/6/2010)
ps. (4/6/2010)
Lynn Pettis (4/6/2010)
Going to make this suggestion again, you may wish to consider hiring a consultant to help you.It is difficult to provide you with the assistance you need over a forum discussion.
I completely agree with Lynn. Find someone who has expertise and let him setup.
Three for the money - get a consultant that has done this before.
The difficulty is not SQL, it's NT, SAN, and Networking. So you are really looking at several consultants plus compliant hardware (not all SAN's can do it, even those that can will charge licensing fees for running the software that allows replication). Log-shipping and mirroring would be much easier for you to implement.
Even with hiring a consultant(s) the consultants will most likely also be speaking with the hardware vendors. I ran a SAN for awhile and when it comes to something like this, being the expert, I had experts from the switch and routing manufacturers, my networking team, representatives from the company that made the SAN. People from the co-location company, people from the provider of the fiber equipment, people from the company who provided the fiber between the sites who used people .... and it goes on and on. this is a VERY complex process and takes a lot of skilled people.
When we did it, it took over six months just two set up two server clusters. The fact is, unless you are working for a fortune 500, you are not going to have the resources. There are very few shops that have done this, it's time consuming, resources consuming, and money consuming.
Overall, there are very few apps that need an instant fail-over to DR, most can take 15 minutes of downtime while logshipping or mirroring are getting up on the DR side.
Please listen to *everyone's* advice, you do not have the experience to do this.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 6, 2010 at 12:16 pm
GregoryF (4/6/2010)
When we did it, it took over six months just two set up two server clusters. The fact is, unless you are working for a fortune 500, you are not going to have the resources. There are very few shops that have done this, it's time consuming, resources consuming, and money consuming.
Overall, there are very few apps that need an instant fail-over to DR, most can take 15 minutes of downtime while logshipping or mirroring are getting up on the DR side.
Please listen to *everyone's* advice, you do not have the experience to do this.
Or are a Financial Institution or Hospital (I remember reading somewhere that their patient systems have to fail-over in 3 to 5 seconds).
April 6, 2010 at 12:54 pm
pankaj.baluni (4/6/2010)
Thanks to all of you for your valuable suggestions...
You're welcome.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 6, 2010 at 12:56 pm
pankaj.baluni (4/6/2010)
AT the time of DR, Storage team will bring up the LUNs for me at the DR Site and I'll turn the SQL servers on. Now as it has the same name and Instance what my PR site's server had so the application which were hosted on it would not face any problem talking to it.
Not possible. These servers would have to be turned off completely and thus you would have to refresh DNS, routing tables etc anyway.
Just leave them up - give them different names, and then assign them a CNAME that is the same as the other. This is stuff that would have to be done during switch over.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 7, 2010 at 8:01 am
CirquedeSQLeil (4/6/2010)
pankaj.baluni (4/6/2010)
AT the time of DR, Storage team will bring up the LUNs for me at the DR Site and I'll turn the SQL servers on. Now as it has the same name and Instance what my PR site's server had so the application which were hosted on it would not face any problem talking to it.
Not possible. These servers would have to be turned off completely and thus you would have to refresh DNS, routing tables etc anyway.
Just leave them up - give them different names, and then assign them a CNAME that is the same as the other. This is stuff that would have to be done during switch over.
Ok... now the question is lets say my PR server is ABCPR1 having 2 instances
Default
ABCPR\XYZ01
and DR Server is ABCDR1 with a CNAME given to it as ABCPR1. It also has 2 instances
Default
ABCDR1\XYZ01
Now, please tell me how using this CNAME would resolve my 'ABCDR1\XYZ01' instance name to 'ABCPR\XYZ01' as application would look for ABCPR1\XYZ01?
Will the CNAME take care of this issue or not? if not, then please suggest a way to go through this...
Rgds,
Pankaj
April 7, 2010 at 8:10 am
pankaj.baluni (4/7/2010)
CirquedeSQLeil (4/6/2010)
pankaj.baluni (4/6/2010)
AT the time of DR, Storage team will bring up the LUNs for me at the DR Site and I'll turn the SQL servers on. Now as it has the same name and Instance what my PR site's server had so the application which were hosted on it would not face any problem talking to it.
Not possible. These servers would have to be turned off completely and thus you would have to refresh DNS, routing tables etc anyway.
Just leave them up - give them different names, and then assign them a CNAME that is the same as the other. This is stuff that would have to be done during switch over.
Ok... now the question is lets say my PR server is ABCPR1 having 2 instances
Default
ABCPR\XYZ01
and DR Server is ABCDR1 with a CNAME given to it as ABCPR1. It also has 2 instances
Default
ABCDR1\XYZ01
Now, please tell me how using this CNAME would resolve my 'ABCDR1\XYZ01' instance name to 'ABCPR\XYZ01' as application would look for ABCPR1\XYZ01?
Will the CNAME take care of this issue or not? if not, then please suggest a way to go through this...
Because you create an alias called SQLPROD.
Normally SQLPROD points to ABCPR. If you have to go to DR, the alias is pointed to ABCDR1.
Just flush the DNS on the clients...
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
April 7, 2010 at 10:32 am
GregoryF (4/7/2010)
Because you create an alias called SQLPROD.Normally SQLPROD points to ABCPR. If you have to go to DR, the alias is pointed to ABCDR1.
Just flush the DNS on the clients...
Thanks for answering that. You really need to involve a network person for this. The network person would understand this and be able to assist substantially.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 15 posts - 16 through 29 (of 29 total)
You must be logged in to reply to this topic. Login to reply