Discussions specific to the VMware vSphere hypervisor
lp@albersdruck.de
Enthusiast
Posts: 81
Liked: 32 times
Joined: Mar 25, 2013 7:37 pm
Full Name: Lars Pisanec
Contact:

Re: Post v8 Upgrade Observations

Post by lp@albersdruck.de » Nov 29, 2014 7:32 am 1 person likes this post

Just to chime in: the hotfix did resolve my problem. And so far has had no side effects (well after 12 hours :P )

Gostev
SVP, Product Management
Posts: 24094
Liked: 3280 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Post v8 Upgrade Observations

Post by Gostev » Nov 29, 2014 7:50 pm

Thanks for the update, Lars. This sounds promising!

DiabInc
Novice
Posts: 4
Liked: never
Joined: Mar 16, 2014 4:19 am
Full Name: Mats Bengtsson
Contact:

Re: Post v8 Upgrade Observations

Post by DiabInc » Nov 29, 2014 11:09 pm

Minor bug report Veeam 8.

I was running a SureBackup job when i noticed that progress indicator stayed at 0% in the SureBackup job tab, while the progress indicator (% completed) worked normal in running jobs tab.

Vitaliy S.
Product Manager
Posts: 22448
Liked: 1443 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Post v8 Upgrade Observations

Post by Vitaliy S. » Nov 30, 2014 1:30 pm

Thanks for the heads up, Mats.

hyvokar
Expert
Posts: 346
Liked: 21 times
Joined: Nov 21, 2014 10:05 pm
Contact:

Re: Post v8 Upgrade Observations

Post by hyvokar » Dec 01, 2014 9:27 am

Gostev wrote: Please note that sequential write workload cannot represent storage performance, which is measured in IOPS. However, backup storage is not necessarily causing the issue anyway, see what the backup job reports as a bottleneck.
Hi!

This is absolutely true, but since nothing else has changed I just made sure that storage was ok.
It seems that the speed is permanently dropped, so backing up my file server takes now 70-80minutes instead of 25-35 minutes. It doesnt seem to have much impact if vbr has to transfer 7GB or 70GB. Anyway, I can wait for the patch #1, since my backup window is quite big.

Other thing I noticed, all my backup copy jobs to tape device fails now. Opened a Support case on this one.

Tape library: IBM 3573-TL A.40
Used tapes: FOE329L4 [FOE329L4]
GetTapeHeader failed ChannelError: ConnectionReset
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE

v.eremin
Product Manager
Posts: 16232
Liked: 1325 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Post v8 Upgrade Observations

Post by v.eremin » Dec 01, 2014 9:33 am

Your issue seems to be similar to the one discussed here; might be worth posting your ticket number there in order to get a private fix as soon as possible. Thanks.

hyvokar
Expert
Posts: 346
Liked: 21 times
Joined: Nov 21, 2014 10:05 pm
Contact:

Re: Post v8 Upgrade Observations

Post by hyvokar » Dec 01, 2014 1:41 pm 1 person likes this post

Got the fix from Support and tape jobs are working now.
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE

jja
Enthusiast
Posts: 45
Liked: 8 times
Joined: Nov 13, 2013 6:40 am
Full Name: Jannis Jacobsen
Contact:

Re: Post v8 Upgrade Observations (Case # 00691208)

Post by jja » Dec 02, 2014 10:34 am

I registered a case, and uploaded log zip to your ftp.
Hopefully it's the same issue as Lars Pisanec had.

-j

patrickl78
Service Provider
Posts: 32
Liked: 7 times
Joined: Jan 09, 2014 11:16 pm
Full Name: Patrick Leonard
Contact:

Re: Post v8 Upgrade Observations

Post by patrickl78 » Dec 02, 2014 2:37 pm

I am seeing the same backup time issues. They are taking way longer in the two environments I've upgraded to Veeam 8 on. A backup that used to take an hour on Veeam 7 now takes 3.5 hours. I am actually getting better throughput on veeam 8 at 102 MB/s vs Veeam 7 where the processing rate was 45-55 MB/s. Should I open a support case on this?

Vitaliy S.
Product Manager
Posts: 22448
Liked: 1443 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Post v8 Upgrade Observations

Post by Vitaliy S. » Dec 02, 2014 3:01 pm

Yes, you can and send all job logs to review bottleneck stats, amount of changed data and other statistics that would allow us to understand where this difference comes from.

patrickl78
Service Provider
Posts: 32
Liked: 7 times
Joined: Jan 09, 2014 11:16 pm
Full Name: Patrick Leonard
Contact:

Re: Post v8 Upgrade Observations

Post by patrickl78 » Dec 02, 2014 3:36 pm

I am using Forward Incremental keeping 60 days of retention if that helps. It is not a SAN environment (Dell PowerEdge server approx 6 months old with 16 drives and plenty of iOPS). We are using vCenter 5.5 Update 2. Nothing changed infrastructure wise prior to upgrading to Veeam 8.

Thanks,
Patrick

JimmyO
Enthusiast
Posts: 55
Liked: 9 times
Joined: Apr 27, 2014 8:19 pm
Contact:

Re: Post v8 Upgrade Observations

Post by JimmyO » Dec 03, 2014 11:29 am

@patrickl78 - my issues seems more or less identical to yours, forward incremental, local disk and 5.5u2. No infrastructure changes prior to upgrade.

I´m currently working with Veeam support on this. I actually installed the fix for bug 38623, wich improved performance a bit (from 4-5 times slower to appr. 2-3 times slower).

Still - I installed v8 expecting better performance and not much worse. Currently waiting for support log analysis.

patrickl78
Service Provider
Posts: 32
Liked: 7 times
Joined: Jan 09, 2014 11:16 pm
Full Name: Patrick Leonard
Contact:

Re: Post v8 Upgrade Observations

Post by patrickl78 » Dec 03, 2014 2:47 pm

Jimmy,

I have a case open as well and have sent in the logs for the two servers I upgraded. On both servers I upgraded I also run replication jobs and those jobs get the weird Exchange truncating error even though the servers have never had Exchange on them.

Thanks,
Patrick

jja
Enthusiast
Posts: 45
Liked: 8 times
Joined: Nov 13, 2013 6:40 am
Full Name: Jannis Jacobsen
Contact:

Re: Post v8 Upgrade Observations

Post by jja » Dec 04, 2014 6:27 am 2 people like this post

Implemented the hotfix yesterday.
The backups used about 3 hours less time now, so this seems to have done the trick.

-j

patrickl78
Service Provider
Posts: 32
Liked: 7 times
Joined: Jan 09, 2014 11:16 pm
Full Name: Patrick Leonard
Contact:

Re: Post v8 Upgrade Observations

Post by patrickl78 » Dec 05, 2014 3:16 am

Applied the bug fix today with Veeam support. Backups ran successfully but still 3.5 hours. It cut the backup window down by an hour but no where near the usual 1 hour and 15 min on Veeam 7. Support did confirm I was impacted by the issue the bug fix was targeted at but it has not alleviated all of my issues so far. There is a second bug that there is currently no fix for as i understand it from support. I'll upload my logs again to them once this job finishes and hopefully will help them figure out what is going on. There have been no changes to my network infrastructure or backup job prior to the upgrade.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 33 guests