I don't think that this really does what I'm after. This would only work for recent backups, it would not let me process legacy .vbk files.
If I import a .vbk in to Veeam, whilst it appears under Disk (imported), I cannot use it as a source for Backup Copy jobs.
I've got two specific instances where I could use the proposed tool to transform/reprocess .vbk files:
1. With primary backups (~31 days) using fast disk as a local repository, we have found that running backup copies to a dedupe appliance is not feasible, due to the high IO requirements of the transform operations. Simple powershell-scripted copies of the completed .vbk files ingest quickly on dudupe storage and are a good option for us, but we then have to decide whether we a) Enable compression on the primary backup to reduce footprint on the fast disk (at the expense of dedupe appliance footprint), or b) disable compression on the primary backup so that we gain efficiency on the dedupe appliance. As both types of storage are fairly costly, I'd rather have the best of both.
1. Legacy point-in-time vbk files, compressed and stored on dedupe storage in flat files. These are not associated with a current Veeam backup or backup copy job, in fact they're not in the Veeam database at all - they are imported ad-hoc if/when a restore is required. I would like to be able to uncompress these files so we can gain efficiency on the dedupe appliance.