Error message:
C3703 unable to open media EC=can not find tape to be connected
Preceeded with:
E6500 Client connect to tape failed
Backup Configuration:
Two node cluster Primary with SAN option
Two node cluster Distributed with SAN option
Fibre LTO3 (3 drives, 200 slots) tape library
Disk to Disk to tape backup method
Using Global scratch set for Primary and Distributed backup servers
Information:
This error seemed to start when I switched over to the Global scratch method. The global scratch set does work, scratch tapes are used across media pools.
One job used a tape that was in the scratch pool tape #122
An hour later another job wanted to use the same tape (produced the error above) and put the migration job in a hold status.
I released the held migration job later and the job used another scratch tape from the global pool with no problem.
When do the data migration jobs determine which tape to use from the global scratch pool? Does the job check when it is submitted to the job queue or when it actually starts?
There can be a delay for the Data Migration jobs waiting for an available tape drive to use.
C3703 unable to open media EC=can not find tape to be connected
Preceeded with:
E6500 Client connect to tape failed
Backup Configuration:
Two node cluster Primary with SAN option
Two node cluster Distributed with SAN option
Fibre LTO3 (3 drives, 200 slots) tape library
Disk to Disk to tape backup method
Using Global scratch set for Primary and Distributed backup servers
Information:
This error seemed to start when I switched over to the Global scratch method. The global scratch set does work, scratch tapes are used across media pools.
One job used a tape that was in the scratch pool tape #122
An hour later another job wanted to use the same tape (produced the error above) and put the migration job in a hold status.
I released the held migration job later and the job used another scratch tape from the global pool with no problem.
When do the data migration jobs determine which tape to use from the global scratch pool? Does the job check when it is submitted to the job queue or when it actually starts?
There can be a delay for the Data Migration jobs waiting for an available tape drive to use.
