-
- Veeam Software
- Posts: 856
- Liked: 154 times
- Joined: Feb 16, 2012 7:35 am
- Full Name: Rasmus Haslund
- Location: Denmark
- Contact:
Default Backup Mode changed in clean v8 U2?
I just deployed a new v8 install and immediately installed Update 2 before even launching v8.
I then started to create a new backup job and noticed that the job had backup mode set to: Incremental with both Synthetic Full _AND_ Active Full enabled.
I expected it to be Incremental Forever (no synthetic full and no active full).
Has there been a change?
I then started to create a new backup job and noticed that the job had backup mode set to: Incremental with both Synthetic Full _AND_ Active Full enabled.
I expected it to be Incremental Forever (no synthetic full and no active full).
Has there been a change?
Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
Yes, default behavior for clean installations has changed in this update.
However, intention was to make just forward incremental with synthetic full the new default, active full is enabled by mistake (the re-uploaded Update 2 will address this). You can disable active full and save the job settings as the new default, so that new jobs have correct default settings.
However, intention was to make just forward incremental with synthetic full the new default, active full is enabled by mistake (the re-uploaded Update 2 will address this). You can disable active full and save the job settings as the new default, so that new jobs have correct default settings.
-
- Veeam Software
- Posts: 856
- Liked: 154 times
- Joined: Feb 16, 2012 7:35 am
- Full Name: Rasmus Haslund
- Location: Denmark
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
Interesting.
What do you mean re-uploaded Update 2? When will the Update 2 with this fixed be available? FYI I downloaded Update 2 earlier today.
What was the reason for this change from Forever Forward Incremental to Forward Incremental with Synthetic Fulls?
Thanks!
What do you mean re-uploaded Update 2? When will the Update 2 with this fixed be available? FYI I downloaded Update 2 earlier today.
What was the reason for this change from Forever Forward Incremental to Forward Incremental with Synthetic Fulls?
Thanks!
Rasmus Haslund | Twitter: @haslund | Blog: https://rasmushaslund.com
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
You mean the update 2 of the update 2 ?
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
Nope, just re-uploaded image of Update 2 with the one of the changes being fix for the said issue (active full enabled as default). Thanks.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Nov 28, 2014 3:56 pm
- Full Name: Mario Mack
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
Hi Foggy,foggy wrote:Yes, default behavior for clean installations has changed in this update.
However, intention was to make just forward incremental with synthetic full the new default, active full is enabled by mistake (the re-uploaded Update 2 will address this). You can disable active full and save the job settings as the new default, so that new jobs have correct default settings.
can you tell us why the default mode has changed back to forward incremental with synthetic full instead of forever forward incremental?
Regards,
Mario
-
- Chief Product Officer
- Posts: 31803
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Default Backup Mode changed in clean v8 U2?
Per our support org request. Apparently we have way too many users with huge multi-TB drives backup repositories having poor IOPS capacity. They have basically flooded our support due to having performance issues with transform, and most didn't even need to use the new mode due to having enough capacity for multiple fulls.
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 111 guests