Backup strategy advice?

[rct]

Hello,

I have backup jobs running (incremental + weekly synthetic + rollbacks) and I used to store off-site a monthly backup (by manually copying the vbk to a disk) but today the synthetic take too long so I was thinking of doing a forever incremental instead to distribute the synthetic transformation over the week.
The problem is that if I do so I won't have the vbk "on time" because of our 45 backups retention.

Does someone have any advise or solution for my problem?

Thank you
Romain

[foggy]

Have you looked at using the backup copy jobs for that purpose?

[rct]

Thanks for your answer foggy.

Yes avec looked at this but the problem is that we do the copy directly to an eSATA disk (which is nearly full by just copying the vbk) and, correct me if I'm wrong, the backup copy job will need more space.

May be I could set up a repo with enough space for the backup copy job and then copy the monthly full backup but I'm not sure to really understand how to plan the required space for that repo and how to setup the backup copy job.

If I want to do that and use as little space as possible will I need to setup the job with:
- restore points to keep: n (>2)
- Keep 0 weekly backup
- Keep 1 monthly backup
- Keep 0 quaterly backup
- Keep 0 yearly backup
And I will have 2 full backups and n-2 incremental stored on the repository.
I will have one month to copy the monthly backup to disk.

Is that right?

[foggy]

I'd just setup a rotated drive enabled repository, create a backup copy job with 30 days interval, and enable repository cleanup. Here's another topic discussing similar setup. In this case you would need space just for a single full backup.

However keep in mind space requirements increase with time.