Yes, this is by design. Each primary job will always be licensed irrespective of any other primary jobs. There's no logic to try and match similarity of data sources between different primary jobs (the prospect of doing this was investigated in early as this but deemed too complex and error-prone to implement). And since it's overall a very rare scenario to backup the same data twice with different primary jobs, it was an easy decision not to go there.
In the end I think this ended up the right decision though from the perspective of Veeam's support costs: having a File to Object job running successfully does not automatically guarantee that File to Tape jobs protecting the same data will also be running with no issues, considering they target the whole different storage infrastructure type, which will cause its own support issues. And support costs is a big factor for us because we have 100% in-house, enterprise-grade support team which is thus quite expensive. Fully loaded cost of a support case is actually comparable to net to Veeam value from selling those 3 VULs in question.
In the end I think this ended up the right decision though from the perspective of Veeam's support costs: having a File to Object job running successfully does not automatically guarantee that File to Tape jobs protecting the same data will also be running with no issues, considering they target the whole different storage infrastructure type, which will cause its own support issues. And support costs is a big factor for us because we have 100% in-house, enterprise-grade support team which is thus quite expensive. Fully loaded cost of a support case is actually comparable to net to Veeam value from selling those 3 VULs in question.
Statistics: Posted by Gostev — Feb 09, 2024 3:54 pm
![Madonna – Who’s That Girl (1987/2020) [FLAC 24bit/192kHz]](http://imghd.xyz/images/2023/06/08/0093624951148_6004dceff9e1db710a9.jpg)
