VBR11a : Tape Copy Job aborts during Auto-Clean Tape Device event

[ThierryF]

Hello,

I am running VBR11a+SecPatch. My Vmware Vm Backups are taken thru Veeam VBR Backup
job to local scale-out repository and, later, a daily Tape Copy job put on tape all generated
VM Backups using an Oracle SL150 LTO7 equiped tape library.

My Oracle SL150 Tape lib is configured with Device Auto Cleaning at Tape Library HW level.
A set of dedicated library slots contains LTO Cleaning Tape.

When a drive requires cleaning, as soon as Veeam ejects the Tape Media from the drive,
the library automatically load Cleaning Media before continuing its operations.

Most of the time, this works fine when the cleaning occurs at the end
of a TapeCopy Job, when media is unloaded from tape drive and when Veeam
does not require any other media to be loaded into a drive.

But, when a Cleaning is required during a Tape Copy job, for sample because the in-use media
is getting full, I see my Tape Copy job to abort with error(s) such "(...) The semaphore timeout period has expired. DeviceIoControl (...)"
because operation Veeam started takes more time to complete or because
MediaChanger reports busy status due to cleaning operation (out of Veeam Control) in progress.

When this occurs, after Auto-Cleaning operation to be completed, restarting tape copy job
ends like a charm.

Any fix/workaround for such an issue such increasing semaphore timeouts ?
This should be known behaviour ...

Thanks for ideas. I will open a case later if needed.

Th

[Mildur]

Hello Thierry

Have you tried Veeams automated drive cleaning feature? Veeam will take care of the cleaning (if necessary) and starts the tape job after the cleaning process has finished.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[ThierryF]

Hello Fabian,

Thanks for your reply. I cannot turn on Veeam-based cleaning because the physical library
in software-partitionned with another backup solution, each partition having its own drive set
and slot range.

Turning on Veeam-based cleaning, I will need to unset Hw based autocleaning (that is
valid for both library partitions) and will have to decicate 2 sets of cleaning tapes,
one per lib partition and monitor cleaning in both backup solution...

When backup solution #2 will be shutdown, the 2nd lib partition will be san-zoned
to my second scale-out repository, as a second library to extend my tape capacity
and will use WORM Mediums.

Thanks for suggestion

Th