hi support,
1- when the number of retention policy (restore point/day) exceeded, does Veeam proceed with removing backup file independently ? or leave them on storage till next backup (any backup job) to run in order to overwrite data ?
a scenario would be, keep data for 7 days for a backup job that runs once a month.
2- consider a VBR use local storage ntfs/Refs and using forward incremental with weekly synthetic or active full backup.
regarding the size of a full backup file, each full backup file will be independent or does it re-use existing block to save storage ?
i.e a VM size it 50GB, keeping two full backup file on storage would take 100GB or around 50GB + changes ?
Regards,
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 02, 2022 2:56 am
- Contact:
-
- Product Manager
- Posts: 14839
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: retention policy behavior
Hello,
1. backup jobs apply the retention. If it's about number of restore points: the number of restore points need to grow to apply retention (there is no date / time to delete with "number of restore points". That means a backup job has to run). If backup jobs do not exist anymore (backups are orphaned) then the software applies GFS retention in background (V11). In V12, that background retention also works for other orphaned backups with "daily" retention.
2. a full backup is independent. on REFS / XFS blocks are shared (fast clone) with synthetic fulls.
Best regards,
Hannes
1. backup jobs apply the retention. If it's about number of restore points: the number of restore points need to grow to apply retention (there is no date / time to delete with "number of restore points". That means a backup job has to run). If backup jobs do not exist anymore (backups are orphaned) then the software applies GFS retention in background (V11). In V12, that background retention also works for other orphaned backups with "daily" retention.
2. a full backup is independent. on REFS / XFS blocks are shared (fast clone) with synthetic fulls.
Best regards,
Hannes
-
- Novice
- Posts: 5
- Liked: never
- Joined: Oct 02, 2022 2:56 am
- Contact:
Re: retention policy behavior
Thanks Hann
regarding full backup size, are below statement correct?
NTFS:
synthetic full backup size is equal to the size of backup
active full backup size is equal to the size of backup
Refs/ xfs block:
synthetic full backup size is equal to the size of changes only
Active full backup size is equal to the size of backup
Regards
regarding full backup size, are below statement correct?
NTFS:
synthetic full backup size is equal to the size of backup
active full backup size is equal to the size of backup
Refs/ xfs block:
synthetic full backup size is equal to the size of changes only
Active full backup size is equal to the size of backup
Regards
-
- Product Manager
- Posts: 14839
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: retention policy behavior
Hello,
yes, correct.
Best regards,
Hannes
yes, correct.
Best regards,
Hannes
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 228 guests