• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 272
  • Last Modified:

Planning - Good method for Quick recovery of MS server 2008 with SQL database in event of total server failure?

I have a local MS 2008 server running a SQL database.  It is running RAID 5 with SAS drives.  I have machinery that is dependent on this server to have high availability.  If this server has a total melt down (failed motherboard, lightening strike, flooding, etc) after 2 or 3 hours it will start costing me $1,000 + per hour in lost productivity.  I have another building that can house a 2nd server within 200 feet and can connect it together with Ethernet cable or fiber and house a 2nd server.  Our internet connection is slow DSL.  What are some solutions please? (mirrored servers or ???)  All information and detail is appreciated.
0
lew_stoner
Asked:
lew_stoner
4 Solutions
 
Aneesh RetnakaranDatabase AdministratorCommented:
depending on the sql server edition, you can go for Mirroring or log shipping. Never tried Mirroring over a slow network.
If the servers are on the same network, mirroring could do it. Otherwise, setup logshipping.
I assume, all your users access the database thru lan.
0
 
lew_stonerAuthor Commented:
SQL 2008 R2.  Users access database through LAN.  To mirror servers over 10/100/1000 network how is that setup?  Identical servers on the network then some kind of software that does mirroring or ???
0
 
Scott PletcherSenior DBACommented:
Make sure, too, that existing users automatically go to the new server or have an easy way to access the new server in the event the old one fails.  It would be extremely frustrating to have perfect cloning of data and not be able to actually use it!

How much data loss can you afford?  2 hrs?  1 hr?  15 min?  None?   In general, the less time, the more it will cost :-).
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
lew_stonerAuthor Commented:
We can actually afford to lose 1 day of data and we do backup our database nightly.  But if we had to do a complete restore it would be very time consuming and right now we don't have a 2nd server.  So....if something happened today we would order a server, wait for it to arrive and do a bare metal restore - very time consuming.  The lose of data is not the big issue, the bigger issue is the manufacturing machines that receive jobs from the server.  After about 2 hours of down time it starts costing us a lot of $$$$ because we have to shut down manufacturing.  Hope that helps and if you have specific recommendations/solutions please let me know.  If I can provide more information please ask questions.
0
 
Scott PletcherSenior DBACommented:
I'd recommend log shipping.  You can use the built-in SQL log shipping, or you could start with a version of your own.
0
 
lew_stonerAuthor Commented:
So....purchase another computer identical to the one in use or could this be done with a virtual server?  Then nightly do SQL log shipping?  Am I on the right path???  Would I need to purchase another server license and SQL license?
0
 
Scott PletcherSenior DBACommented:
You should be able to use a virtual instance if you want.


>> Would I need to purchase another server license and SQL license? <<
I don't believe so, but licensing has gotten so complex I wouldn't say for sure.  Hopefully someone else has more expertise in licensing matters.
0
 
Casey WeaverNetwork EngineerCommented:
If you're continuing to use SQL 2008, you do not need a license. The server can mirror or log ship without another license indefinitely. In the event of a failover, you are not permitted to use the backup server for more than 30 days in production without a license. 30 days, however, is usually more than enough time to get the primary back online (whether through repair or replacement).
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Casey is right about the licensing. For backups server you won't need an extra license if the server is shutted down. You are allowed to turn on the server for patching purposes only.
Another solution is to create a cluster with the 2nd server so you'll always need a single MSSQL license but two licenses of Windows Server. In the case of one of the servers fails a fail over will occur. For this solution you'll need a NAS solution also. It all depends on the money.
0
 
lew_stonerAuthor Commented:
Thanks for all your input, very helpful!  Lew
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now