netbackup media tape duplication / concern
Hello
My question is regarding "preserve multiplexing" in duplicating backup images on media tapes in NetBackup from LTO7's to LTO8 via the netbackup admin console.
Our layout is this. Netbackup 10.5.0.1 RHEL8 environment running on a single server that serves as both master/media. This netbackup environment has been around for sometime - another words it has been upgraded from the early days of NBU 7* to the current version its on now with multiple hardware refreshes and OS refreshes.
Our storage units are the following
We have two Overland LTO7 libraries and we also no have 2 overland LTO8 libraries.
The storage units from the admin console look like this -
the name ending in tld-0 and tld-1 are the LTO7 tape libraries and the tld-2 and tld-3 are the LTO8 libraries.
We are wanting to duplicate our LTO7 archive tapes and/or tapes that have an INFINTY expired date to the new LTO8 tapes.
A little history behind this on our project we had a previous co-worker years ago that duplicated our LTO5s to the current LTO7s and I was able to find some of his notes and on the admin console CATALOG section where you can perform the "duplicate" option he had also stated to check the box on the gui to PRESERVE MULTIPLEXING. So basically this is were my question has come about as I ran a quick test to perform a duplication of some images on a LTO7 tape to duplicate them to a LTO8 tape. But my duplication job failed right away with a status 154 ((154) storage unit characteristics mismatched to request )
detailed status of the job showed this -
Aug 22, 2025, 3:52:27 PM - begin Duplicate
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5536) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5536) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5536) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5536) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - end Duplicate; elapsed time 0:00:01
Aug 22, 2025, 3:52:28 PM - requesting resource kbs-pgrid-1-hcart-robot-tld-2
Aug 22, 2025, 3:52:28 PM - requesting resource 0832L7
Aug 22, 2025, 3:52:28 PM - reserving resource 0832L7
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5531) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5531) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5531) NetBackup status: 154, EMM status: Storage unit is not compatible
Aug 22, 2025, 3:52:28 PM - Error nbjm (pid=5531) NetBackup status: 154, EMM status: Storage unit is not compatible
storage unit characteristics mismatched to request (154)
So as you can see in SNIP above the storage units all have multiplexing set to 1 which I believe means its not active on the storage units/libraries. But just about all the policies have the multiplexing enable except I believe the MSSQL policies.
I myself do not recall changing the multiplex option on the storage units. When I recently added the Overland LTO8 libraries I just made them the same setting as what was in place for the LTO7 libraries.
I was able to get my test duplication job to run but I had to change the multiplexing from 1 to 32 on the LTO8 library (destination library for duplication).
Am i correct in that I need to have multiplexing enabled on the libraries for the destination library in order to preserve multiplexing. In GENERAL If the policies have multiplexing set should the drives as well have it set to something other then 1?
I can see in the admin console under MEDIA STATUS that a lot of the old LTO7 tapes that were probably from the previous duplication task done by the former co-workers has a MEDIA status = Active multiplexed or some have FULL Multiplexed.
Then I see some of the newer LTO7 series of tapes have MEDIA STATUS = FULL
So should the storage UNITS have MULTIPLEX enabled (something other then 1) if the POLICIES have multiplex set to something other then 1. ? Any advice or suggestions would be appreciated.
Im thinking we need to have the Storage units set to multiplexing permanently (something other then 1) not just for the duplication task but for normal backups but honestly Im not sure.
Thanks
BC

