Skip to main content
Question

File to Tape full backup how about add automatic mark tape as free


Forum|alt.badge.img+1

I have to remember to get into Tape Infrastructure and mark tape a free to clear it.   How about add the feature into the tape backup job?   Every other backup I ever used from Arcserve, Symantec, Linux based had this feature.   

10 comments

Tommy O'Shea
Forum|alt.badge.img+5
  • Veeam Legend
  • July 3, 2026

I don’t believe there is any setting for automatically clearing the contents of a tape.

If a tape in a media pool’s retention is expired (and all tapes dependent on it), then it will be used in subsequent backup jobs automatically. This is only within the same Media Pool, it does not get moved to the Free Media Pool automatically.


CMF
Forum|alt.badge.img+8
  • Veeam Legend
  • July 3, 2026

Hi ​@SCSIraidGURU ,

My Script that i have written about in this article takes expired Tapes and put them back into the free Pool. If you let it run as an scheduled job it would be some kind of automatism I guess.

 

Regards

Chalid


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • July 4, 2026

I know it doesn’t clear a tape for full backup to tape.   I am asking them to add it to the job.    


matheusgiovanini
Forum|alt.badge.img+9

Hi,

I understand your point as a feature request, and I agree that automation can be useful in some tape environments.

However, I think automatically marking tapes as Free from the job would need to be handled very carefully. The Media Pool retention and media set cycle exist to keep tape rotation under control. This helps the administrator track media usage, understand if the current number of tapes is enough, plan tape-out/offsite rotation, and identify when new tapes may be needed.

It also helps with operational control in cases where tapes become bad, get stuck in the drive, are protected, or when the environment has more than one Media Pool. Moving or freeing media automatically could create confusion or even risk overwriting data that should still be restorable.

Another important point is that expired media can still be used for restore until it is overwritten. So keeping the media inside the correct Media Pool after expiration is also an extra safety layer.

For me, manually marking a tape as Free is more of an administrative action than something the backup job should do automatically. Maybe it could exist as an optional setting, disabled by default, with a very clear warning, but the safest approach in most cases is still to manage this through Media Pool retention and media set configuration.


matheusgiovanini
Forum|alt.badge.img+9

Just to add one more point:

If the goal is to automatically move expired tapes back to the Free Media Pool so other Media Pools can use them, maybe it is also worth reviewing the Media Pool sizing and tape rotation design.

When a tape expires, it is available to be overwritten, but it can still be used for restore until it is actually overwritten. This is important because, in many tape chains, the first tapes to expire may contain full backups, and those tapes can be essential for restoring the following backups in that set.

So even if the media is expired and technically reusable, moving it automatically to the Free Media Pool could make it easier for another Media Pool/job to overwrite it sooner than expected. That is why I believe this kind of operation should remain under administrative control, or at least be protected by very clear warnings if implemented as an optional feature.

In my opinion, if this is needed frequently, it may indicate that the Media Pools, retention, or number of tapes should be reviewed.


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • July 4, 2026

In arcserve and Symantec it was a check box in the tape job to erase the tape before running the job.   It was not mandatory, you had to check it.


matheusgiovanini
Forum|alt.badge.img+9

In arcserve and Symantec it was a check box in the tape job to erase the tape before running the job.   It was not mandatory, you had to check it.

Yes, I think the difference here is not only the erase option itself, but the logical media structure behind each product.

In Veeam, a tape assigned to a Media Pool remains tied to that Media Pool. When the tape is expired and online, the same Media Pool can select it again for a future tape job when free media is required, usually reusing the oldest expired tape available first. The tape will then be overwritten according to the retention logic.

From a practical point of view, this is close to the Short Erase concept, because Short Erase does not physically erase all data from the tape, it wipes the tape header, where the information about the data stored on the tape is kept. But the important point is that this does not automatically move the tape to the Free Media Pool or make it available to other Media Pools or jobs.

So I understand that Symantec or Arcserve may expose this kind of erase option differently, but the media handling structure is different. In Veeam, automatically erasing or moving expired tapes between Media Pools could affect retention, media sets, and restore planning. That is why I think this kind of operation would need strong warnings and clear administrative control if implemented.

 


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • July 4, 2026

Each tape is assigned to that media pool for the job.   I use the same tape each job.


matheusgiovanini
Forum|alt.badge.img+9

Each tape is assigned to that media pool for the job.   I use the same tape each job.

Yes, I see your point. I think we may be talking about slightly different scenarios now.

If the same tape is reused by the same job, or even by different jobs using the same Media Pool, that makes sense and it is expected behavior when the tape is expired/available according to the retention rules.

My original point was more about the initial idea of automatically erasing/freeing/moving an expired tape from one Media Pool so it could be used by another Media Pool/job. That is the part I see as more sensitive in Veeam, because tape ownership, retention, media sets and restore planning are tied to the Media Pool structure.

So yes, I understand that other products may expose this erase/reuse workflow differently, and that can make sense in their own architecture. I just think that in Veeam this needs to be handled carefully, with clear admin control and warnings, because the media handling logic is different.

Anyway, I think we are probably looking at this from different product backgrounds, which is completely fine. I just wanted to clarify the Veeam behavior and the risk I see with automatic movement/erase across Media Pools.


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • July 5, 2026

Veeam seems to be moving from tape to their cloud solution.   Claude AI erased a companies servers, backups to cloud.  Wiped all their data.   

In April 2026, an autonomous AI coding agent powered by Anthropic's Claude Opus 4.6 model accidentally deleted the entire production database and backups of a software startup named PocketOS. The automated wipeout took exactly nine seconds to complete, resulting in a severe 30-plus-hour outage for the company's car rental clients. [1, 2, 3]

Once my tapes are done and pulled from the drives, AI can't touch them.