ello David,
i am pleased with your post on this matter.
To understand a little about our situation,
We do a backup from a DAG cluster to a hardening repository with about 35 days retention time.
Then a legacy copy job to a second repository and from there with a tape backup job and this data is written once a week to a virtual tape library with a retention time of about 370 days.
This allows us to start a restore from tape in the event of a restore request from our Exchange department.
However, there are a few points to bear in mind.
Up to V11, we were able to start the restore from the individual DAG clusters and we only had to export approx. 4.5 TB from tape to our CS8800 VTL from Fujitus.
We can use a prefetch job to load the restore of the virtual tapes required by Veeam in parallel into the cache of the CS8800 VTL. This speeds up the restore from tape enormously.
However, we usually only had to have one free disk space on a repository of more than 4.5 TB.
Now with the V12 we have to restore 27 TB from the VTL without the workarand with the legacy job and also have 27 TB of free space on a repository.
So with more than 3000 mail boxes it can happen that several restore from tape jobs can be done in parallel.
This means that 27 TB restore x restore jobs also require more repository capacity for the restore.
So a restore direct from tape would of course be an incredibly great function in Veeam.
Also for the prefetch job on our CS8800 Eternus ,
A prefetch job that could automatically start the prefetch job during the restore from tape would be a great enhancement.
Since our external administrators have to be on our "proactive" action during a restore, so that we have to generate the prefetch job ourselves in a script.
prefetch is integrated into the restore from tape at Networker from Dell and also at Comvault, unfortunately Veeam is not competitive here.
i am pleased with your post on this matter.
To understand a little about our situation,
We do a backup from a DAG cluster to a hardening repository with about 35 days retention time.
Then a legacy copy job to a second repository and from there with a tape backup job and this data is written once a week to a virtual tape library with a retention time of about 370 days.
This allows us to start a restore from tape in the event of a restore request from our Exchange department.
However, there are a few points to bear in mind.
Up to V11, we were able to start the restore from the individual DAG clusters and we only had to export approx. 4.5 TB from tape to our CS8800 VTL from Fujitus.
We can use a prefetch job to load the restore of the virtual tapes required by Veeam in parallel into the cache of the CS8800 VTL. This speeds up the restore from tape enormously.
However, we usually only had to have one free disk space on a repository of more than 4.5 TB.
Now with the V12 we have to restore 27 TB from the VTL without the workarand with the legacy job and also have 27 TB of free space on a repository.
So with more than 3000 mail boxes it can happen that several restore from tape jobs can be done in parallel.
This means that 27 TB restore x restore jobs also require more repository capacity for the restore.
So a restore direct from tape would of course be an incredibly great function in Veeam.
Also for the prefetch job on our CS8800 Eternus ,
A prefetch job that could automatically start the prefetch job during the restore from tape would be a great enhancement.
Since our external administrators have to be on our "proactive" action during a restore, so that we have to generate the prefetch job ourselves in a script.
prefetch is integrated into the restore from tape at Networker from Dell and also at Comvault, unfortunately Veeam is not competitive here.
Statistics: Posted by maregg — Aug 25, 2025 7:10 am
![VA – DVD-Audio Music Sampler Vol.2 (2003) [DVD-Audio ISO]](http://imghd.xyz/images/2026/05/13/4lSo1rN.jpg)
