Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hot to mirror a SQL server

Status
Not open for further replies.

dpsmith

IS-IT--Management
Feb 4, 2002
74
US
Hello. SQL newbie here asked to find out if we can do this.
Company has SQL2K server linked to webserver via IP#.
Must be up 24/7. This is mission critical.
Big-guys concerned about server crash.
Not concerned about data loss though (we have that covered up the ying-yang!) but rather down-time.
A reinstall and restore taking several hours is not an option. Company employees and outside customers must have access to SQL server.
Can we buy second SQL server and have the data coming in from the Webserver mirrored so that if one server crashes our customers and employees never notice?
Is this possible?
I have a few SQl books.
What is the procedure I'm looking for called?
Not luck with the term mirroring.
TIA.

DSmith
 
SQL Clustering (Active/Passive) would be the fastest way to garuntee uptime. In a SQL Cluster if the active node goes offline for some reason then the passive node would come almost seemlessly. The bonus to clustering as that you wouldn't have to change any configs on your web site to have the change take effect.

Another alternative would be replication. Where you copy your database to a second server, and through Publishing and subscription you would keep the 2 servers in synch. THe downfall to this is that if your primary server went offline you would have to change your configs to point at the backup.

Licensing would also be a factor. In active passive you only license the active node whereas the replication way you would have to have full licenses on both servers.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck
 
Another solution is Log Shipping.
This consists of 3 automated steps:
1. Backup of Source DB.
2. Copy of Backup file to Destination Server.
3. Restore of DB to Destination Server.
(we do this at 15 minutes intervals)

This allows you to have a (there and there abouts) a copy of the Database on another machine.

So in case of server crash, either re-name the destination server(change IP too) OR Point the clients to the new machine and away you go.

I use this, its simple and it works very well.
TK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top