Release Information for Proxmox Virtual Environment Plug-In v12.1.3.197

This update to the Proxmox Virtual Environment Plug-In for Veeam Backup & Replication requires:

• Veeam Backup & Replication build 12.3.0.310
  You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.
  
• Proxmox Virtual Environment Plug-In for Veeam Backup & Replication build 12.1.1.1024
  You can check the current build number within the installed applications list.

After the updated Proxmox Virtual Environment Plug-In is installed, the Plug-In build number will be 12.1.3.197.

• Support for Non-Root User Access — Enhance your security setup by integrating Proxmox VE into Veeam Backup & Replication with a sudo user instead of the root user. Enjoy greater control and protection without compromising on functionality. For more information review KB4701.
• Support for Open vSwitch (OVS) — Open vSwitch, crafted specifically for virtualized environments, delivers optimal performance and flexibility for complex infrastructures.
• Support for Smart Object Storage API — Smart Object Storage API (SOSAPI) allows object storage vendors to more deeply integrate with Veeam Backup & Replication and improve performance and user experience. Proxmox VE backup jobs will now interact with SOSAPI-enabled object storage using extended SOSAPI capabilities instead of regular S3 API.
• Support for Nested Pools — Now offering seamless integration of Nested Pools, enabling users to manage and back up virtual machines within nested environments efficiently. 
• Backup engine enhancements — multiple threads are now utilized to read data, resulting in better performance.

• When restoring backups from different hypervisors, the virtual machine's OS type is set as 'other.'
  
  Now, when restoring from other hypervisors to Proxmox VE (PVE), the restored machine will have the correct OS type, reflecting that of the original backup.
• Backups of powered-off VMs with PCIe passthrough devices fail.
  
  Now, if a PCIe passthrough device is skipped from processing, the job will not process these devices in the backup configuration. As a result, such devices will not be restored as to avoid any conflicts. Such devices should be added manually after the restore.
• Backup of linked clones only processes the base disk without capturing delta changes.
  
  Now, backup jobs will fail if a VM is a linked clone, preventing false assurances of successful backups when only the base disk is backed up without the delta.