V7 Patch 3 duplicating tape

[scott.anderson]

Have upgraded a couple of Veeam 7 installations this week with patch3.

Both times the installation using IBM TS3100 tape libraries.

Both times Veeam has detected the old config of the library as off line (including all of the tape pools) and created a new instance of the tape library@!

The existing tape jobs then fail as the library that they are referencing is "offline".

I've worked round it by creating new tape pools for the tape jobs on the new instance and then manually adding all of the tapes back into the corresponding pools (with a catalog job to pick up the data catalog).

Just wondering if anyone else has see this? Ans is there a less time consuming way to get all of the tapes back into use?

[foggy]

Scott, this looks like the known issue, please review the following KB article: http://www.veeam.com/kb1858. Probably, the provided solution would require less effort to get back on the track.

[HussainMahfood]

thanks foggy for the link. it solved my issue.

just opened a case for this issue above.

I will close it now because of this great forum.

[foggy]

You're welcome, thanks for confirming the solution has worked for you.

[hmshih]

We have "backup to tape" problem since day one (version 7). I am wondering the Veeam software is just not working well with tape by default. anybody has the similar experiences?

[Gostev]

Your observation is correct. v7 is literally "day 1" of backup to tape functionality. As with any new functionality, it takes some time to stabilize and catch issues which are impossible to reproduce in testing. Besides, tape is unique in the way that the amount of different tape devices is totally immense (and each device will have its own problems and peculiarities). Vast majority of issues we had to deal with so far were device-specific.

At this point however (as of Patch #3), we are happy with the support load on tape related support cases, and can conclude that the stabilization period is over for the most part. The above is one of two remaining annoying issues that slipped into the latest build, we are planning to address them with the newer Patch #3a build.

Thanks!

[lwarrenkc]

The fix worked for us as well. We just applied Patch 3 and our Tape Lib did the same thing. We have a Dell TL2000 which shows up in Veeam as a IBM 3573-TL C.30. I followed the KB instructions and it cleared up the issue with no problem. Thanks for having these great posts out here. Veeam Rocks!

[veremin]

Thank you, Lee, for confirming that the fix solved the issue for you; highly appreciated.