Dear Veeam community,
Here is my "official" feature request: Authorize multiple jobs to request tapes from the same media pool. This comes after weeks of investigation with support (#00850675), and seems the minimal requirement to support "big" tape jobs, ie: more than 12TB in less than 24 hours.
Problem: When a job starts, it locks the media pool and will only release it when finished. Another job that could run on another drive in the same library can not request tapes from the same media pool until first jobs is finished, greatly limiting the throughput to only one drive. The only alternative is to add more media pools, adding far too much complexity and fragmentation in the library.
Why is this needed: As Veeam is not implementing tape multi-streaming (ie: writing the same job to multiple tapes in parallel), the only alternative for "big data volumes" is to run multiple jobs in parallel on individual drives. Managing more jobs already adds complexity, but fragmenting the media pools decrease efficiency dramatically and totally "disconnect" the pools from what they should be (ie: Daily, Weekly, Monthly...).
Expected result: A job should not lock the media pool but only the tape it is currently using. Other jobs should be able to claim another (free) tape in the same pool.
My experience on this: I have totally changed my strategy because of tape issues...
6 month ago, I had 3-4 jobs backing up 400 VMs to 2 big repositories. It was easy to manage and error prone: basically we did backup everything, and were sure no VM was left away. And then we started to implement tape "for real"...
Fast forward 6 months: I have 15 jobs, backing up to 7-8 repositories. We have also added copy jobs and their own repositories as a "buffer", because tape jobs were locking the main repositories thus preventing production backups to run. Everything is now more complex, our storage usage as exploded and it definitely requires more time to manage, but my VM count and volume increased only by 5% and this makes it hard to explain to management... And still can't come up with a viable tape strategy...
We need a solution, as 12TB in 24 hours (basically 1 LTO6 drive full speed) does not seem "that" big in my opinion and set the bar quite low for tape users.