It seems like we never have enough time to get everything done that we need to do during our time off. Before you know it, the weekend’s over and there’s still items left on our ‘to-do’ list. That’s certainly the way it is for enterprise backups. If you’re a backup administrator, you know the routine too well. Full and incremental backups take an enormous amount of time. They also consume a lot of resources and bandwidth. Because of their negative impact on production environments, we schedule backup jobs during off-peak hours. The problem is that window just never seems to be quite long enough and with burgeoning data repositories and an expanding application portfolio, that window seems to only get smaller. Face it, scheduling backups in the hope they complete in time without interfering with one another is stressful. Administrators can only hope the last backup job completes before users begin to trickle in Monday morning. If not, users will be competing with those same backup jobs for network bandwidth and server utilization resources and the help desk phones begin to ring.