I'm testing currently the new Veeam v11 feature to copy/duplicate/clone tapes. The feature is available in the GUI as also via PowerShell, but must be executed manually. Manually executed in the GUI the feature is working as expected fine.
It would be nicer, if I could to automate this part .... so directly after a File2Tape/Backup2Tape Job as a Powershell Post-Script the previously written tapes will be cloned. I made some test the Start-VBRTapeCopy PS commandlet based on the media pool, but I received no satisfied result so far like that with appropriate param depending tapes were not copied.
the aim of this small script will
1.) define source Media Pool, where the File2Tape/Backup2Tape Medias are located.
2.) getting the very latest tape in this pool to which data has been written
3.) define a target media pool for the cloned/copied tapes
4.) starting Tape Copy Job of the latest tape in source media pool including the related dependent tapes
Result: Job is starting as expected. In case there was originally one source tape it is getting cloned to the target media pool. In case the media set consisted based on several tapes, still only the latest tape is getting cloned.
So it looks currently a little like the param "-AddDependentMediumAutomatically" is being ignored. If I would copy the tape in the Veeam Management Console then the wizard is asking correctly if the dependent tapes should be added ... which actually works there.
Thanks for reply. The fact that the behavior is different when you perform the same actions on UI makes me think that we're discussing a technical issue related to the parameter being ignored. From my point of view, you should contact our support team and ask them to have a closer look at the problem.