yesterday i updated our Lab to v12.1.
During the Update there was a warning File to Tape Jobs will start consume licences....
I know the change from v11 to 12. But in My Case it was a v12 to v12.1 update and the job mentioned in the warning is an NDMP Job. It copies Files from a Netapp Filer via NDMP.
According to the helpcenter: Support of NDMP servers backup to tape is included in the Veeam Universal License and does not consume Veeam licenses. When using a legacy socket-based license, the Enterprise Plus edition of Veeam Backup & Replication is required.
I have done some testing and backuped more than 500gb, the job does NOT consume any VUL/NAS licence. Therefore i job that this is a false positive warning in the upgrade wizard. Or are there any licence changes?
No worries regarding the NDMP jobs being licensed. NDMP backup continues to operate without capacity or instance license and requires only Veeam B&R Enterprise Plus edition.
It appears to be a bug with the upgrade notification: it is shown whenever you have a file to tape job. NDMP backup is built on top of file to tape job, thus the check works and shows you the notification whenever you have NDMP added as source, but this message is totally irrelevant for NDMP backups. We will fix it in next versions, thank you for your report!
It looks like from the response from Dima P that there is no charge and it is a bug with the configuration check
No worries regarding the NDMP jobs being licensed. NDMP backup continues to operate without capacity or instance license and requires only Veeam B&R Enterprise Plus edition.
It appears to be a bug with the upgrade notification: it is shown whenever you have a file to tape job. NDMP backup is built on top of file to tape job, thus the check works and shows you the notification whenever you have NDMP added as source, but this message is totally irrelevant for NDMP backups. We will fix it in next versions, thank you for your report!
Is the above 100% correct and there are no charges for NDMP file to tape backups?
The mentioned issue is indeed purely cosmetically and does not affect license consumption. We will fix this reporting glitch with the upcoming cumulative patch. Thank you!
Fixed in 12.1.1