Tape ejected after first server

[corsbj]

We have a job that backs up data from 6 servers, but it asks for next tape after having backed up the first server. We're using LTO 6, so there's 2.4TB on each tape.
I've enabled the eject tape on completion option, but I don't hope that's what does this?

[Shestakov]

Hello Simon,
That sounds strange. Do these 6 servers backed up to the same or different files? What is the size of the file(s)?
By the way, what product version are you at?
Thanks!

[corsbj]

I'm not sure what you mean by backup to same or different files?
If I look at the job status, it's transmitted 255GB data when the tape is ejected. If it matters, they're SQL backup files, so pretty large ones.
We're running version 9.0.0.1491.

[Shestakov]

I meant source backup job(s) of those 6 servers. Does it backup all 6 VMs in the same job to a single file?

[corsbj]

It's a file backup, not a VM backup.

[Shestakov]

Could you clarify it? Is your primary job "file copy job" and secondary is file to tape?
Thanks!

[corsbj]

The primary jobs make VM backups of most of our servers to disk. Due to company policy, I need to put some of the content of our fileserver on tape so they can be stored off-site.
The fileserver isn't part of the VM backups I do, since some of the data is sensitive and need to only be on that server or the tapes.
I've configured the job through the "File to tape" wizard in the Tape infrastructure menu.

[Shestakov]

Thanks for the clarification, Simon.
Check if Create new media set for every backup session option is set. You need to change it if you don`t want to use new tape for each backup run.

[corsbj]

The problem is it ejects the tape after the first server, not after the first complete run.
I've removed the "Eject tape on completion" option and it now seems to be running fine.
I'll let you know how it turns out.

I'm going to enable the "new media set for every session" option I think.
We do a full backup every day anyway, and archive the last tape of the month every month.

[corsbj]

The job completes with no problems now.
I removed the "eject on completion" option and enabled the "new media set for every session". Seems to have done the trick.

[Shestakov]

Thanks for updating, Simon!

The problem is it ejects the tape after the first server, not after the first complete run.
I've removed the "Eject tape on completion" option and it now seems to be running fine.

I`ll ask our QA team to double-check the behavior.
Thanks!

[Shestakov]

Simon, that may be a bug, for closer investigation logs are needed. Could you contact Veeam technical support for further inquiry?
Thanks!

[Berniebgf]

May be seeing a similar issue here....

Tape job will not re-leverage existing tape after ejection from library drive.... (Tape job has multiple disk backup jobs as source)
"Insert a valid tape into the library, oldest retained tape XXXX, last writeen tape XXXX" this despite tape available and had just been used to backup the first disk based job...

Have another thread open with some clarification first..

thanks

BT

[Shestakov]

Bernard, if you have a support case number for that issue, please post it here.
Thanks!

[Dima P.]

To clarify, you guys are using Standalone Drives, right?

[corsbj]

I'm using a standalone drive on another server, yes.

[Dima P.]

Hi guys,

There is a private fix for the described issue with standalone drives. In order to get a fix, kindly, reach our support team. Thanks.