Comprehensive data protection for all workloads
Post Reply
Louharle
Influencer
Posts: 24
Liked: never
Joined: Jan 20, 2010 5:30 pm
Full Name: Louis Harle
Contact:

Initiate Veeam Job cleanup manually

Post by Louharle »

Hello all - we are running in to an issue where we have a job that runs w/21 days retention and also runs an ACTIVE FULL once a week. This is causing disk space issues for us so I have modified the ACTIVE FULL to be monthly. My question is how can I force the job to clean up the outdated/un-needed ACTIVE FULLS that are still out there and wean it down to one? Thanks in advance. V10 FYI.
Egor Yakovlev
Product Manager
Posts: 2581
Liked: 708 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Initiate Veeam Job cleanup manually

Post by Egor Yakovlev »

Hi Louis,

- Daily Backup with Active Full weekly, Retention 21 = will yield a backup chain of 27 restore points with total of 4 Full backups and 23 increments before retention cleanup happens.
- Daily Backup with Active Full monthly, Retention 21 = will yield a backup chain of 52 restore points with total of 2 Full backups and 50 increments before retention cleanup happens.
I doubt it will be much of savings there by changing Weekly to Monthly full(trading 2 Fulls for cost of 27 additional increments).

In your case I would change backup chain type from classic Forward Incremental to Forever-Forward Incremental by disabling all periodic full backups(Synthetic\Active), ran a manual Active Full to start chain a fresh and enjoyed 1 Full + 20 increments rotated automatically on a daily basis. Is it possible to bear with lack of space for another week until we start clearing older chains?

/Cheers!
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 33 guests