v.Eremin wrote:If a media doesn't belong to existing or free media pool, a tape job pointed to the said media pool won't be able to use it. Thus, you need to move media either to the given or free media pool manually.
Do you use barcodes?
That's what I would have thought, hence the email alert. But then why does it move it to the free pool itself and start using it?
No. We've only got a single tape drive, no auto loader, and assumed it can't read barcodes. Is there a possibility that it could? I'm guessing not.
Does it store the name on the tape itself, on the cartridge chip, or only in Veeam's database? Is there a risk it'll ever get the names wrong?
Dima P. wrote:According to my test results, it stores the name in local catalogue only, so proper labelling and naming the tapes properly within one backup console is almost a mandatory.
unique serial number or something
Is there a chance it will be wiped after erasing the tape, causing Veeam to become confused about which name I've given it?
Dima P. wrote:Well, after you are erasing the tape media it should keep the given name (since its linked with this ID), however, when you are Removing tape media from catalogue – it loses the links between media name and internal ID.
This is actually a good catch, thanks for bringing our attention to this scenario. I believe the best way in terms of blind tape management is to somehow keep the given name on the media – will discuss with the team how this could be accomplished. Thanks again!
This is a problem that cannot happen with barcoded tapes and loaders, correct?
Would I be right in assuming that emphasis is given to using Veeam with loaders?... I'm hoping we don't come across more things that are poorly supported with standalone drives.
Dima P. wrote:Mind me asking before I answer, why do you care about the given tape name when the data itself was erased? Is this somehow referring to your internal media rotation and labeling?
If the internal id is written to the tape, how does it retain it after erasing? Does it rewrite it? Is the cartridge memory not involved at all?
Users browsing this forum: Yahoo [Bot] and 9 guests