Scale-out Repository not working as it should - 00464187

VMware specific discussions

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby SyNtAxx » Wed Feb 17, 2016 4:16 pm

any updates?
SyNtAxx
Expert
 
Posts: 127
Liked: 14 times
Joined: Fri Jan 02, 2015 7:12 pm

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby Vitaliy S. » Wed Feb 17, 2016 5:00 pm

QA team is verifying it. Our support team will notify you once it is available!
Vitaliy S.
Veeam Software
 
Posts: 19546
Liked: 1100 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby prabhash.jena » Fri Feb 19, 2016 10:53 am

Gostev wrote:Thanks! You can also refer them to issue ID 69045 as there is a chance this may be the same issue. The hot fix for 69045 is currently with QC for validation.


Thanks! I have shared the information with support.

My current situation is like this after I made manual changes to get the backups to work.
Extent1 – 50 TB Free space – 13 TB
Extent2 – 23 TB Free space – 02 TB
Extent3 – 20 TB Free space – 03 TB

Now the question is, when Extent2 or 3 becomes full will SOBR automatically redirects backup data to Extent1?
The extents are CIFS shares on 2 node Microsoft Scale-out File clusters.
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby foggy » Fri Feb 19, 2016 10:58 am

Yes, data will be placed on extent where enough space is available.
foggy
Veeam Software
 
Posts: 14728
Liked: 1078 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby Gostev » Fri Feb 19, 2016 11:48 pm

Vitaliy S. wrote:QA team is verifying it.

And they've been doing a really good job as emails from builder told me this hot fix was rebuilt 3 times already ;)
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby prabhash.jena » Mon Feb 29, 2016 9:34 pm 1 person likes this post

Gostev wrote:Thanks! You can also refer them to issue ID 69045 as there is a chance this may be the same issue. The hot fix for 69045 is currently with QC for validation.


I provided the information to the support team. After few days I was provided with a fix. I have applied the fix.
It will be a week or so before I can conclude that the jobs are being redirected to another extent in case one of the extent goes full and runs out of space.
Thanks for your inputs :)

Prabhash
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby SyNtAxx » Mon Mar 14, 2016 9:19 pm

I seem to be running into the issue again, repo has 21TB free. The hotfix was applied a few weeks back.

-Nick

-
SyNtAxx
Expert
 
Posts: 127
Liked: 14 times
Joined: Fri Jan 02, 2015 7:12 pm

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby Gostev » Mon Mar 14, 2016 10:23 pm

At this time you should just get Update 1 from support, as it fixes all the related issues.
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby prabhash.jena » Thu Oct 06, 2016 12:32 pm

Hi Gostev,

I can confirm the scale out repository doesn't work as intended by Veeam atleast in my case. I experienced the same issue where 1 extent got full and the job failed instead of redirecting it to another extent which had more than 20TB free space.
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby foggy » Thu Oct 06, 2016 12:33 pm

Do you have Update 2 installed?
foggy
Veeam Software
 
Posts: 14728
Liked: 1078 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby prabhash.jena » Thu Oct 06, 2016 1:38 pm

Yes. 9.0.0.1715. I am kind of early bird with application & system updates.
prabhash.jena
Enthusiast
 
Posts: 35
Liked: 2 times
Joined: Fri Jan 16, 2015 1:32 pm
Full Name: Prabhash Kumar Jena

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby foggy » Thu Oct 06, 2016 1:40 pm

Then involving support is recommended to investigate the reasons of this behavior.
foggy
Veeam Software
 
Posts: 14728
Liked: 1078 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby pirx » Sat Feb 04, 2017 9:46 am

Running 9.5U1 here and see the same problems.

Error: No scale-out repository extents have sufficient disk space to store the backup file.

There are 58TB of 100TB free. Seems that SOBR is not working as expected at all.
pirx
Enthusiast
 
Posts: 69
Liked: 7 times
Joined: Sun Dec 20, 2015 6:24 pm

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby Gostev » Sat Feb 04, 2017 5:40 pm

@Pirx what is the support case ID for this? All known issues around SOBR have been fixed in 9.5, so this must be something different.
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Scale-out Repository not working as it should - 00464187

Veeam Logoby pirx » Mon Feb 06, 2017 9:22 am

#02059754

Code: Select all
Please note that we try to allocate the space on the extents at the very beginning of the job. The space is allocated according to the following criteria : full backup - 50% of the VM size, increment - 10%. Sure it could be plenty of free space but once all the jobs are started at the same time, it is possible that all the space is allocated and that's why all the jobs will fail. For such kind of situations we recommend two registry keys that will reduce the percentage of the space allocation : Name: SOBRFullCompressRate Type: REG_DWORD Value: 25 Name: SOBRIncrementCompressRate Type: REG_DWORD Value: 5 Both keys should be added at the veeam server in HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\ Please add both keys, restart the jobs and let me know about the results


All full jobs are finished now, we started them one after the other. I'll see if I can reproduce this with the given regkey settings. We use 14 primary restore points on this repository, but the backup copy repositories are SOBR too, so we should see the same effect (maybe later because our copy SOBR's are bigger because they must hold backups for 10 weeks).
pirx
Enthusiast
 
Posts: 69
Liked: 7 times
Joined: Sun Dec 20, 2015 6:24 pm

PreviousNext

Return to VMware vSphere



Who is online

Users browsing this forum: EricB, ilya.konopak and 37 guests