Hi there,
Please explain to me if I opted not to run periodic fulls or synthetic fulls for a backup job, what are the effects and what does that mean for the restore process exactly? and if I had to decide to run synthetic fulls what would my calculations need to be if I had to scope storage capacity?
-
- Enthusiast
- Posts: 55
- Liked: never
- Joined: Oct 23, 2019 3:08 pm
- Full Name: Jaques Coetsee
- Contact:
-
- Product Manager
- Posts: 2584
- Liked: 710 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Not running periodic fulls or synthetic fulls?
Hi Jaques,
In this case your Backup Job will have Forever-Forward Incremental backup mode, having a Single Full backup followed by a chain of incremental backups. This chain type takes less load on repository to be created(good for slow storage case), however since it has only 1 Full, all chain increments are linked to it. So in case of Full backup corruption, entire chain will lose it's consistency. Also it is not recommended to go above 30 days Retention with such chain.
You can calculate approximate Backup Repository storage requirement using Restore Points Simulator.
Thanks!
In this case your Backup Job will have Forever-Forward Incremental backup mode, having a Single Full backup followed by a chain of incremental backups. This chain type takes less load on repository to be created(good for slow storage case), however since it has only 1 Full, all chain increments are linked to it. So in case of Full backup corruption, entire chain will lose it's consistency. Also it is not recommended to go above 30 days Retention with such chain.
You can calculate approximate Backup Repository storage requirement using Restore Points Simulator.
Thanks!
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 34 guests