Skip to main content
  • EN

hello, thanks, i am running out of space on a linux server that i use for backup copy jobs.

i am not sure the ways to free space without creating a nightmare…

by way of example, this is the setting for a backup copy job

what would happen if i changed the retention policy from 30 days to 7 days?
not sure i really need 30 days, as this is in addition to the main backup policy
i would assume that veeam will not delete the older .vib files from day 8 to 30, correct?

so i think i need to manually prune those older .vib files?
but not wanting to affect veeam ability about keeping certain full backups longer for archival purposes.

please, any advise at all about that setup or if any additional information is needed?

thanks, david

If you change the policy it should run the retention to remove old backup chains to free space.

You can also use an S3 backup repo as part of SOBR to allow you to maintain archives in the capacity tier to free up performance tier space.

You can also use an S3 backup repo as part of SOBR to allow you to maintain archives in the capacity tier to free up performance tier space.

That is also a good option if those older restore points are required to be kept.  Good catch!

Hi @asdffdsa6132 

 

The above answer is very helpful from the legends but I added some a little bit feedback from my end.

 

As per my bit experience I have solved a few issues in my environment by using the Veeam calculator and calculating the size in multiple ways but you can calculate your backup size using the below Veeam calculator and even you can build your scenarios as well.

Try this and keep us posted.

https://www.veeam.com/calculators

Another thing to consider: is your Linux repository build as a hardened repository and so with XFS? Then it would be a bit tricky to get rid of unwanted restore points. 

but besides Hardened/Immutable functions, I would recommend to use it, for FastClone/BlockClone functions, to safe a lot of space! 
 

the picture is only an example, right? I don’t know your environment, but 1TB is normally not a good capacity for a repository. 
 

 

 

Comment


Terms & Conditions