To be really clear, we have two situations:

1. Our S3 bucket fills up with objects.
2. We want a full backup to be performed every two incremental runs, so we can keep the S3 bucket in check.

@olivierlambert One of the questions I had in the post was also that we need to solve the problem of purging information older than 2 months and that the jobs we have as incremental backup can be configured to be full every 2 incrementals so we don't save infinite information in S3.

This is a standard configuration that we have with the jobs.

We probably have an error in the job configuration that causes S3 to fill up with objects and we don't get the results we expect with the backups and their debugging.

@olivierlambert The idea is that by putting two S3 repositories together you distribute the copies and don't duplicate them.

Hi,
I have a backup job that uses two S3 repository.

We're having trouble with the fact that instead of distributing executions between both repositories, it's making copies in both. Is there a way to distribute the load between repositories without duplicating them?

On the other hand, we want to make it do a full backup from an incremental backup job every 2 executions and only save the last 4 backups so as not to use more space.

Thanks.