B&R v9 oddities (maybe bugs)

Availability for the Always-On Enterprise

B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Tue Jan 12, 2016 11:00 pm 1 person likes this post

I've just upgraded from 8 to 9 and the upgrade itself was fine.

I then wanted combine two repos into a scale out repo but everytime I tried I got an error saying it couldn't access a folder on one of the repos. The folder was from an old backup job that had been removed and deleted a long while ago. I'm assuming this was associated with an orphan record in the database about that job that wasn't removed properly. I ended up completely removing that repo from B&R and re-adding it. After that I could build the scale out repo with it.

The other issue I've seen so far is that an Exchange job that was running perfectly fine in 8 gave me this error on one of the Exchange servers

"Error: BlobCall: Undefined function id: 54"

and failed. That's not one I've seen before and if it persists I'll log a support job for it (the job is still running).

Also, config backups don't appear to be able to go to scale out repos, which means you'll need to keep a separate repo for them if you were planning on running just one big scale out repo. Still adding a 1GB repo on a proxy somewhere isn't a huge issue

Other than that, things have gone well. Per VM backup chains are on and working. EMC SAN's are added and having the console locally is very nice (although I'm not sure about the flat look and the "blandness")
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby vmniels » Tue Jan 12, 2016 11:08 pm 2 people like this post

Do keep in mind that you could create a folder one of the 2 repositories and add that one to VBR again to save your configuration.

For example on a Windows server:
E:\BACKUPS (this will be part of SOBR)
E:\CONFBACKUP (this won't be part of SOBR)
VCP-DCV
Veeam Certified Architect (VMCA)
http://foonet.be
vmniels
Veeam Software
 
Posts: 1584
Liked: 349 times
Joined: Mon Jul 15, 2013 11:09 am
Full Name: Niels Engelen

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby Dima P. » Tue Jan 12, 2016 11:27 pm

DaveWatkins,
"Error: BlobCall: Undefined function id: 54"

This one needs to be investigated with support team for sure. If the issue persists, kindly, open a support case and post the case ID this thread.
config backups don't appear to be able to go to scale out repos

That’s by design but the workaround Niels suggested sound good.
Dima P.
Veeam Software
 
Posts: 6523
Liked: 454 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Wed Jan 13, 2016 12:13 am

Yeah, the config backup one wasn't really anything to worry about for me, just thought I'd put it here so others saw it. Plenty of ways to work around it easily.

The Scale out issue was interesting, but I'm guessing was more related to v8 not cleanly removing the DB records about that folder than anything to do with v9. Still waiting for that exchange job to finish so I can retry it and see f the error persists
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby Delo123 » Wed Jan 13, 2016 1:18 am 1 person likes this post

Dave,

just updated to V9 and after reading your post i ran an incremental backup of our Exchange 2010 DAG Cluster, all fine here...
Delo123
Expert
 
Posts: 351
Liked: 101 times
Joined: Fri Dec 28, 2012 5:20 pm
Full Name: Guido Meijers

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby Dima V. » Wed Jan 13, 2016 9:12 am

DaveWatkins,

DaveWatkins wrote:I then wanted combine two repos into a scale out repo but everytime I tried I got an error saying it couldn't access a folder on one of the repos. The folder was from an old backup job that had been removed and deleted a long while ago. I'm assuming this was associated with an orphan record in the database about that job that wasn't removed properly. I ended up completely removing that repo from B&R and re-adding it. After that I could build the scale out repo with it.


Can you please clarify. It may help us to improve our code.
If I understand right you had orphaned job which was pointed to to that Repository, had some runs in the past, but there wasn't any registered backups (even failed) neither under Disk->Backup nor under Disk->Imported?
Dima V.
Veeam Software
 
Posts: 45
Liked: 6 times
Joined: Thu Oct 21, 2010 8:54 am
Full Name: Dmitry Vedyakov

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Sun Jan 17, 2016 11:05 pm

That's correct, there was no record of the old job anywhere in the UI. All the Repo backups had been removed from the GUI and the job had been deleted months ago.

I've just stumbled upon a new issue but this one will likely need to go via support. My Scale out repo consists of 2 repos, one had ~500GB free and the other has 9TB. I've created a new job with 12 VM's abd about 350GB of data in the VM's total.

When running the job the first 3 VM's start backing up fine, but the remaining all fail immediately with:

" Unable to allocate processing resources. Error: No scale-out repository extents have sufficient disk space to store the backup file. "

There is another backup in progess to this scale out repo going but there is plenty of free space available and even if the other job is "locking" a repo even the server with 500Gb free would be enough to store the initial backups of these VM's

Retrying the job after it finished and then the next 3 VM's start backing up fine and the remaining 6 fail again. I'll keep retrying until I have all 12 VM's with backup files on the repo and then launch a normal backup and see what happens
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby foggy » Tue Jan 19, 2016 10:07 am

This last one indeed looks unexpected, however can be caused by the space estimation algorithm used during backup to scale-out repository. So please contact technical support with this for confirmation.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby I.Makaryev » Tue Jan 19, 2016 3:39 pm

DaveWatkins wrote:
Retrying the job after it finished and then the next 3 VM's start backing up fine and the remaining 6 fail again. I'll keep retrying until I have all 12 VM's with backup files on the repo and then launch a normal backup and see what happens


Hello, Dave!
Do you use VMware?
Two questions more - do your VMs have thick or thin provisioned disks? How much "used storage" space is VMware reporting for that VMs?
Thanks.
I.Makaryev
Veeam Software
 
Posts: 15
Liked: 5 times
Joined: Fri Dec 21, 2012 8:53 am
Full Name: Igor Makaryev

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Thu Jan 21, 2016 8:51 pm

Yes, these are all running on VMWare 6U1 and the VM's are thick provisioned. Used storage space is a mix but in all cases the full size of the provisioned disks (between 25GB and a couple of hundred GB depending on the VM in question)
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby foggy » Fri Jan 22, 2016 11:27 am

Large thick disks with small amount of actual data can easily confuse backup repository space estimation. Job logs will tell whether this is the cause of this behavior.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Sun Jan 24, 2016 7:27 pm

It isn't/wasn't. The disks didn't have a lot of free space in fact most of them are at about 80% full. Also if that were the case surely retrying the job wound't have fixed it (or at least allowed it to start 3 more backups).

To reiterate, none of the VM's by themselves would have filled any of the underlying repo's, In fact the total size of all the VM's in the job would not have filled up one of the underlying repos even if all the disks were at 100% usage
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby foggy » Mon Jan 25, 2016 11:12 am

Anyway, we're interested in further investigation of this behavior, so contacting support is recommended.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby SyNtAxx » Sun Feb 07, 2016 8:54 pm

foggy wrote:Anyway, we're interested in further investigation of this behavior, so contacting support is recommended.


I'm interested also, as I seem to be seeing similar behavior(s).

'Unable to allocate processing resources. Error: No scale-out repository extents have sufficient disk space to store the backup file. '

There is currently 38.5TB free of 64TB.

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

Re: B&R v9 oddities (maybe bugs)

Veeam Logoby DaveWatkins » Sun Feb 07, 2016 8:58 pm

It didn't ever open a ticket for this as we have some other stuff going on taking my time and I didn't have the time to dedicate to it (new SAN, wireless upgrade etc), and I could work around it for now. Given the ease with which I can replicate it I figured it could wait. Nick, you're welcome to open a ticket yourself
DaveWatkins
Expert
 
Posts: 271
Liked: 68 times
Joined: Sun Dec 13, 2015 11:33 pm

Next

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot] and 57 guests