Veeam Backup & Replication 4.1.1 | Release Notes
Known Issues General • IDE VM disks are not supported for disk exclusion functionality. • File and Printer Sharing must be enabled on guest VM in order for Veeam VSS integration to function properly. • Windows Storage Server is not supported for Veeam Backup and Veeam Backup Enterprise Manager servers. • Only "Password" authentication method is supported for Linux hosts. vSphere • Processing of vSphere Fault-Tolerant (FT) VMs is not supported. • Thin-provisioned disks are replicated as thick disks. • If VM with thin-provisioned disks has one or more snapshots, then restoring “Network” mode backup of this VM will restore disks as thick. • Restore and replication of VMs from ESX 4.0 to earlier versions of ESX is not supported due to incompatible virtual hardware versions. Restore and replication of VMs from earlier versions of ESX to ESX 4.0 is supported. • VMs with IDE virtual disks cannot be processed with VCB and “vStorage API Virtual Appliance” job mode. To workaround this limitation, use any other processing modes. Backup and Replication • Virtualized Veeam Backup server using Microsoft iSCSI Software Initiator for iSCSI storage access may crash or reset while running VMware vStorage API “SAN” mode job due to interoperability issues with iSCSI Initiator. To avoid the issue, use Windows 2008 or later for Veeam Backup VM, or create Veeam Backup VM with IDE virtual disks. • Virtualized Veeam Backup server cannot backup, replicate or copy itself with jobs using vStorage API “Virtual Appliance” mode. • If ESX datastore hosting Veeam Backup VM has less free space than biggest virtual disk of backed up VM, Virtual Appliance mode fails with the insufficient disk space error. • Jobs in “Network” processing mode may fail if a VM is being migrated to another host with VMotion. Use vStorage API or VCB modes to avoid such problems. • Backup, replication and copying of VM with snapshots in Network mode only processes active snapshot tree in case of multiple trees. • Jobs in “VCB” processing mode fail when the account or password used to add vCenter or ESX server contains spaces. • “VM Copy” jobs do not support disk exclusions functionality. • Due to NFS implementation specifics on certain NFS storage, job may fail with rollback file deletion errors. Despite the error status, backups and replicas are created successfully, and required VRB files are deleted properly according to the retention policy. If you are experiencing this issue, please contact Veeam support to obtain registry mod enabling jobs to ignore this error. • Replication job with ESXi target starts failing with “An attempt was made to access the data beyond the end of the virtual disk” error after source VM disk size is increased. To work around this issue, remove replica VM, and re-create the replication job after making changes to source VM disk size. Restore and Failover • If a replicated VM is started using means other than Veeam Backup user interface, all existing restore points become unusable. • Initiating multiple concurrent operations (failover, undo failover, restore guest files) against replica VMs located on ESXi server is not recommended due to ESXi open connections limit.
Page | 8 February 18, 2010 build version 4.1.1.105