-
- Expert
- Posts: 101
- Liked: 4 times
- Joined: Aug 28, 2014 12:16 pm
- Contact:
Re: Offsite Incremental to Synthetic Full Utility
Folks, is this be a topic for a feature request ?
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Offsite Incremental to Synthetic Full Utility
Yes, we keep all the related requests in this thread.
-
- Influencer
- Posts: 13
- Liked: 2 times
- Joined: Aug 29, 2019 2:22 pm
- Full Name: Yavor I
- Contact:
[MERGED] Manual optimization and / or merge
Hello.
We have Veeam 4a.
Is there a way to run manual optimization or manual merge?
We have restrictions to run backups during the day, but the night is not enough. I need to find a way to split the optimization and merge processes from the backup.
Thank you
We have Veeam 4a.
Is there a way to run manual optimization or manual merge?
We have restrictions to run backups during the day, but the night is not enough. I need to find a way to split the optimization and merge processes from the backup.
Thank you
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
-
- Enthusiast
- Posts: 37
- Liked: 1 time
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
[MERGED] Storage Heath check / Synthetic Full as background job instead of inline?
The Backup Files Health Check operation is scheduled at the end of the configured jobs run.
The problem is that the Health Check operation can take a very long time (maybe full day) on larger jobs which then might disrupt the next scheduled job run.
Wouldn't it be better to let that operation run as a background job? Any fault found can be corrected at the next opportunity.
As it is today, all the backups in the same job miss the backup schedule if the job takes too long time to finish.
Synthetic full is even worse, it can take three full days to finish on the largest job (50TB, ReFS+Dedup) and on a weekly schedule that catastrophic long time.
During that time no incremental backups are running on the job.
The problem is that the Health Check operation can take a very long time (maybe full day) on larger jobs which then might disrupt the next scheduled job run.
Wouldn't it be better to let that operation run as a background job? Any fault found can be corrected at the next opportunity.
As it is today, all the backups in the same job miss the backup schedule if the job takes too long time to finish.
Synthetic full is even worse, it can take three full days to finish on the largest job (50TB, ReFS+Dedup) and on a weekly schedule that catastrophic long time.
During that time no incremental backups are running on the job.
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Offsite Incremental to Synthetic Full Utility
Hi Dejan, merging your request since it seems somewhat related to the ones discussed above. Btw, is your ReFS repository FastClone enabled?
Who is online
Users browsing this forum: Egor Yakovlev, harbinger, Mildur, Semrush [Bot] and 99 guests