That should be no problem if you have configured the standard backup mode (forward incremental with synthetic full or active full). I guess I'm hoping Veeam has some sort of write up on how to minimally introduce a tape infrastructure like this. vbk file here and there based on how the original backup job runs.Īdditionally, when it comes time to overwrite a tape, if I overwrite the wrong tape, the whole backup chain could be lost if any required vbk or vib is erased.Īside from upgrading to "Enterprise" for Veeam integrated backup-to-tape functionality, what are my options? I really don't want to have to manage my tapes "out of band" like this :/ vib files all over the place and a restore could be a nightmare.
Originally, I was hoping to be able to put in one tape each day of the week (or even GFS), and file-to-tape can do incremental backups, however, with this rotation, I'll have incremental. Therefore, what are the best practices to integrate a tape solution into an existing backup infrastructure with only file-to-tape functionality? It seems I need to add my VBR backup repository again as a "file share" and then back that up to get Veeam backup files on tape. I only have a VBR "Standard" license which means my shiny new Quantum LTO-8 drive and tapes can't barely do anything since file-to-tape is the only supported tape backup method.
0 kommentar(er)
