Business continuity planning sucks. You have to think of all the things that can go wrong that can interrupt your business and then design strategies to mitigate them in advance. It's a lot of important work, and if you're  lucky, it will be mostly wasted effort.

But every team still needs a disaster recovery plan. Regulation such as Sarbanes-Oxley may require thorough business continuity plans. Or it may be a demanding business environment that demands results even when your file server is dead.

For some processes, just backing up the data is enough. Keeping a nightly offsite backup of the HR database is probably okay, since HR data is fairly static from day to day in most companies.

But your team's code is different. Code is a living artifact that changes throughout every day. So if you're making daily offsite backups, that's probably not good enough in case of a disaster. Recovering from offsite backup may take hours/days, and even then the backup is going to be missing revisions so you'll have to waste time re-adding old revisions. Your code needs a more active recovery strategy.

ProjectLocker's disaster recovery can help by keeping a secure up-to-date replica of your in-house code repository. In case of a disaster with the main repository, just tell your team to point at the ProjectLocker repository. Voila: they're back to work! Even if the office is flooded and the offsite backups haven't been reloaded yet.

Click here to learn more about disaster recovery for your code:

Bonus: check out this overview I wrote last year about disaster recovery for Subversion.