If you run a company where your major interaction with your customers is through a website interface, then it would serve you well if you were mirroring that website in a secondary location, whereby customers trying to resolve the DNS of one server, can be redirected to another. In case you cluster the application so that you are able to make that switch. Clustering will also help you to reroute your data through an alternate node should an unplanned incident happen on the node outside your organizational premises. This is something which helps you to become more fault tolerant regardless of the fact that the solution you might be running isn't a high availability solution. So if PTCL gets a cable fault, at least you can still be running your operation.

It is also important to have role-based recovery in place, rather than specify one, single individual who will be responsible for a specific task in the time when the crisis is hot. Different people react differently in the time of crisis and you don't want to have to put someone in a place he or she can't handle. Rather, put the position or job description to manage the recovery.

Here are some of the standard backup measures which you may want to keep in mind:

-- Backups made to tape or high capacity, highly available media and sent off-site at regular intervals (preferably daily)

-- Backups made to disk on-site and automatically copied to off-site disk, or made directly to off-site disk