I have two Windows servers , one 2008 SBS the other one 2003. I have a SQL database on one of them and want to keep a slave copy of that database on the other (for lets say the unlikely case that a 100 year hurricane wipes out the office with the server).
I have a second instance of the DB based application on the second server. At this time, if the main box gets wiped out, I would have to restore the DB from a backup and move the license for the application to the second box (couple of phonecalls/emails). Rather than doing that, I would like to keep a current copy of the DB on the failover server at a separate location (same domain, same network hooked together via ipsec tunnels). It would save me the restoring from backup step and allow staff to work via remote desktops etc.
Two ways I imagine I can do this:
- somehow make SQL write every change to a replica of the database
- use DFS to create a mirror of a folder with the SQL database
Anyone have some good pointers for doing one vs. the other and how to go about this.
(and no, I can't move all of this to an apple or Linux server)
I have a second instance of the DB based application on the second server. At this time, if the main box gets wiped out, I would have to restore the DB from a backup and move the license for the application to the second box (couple of phonecalls/emails). Rather than doing that, I would like to keep a current copy of the DB on the failover server at a separate location (same domain, same network hooked together via ipsec tunnels). It would save me the restoring from backup step and allow staff to work via remote desktops etc.
Two ways I imagine I can do this:
- somehow make SQL write every change to a replica of the database
- use DFS to create a mirror of a folder with the SQL database
Anyone have some good pointers for doing one vs. the other and how to go about this.
(and no, I can't move all of this to an apple or Linux server)