garychu
asked on
Preparing a standby MSSQL 2000 Server computer
In a Windows SBS 2003 domain, there is a member server, configured with MSSQL Server 2000 in support of a mission critical ERP application. Routinely, the application database is backuped via an Enterprise Manager maintenance plan. Additionally, the master, model and msdb databases are also backuped at the same time.
I am planning to prepare a standby server and would appreciate some ideas and suggestions from experienced quarters. Specifically,
- The standby server computer is of a different hardware configuration - consequently, restoring from an image backup is of limited use.
- Instead, I plan to have MSSQL and the ERP application installed fresh on the standby server, and
- Ready for the most recent database backup available to be restored in a disaster recovery situation.
- Will MSSQL 2000 server configuration be fully restored from just the master, model and msdb databases, in addition to the application database?
- Given the above scenario, are there any other considerations? And gotchas that I should be aware of?
As you can see, it would be weight off my mind once I have got a standby server ready to spring into action, should the need ever arises. Thanks
I am planning to prepare a standby server and would appreciate some ideas and suggestions from experienced quarters. Specifically,
- The standby server computer is of a different hardware configuration - consequently, restoring from an image backup is of limited use.
- Instead, I plan to have MSSQL and the ERP application installed fresh on the standby server, and
- Ready for the most recent database backup available to be restored in a disaster recovery situation.
- Will MSSQL 2000 server configuration be fully restored from just the master, model and msdb databases, in addition to the application database?
- Given the above scenario, are there any other considerations? And gotchas that I should be aware of?
As you can see, it would be weight off my mind once I have got a standby server ready to spring into action, should the need ever arises. Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
And considerations that I will most definitely take onboard.
Meanwhile, can you help me on;
1. It is too costly to configure a standy server with close enough grunt to the production server, to be acceptable to management. I suppose it would be okay to agree on a limited (much smaller than normal) number of key users and period of time the standy server will be used. The time it takes for the production server to be replaced. You think this will be okay?
2. I have not thought about the transaction logs. Will the transaction logs be backuped as well in a Full Backup scenario? Presently, backup time is not a key consideration. 24 hour old backup is acceptable to management.
3. Script apllication databases - what is meant by this?
Your continued feedback and suggestions would be very much appreciated. Thanks again.