Attempo Live Backup makes life miserable for developers.

Our company has had to switch from TSM to Attempo's Live Backup. It's wreaking havoc on developer productivity.

Builds, of which developers do dozens each day, delete and recreate thousands of files over the period of about 5 minutes. The backup system sees all of this disk activity and thinks "Oh boy, better get started caching changes and streaming them to the backup server!" Never mind the fact that those 150,000 class files are a compiler artifact and can be reproduced at will by running javac after checking out the appropriate source code from subversion--another backup system.

So what's a developer to do? Spend an hour configuring Attempo to ignore class files, war files, jar files, zip files, etc. The biggest bang for the buck I got was telling Attempo to ignore the many dozen "target" directories in my build tree, which is where most of the action takes place. It takes an hour to do this because you have to add the directories one by one. It would be really great if Attempo could use regexes for client side exclude directories and files.

Doing all of this configuration of Attempo greatly sped up my builds.