Not sure that I got it. Could you please elaborate on what exactly are you trying to achieve?Is it possible to create a job in Retrospect which writes the related backup files from Veeam onto, with the possibility to restore them again to it's original destination if needed?
from the point of view of another backup software, Veeam backups are just files, so you can use retrspect (or any other solution) to send backup files to the tape with no issue.
dellock6 wrote: Curious, why not using Veeam also for the tape offloading?
tdewin wrote:Those file can also be easily imported by using the import functionality or by adding/rescanning the repository where they are located at. All meta data for fast importing the chain is in those VBM files in the same directory as the backup itself
pronto wrote:Sounds great. Which files are necessary for that procedure? Both vbm and vbk files related to the affected backup? The vbm file alone is not enough because the vbk file is consuming the most disk space.
pronto wrote:After I transfered those files to tape, how should I proceed to get rid of those out dated backups? Simple delete the folder with the associated vbm and vbk files and/or delete the job in Veeams frontend from the job section?
foggy wrote:You need the entire backup chain to be able to restore from any restore point in it (VBK - full backup, VRB/VIB - incremental backup, VBM - metadata file).
foggy wrote:Veeam B&R job takes care of the backups falling out of the specified retention.
pronto wrote:I guess that it is not a good idea to use a tape library or a tape drive with two seperate applications. We have quite a lot of servers we have to backup with a normal backup application because they are not virtualized.
Users browsing this forum: Google [Bot] and 36 guests