Clustered SQL servers in DR Hotsite

FAQ

Profile

Clustered SQL servers in DR Hotsite

Database Help (Home) -> Clustering

Next: Shutdown or reboot

Author

Message

External

Since: Jan 31, 2008
Posts: 2

(Msg. 1) Posted: Thu Jan 31, 2008 9:06 am Post subject: Clustered SQL servers in DR Hotsite Archived from groups: microsoft>public>sqlserver>clustering (more info?)

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To avoid having to change any ODBC connections or application configurations the SQL virtual server names will need to be the same at the hotsite as they are at the normal location. The IP address scheme is different at the hotsite. There will be a separate DNS server at the hotsite. The hotsite will be connected to the network here at all times. My question is, will SQL server allow identical virtual server names on the same network at the same time? I tend to think not. The other kicker to all this is there is a database (it's a VMWare database) that I need to keep a constantly updated copy both here and at the hotsite. That's why I would like to have both the hotsite and local clusters up at the same time so I could do replication between the clusters. Thanks for any help anyone can provide Matt >> Stay informed about: Clustered SQL servers in DR Hotsite

Tom Moreau

External

Since: Apr 21, 2004
Posts: 502

(Msg. 2) Posted: Thu Jan 31, 2008 9:23 am Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

You don't really need to have servers with identical names. What you can do is create a DNS alias to point to the primary server and have your apps use the alias. In the event of a disaster, you can update the DNS alias to point to the DR site. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "md" wrote in message I have to bring up a second set of clustered SQL servers at a DR Hotsite. To avoid having to change any ODBC connections or application configurations the SQL virtual server names will need to be the same at the hotsite as they are at the normal location. The IP address scheme is different at the hotsite. There will be a separate DNS server at the hotsite. The hotsite will be connected to the network here at all times. My question is, will SQL server allow identical virtual server names on the same network at the same time? I tend to think not. The other kicker to all this is there is a database (it's a VMWare database) that I need to keep a constantly updated copy both here and at the hotsite. That's why I would like to have both the hotsite and local clusters up at the same time so I could do replication between the clusters. Thanks for any help anyone can provide Matt >> Stay informed about: Clustered SQL servers in DR Hotsite

External

Since: Jan 31, 2008
Posts: 2

(Msg. 3) Posted: Thu Jan 31, 2008 1:05 pm Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

That's an interesting idea. Does ODBC/OLEDB just use the server name to resolve to the IP address? If that's the case, then in the event of a disaster all that would really need done is the entry for the virtual server here could be changed to point up to the hotsite. That seems too easy! Matt "Tom Moreau" wrote in message > You don't really need to have servers with identical names. What you can > do > is create a DNS alias to point to the primary server and have your apps > use > the alias. In the event of a disaster, you can update the DNS alias to > point to the DR site. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "md" wrote in message > > I have to bring up a second set of clustered SQL servers at a DR Hotsite. > To > avoid having to change any ODBC connections or application configurations > the SQL virtual server names will need to be the same at the hotsite as > they > are at the normal location. The IP address scheme is different at the > hotsite. There will be a separate DNS server at the hotsite. The hotsite > will be connected to the network here at all times. > > My question is, will SQL server allow identical virtual server names on > the > same network at the same time? I tend to think not. > > The other kicker to all this is there is a database (it's a VMWare > database) > that I need to keep a constantly updated copy both here and at the > hotsite. > That's why I would like to have both the hotsite and local clusters up at > the same time so I could do replication between the clusters. > > Thanks for any help anyone can provide > > Matt > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Tom Moreau

External

Since: Apr 21, 2004
Posts: 502

(Msg. 4) Posted: Thu Jan 31, 2008 1:35 pm Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Just make sure your connect strings don't use raw IP's. Put the alias in there and it's all good. Make sure that the TTL for the alias is 0. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "md" wrote in message That's an interesting idea. Does ODBC/OLEDB just use the server name to resolve to the IP address? If that's the case, then in the event of a disaster all that would really need done is the entry for the virtual server here could be changed to point up to the hotsite. That seems too easy! Matt "Tom Moreau" wrote in message > You don't really need to have servers with identical names. What you can > do > is create a DNS alias to point to the primary server and have your apps > use > the alias. In the event of a disaster, you can update the DNS alias to > point to the DR site. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "md" wrote in message > > I have to bring up a second set of clustered SQL servers at a DR Hotsite. > To > avoid having to change any ODBC connections or application configurations > the SQL virtual server names will need to be the same at the hotsite as > they > are at the normal location. The IP address scheme is different at the > hotsite. There will be a separate DNS server at the hotsite. The hotsite > will be connected to the network here at all times. > > My question is, will SQL server allow identical virtual server names on > the > same network at the same time? I tend to think not. > > The other kicker to all this is there is a database (it's a VMWare > database) > that I need to keep a constantly updated copy both here and at the > hotsite. > That's why I would like to have both the hotsite and local clusters up at > the same time so I could do replication between the clusters. > > Thanks for any help anyone can provide > > Matt > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Chasman

External

Since: Feb 01, 2008
Posts: 3

(Msg. 5) Posted: Fri Feb 01, 2008 11:03 am Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Tom, I have a similiar situation. I have to setup a DR site to mirror my primary site. My live site is in the US. I am running Windows 2003 Enterprise 64-bit with MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK with the same setup. Unfortunately the engineer before me used MS Sql 2005 standard and not the enterprise edition. What I need to do is backup my live site to the UK and keep it synced with the US. If my prime site goes down then I recover to the UK site. I have around 100gb of data in about 24 databases. The link from the US to the UK is an E3 45mb/sec. This is shared by other users. Any suggestions on how to keep the UK site relatively current in respect to the US site? Any help you could offer would be greatly appreciated. Charles "Tom Moreau" wrote in message > Just make sure your connect strings don't use raw IP's. Put the alias in > there and it's all good. Make sure that the TTL for the alias is 0. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "md" wrote in message > > That's an interesting idea. Does ODBC/OLEDB just use the server name to > resolve to the IP address? If that's the case, then in the event of a > disaster all that would really need done is the entry for the virtual > server > here could be changed to point up to the hotsite. That seems too easy! > > Matt > > "Tom Moreau" wrote in message > >> You don't really need to have servers with identical names. What you can >> do >> is create a DNS alias to point to the primary server and have your apps >> use >> the alias. In the event of a disaster, you can update the DNS alias to >> point to the DR site. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "md" wrote in message >> >> I have to bring up a second set of clustered SQL servers at a DR Hotsite. >> To >> avoid having to change any ODBC connections or application configurations >> the SQL virtual server names will need to be the same at the hotsite as >> they >> are at the normal location. The IP address scheme is different at the >> hotsite. There will be a separate DNS server at the hotsite. The hotsite >> will be connected to the network here at all times. >> >> My question is, will SQL server allow identical virtual server names on >> the >> same network at the same time? I tend to think not. >> >> The other kicker to all this is there is a database (it's a VMWare >> database) >> that I need to keep a constantly updated copy both here and at the >> hotsite. >> That's why I would like to have both the hotsite and local clusters up at >> the same time so I could do replication between the clusters. >> >> Thanks for any help anyone can provide >> >> Matt >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Tom Moreau

External

Since: Apr 21, 2004
Posts: 502

(Msg. 6) Posted: Fri Feb 01, 2008 11:14 am Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

You have a few options: 1) Database mirroring 2) Log shipping 3) Data Protection Manager In all cases, the initial synch involves taking a full backup. You'll have to restore the backup to the UK site and any log backups that were taken since the full backup. At that pint, you are synched and you can turn on log shipping or DB mirroring. I'm not entirely sure how DPM works. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "Chasman" wrote in message Tom, I have a similiar situation. I have to setup a DR site to mirror my primary site. My live site is in the US. I am running Windows 2003 Enterprise 64-bit with MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK with the same setup. Unfortunately the engineer before me used MS Sql 2005 standard and not the enterprise edition. What I need to do is backup my live site to the UK and keep it synced with the US. If my prime site goes down then I recover to the UK site. I have around 100gb of data in about 24 databases. The link from the US to the UK is an E3 45mb/sec. This is shared by other users. Any suggestions on how to keep the UK site relatively current in respect to the US site? Any help you could offer would be greatly appreciated. Charles "Tom Moreau" wrote in message > Just make sure your connect strings don't use raw IP's. Put the alias in > there and it's all good. Make sure that the TTL for the alias is 0. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "md" wrote in message > > That's an interesting idea. Does ODBC/OLEDB just use the server name to > resolve to the IP address? If that's the case, then in the event of a > disaster all that would really need done is the entry for the virtual > server > here could be changed to point up to the hotsite. That seems too easy! > > Matt > > "Tom Moreau" wrote in message > >> You don't really need to have servers with identical names. What you can >> do >> is create a DNS alias to point to the primary server and have your apps >> use >> the alias. In the event of a disaster, you can update the DNS alias to >> point to the DR site. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "md" wrote in message >> >> I have to bring up a second set of clustered SQL servers at a DR Hotsite. >> To >> avoid having to change any ODBC connections or application configurations >> the SQL virtual server names will need to be the same at the hotsite as >> they >> are at the normal location. The IP address scheme is different at the >> hotsite. There will be a separate DNS server at the hotsite. The hotsite >> will be connected to the network here at all times. >> >> My question is, will SQL server allow identical virtual server names on >> the >> same network at the same time? I tend to think not. >> >> The other kicker to all this is there is a database (it's a VMWare >> database) >> that I need to keep a constantly updated copy both here and at the >> hotsite. >> That's why I would like to have both the hotsite and local clusters up at >> the same time so I could do replication between the clusters. >> >> Thanks for any help anyone can provide >> >> Matt >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Chasman

External

Since: Feb 01, 2008
Posts: 3

(Msg. 7) Posted: Fri Feb 01, 2008 11:55 am Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Tom, I was wondering if you can Upgrade from MS SQL 2005 standard to MS SQL 2005 EE ? If so would MS SQL 2005 EE peer replication resolve my issue any better than, Database mirroring, Log shipping or Data Protection Manager? Thanks, Charles "Tom Moreau" wrote in message > You have a few options: > > 1) Database mirroring > 2) Log shipping > 3) Data Protection Manager > > In all cases, the initial synch involves taking a full backup. You'll > have > to restore the backup to the UK site and any log backups that were taken > since the full backup. At that pint, you are synched and you can turn on > log shipping or DB mirroring. I'm not entirely sure how DPM works. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "Chasman" wrote in message > > Tom, > > I have a similiar situation. I have to setup a DR site to mirror my > primary > site. > > My live site is in the US. I am running Windows 2003 Enterprise 64-bit > with > MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK > with the same setup. Unfortunately the engineer before me used MS Sql > 2005 > standard and not the enterprise edition. What I need to do is backup my > live > site to the UK and keep it synced with the US. If my prime site goes down > then I recover to the UK site. > > I have around 100gb of data in about 24 databases. The link from the US to > the UK is an E3 45mb/sec. This is shared by other users. Any suggestions > on > how to keep the UK site relatively current in respect to the US site? > > Any help you could offer would be greatly appreciated. > > Charles > > "Tom Moreau" wrote in message > >> Just make sure your connect strings don't use raw IP's. Put the alias in >> there and it's all good. Make sure that the TTL for the alias is 0. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "md" wrote in message >> >> That's an interesting idea. Does ODBC/OLEDB just use the server name to >> resolve to the IP address? If that's the case, then in the event of a >> disaster all that would really need done is the entry for the virtual >> server >> here could be changed to point up to the hotsite. That seems too easy! >> >> Matt >> >> "Tom Moreau" wrote in message >> >>> You don't really need to have servers with identical names. What you >>> can >>> do >>> is create a DNS alias to point to the primary server and have your apps >>> use >>> the alias. In the event of a disaster, you can update the DNS alias to >>> point to the DR site. >>> >>> -- >>> Tom >>> >>> ---------------------------------------------------- >>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>> SQL Server MVP >>> Toronto, ON Canada >>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>> >>> >>> "md" wrote in message >>> >>> I have to bring up a second set of clustered SQL servers at a DR >>> Hotsite. >>> To >>> avoid having to change any ODBC connections or application >>> configurations >>> the SQL virtual server names will need to be the same at the hotsite as >>> they >>> are at the normal location. The IP address scheme is different at the >>> hotsite. There will be a separate DNS server at the hotsite. The hotsite >>> will be connected to the network here at all times. >>> >>> My question is, will SQL server allow identical virtual server names on >>> the >>> same network at the same time? I tend to think not. >>> >>> The other kicker to all this is there is a database (it's a VMWare >>> database) >>> that I need to keep a constantly updated copy both here and at the >>> hotsite. >>> That's why I would like to have both the hotsite and local clusters up >>> at >>> the same time so I could do replication between the clusters. >>> >>> Thanks for any help anyone can provide >>> >>> Matt >>> >>> >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Tom Moreau

External

Since: Apr 21, 2004
Posts: 502

(Msg. 8) Posted: Fri Feb 01, 2008 12:14 pm Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Yes, you can upgrade. Check out "Version and Edition Upgrades" in the BOL. Peer-to-peer replication allows both DB's to be online concurrently, and be updateable. Dunno if you need that or not. One drawback is that you have to handle identity columns is a special way, so as to avoid collisions. DB mirroring is still an option without going to EE, which can keep your costs down. You don't get automatic failover, but often you don't want that in a DR situation. You like to declare a disaster after examining the situation first. Also, if you want to use the remote site for reporting, you can create a DB snapshot off of the mirror. Yeah, it's static but it can be useful for off-loading some reporting. Here, too, you need EE. Also, if your remote site is used only for DR - i.e. no reporting or anything - I believe you don't need an extra license. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "Chasman" wrote in message Tom, I was wondering if you can Upgrade from MS SQL 2005 standard to MS SQL 2005 EE ? If so would MS SQL 2005 EE peer replication resolve my issue any better than, Database mirroring, Log shipping or Data Protection Manager? Thanks, Charles "Tom Moreau" wrote in message > You have a few options: > > 1) Database mirroring > 2) Log shipping > 3) Data Protection Manager > > In all cases, the initial synch involves taking a full backup. You'll > have > to restore the backup to the UK site and any log backups that were taken > since the full backup. At that pint, you are synched and you can turn on > log shipping or DB mirroring. I'm not entirely sure how DPM works. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "Chasman" wrote in message > > Tom, > > I have a similiar situation. I have to setup a DR site to mirror my > primary > site. > > My live site is in the US. I am running Windows 2003 Enterprise 64-bit > with > MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK > with the same setup. Unfortunately the engineer before me used MS Sql > 2005 > standard and not the enterprise edition. What I need to do is backup my > live > site to the UK and keep it synced with the US. If my prime site goes down > then I recover to the UK site. > > I have around 100gb of data in about 24 databases. The link from the US to > the UK is an E3 45mb/sec. This is shared by other users. Any suggestions > on > how to keep the UK site relatively current in respect to the US site? > > Any help you could offer would be greatly appreciated. > > Charles > > "Tom Moreau" wrote in message > >> Just make sure your connect strings don't use raw IP's. Put the alias in >> there and it's all good. Make sure that the TTL for the alias is 0. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "md" wrote in message >> >> That's an interesting idea. Does ODBC/OLEDB just use the server name to >> resolve to the IP address? If that's the case, then in the event of a >> disaster all that would really need done is the entry for the virtual >> server >> here could be changed to point up to the hotsite. That seems too easy! >> >> Matt >> >> "Tom Moreau" wrote in message >> >>> You don't really need to have servers with identical names. What you >>> can >>> do >>> is create a DNS alias to point to the primary server and have your apps >>> use >>> the alias. In the event of a disaster, you can update the DNS alias to >>> point to the DR site. >>> >>> -- >>> Tom >>> >>> ---------------------------------------------------- >>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>> SQL Server MVP >>> Toronto, ON Canada >>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>> >>> >>> "md" wrote in message >>> >>> I have to bring up a second set of clustered SQL servers at a DR >>> Hotsite. >>> To >>> avoid having to change any ODBC connections or application >>> configurations >>> the SQL virtual server names will need to be the same at the hotsite as >>> they >>> are at the normal location. The IP address scheme is different at the >>> hotsite. There will be a separate DNS server at the hotsite. The hotsite >>> will be connected to the network here at all times. >>> >>> My question is, will SQL server allow identical virtual server names on >>> the >>> same network at the same time? I tend to think not. >>> >>> The other kicker to all this is there is a database (it's a VMWare >>> database) >>> that I need to keep a constantly updated copy both here and at the >>> hotsite. >>> That's why I would like to have both the hotsite and local clusters up >>> at >>> the same time so I could do replication between the clusters. >>> >>> Thanks for any help anyone can provide >>> >>> Matt >>> >>> >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Chasman

External

Since: Feb 01, 2008
Posts: 3

(Msg. 9) Posted: Fri Feb 01, 2008 1:27 pm Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Tom, How do the three methods you mentionned compare with using replication? Any method better then another? Thanks, Charles "Tom Moreau" wrote in message > Yes, you can upgrade. Check out "Version and Edition Upgrades" in the > BOL. > Peer-to-peer replication allows both DB's to be online concurrently, and > be > updateable. Dunno if you need that or not. One drawback is that you have > to handle identity columns is a special way, so as to avoid collisions. > > DB mirroring is still an option without going to EE, which can keep your > costs down. You don't get automatic failover, but often you don't want > that > in a DR situation. You like to declare a disaster after examining the > situation first. > > Also, if you want to use the remote site for reporting, you can create a > DB > snapshot off of the mirror. Yeah, it's static but it can be useful for > off-loading some reporting. Here, too, you need EE. > > Also, if your remote site is used only for DR - i.e. no reporting or > anything - I believe you don't need an extra license. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "Chasman" wrote in message > > Tom, > > I was wondering if you can Upgrade from MS SQL 2005 standard to MS SQL > 2005 > EE ? If so would MS SQL 2005 EE peer replication resolve my issue any > better > than, Database mirroring, Log shipping or Data Protection Manager? > > Thanks, > Charles > > "Tom Moreau" wrote in message > >> You have a few options: >> >> 1) Database mirroring >> 2) Log shipping >> 3) Data Protection Manager >> >> In all cases, the initial synch involves taking a full backup. You'll >> have >> to restore the backup to the UK site and any log backups that were taken >> since the full backup. At that pint, you are synched and you can turn on >> log shipping or DB mirroring. I'm not entirely sure how DPM works. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "Chasman" wrote in message >> >> Tom, >> >> I have a similiar situation. I have to setup a DR site to mirror my >> primary >> site. >> >> My live site is in the US. I am running Windows 2003 Enterprise 64-bit >> with >> MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK >> with the same setup. Unfortunately the engineer before me used MS Sql >> 2005 >> standard and not the enterprise edition. What I need to do is backup my >> live >> site to the UK and keep it synced with the US. If my prime site goes down >> then I recover to the UK site. >> >> I have around 100gb of data in about 24 databases. The link from the US >> to >> the UK is an E3 45mb/sec. This is shared by other users. Any suggestions >> on >> how to keep the UK site relatively current in respect to the US site? >> >> Any help you could offer would be greatly appreciated. >> >> Charles >> >> "Tom Moreau" wrote in message >> >>> Just make sure your connect strings don't use raw IP's. Put the alias >>> in >>> there and it's all good. Make sure that the TTL for the alias is 0. >>> >>> -- >>> Tom >>> >>> ---------------------------------------------------- >>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>> SQL Server MVP >>> Toronto, ON Canada >>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>> >>> >>> "md" wrote in message >>> >>> That's an interesting idea. Does ODBC/OLEDB just use the server name to >>> resolve to the IP address? If that's the case, then in the event of a >>> disaster all that would really need done is the entry for the virtual >>> server >>> here could be changed to point up to the hotsite. That seems too easy! >>> >>> Matt >>> >>> "Tom Moreau" wrote in message >>> >>>> You don't really need to have servers with identical names. What you >>>> can >>>> do >>>> is create a DNS alias to point to the primary server and have your apps >>>> use >>>> the alias. In the event of a disaster, you can update the DNS alias to >>>> point to the DR site. >>>> >>>> -- >>>> Tom >>>> >>>> ---------------------------------------------------- >>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>>> SQL Server MVP >>>> Toronto, ON Canada >>>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>>> >>>> >>>> "md" wrote in message >>>> >>>> I have to bring up a second set of clustered SQL servers at a DR >>>> Hotsite. >>>> To >>>> avoid having to change any ODBC connections or application >>>> configurations >>>> the SQL virtual server names will need to be the same at the hotsite as >>>> they >>>> are at the normal location. The IP address scheme is different at the >>>> hotsite. There will be a separate DNS server at the hotsite. The >>>> hotsite >>>> will be connected to the network here at all times. >>>> >>>> My question is, will SQL server allow identical virtual server names on >>>> the >>>> same network at the same time? I tend to think not. >>>> >>>> The other kicker to all this is there is a database (it's a VMWare >>>> database) >>>> that I need to keep a constantly updated copy both here and at the >>>> hotsite. >>>> That's why I would like to have both the hotsite and local clusters up >>>> at >>>> the same time so I could do replication between the clusters. >>>> >>>> Thanks for any help anyone can provide >>>> >>>> Matt >>>> >>>> >>> >>> >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Tom Moreau

External

Since: Apr 21, 2004
Posts: 502

(Msg. 10) Posted: Fri Feb 01, 2008 1:35 pm Post subject: Re: Clustered SQL servers in DR Hotsite [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)

Typically, replication is not considered a High Availability (HA) technology. It's more for performance and distributed processing. There is no graceful failover and failback that you can get with the other HA technologies. -- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau "Chasman" wrote in message Tom, How do the three methods you mentionned compare with using replication? Any method better then another? Thanks, Charles "Tom Moreau" wrote in message > Yes, you can upgrade. Check out "Version and Edition Upgrades" in the > BOL. > Peer-to-peer replication allows both DB's to be online concurrently, and > be > updateable. Dunno if you need that or not. One drawback is that you have > to handle identity columns is a special way, so as to avoid collisions. > > DB mirroring is still an option without going to EE, which can keep your > costs down. You don't get automatic failover, but often you don't want > that > in a DR situation. You like to declare a disaster after examining the > situation first. > > Also, if you want to use the remote site for reporting, you can create a > DB > snapshot off of the mirror. Yeah, it's static but it can be useful for > off-loading some reporting. Here, too, you need EE. > > Also, if your remote site is used only for DR - i.e. no reporting or > anything - I believe you don't need an extra license. > > -- > Tom > > ---------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS > SQL Server MVP > Toronto, ON Canada > https://mvp.support.microsoft.com/profile/Tom.Moreau > > > "Chasman" wrote in message > > Tom, > > I was wondering if you can Upgrade from MS SQL 2005 standard to MS SQL > 2005 > EE ? If so would MS SQL 2005 EE peer replication resolve my issue any > better > than, Database mirroring, Log shipping or Data Protection Manager? > > Thanks, > Charles > > "Tom Moreau" wrote in message > >> You have a few options: >> >> 1) Database mirroring >> 2) Log shipping >> 3) Data Protection Manager >> >> In all cases, the initial synch involves taking a full backup. You'll >> have >> to restore the backup to the UK site and any log backups that were taken >> since the full backup. At that pint, you are synched and you can turn on >> log shipping or DB mirroring. I'm not entirely sure how DPM works. >> >> -- >> Tom >> >> ---------------------------------------------------- >> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >> SQL Server MVP >> Toronto, ON Canada >> https://mvp.support.microsoft.com/profile/Tom.Moreau >> >> >> "Chasman" wrote in message >> >> Tom, >> >> I have a similiar situation. I have to setup a DR site to mirror my >> primary >> site. >> >> My live site is in the US. I am running Windows 2003 Enterprise 64-bit >> with >> MS Sql 2005 64-bit in a cluster environment. I have my DR site in the UK >> with the same setup. Unfortunately the engineer before me used MS Sql >> 2005 >> standard and not the enterprise edition. What I need to do is backup my >> live >> site to the UK and keep it synced with the US. If my prime site goes down >> then I recover to the UK site. >> >> I have around 100gb of data in about 24 databases. The link from the US >> to >> the UK is an E3 45mb/sec. This is shared by other users. Any suggestions >> on >> how to keep the UK site relatively current in respect to the US site? >> >> Any help you could offer would be greatly appreciated. >> >> Charles >> >> "Tom Moreau" wrote in message >> >>> Just make sure your connect strings don't use raw IP's. Put the alias >>> in >>> there and it's all good. Make sure that the TTL for the alias is 0. >>> >>> -- >>> Tom >>> >>> ---------------------------------------------------- >>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>> SQL Server MVP >>> Toronto, ON Canada >>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>> >>> >>> "md" wrote in message >>> >>> That's an interesting idea. Does ODBC/OLEDB just use the server name to >>> resolve to the IP address? If that's the case, then in the event of a >>> disaster all that would really need done is the entry for the virtual >>> server >>> here could be changed to point up to the hotsite. That seems too easy! >>> >>> Matt >>> >>> "Tom Moreau" wrote in message >>> >>>> You don't really need to have servers with identical names. What you >>>> can >>>> do >>>> is create a DNS alias to point to the primary server and have your apps >>>> use >>>> the alias. In the event of a disaster, you can update the DNS alias to >>>> point to the DR site. >>>> >>>> -- >>>> Tom >>>> >>>> ---------------------------------------------------- >>>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS >>>> SQL Server MVP >>>> Toronto, ON Canada >>>> https://mvp.support.microsoft.com/profile/Tom.Moreau >>>> >>>> >>>> "md" wrote in message >>>> >>>> I have to bring up a second set of clustered SQL servers at a DR >>>> Hotsite. >>>> To >>>> avoid having to change any ODBC connections or application >>>> configurations >>>> the SQL virtual server names will need to be the same at the hotsite as >>>> they >>>> are at the normal location. The IP address scheme is different at the >>>> hotsite. There will be a separate DNS server at the hotsite. The >>>> hotsite >>>> will be connected to the network here at all times. >>>> >>>> My question is, will SQL server allow identical virtual server names on >>>> the >>>> same network at the same time? I tend to think not. >>>> >>>> The other kicker to all this is there is a database (it's a VMWare >>>> database) >>>> that I need to keep a constantly updated copy both here and at the >>>> hotsite. >>>> That's why I would like to have both the hotsite and local clusters up >>>> at >>>> the same time so I could do replication between the clusters. >>>> >>>> Thanks for any help anyone can provide >>>> >>>> Matt >>>> >>>> >>> >>> >> >> > > >> Stay informed about: Clustered SQL servers in DR Hotsite

Display posts from previous:

Related Topics:

Clustered SQL server 2005 - Maintenance plan problem - Hi Everyone, Short Problem. Here is my config: - SQL Cluster Active/Passive - MSSQL 2005 SP2 - On the nodes: SQL engine, Worstation components - Windows 2003 SE SP2 Here is my problem: - When logged on the primary node (active one) I can browse..

Passwords for cluster and servers - I have a 2 node cluster running Win2000 enterprise and MS clustering. Also SQL server. Would there be a problem using the same domain password for SQL and for the clustering service? I thought I read that there may be a problem but I don't recall where...

System DSN for mirrored servers - Hello! I've set up an HA environment for a customer. That includes two IIS-servers, with Network Load Balancing between them, and two SQL 2005 Standard with mirroring and one SQL 2005 Express as witness. For the webpages I read that I just have to ad...

Maximize memory usage on active-active sql cluster - we have an active-active sql cluster configured as follow: server A - 4gb ram - sql server instance #1 server B - 4gb ram - sql server instance #2 currently each sql instance is configured to use at most 2gb of ram. in case of failover, both instances..

SQL Clustering Options - I have read that SQL Server with MSCS supports an Active/Active setup via a NAS, however, DOES NOT support and Active/Active setup via a SAN. Can anyone shed light on this? Any support documentation that would help would be great! Thank you.

	Database Help (Home) -> Clustering	All times are: Pacific Time (US & Canada)
Page 1 of 1

You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum