Pre-Installation Setup for Veeam Backup & Replication > Known Issues and Limitations (Veeam Backup & Replication)
  
Version 10.3.00P13
Known Issues and Limitations (Veeam Backup & Replication)
• Backup File Names
Veeam allows a backup job to have different backup and retention policies. For certain configuration types such as, Synthetic Full Backup or Forever Forward Incremental Backup Retention Policy, one of the *.vib files is renamed as *.vbk at regular intervals by Veeam. In APTARE IT Analytics, the Veeam Data Collector retrieves backup information for a specified period of time at regular intervals. This set of backup information may contain file names with a *.vib extension (instead of *.vbk) and display in the Job Details report.
For details about the various use cases, see https://helpcenter.veeam.com/docs/backup/vsphere/backup_files.html?ver=95.
As you compare APTARE IT Analytics reports to native Veeam reports, if there are discrepancies in the files, you can force a historic data collection to examine the details. Additionally, when validating APTARE IT Analytics reports against Veeam reports, focus on the file names and not the file extensions.
• Successful Endpoint Backup Jobs Displaying Size = 0.00 Bytes
Occasionally, Veeam will create additional maintenance jobs such as Full backup file merge completed successfully and there is not a data size associated with the job. These jobs will be displayed with a status of Successful but without an associated data size.
• Veeam Collection does not support collection of jobs or backup data which are based on VMware Tags.