Hi, being unable to copy backups doesn’t sound right, the point of immutability is you can read as many times as you want but only write once. So you should still be able to backup to tape.
Question, how comes you’re using files to tape instead of machine backup to tape? You can get Veeam to write all of your backups to tape as they come through instead of in a weekly batch
Just for two cents, I ran into a customer script that was copying out vbk files once a year, it worked before but when they changed their repo to immutable it stopped working. Mind you I did not investigate much because I told them better to stay away from things like that and let Veeam handle everything automatically. Also won’t file to tape jobs now get hit with that new License change? i.e they are treated like NAS backups so $$$$.
Also won’t file to tape jobs now get hit with that new License change? i.e they are treated like NAS backups so $$$$.
Veeam Backup files are automatically excluded from consuming such licenses.
Best,
Fabian
Also won’t file to tape jobs now get hit with that new License change? i.e they are treated like NAS backups so $$$$.
Veeam Backup files are automatically excluded from consuming such licenses.
Best,
Fabian
ah ok. So if I am doing a file to tape job but the files are .vbk and .vib then I am alright? That is very good to know. Thanks @Mildur
Correct. All Veeam backup files are excluded from license consumption in File to Tape backup jobs. We have the complete list in our user guide:
Instance Consumption for NAS Backup and File to Tape Jobs - User Guide for VMware vSphere (veeam.com)