Warm Standby Server

Experts,
I have a SQL 2005 database server which has about 20 user databases which  total upto 1 TB.We have nightly backups and they go onto the tape eventually everyday.
In case this server crashes what are my options beside restoring from the backups.
someone mentioned Warm Standby Server, is it a feasible solution? pros and cons? basically we want to reduce the down time.

please suggest
regards

crishna1Asked:
Who is Participating?
 
RiteshShahCommented:
You could go for high availability concept of SQL Server like Mirroring, Replication, clustering, log shipping etc.
0
 
RiteshShahCommented:
you can maintain warm stand by server with Log Shipping, which is not a bad idea. have a look at below URL

http://www.aldex.co.uk/continuity.html

http://www.experts-exchange.com/Database/Sybase/Q_23979216.html
0
 
chapmandewCommented:
log shipping is the way to go here, database mirroring would also work if you have the correct server version.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
crishna1Author Commented:
Thanks for the updates.

I have a sql server 2005 database server, machine A(primary dbserver), with 20 databases on it. I have hardware available for another SQL Server 2005. What do i do from here?  
1) intall SQL Server 2005 on machine B (which would be standby server)
 and then what are the steps to do..? i am guessing
2) backup the 20 databases  from Server A
3) restore them on Server B

4) how do i transport the transaction log from server A to B?
Can this be automated, if so how? can i set it to happen every hour?
 or what  is the optimal way of doing it?

regards...
0
 
chapmandewCommented:
Log shipping is an automated process....follow this wizard.

http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1309728,00.html
0
 
crishna1Author Commented:
it has been decided to go with clustering, can you point me with some good notes for SQL Server 2005 clustering? is there a sstep by step setup?
0
 
crishna1Author Commented:
i guess so. Thanks for the updates. i just created a second instance on sql server 2005 and having issue connection. i verified that the "allow remote connections" is checked . i believe something is wrong with the TCP/IP port. i played with SQL Configuration Manager and messed it up. how do i fix it? the first instance is working fine and it is listening on port 1433. The error log for the named isntance is showing , port 3000 and 3831, what do i have to do?
0
 
chapmandewCommented:
new question....this is nothing related to your current question.  please close this question out and submit a new one.
0
 
RiteshShahCommented:
yeah, me either aggree with Chapman.
0
 
RiteshShahCommented:
as about original question of Warm Standby server, we have given answer in first three post itself.
0
 
crishna1Author Commented:
chapmandew, you mentioned clustering involves quite a bit of money, approx how much u think?
0
 
RiteshShahCommented:
well it needs some special server and special kind of expertise, it depends on what servers and expert you choose
0
 
chapmandewCommented:
it will require specialized hardware, and maintenance....you're probably talking several hundred thousand to do it correctly and robustly.
0
 
crishna1Author Commented:
even just for failover clustering? Active/Passive?
0
 
chapmandewCommented:
Yep...the licenses aren't whats going to cost you the most in active/passive...its the hardware that you have to pay for that will basically be sitting idle when you're on one node.  Its not a cheap solution...a good one, YES...a cheap one to do right, no.
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.

All Courses

From novice to tech pro — start learning today.