We've talked about this before and it is something that we think we want to do. There are some problems though that don't make the situation as ideal as it sounds. For example you cannot backup data to S3. You can only send your backup files there after you have taken a backup. If we wanted to do this we would need to have a separate subcommand in cbbackupmgr that you would run after a backup which would store a specific backup files in s3 and record the fact that your backup was no longer in the local repository. If you did a restore or a merge we would also need to be able to download the backups needed before actually running the commands.
Improvement
Major
We've talked about this before and it is something that we think we want to do. There are some problems though that don't make the situation as ideal as it sounds. For example you cannot backup data to S3. You can only send your backup files there after you have taken a backup. If we wanted to do this we would need to have a separate subcommand in cbbackupmgr that you would run after a backup which would store a specific backup files in s3 and record the fact that your backup was no longer in the local repository. If you did a restore or a merge we would also need to be able to download the backups needed before actually running the commands.