We have a production SQL 2000 Server and we want to build
an offline-recovery server where we can install
applications, restore databases, and test client
connectivity. I would build this server exactly like our
production server, restore the msdb, model databases,
etc. Would I be better off having this server on a test
lan seperate from my production server, or can I have
both these servers(different names and IPs or course)on
the same network. What would be a better way of
introducing this recovery server, and is this even
possible?
Thanks,
Alex
Hi Alex,
You can have Two separate SQL Servers on the network.
If you are using SQL Server 2000 Enterprise Edition, then you can use the
Log Shipping Feature of the SQL Server to create a Warm Backup. This backup
Server can be used for reports. The users would have read only access to
the Warm Standby Server.
Please refer to the following white paper that has steps to setup Log
Shipping and steps to convert a standby server to a production server, in
case the Production server crashes.
http://support.microsoft.com/default...l%2fcontent%2f
2000papers%2fLogShippingFinal.asp
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, February 12, 2012
Building a Recovery/Test SQL Server
Labels:
buildan,
building,
database,
databases,
installapplications,
microsoft,
mysql,
offline-recovery,
oracle,
production,
recovery,
restore,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment