"Backup" is not a component of revision control software. If one has such 'backup functions' they're just window dressing.

What you must be talking about (well, I hope anyway) is the capability of a revision control system to be backed up on the fly, similar to the tools used to backup a live subversion repo without causing corruption. Git has such functionality; simply do a fetch from a remote repo, then backup the result.

If you're expecting revision control systems to include some sort of "backup suite", sorry, this is *NIX, not Microsoft. The tools do a particular job and it's up to you to plug that into your infrastructure, including your pre-existing backup infrastructure, which i'm sure your company must have. It would be laughable if they didn't have backup infrastructure already.

I've seen a company with contracts guaranteeing 100% uptime, while running things off of a single MS server with no backups. It's entirely possible for software companies to be this stupid.

> It's like a RAID-5 where you have to tell it to rebuild a new disk.

Well, you do have to give it a new disk first, right? Or do you expect the RAID-5 array to automate the process of purchasing and installing a replacement disk?