Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
nhuanlieu
Starting Member
27 Posts |
 Posted - 2009-06-18 : 13:14:34
|
| Hello, we are using SQL Server 2005 and are thinking about an option where we have 1 DR (Disaster Recovery) SQL box to host 3 PROD servers whenever DR strikes. Having a 1:1 ratio would be nice, but is only a remote chance due to budget constraints.The capacity of the DR is exactly the same of the 3 PROD with the exception of the disk space, where it can host all combined volume of the 3 PROD dbs. Obviously, the performance will be a big hit, but management thought process is at least it gets us up and running.Wonder what other gotchas do we need to be aware for a 1:M DR SQL setup compares to a 1:1 DR setup? Below are the obvious one:* Consolidations of logins, jobs, operators, etc. -- we probably have to designate 1 master for msdb, logins, alerts among the 3 and manually scripts in the other 2 set daily? Thanks. |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2009-06-18 : 15:19:14
|
| you should have the entire end to end list of al lthe tasks you (or a DBA ) should be performing in case of a disaster.. the checklist should be comprehensive including what steps you need to do to bring the prod offline until you bring it back online on the DR site.. check if you have any duplicate objects - logins, dtaabases etc from different db's that might cause issues.. etc and finally... practice the entire exercise and perfect the checklist with each practice... its best to have scheduled downtimes on a frequent basis (may be once every 2 months) to have this practice run so you are as much prepared as you can in the real event of a disaster..Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
|
|
|
1:1 vs. 1:M Disaster Recovery SQL setup