LTO 7 media, restore LTO 8 drive

[soolean]

Hello.

I want to restore a backup on LTO 7 media from LTO8 drive, but the process does not start.

08.Ara.2023 14:40:52 - awaiting resource BNV420.
A pending request has been generated for this resource request.
Operator action may be required. Pending Action: No action,
Media ID: BNV420, Barcode: BNV420L7, Density: hcart, Access Mode: Read,
Action Drive Name: N/A, Action Media Server: asg100vnb02, Robot Type(Number): 0(N/A),
Volume Group: 001_00002_TLD, Action Acs: N/A, Action Lsm: N/A

[StefanosM]

• Insert the tape with Media ID: BNV420, Barcode: BNV420L7 in the library with number 0
• run inventory robot 0
• open the java gui, go to device monitor and accept the pending request

[quebek · Accepted solution]

Hey

make sure that your storage unit matches tape density - both should be of the same type, it hcart....

if lto7 tape is not of this type run the following: 

vmchange -m BNV420 -new_mt hcart2 

where hcart2 is your LTO8 storage unit density type.

[soolean]

How do I know that?

---> make sure that your storage unit matches tape density - both should be of the same type, it hcart...

the media shows up as HCART2

Let me give you some information

This LTO7 media was written on an HP LTO 7 device

[quebek]

Hello

Well, LTO is a standard which is backward compatible, so in your case you are still good to read LTO7 media in LTO8 tape drive. See this https://www.lto.org/lto-generation-compatibility/

Below some excerpt:

• LTO drive generations 1-7 are able to read tapes from two generations prior and are able to write to tapes from the prior generation.
• LTO-8 drives can read and write to LTO-7 and LTO-8 media, including
  LTO-7 Type M.
• LTO-9 drives can read and write to LTO-8 and LTO-9 media only.
• With a published roadmap, LTO technology allows you to better forecast how to address your future technology as you consider your needs today.

So change the LTO7 media type to match your LTO8 storage unit type and your restore should progress.

[soolean]

'vmchange' is not recognized as an internal or external command,
operable program or batch file.

[quebek]

what is your OS where NBU primary is running??

[soolean]

Windows Server 2016 

OK,

I gave the command in the wrong directory. When I searched the internet, I found it again on this site.

C:\Programme Files\Veritas\Volmgr\bin>