Why do jobs wait for a tape drive to be available to create the backup map?

[stewsie]

Hi

Interested to know why Full tape backup jobs need to wait for a tape drive to be available before it can create the full backup map which I thought was written to the repository where the backup files are located? Or am I getting confused with the purpose of the vsb file?

Why can this file not be created as soon as the job is scheduled to run so that when a tape drive is available time is not then wasted locking a tape drive to create the full backup map?

Cheers

[veremin]

This is more like a by design behaviour. .VSB files get created rather fast, so, there would not be any noticeable improvements, should they be created in advance (before tape infrastructure is ready).

Or you experience any issues with the current implementation?

Thanks.!

[stewsie]

Thanks for the reply. For large full backups the creation of the backup map can take a number of hours which is why I was asking as this just adds delays to the tape job

[veremin]

The described behaviour looks unexpected, so may I ask you to open a ticket and provide its number here? We will investigate the case internally and see whether there is a room for further optimizations. Thanks!

[stewsie]

03380837 opened and logs added to the case

[veremin]

Passed it to QA and DEV teams for further investigation. Thanks!