Replace tapes on autoloader while backup jobs executing

You need to configure a mail slot first on the autoloader, and then run an import job. Even if you can somehow unlock the library (BE will maintain a lock on the library basically preventing you from ejecting the cartridges) and put in a tape, BE will not recognise it.

There will be a section in the Admin Guide on how to configure this. Just give it a read and make the changes.

Thanks!

An import job is your likely answer.

Even if you can somehow unlock the library (BE will maintain a lock on the library basically preventing you from ejecting the cartridges) and put in a tape, BE will not recognise it.

BE hasn't locked tape libraries (by default) for a number of years now.

Assuming htat you are using bar codes on your tapes and change tapes manually (without an import job), a Backup Exec Scan job or an import job will recognize the changed media.

 

Do you perhaps know from which version? BE 2010 R3 was still doing this.

Do you perhaps know from which version? BE 2010 R3 was still doing this.

It was changed in BE 2012 and up.

http://www.veritas.com/docs/000037198

"How to change Backup Exec's robotic library locking behavior"

Thanks Larry!

Unless you are using barcode labels, it is not possible to introduce new tapes to the tape library while a job is running.  Without barcode labels, you need to run an inventory job to get the new tapes recognised by BE and the inventory job will be queued behind the backup job that is currently running.  I am not sure whether a scan job will run at the same time when the backup job is still in progress.  The safest way is to do an import if you are using barcode labels.

On a longer term, if your library does not have the capacity to handle jobs run over a couple of days, then you should be looking at a library with more slots or replacing the tape drive with a higher capacity one.

Unless you are using barcode labels, it is not possible to introduce new tapes to the tape library while a job is running.

This blanket statement is not universally true.  It may be true for some very unique environments or with peculiar (old) tape libraries.  When BE cannot find usable media in the library, BE prompts the user to import more tapes, which generally works fine.

Without barcode labels, you need to run an inventory job to get the new tapes recognised by BE and the inventory job will be queued behind the backup job that is currently running.

An import job works fine here, with or without bar code labels.  Obviously using bar code labels is highly suggested.

I am not sure whether a scan job will run at the same time when the backup job is still in progress

Generally, yes, a scan can be run at any time.  In the old days a scan was just a "background process" and not a bona fide "job".  When "scan" became a "real" job (maybe in BE 2012?) it would not run at the same time as other jobs, but that got quickly fixed in a service pack as I recall.

 

I would suggest that you read my comment carefully and in the full context. Who would put new tapes into a library when a job is running if they are not required by the job? How do you introduce new tapes into a tape library when a job is running if you are not using barcode labels? They would not be recognised until you run an inventory job which can only be run when the running job has finished. What is the point of importing a tape without barcode label? the tape is useless until an inventory job can be done on it.

How do you introduce new tapes into a tape library when a job is running if you are not using barcode labels? They would not be recognised until you run an inventory job which can only be run when the running job has finished. What is the point of importing a tape without barcode label? the tape is useless until an inventory job can be done on it.

As Craig and I both mentioned: use an import job.  Regardless of it having a bar code, BE will know that the contents of that library slot have changed.  Therefore BE will mount the unknown tape to determine what it is and to see if it can be used for the currently running backup job.

If my statement has no merit, then I assume that you think BE is defective when it asks customers to import a tape when there are no available tapes within the library?  If so, then BE has had that unfixed defect for over 15 years?  Remember, way back when, bar codes were a luxury and many libraries did not even have bar code readers (or they were an option).  Bar codes were never required by Backup Exec.  In fact, Backup Exec tolerates tapes with duplicate bar codes (unlike NetBackup) as BE really uses the media GUID as the real tape identifier, which can only be read when the tape is mounted in the drive.  Of course bar codes are highly suggested and are much more popular now.

...will a tape without a barcode not be used? I've always been led to believe it will select the tape imported and if it is available, then use it. The label would be auto-generated by BE and show accordingly in the job log. Not sure that the default behaviour would always require a barcode.

If not suitable, then it would lead to the job queueing again.

Cheers!