-
- Influencer
- Posts: 16
- Liked: 1 time
- Joined: Sep 11, 2014 8:45 am
- Full Name: Roman Petrov
- Contact:
Tape jobs fail after switching to VBR 8
Hi! When I had VBR 7 installed, I was able to perform tape backups with my IBM 3573 TL.
After switching to v8 I cannot do it anymore. During running of any job I am getting such a message "GetTapeHeader failed ChannelError: ConnectionReset"
I also cannot perform either Inventory Library or Catalog Library - they fail with the same error.
From the tape library's side I can perform tape inventory successfully and the library seems to work well. What I've done so far:
1. Restarting Veeam server
2. Restarting tape library
3. Disabling tape drives in Device Manager, removing media pools and all tape jobs, deleting the library itself. And it still doesn't work.
Any suggestions?
Case # 00680055
After switching to v8 I cannot do it anymore. During running of any job I am getting such a message "GetTapeHeader failed ChannelError: ConnectionReset"
I also cannot perform either Inventory Library or Catalog Library - they fail with the same error.
From the tape library's side I can perform tape inventory successfully and the library seems to work well. What I've done so far:
1. Restarting Veeam server
2. Restarting tape library
3. Disabling tape drives in Device Manager, removing media pools and all tape jobs, deleting the library itself. And it still doesn't work.
Any suggestions?
Case # 00680055
-
- Product Manager
- Posts: 20284
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape jobs fail after switching to VBR 8
Just out of curiosity - have you tried to erase given mediums and start a tape job anew? Thanks.
-
- Influencer
- Posts: 16
- Liked: 1 time
- Joined: Sep 11, 2014 8:45 am
- Full Name: Roman Petrov
- Contact:
Re: Tape jobs fail after switching to VBR 8
Quick erasing failed with the same error. Full erasing have started a half hour ago and still workingv.Eremin wrote:Just out of curiosity - have you tried to erase given mediums and start a tape job anew? Thanks.
Thanks!
-
- Product Manager
- Posts: 20284
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape jobs fail after switching to VBR 8
Let's see whether full erase will allow you to proceed any futher. Anyway, keep working with the support team on finding the root cause of that behaviour. Thanks.
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Mar 14, 2012 12:13 pm
- Full Name: Ryan Hayes
- Contact:
Re: Tape jobs fail after switching to VBR 8
Were you able to get this resolved? I'm running into the same issue and was going to open an incident as well.
-
- Influencer
- Posts: 16
- Liked: 1 time
- Joined: Sep 11, 2014 8:45 am
- Full Name: Roman Petrov
- Contact:
Re: Tape jobs fail after switching to VBR 8
Hi! Unfortunately my problem is still solving. I will update the posthayesr1 wrote:Were you able to get this resolved? I'm running into the same issue and was going to open an incident as well.
-
- Product Manager
- Posts: 20284
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape jobs fail after switching to VBR 8
Hi, Ryan,
Please, open your own ticket with our support team. Having as much information as possible will let us find the root cause faster.
Thanks.
Please, open your own ticket with our support team. Having as much information as possible will let us find the root cause faster.
Thanks.
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Mar 14, 2012 12:13 pm
- Full Name: Ryan Hayes
- Contact:
Re: Tape jobs fail after switching to VBR 8
I just opened an issue as well. My case number is 00682788
-
- Product Manager
- Posts: 14417
- Liked: 1576 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Tape jobs fail after switching to VBR 8
Hello all,
QA and DEV teams found the root of this problem. Once the hotfix is ready – you get it ASAP. Thank you for your patience!
QA and DEV teams found the root of this problem. Once the hotfix is ready – you get it ASAP. Thank you for your patience!
-
- Expert
- Posts: 149
- Liked: 34 times
- Joined: May 01, 2012 11:56 am
- Full Name: Stuart Green
- Contact:
Re: Tape jobs fail after switching to VBR 8
Can anyone confirm what the root cause of this was?
I had an issue straight away also moving to Veeam 8 from 7. B2T jobs failed due to tape block size detected did not match drive default block size. I had to use mt.exe to set correct block size on media. Long and short erase does not change the tape block size that currently exists. I have had to set all my tape media block size for those that were not the default block size of my drives. Apparently there has been a change in Veeam 8 code which now does extra checking for this.
I had an issue straight away also moving to Veeam 8 from 7. B2T jobs failed due to tape block size detected did not match drive default block size. I had to use mt.exe to set correct block size on media. Long and short erase does not change the tape block size that currently exists. I have had to set all my tape media block size for those that were not the default block size of my drives. Apparently there has been a change in Veeam 8 code which now does extra checking for this.
-
- Product Manager
- Posts: 14417
- Liked: 1576 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Tape jobs fail after switching to VBR 8
Stuart,
Have you opened a support case? Can you provide the case ID to check the details of support team investigation? Thank you in advance.
Have you opened a support case? Can you provide the case ID to check the details of support team investigation? Thank you in advance.
-
- Expert
- Posts: 149
- Liked: 34 times
- Joined: May 01, 2012 11:56 am
- Full Name: Stuart Green
- Contact:
Re: Tape jobs fail after switching to VBR 8
Dmitry the SR is 00685458.
For reference the errors I was receiving was:
Failed to start new tape backup session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed StartSessionTape failed When accessing a new tape of a multivolume partition, the current block size is incorrect. Tape read error When accessing a new tape of a multivolume partition, the current block size is incorrect.
For reference the errors I was receiving was:
Failed to start new tape backup session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed StartSessionTape failed When accessing a new tape of a multivolume partition, the current block size is incorrect. Tape read error When accessing a new tape of a multivolume partition, the current block size is incorrect.
-
- Product Manager
- Posts: 14417
- Liked: 1576 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Tape jobs fail after switching to VBR 8
Thank you!
As far as I know, the block size auto detection mechanism was not changed since v7 and during read operations the existing block size on your media should be equal to the supported block size on you drive. Any chance you used media in the question with one drive and then loaded them into other drive?I have had to set all my tape media block size for those that were not the default block size of my drives. Apparently there has been a change in Veeam 8 code which now does extra checking for this.
-
- Expert
- Posts: 149
- Liked: 34 times
- Joined: May 01, 2012 11:56 am
- Full Name: Stuart Green
- Contact:
Re: Tape jobs fail after switching to VBR 8
I am using only a HP MSL G3 series (MSL8096) with 4 x 3280 Ultrium FC drives. So the drives are the same/same firmware. So when you say moved from drive to another there are a possible of 4 same drives for it to use.
Veeam 8 is setting the block size on tape media as displayed with this recent job error:
Veeam 8 is setting the block size on tape media as displayed with this recent job error:
SetTapeMediaBlockSizeToDrive failed Failed to send command An established connection was aborted by the software in your host machine
-
- Novice
- Posts: 4
- Liked: never
- Joined: Feb 05, 2009 1:08 pm
- Contact:
Re: Tape jobs fail after switching to VBR 8
Any news on this?
We have exactly the same problem with HP 1x8 Autoloader equipped with LOT4 drive - After upgrading V7 to V8 it broke down with the block size error on tape backups.
Unfortunately we are still in evaluation phase so calling support may not be an option. Hotfix welcome
BTW: Where do i get the aforementioned mt.exe?
We have exactly the same problem with HP 1x8 Autoloader equipped with LOT4 drive - After upgrading V7 to V8 it broke down with the block size error on tape backups.
Unfortunately we are still in evaluation phase so calling support may not be an option. Hotfix welcome
BTW: Where do i get the aforementioned mt.exe?
-
- Novice
- Posts: 8
- Liked: never
- Joined: Nov 11, 2014 10:45 am
- Full Name: Klaus Rörig
- Contact:
[MERGED] Importing backup tapes.
Hello!
Importing, inventorting and cataloging tapes results in the following error:
I thinks it's the same as here: http://forums.veeam.com/tape-f29/tape-j ... 24174.html
CASE ID: 00691845
Klaus
Importing, inventorting and cataloging tapes results in the following error:
Code: Select all
01.12.2014 16:51:33 Processing started at Montag, 1. Dezember 2014 16:51:32
01.12.2014 16:51:36 Drive 256 (Drive ID: Tape1) locked successfully
01.12.2014 16:51:38 Error Failed to inventory tape in Drive 256 (Drive ID: Tape1) Error: ChannelError: ConnectionReset
01.12.2014 16:51:38 Error Completed with error at Montag, 1. Dezember 2014 16:51:38
CASE ID: 00691845
Klaus
-
- Expert
- Posts: 149
- Liked: 34 times
- Joined: May 01, 2012 11:56 am
- Full Name: Stuart Green
- Contact:
Re: Tape jobs fail after switching to VBR 8
mt.exe is here http://www.holistech.co.uk/sw/mt/mt.html
If you want to query the blocksize detected by the drive for your media in the drive
First move the tape into the drive. You can do this via a WEB UI your tape library might have.
Or Inventory the tape in Veeam.
You issue the command first command for each drive you have a tape you want to query. Then the second to get the block size of the media.
C:\> mt drivestatus tapeX
C:\> mt mediastatus tapeX
You can also get this info from Device Manager and Properties on the Tape Drive and from the tabs that are presented there you can see block size detected.
If you see a mismatch you can set the block size for the media using mt - of course be careful there is no data on that media you may want to restore from.
BTW: Short Erase and Long Erase do not change a block size for media in my drives.
If you want to query the blocksize detected by the drive for your media in the drive
First move the tape into the drive. You can do this via a WEB UI your tape library might have.
Or Inventory the tape in Veeam.
You issue the command first command for each drive you have a tape you want to query. Then the second to get the block size of the media.
C:\> mt drivestatus tapeX
C:\> mt mediastatus tapeX
You can also get this info from Device Manager and Properties on the Tape Drive and from the tabs that are presented there you can see block size detected.
If you see a mismatch you can set the block size for the media using mt - of course be careful there is no data on that media you may want to restore from.
BTW: Short Erase and Long Erase do not change a block size for media in my drives.
-
- Influencer
- Posts: 16
- Liked: 1 time
- Joined: Sep 11, 2014 8:45 am
- Full Name: Roman Petrov
- Contact:
Re: Tape jobs fail after switching to VBR 8
Yesterday I received a new Tape Agent from VEEAM's support team. I just replaced my old agent with a new one and tape jobs run well, including inventory, recording and restoring from tapes. I suppose you guys should wait a bit.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Feb 05, 2009 1:08 pm
- Contact:
Re: Tape jobs fail after switching to VBR 8
Thanks for the link to mt.exe - unfortunately drive and both tapes of the session which is failing have identical blocksize of 131072.
I will try to use some new tapes see if that makes any difference for now.
I will try to use some new tapes see if that makes any difference for now.
-
- Product Manager
- Posts: 20284
- Liked: 2258 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Tape jobs fail after switching to VBR 8
Hi, Martin, even though you're on evaluation license, you can still open a ticket with our support team and get the updated agent, once your issue is confirmed to be the similar one. Thanks.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 07, 2016 8:13 am
- Full Name: Chanchal Sharma
- Contact:
Re: Tape jobs fail after switching to VBR 8
Is there any solution available for this?
We are facing the exact issue with IBM TS2900 and case is already opened(# 01752800) yet to get a solution
We are facing the exact issue with IBM TS2900 and case is already opened(# 01752800) yet to get a solution
-
- Veteran
- Posts: 354
- Liked: 72 times
- Joined: Jun 30, 2015 6:06 pm
- Contact:
Re: Tape jobs fail after switching to VBR 8
Walked into it here this morning as well, V9 w/ latest updates, etc.
"Failed to start new tape backup session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed StartSessionTape failed When accessing a new tape of a multivolume partition, the current block size is incorrect. Tape read error When accessing a new tape of a multivolume partition, the current block size is incorrect."
I tried doing a quick erase on the tapes in question but I think I saw somewhere in these merged threads it didn't help another user.
"Failed to start new tape backup session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed
Failed to prepare to start new tape session: StartSessionTape failed StartSessionTape failed When accessing a new tape of a multivolume partition, the current block size is incorrect. Tape read error When accessing a new tape of a multivolume partition, the current block size is incorrect."
I tried doing a quick erase on the tapes in question but I think I saw somewhere in these merged threads it didn't help another user.
VMware 6
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
Veeam B&R v9
Dell DR4100's
EMC DD2200's
EMC DD620's
Dell TL2000 via PE430 (SAS)
-
- Product Manager
- Posts: 14417
- Liked: 1576 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Tape jobs fail after switching to VBR 8
Hi rreed,
Can you double-check the tape library firmware is up to date?
Can you double-check the tape library firmware is up to date?
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 31 guests