v9 Tape Inventory Error

Everything about backing up to tape

v9 Tape Inventory Error

Veeam Logoby hoFFy » Fri Jan 15, 2016 4:41 pm 2 people like this post

After installing v9 and using brand new Tandberg LTO-5 and LTO-6 drives and tapes (newest driers and firmware) on seperate vSphere-Hosts I was unable to do an inventoriation, error message in german was "unzulässige Funktion" in english it might be "function not allowed"

Logfile shows:
Code: Select all
[15.01.2016 16:36:29] <01> Info                   [AP] (5f72) state: ready
[15.01.2016 16:36:29] <07> Info             [AP] (5f72) output: >
[15.01.2016 16:36:29] <01> Info     [TapeService] GetMediaInfo, drive sym link '\\.\Tape0', changer sym link '\\.\Tape0'
[15.01.2016 16:36:29] <01> Info     [TapeService] Connecting to tape service on '192.168.10.221:6166'
[15.01.2016 16:36:29] <01> Info     [CProxyRpcInvoker] RpcInvoker HashCode:41421720 was disposed
[15.01.2016 16:36:29] <01> Info             [AP] (5f72) command: 'getTapeMediaId\n\\.\Tape0\n'
[15.01.2016 16:36:29] <07> Info             [AP] (5f72) output: <error code="0">
[15.01.2016 16:36:29] <08> Info             [AP] (5f72) output: Empty MTF media
[15.01.2016 16:36:29] <08> Info             [AP] (5f72) output: --tr:TapeReader failed to read media header.
[15.01.2016 16:36:29] <08> Info             [AP] (5f72) output: </error>
[15.01.2016 16:36:29] <08> Info             [AP] (5f72) output: >
[15.01.2016 16:36:29] <01> Info             [AP] (5f72) command: 'setTapeMediaBlockSizeToDrive\n\\.\Tape0\n1048576\n'
[15.01.2016 16:36:29] <08> Info             [AP] (5f72) output: >
[15.01.2016 16:36:29] <01> Info             [AP] (5f72) command: 'writeTapeHeader\n\\.\Tape0\n\n0\nMTF Media Label|1.0|Veeam|Backup & Replication 9.0|2016.01.15.16:36:29|Veeam 2016.01.15.16:36:29|1|{9d65f2ae-6124-47c4-9a86-c358d4a50e10}||\nFalse\n'
[15.01.2016 16:36:32] <07> Error                  [AP] (5f72) error: Unzulässige Funktion
[15.01.2016 16:36:32] <07> Error          Tape read error
[15.01.2016 16:36:32] <07> Error          --tr:Error code: 0x00000001
[15.01.2016 16:36:32] <07> Error          --tr:TapeStream failed to read block.
[15.01.2016 16:36:32] <07> Error          --tr:TapeStream initialization FAILED
[15.01.2016 16:36:32] <07> Error          --tr:Failed to create MtfStream.
[15.01.2016 16:36:32] <07> Error          --tr:TapeWriter failed to init tape media, mediaName: , mediaFamilyId: 0, mediaLabel: MTF Media Label|1.0|Veeam|Backup & Replication 9.0|2016.01.15.16:36:29|Veeam 2016.01.15.16:36:29|1|{9d65f2ae-6124-47c4-9a86-c358d4a50e10}||.
[15.01.2016 16:36:32] <07> Error          --tr:Cannot write tape header '', mediaId: '0'.
[15.01.2016 16:36:32] <07> Error          --tr:Client failed to process the command. Command: [writeTapeHeader].
[15.01.2016 16:36:32] <07> Error          --tr:event:3:
[15.01.2016 16:36:32] <08> Info                   [AP] (5f72) state: closed
[15.01.2016 16:36:32] <01> Error    WriteTapeHeader failed (Veeam.Backup.Common.CAgentException)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Backup.AgentProvider.CBackupClient.WriteTapeHeader(String tapeName, String mediaName, Int32 mediaId, String label, Boolean longErase)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.TapeDriveEx.WriteTapeHeader(Boolean longErase)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.TapeDriveEx.FindOrWriteMediaLabel(Boolean& isWriten)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.CTapeDriveInventory.InventoryWithoutBarcode(Boolean forceReadHeader)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.CTapeDriveInventory.Inventory(Boolean forceReadHeader)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.CTapeDriveInventory.InventoryHeader(TapeDrive tapeDrive, TapeMedium supposedTapeMedium, IBackupClient backupClient, ITapeDuplicateBarcodeChecker duplicateBarcodeChecker)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Tape.Core.CTapeInventoryPerformer.InventoryDrive(TapeDrive tapeDrive, TapeMedium supposedTapeMedium)
[15.01.2016 16:36:32] <01> Error    Unzulässige Funktion (Veeam.Backup.Common.CCppComponentException)
[15.01.2016 16:36:32] <01> Error    Tape read error (Veeam.Backup.Common.CCppComponentException)
[15.01.2016 16:36:32] <01> Error       in c++: Error code: 0x00000001
[15.01.2016 16:36:32] <01> Error       in c++: TapeStream failed to read block.
[15.01.2016 16:36:32] <01> Error       in c++: TapeStream initialization FAILED
[15.01.2016 16:36:32] <01> Error       in c++: Failed to create MtfStream.
[15.01.2016 16:36:32] <01> Error       in c++: TapeWriter failed to init tape media, mediaName: , mediaFamilyId: 0, mediaLabel: MTF Media Label|1.0|Veeam|Backup & Replication 9.0|2016.01.15.16:36:29|Veeam 2016.01.15.16:36:29|1|{9d65f2ae-6124-47c4-9a86-c358d4a50e10}||.
[15.01.2016 16:36:32] <01> Error       in c++: Cannot write tape header '', mediaId: '0'.
[15.01.2016 16:36:32] <01> Error       in c++: Client failed to process the command. Command: [writeTapeHeader].
[15.01.2016 16:36:32] <01> Error       in c++ event: ClientErrorEvt
[15.01.2016 16:36:32] <01> Error       bei Veeam.Backup.AgentProvider.CClientAgentProtocol.WaitUntilWorking(Int32 timeout)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Backup.AgentProvider.CClientAgentProtocol.DoAgentCommand(String command, String logCommand, Boolean doWait, Nullable`1 outputLogLevel)
[15.01.2016 16:36:32] <01> Error       bei Veeam.Backup.AgentProvider.CBackupClient.WriteTapeHeader(String tapeName, String mediaName, Int32 mediaId, String label, Boolean longErase)
[15.01.2016 16:36:32] <01> Info     [Session] Id 'a9b37daa-7342-488a-b729-6f4b866496c2', State 'Stopped'
[15.01.2016 16:36:32] <01> Info     Disposing CBackupClient [0x27e1210]
[15.01.2016 16:36:32] <01> Info             [AP] Disposing client from thread 1
[15.01.2016 16:36:32] <01> Info     Disposing BaseAgentProtocol [0x26ea292]
[15.01.2016 16:36:32] <01> Info     Disposing CSocketAgentService [0x1e3b723], sessionId [5f72]
[15.01.2016 16:36:32] <01> Info     [SocketAgentService] Closing connection to agent 'BKP01.tischlerei.local', id 5f72

The solution was to change the block size from the default value 1048576 to 65536
VMCE 7 / 8 / 9, VCP-DC 5 / 5.5 / 6, MCITP:SA
Blog: machinewithoutbrain.de
hoFFy
Veeam ProPartner
 
Posts: 161
Liked: 25 times
Joined: Fri Apr 27, 2012 1:10 pm
Location: Germany / Lohne
Full Name: Sebastian Hoffmann

Re: v9 Tape Inventory Error

Veeam Logoby Gostev » Fri Jan 15, 2016 8:44 pm

Thanks for sharing. Glad we added the capability to change block size!
Gostev
Veeam Software
 
Posts: 21386
Liked: 2348 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: v9 Tape Inventory Error

Veeam Logoby hoFFy » Mon Jan 18, 2016 9:40 am

I like your humor ;-) But I don't believe that its intended to fail if the drive is used "out of the box" without adjusting the block size, isn't it?
VMCE 7 / 8 / 9, VCP-DC 5 / 5.5 / 6, MCITP:SA
Blog: machinewithoutbrain.de
hoFFy
Veeam ProPartner
 
Posts: 161
Liked: 25 times
Joined: Fri Apr 27, 2012 1:10 pm
Location: Germany / Lohne
Full Name: Sebastian Hoffmann

Re: v9 Tape Inventory Error

Veeam Logoby Dima P. » Mon Jan 18, 2016 1:33 pm

Hi Sebastian,

Can you clarify is that two separate standalone tape drives or two drives within one tape library? Thanks
Dima P.
Veeam Software
 
Posts: 6231
Liked: 439 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: v9 Tape Inventory Error

Veeam Logoby hoFFy » Mon Jan 18, 2016 2:12 pm

Two customers, each with a new new SAS-attached Tandberg LTO (5 and 6) drive. One customer became a new vSphere Host, together with a fresh VM for Veeam 9, the other one got a new drive and Veeam has been upgraded to v9 (don't now exactly if upgraded, a colleage did it)
VMCE 7 / 8 / 9, VCP-DC 5 / 5.5 / 6, MCITP:SA
Blog: machinewithoutbrain.de
hoFFy
Veeam ProPartner
 
Posts: 161
Liked: 25 times
Joined: Fri Apr 27, 2012 1:10 pm
Location: Germany / Lohne
Full Name: Sebastian Hoffmann

Re: v9 Tape Inventory Error

Veeam Logoby Dima P. » Mon Jan 18, 2016 3:10 pm

Thanks. To clarify was that a brand new tape media or media that was previously used by us (or any other tape software)?
Dima P.
Veeam Software
 
Posts: 6231
Liked: 439 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: v9 Tape Inventory Error

Veeam Logoby hoFFy » Fri Jan 22, 2016 10:51 am

The tapes were brand new
VMCE 7 / 8 / 9, VCP-DC 5 / 5.5 / 6, MCITP:SA
Blog: machinewithoutbrain.de
hoFFy
Veeam ProPartner
 
Posts: 161
Liked: 25 times
Joined: Fri Apr 27, 2012 1:10 pm
Location: Germany / Lohne
Full Name: Sebastian Hoffmann

Re: v9 Tape Inventory Error

Veeam Logoby Dima P. » Fri Jan 22, 2016 3:12 pm

Thanks Sebastian. May I ask you to open the case - we want to check the logs to be sure.
Dima P.
Veeam Software
 
Posts: 6231
Liked: 439 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: v9 Tape Inventory Error

Veeam Logoby Y2kovu » Wed Feb 24, 2016 12:06 am

Got another seemingly confirmed case (pending a stretch of observe-and-report to follow) where setting the block size to 65536 on a standalone tape drive, this time a Quantum Ultrium LTO5 attached via SAS, was what resolved this issue. Internal support, refer to case 01673028.
Y2kovu
Veeam Software
 
Posts: 4
Liked: never
Joined: Tue Dec 02, 2014 8:13 pm

Re: v9 Tape Inventory Error

Veeam Logoby Chuck » Fri Mar 11, 2016 6:21 pm 1 person likes this post

I wanted to share with everyone in case you had other customers call in with this problem:

Backup Fails with Error:
WriteTapeHeader failed incorrect function. Tape read error Incorrect function. (Error occurs right after the tape is mounted)

The fix for this was to go into the properties of the tape drive (Tape Infrastructure / Libraries / ADIC Scalar i500 660G (<-- this is my Tape Library yours may be different) / Drives) and change the Block Size from ***** to 65536 (I have not tried any others you may want to experiment. The setting for the Block Size was 1048576.


Notes:
1)Hardware Used: Quantum Scalar I500 / IBM Ultirium-TD6 LTO-6 / Firmware Level E6R6 / No FC i/o Blade Connected
2)Backup Software used: Veeam
a.Cause of the problem: Upgrade Veeam from 8.0 to 9.0 (I am not for sure what the block size was set to in Veeam 8 by default but Veeam 9 sets the blocksize by default to 1048576)
3)Setup: Drives are set up in Point-to-Point Mode Connected to a FC Switch. FC Switch is set to Zone only the Fiber of the Tape Drives and the HBA in the ESXi Server. The Guest in the ESXi Server is a Windows 2k12 OS with the Tape Drivers loaded. The Virtual Hardware of the Tape drive includes the Library and each tape drive as SCSI devices.
4)To have this configuration work as it is unsupported by VMWare: Once the system is online load tape media into each drive / rescan the HBA and then ESX will enable the path for the drives. Once that step is completed turn on the guest and the guest will control the drives.


Hope this helps someone
Chuck
Lurker
 
Posts: 1
Liked: 1 time
Joined: Fri Mar 11, 2016 6:12 pm
Full Name: Chuck W

[MERGED] WriteTapeHeader Error after version 9 upgrade

Veeam Logoby lostsurfer » Mon Mar 14, 2016 1:15 pm

So I upgraded to the latest version of veeam and since then I can't get my backup to tape, I get the following error.

Code: Select all
WriteTapeHeader failed Incorrect function. Tape read err Incorrect Function.

Anyone have any ideas? Thanks
lostsurfer
Novice
 
Posts: 6
Liked: 1 time
Joined: Wed Dec 17, 2014 7:37 pm

[MERGED] Re: WriteTapeHeader Error after version 9 upgrade

Veeam Logoby Shestakov » Mon Mar 14, 2016 2:29 pm

Hello!
Please provided your support case number as required by the forum`s rules.
One of our customers had a similar issue which was solved by changing a block size, but I would suggest contacting technical support first.
Thanks!
Shestakov
Veeam Software
 
Posts: 4842
Liked: 393 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov


Return to Tape



Who is online

Users browsing this forum: No registered users and 13 guests