Hello everyone,
We are planning to expand our current tape infrastructure by adding an expansion module to our existing LTO-8 tape library.
Our current setup consists of 2 tape drives and 40 slots. After the expansion, we will have a total of 4 tape drives and 80 slots. The tape drives use Fibre Channel (FC) to transfer data from the primary server.
Reason
Our RTO and RPO have increased significantly, as we are now transferring around 200 TB of data per week. We need to improve them.
I also have the feeling that our current logical infrastructure design may not be the most efficient. We are currently using Veeam Backup & Replication to perform our backup-to-tape operations.
Current
We currently have a single Standard Media Pool containing all our tapes. None of them are WORM tapes.
We use a single tape job with no incremental backups, which copies only the weekly full backups to tape. Parallel processing is enabled in the job, allowing it to use both LTO-8 drives simultaneously. The tapes are labelled both logically and physically according to their retention category: weekly, monthly, and yearly. We also label each tape with a DIMO. We do not use quarterly tapes.
Our current process is entirely manual. We select and insert different tapes depending on the occasion, rather than having an automated process. To be honest, I really dislike our current labelling system. All tapes have the same retention settings in Veeam. We manage retention manually by moving the tapes and storing them physically for the required period.
Proposed
Since we will have 80 slots available, I was thinking about using the additional capacity to keep the weekly tapes and, potentially, future daily tapes loaded in the library, as these will be the tapes we use most frequently. Our weekly tape rotation requires a total of 64 tapes, so this would allow us to keep them in the library instead of having to move around 16 weekly tapes to our off-site vault.
However, this raises my first question: Is it recommended to leave tapes loaded in the library when they are not actively being used?
I understand that these are not WORM tapes and that, in the event of a cyberattack, they could potentially be exposed to overwriting. One idea I had was to use the physical write-protect switch on the tapes to prevent them from being overwritten while they are idle.
On the other hand, I have also considered the risk of a physical incident in the data centre, although we consider the likelihood of a fire or flood to be relatively low.
Is this a reasonable approach, or is it strongly recommended to remove written tapes from the library and store them in an off-site vault?
For those managing larger tape libraries with many slots, how do you typically handle this? Do you leave tapes stored in the library and use the available slots as intended, or do you still remove written tapes manually, as we currently do?
From a Veeam configuration perspective, I am considering the following changes:
- Media Pool: Use a single GFS Media Pool containing all retention types, excluding quarterly tapes.
- Tape labelling: Eliminate our current logical and physical labelling system and rely entirely on barcodes to identify the tapes.
- Tape job configuration: Keep parallel processing enabled and configure the job to use all four tape drives.
- Media Vault: Set up a Media Vault in Veeam to better organise and track the tapes stored outside the library, as I understand this functionality is available in Veeam.
These changes would be implemented progressively as our tape operations evolve, rather than all at once.
Do you have any recommendations regarding this approach? Are there any potential pitfalls or configuration changes that you would advise against?
Thanks!!