 | |
Clustered SQL servers in DR Hotsite
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#91
 
| |||
| |||
|
Re: Clustered SQL servers in DR Hotsite -
02-01-2008
, 12:35 PM
|
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" <ian__20 (AT) hotmail (DOT) com> wrote in message news:eqVeRNPZIHA.1532 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 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" <tom (AT) dont (DOT) spam.me.cips.ca> wrote in message news:e%23iyB2OZIHA.1532 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 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" <ian__20 (AT) hotmail (DOT) com> wrote in message news:e50Z9vOZIHA.4180 (AT) TK2MSFTNGP06 (DOT) phx.gbl... 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" <tom (AT) dont (DOT) spam.me.cips.ca> wrote in message news:%23LY9cgDZIHA.4208 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 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" <someone (AT) microsoft (DOT) com> wrote in message news:epY7QPDZIHA.4896 (AT) TK2MSFTNGP06 (DOT) phx.gbl... 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" <tom (AT) dont (DOT) spam.me.cips.ca> wrote in message news:ODNaSTBZIHA.5896 (AT) TK2MSFTNGP02 (DOT) phx.gbl... 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" <someone (AT) microsoft (DOT) com> wrote in message news:O5skCKBZIHA.220 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 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 |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.