0 Directories and 0 files backed up successfully

[kennocha]

It is not going offline, and as I said I have two identical sites, doing the exact same thing. If I restart the job by hand it runs off on its merry way.

[Dima P.]

Stephen,

Any chance you checked your tape library logs?

[kennocha]

Finally had time to check the log.

The logs are clean and error free.

We used to use symantec and never had problems with this portion of things. Just everything else

[Dima P.]

Thank you.

Then, I guess, we have to go back to the very start: could you please elaborate what tape library, medium changer and tape drives you are using and how the connection to VBR is configured (any chance it is cofigured via iSCSI)?

[kennocha]

Both sites have a Dell PV124t. One is LTO5, the other is LTO 6.

Both are using external SAS to the physical veeam server they use.

[Dima P.]

Hello Stephen,

Thank you for details! Could you, please, clarify what your repository and how it is connected to Veeam server? Thank you.

[kennocha]

The repository and everything is running on one supermicro server.

[Dima P.]

Stephen,

Thank you, for me know it does not look like a connectivity issue between library/repository and VBR so, please, keep working with the support team - I noticed that they asked you to reconfigure the tape jobs from scratch some time ago, probably they need a new portion of logs to investigate it further. Thank you.

[macademy]

I seem to be having the same issue, did you ever get a resolution to this?

We've had Veeam for about a month now and it runs perfectly most of the time. But the secondary target job to tape has failed twice this month with the error "This server requires retry, postponing".

It looks as though the backup job that has just completed is keeping a lock on the backup file which is preventing it from being backed up to tape.

I have an open support case for this.

[Dima P.]

Ian,

Yes it might be just configuration issue, as all the bugs we had in previous versions related to this problem were fixed. Please continue to work with the support team, and if possible post here the case ID so we could track your case. Thank you.

[macademy]

Case ID is 00693579.

Thanks