Veeam_Backup_4_1_2_Release_Notes
Veeam_Backup_4_1_2_Release_Notes
2 | Release Notes
Page | 1
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
New Features
The following is a list of new features introduced in the Veeam Backup & Replication 4.1.2:
• Support for VMware vSphere 4.1. Veeam Backup & Replication now supports
VMware vCenter Server 4.1 and VMware ESX(i) 4.1.
• Virtual Appliance mode enhancements. A number of HotAdd reliability
enhancements (see the Resolved Issues section for more information).
The following is a list of new features introduced in the Veeam Backup & Replication 4.1.1:
• Support for Exchange 2010. Veeam Backup & Replication VSS integration now
supports application level quiescence of Microsoft Exchange 2010 servers.
• Snapshot removal warning. Failure to remove snapshot is now classified as warning
event, as opposed to informational. This behavior can be disabled with registry mod.
• Support for outdated VMware Tools. Veeam Backup & Replication software jobs
will now attempt to process VM even if VMware Tools are outdated with the
corresponding warning is logged in the session results, instead of skipping such VMs
completely. This should allow larger customers to perform VMware Tools upgrades
on VMs in stages and still get backups created.
The following is a list of new features introduced in the Veeam Backup & Replication 4.1:
• Replication to ESXi. Veeam Backup & Replication now supports replication to the
paid/licensed version of VMware ESXi.
• SNMP notifications. New option for per-job and per-VM backup status notification
allows easy integration of Veeam Backup activity into your legacy monitoring system.
• Regulatory compliant backups. A new standalone restore utility can be put on a
tape with your backup data to allow for VM restore independent of the Veeam
Backup & Replication software.
• vRDM CTK support. ESX4 changed block tracking enabled processing is now
supported for virtual raw device mapping (vRDM) virtual disks.
• Multi-OS file level restore improvements. Multi-OS FLR virtual appliance no longer
requires DHCP to be present in the environment, and uses NAT mode instead for
better compatibility and increased security. Legacy DHCP mode is still available with a
registry mod.
• Enterprise Manager daily statistics improvements. In addition to summary of last
sessions for all jobs, the daily summary email now includes summary of all sessions in
the past 24 hours.
• Support for rotated media. Veeam Backup can now be instructed to automatically
re-create full backup file if it is missing from the backup storage to better support
scenarios with rotated media as backup target. This behavior can be enabled with a
registry mod.
• Customizable timeouts. Default Veeam Backup operations timeout (100 sec) can
now be customized with a registry mod to allow for better support of certain
scenarios such as backup to remote Linux server.
• vStorage API components update. vStorage API for Data Protection redistributed
modules update to version 1.1.1 for added reliability.
Page | 2
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Resolved Issues
The following is a list of issues resolved in the Veeam Backup & Replication 4.1.2:
Backup and Replication
• Workaround for ESX4 changed block tracking issue with snapshot reversal. For more
information, please refer to VMware KB, and this topic.
• Failed or terminated Virtual Appliance mode jobs leaves the drive mounted inside the
backup VM, which prevents correct snapshot removal.
• Virtual Appliance jobs may fail to process any VMs on certain backup servers due to
invalid SCSI PortId configuration registry settings.
• Under certain circumstances, jobs may fail to correctly initiate automated retry cycle.
• Replication job may fail while processing -aux.xml file.
• Running job can sometimes be incorrectly marked as Failed with the “Job has failed
unexpectedly“error logged in the sessions' history while the job is still running. This
does not affect job execution, and backup file is created properly.
• vCenter Server events logged by Veeam Backup contains incorrect job status
information, always showing jobs as failed.
Veeam VSS
• On certain Windows 2008 configurations, network connection used for Veeam VSS
processing may remain open after backup completes.
Restore
• VM may fail to start automatically after failover with the “The operation is not allowed
in the current state” error.
Enterprise Manager
• Enterprise Manager may fail to collect data from Veeam Backup server having
multiple NIC in different subnets.
The following is a list of issues resolved in the Veeam Backup & Replication 4.1.1:
Backup and Replication
• Processing virtual machine with thin disks that was previously restored from backup
file produced by changed block tracking enabled job may produce inconsistent
backups or replicas.
• VM processing may fail with the following error for ESX hosts which names start with
numbers: “Cannot convert a string containing an (Ipv4) Internet Protocol dotted address”
• Starting multiple jobs at the same time may result in some jobs remain hanging in the
“Starting” status.
Restore
• VM failover may fail after sequential failovers of multiple VMs have been performed
on the same ESXi host.
• Running multiple jobs, failover/undo failover operation, or file level restore
operations against replica VMs on the same ESXi host may cause running out ESXi
host connection limit and crashing Veeam Backup agent.
• In environments with vCenter server upgraded from version 1.x, VM registration
happening as a part of full image restore or replication fails with the following error:
“Child VM for object your-infrastructure-object was not found”.
Enterprise Manager
• Next Run column on the Jobs tab does not have sort functionality implemented. This
issue is resolved for new Enterprise Manager 4.1.1 installations only.
Page | 3
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
The following is a list of issues resolved in the Veeam Backup & Replication 4.1:
Backup and Replication
• Auxiliary snapshots created by ESX host may not be removed in vStorage API “Virtual
Appliance” processing mode.
• “Consolidate helper” snapshot may fail to remove when vStorage API job is manually
stopped.
• Replication and backup jobs hang if SSH connection to the target server drops.
• Processing VMs running on free ESXi 3.5 hosts with the following error: "Session not
authenticated".
• Depending on Veeam Backup server Internet Explorer proxy settings, jobs may be
failing with the following error: "407 Proxy Authentication Required".
• VM with VMX-files containing commented strings cannot be processed.
• Backup results cannot be set for VMs located on standalone ESX server.
• Veeam VSS fails to process Microsoft Windows 7 VMs with the following error:
“windows7Guest is not supported”.
Restore
• Replication and full image restore process in the service console agent based mode
does not eagerly zero empty VMDK blocks, resulting in disk consistency check errors
for certain Linux file systems.
• Full image restore process may fail with the following error: “Child VM for object your-
infrastructure-object was not found”.
Enterprise Manager
• Under certain circumstances, collecting data may fail with the following errors: "Illegal
characters" or "Semicolon expected".
• “Last 24 hours” Enterprise Manager page statistics produces incorrect summary
statistics if some jobs run longer than 24 hours.
PowerShell
• The “SetResultsToVmAttribute” attribute in the “VBRJobOptions” commandlet is not
implemented.
Upgrade
• Upgrade of v3 backup and replica storage file format may hang for large files with the
job status displaying “Repairing backup from previous rollback” at 0%.
• Upgrade of v3 backup and replica storage file format may fail if the latest job run
before upgrade was aborted or terminated.
Page | 4
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
System Requirements
VMware Infrastructure
Platforms
• vSphere 4
• Infrastructure 3 (VI3)
Hosts
• ESX(i) 4.x
• ESX(i) 3.x
• Server 2.0 (experimental support)
Software
• Virtual Center 4.x (optional)
• Virtual Center 2.x (optional)
Virtual Machines
Hardware
• All types and versions of virtual hardware are supported, except independent and
physical RDM disks (virtual RDM disks are supported). You can use disk exclusion
functionality to exclude some of the unsupported disks from backup/replication.
• MBR disk partition table is required for file-level restore, GPT disks are not supported.
OS
• All operating systems supported by VMware are supported.
• Microsoft Windows VSS integration is supported for Windows XP (32bit only),
Windows 2003, Windows 2008 and Windows 2008 R2.
• Built-in file-level restore supports Microsoft Windows file systems only (NTFS, FAT and
FAT32). Dynamic disks support is limited for built-in file level restore.
• Multi-OS file level restore wizard supports the following guest OS and file systems:
Supported File Systems
Guest OS
Linux ext
ext2
ext3
ext4
ReiserFS
JFS
XFS
Unix JFS
XFS
UFS
BSD UFS
UFS2
Mac HFS
HFS+
Windows NTFS
FAT
FAT32
• Multi-OS file level restore supports Linux LVM (Logical Volume Manager) and
Microsoft Windows LDM (Logical Disk Manager) dynamic disks.
Page | 5
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Software
• VMware Tools
Page | 6
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Backup Target
Backup can be performed to the following targets:
• Storage Area Network devices (Veeam Backup server must be connected directly into
SAN fabric and the corresponding volumes must be seen in the Microsoft Windows
Disk Management snap-in).
• Network Attached Storage devices able to represent itself as CIFS (direct operation) or
NFS share (storage must be mounted on ESX host or Linux server).
• Direct Attached Storage connected to Veeam Backup server, including USB drives.
• Any x86/x64 Windows or Linux based computer (or ESX host) meeting the following
minimum system requirements below:
Hardware
Processor: x86/x64 (using faster processors improves backup performance when using
Linux targets due to backup compression being offloaded to the target server).
Memory: 256 MB RAM.
Hard Disk: Using faster local storage (fast high-RPM hard drives, RAID0 configurations)
generally improves backup performance.
Hard Disk Space: Sufficient disk space required to store the backup files according to
the selected retention policy.
Network: 1Gb/sec recommended due to backup performance considerations.
OS
o Microsoft Windows
o All major Linux distributions
o ESX 3.x
o ESX 4.0
Replication Target
Hosts
• ESX(i) 3.x
• ESX(i) 4.x
Page | 7
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | 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.x 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 must not be used to backup, replicate or copy itself
with jobs using the 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.
Page | 8
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Page | 9
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Page | 10
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Page | 11
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Licensing
Veeam Backup is licensed per CPU Socket ("CPU Sockets") for each Managed Server. Managed
Server is defined as VMware ESX(i) server that is backed up, recovered, collected data from or
otherwise managed by the software. "CPU Sockets" means a single, physical chip that houses
not more than six (6) processor cores on the managed server.
The trial license key is sent to you after registering the product with Veeam Software at:
http://www.veeam.com/vmware-esx-backup/download.html. After registering the product
you will receive a trial license key. The trial license is valid for 30 days from the moment of
registration.
To obtain a full license key for the desired number of sockets, refer to
http://www.veeam.com/buy-end-user.html
The full license includes a one-year maintenance plan. To renew your maintenance plan,
please contact Veeam Customer Support at: [email protected].
Page | 12
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Technical Support
We offer email and phone technical support for customers on maintenance and assistance
during the evaluation period. For better experience please provide the following when
contacting our technical support:
• Information about operating system and database you are using.
• Error message and/or accurate description of the problem.
• Log files. To browse to the log files, select Help > Support Information... from the
main menu.
To submit your support ticket or obtain additional information please visit
http://www.veeam.com/support.html
Hint: Before contacting technical support, you may be able to find a resolution to your
issue at Veeam community forums at: http://www.veeam.com/forums.
Page | 13
August 4, 2010 build version 4.1.2.125
Veeam Backup & Replication 4.1.2 | Release Notes
Address 6479 Reflections 400 Thames Level 21 & 22, Evert van de
Drive, Suite 200 Valley Park 201 Beekstraat 310,
Columbus, Ohio Thames Valley Miller Street 1118 CX
43017 Park Drive North Sydney Schiphol
Reading, NSW 2060, Centrum
Berkshire RG6 Australia The Netherlands
1PT
Phone +1-614-339-8200 +44 (0) 1276- +61 2 8014 7476 +31(0)20 654 18
804-501 05
Page | 14
August 4, 2010 build version 4.1.2.125