Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Recently our web-server crashed and we had to recover everything from a backup which took the whole day(totally unacceptable in our business).

So my question is, how can I create a complete mirror of the server that I can use (switch dns to) in case the same disaster happens in the future?

Our main server is on Amazon with Windows 2008/IIS + Postgresql 9.1. I was thinking on creating the same server on a different location as a complete mirror with the database replication. But I'm not sure how to implement IIS instance mirroring over the internet...

So my question is, how can I create a complete mirror of the server that I can use (switch dns to) in case the same disaster happens in the future?

share|improve this question

1 Answer 1

Although Postgresql has a large number of replication options, if I understand your problem right, it is more about fundamental stability of operating systems and server applications, IIS & Postgres.

There is a similar answer provided for Amazon EC2 http://stackoverflow.com/questions/6940265/deploying-a-high-availability-postresql-9-0-on-amazon-ec2-with-pgpool-ii

Personally, I'd be more partial to a VMware solution using something like the following:

circuit diversity / ISP diversity
VMs with HA & FT configuration
Assumes no single point of failure in above.

The VMs should use the same DNS information if a FT event occurs.

You can expand this via F5 load balancers and duplicate sites if needed.


VMware Fault Tolerance Datasheet http://www.vmware.com/files/pdf/VMware-Fault-Tolerance-FT-DS-EN.pdf

VMware / F5 http://www.vmware.com/files/pdf/partners/desktop/f5-for-virtualized-it-environments.pdf

share|improve this answer
Thank you for your answer. The problem is that I won't be able to implement VM approach since my mirror server would be on our local hosting facility. So, the main server is on the West Coast and the mirror would be on the East Coast. –  Timka Jun 25 '12 at 0:44
You can have either both DBs at the same location, or 3 DBs, lets say West Coast A, B, and East Coast C? The DB location can be independent of the VM locations, if VMs are needed. –  Brennan Jun 25 '12 at 13:25
Unfortunately, the requirement was to keep it simple - 2 servers, syncing the data between the master server and the slave along with the db replication –  Timka Jun 26 '12 at 1:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.