Veeam Backup 6 1 Release Notes
Veeam Backup 6 1 Release Notes
1 RELEASE NOTES
This Release Notes document provides last-minute information about Veeam Backup & Replication 6.1, including system requirements, installation and upgrade procedure, as well as relevant information on technical support, documentation, online resources and so on. The current version of Veeam Backup & Replication 6.1 is available for download at: http://www.veeam.com/vmware-esx-backup/download.html starting from June 4, 2012. See next: System Requirements Known Issues Installing Veeam Backup & Replication Uninstalling Veeam Backup & Replication Upgrading Veeam Backup & Replication Licensing Updating Veeam Backup & Replication License Technical Documentation References Technical Support Contacting Veeam Software
System Requirements
VMware Infrastructure
Platforms Hosts ESX(i) 5.0 ESX(i) 4.x ESX(i) 3.5 vCenter Server 5.0 (optional) vCenter Server 4.x (optional) Virtual Center 2.5 (optional) vSphere 5.0 vSphere 4.x Infrastructure 3.5 (VI3.5)
Software
Unix
Multi-OS file level restore supports Linux LVM (Logical Volume Manager) and Microsoft Windows LDM (Logical Disk Manager) dynamic disks. VMware Tools (optional)
Software
Software
Software
Software Microsoft SQL Server 2005/2008 (SQL 2005 SP4 Express is included in the setup) System Center Virtual Machine Manager 2008 R2 Admin UI (optional, to be able to register SCVMM 2008 servers with Veeam Backup & Replication infrastructure) System Center Virtual Machine Manager 2012 Admin UI (optional, to be able to register SCVMM 2012 servers with Veeam Backup & Replication infrastructure) Microsoft .NET Framework 2.0 SP1 (included in the setup) Microsoft PowerShell 2.0 or later (optional)
For Hyper-V off-host backup proxy server, only the following operating system is supported:
Server Software
Client Software
Backup Target
Backup can be performed to the following targets: Direct Attached Storage (DAS) connected to the backup repository server, including USB drives. Network Attached Storage (NAS) able to represent itself as CIFS (SMB) share (direct operation), or NFS share (must be mounted on a Linux backup repository server). Storage Area Network (SAN). Backup repository server must be connected directly into SAN fabric via hardware HBA or software iSCSI initiator, and the corresponding volumes must be seen in the Microsoft Windows Disk Management snap-in.
Known Issues
General Backup infrastructure By default, storage infrastructure is rescanned every 24 hours. Perform Rescan Storage operation manually after storage infrastructure changes, otherwise backup proxies will not see the newly added volumes immediately. Backup proxy server cannot backup to a CIFS share based backup repository when CIFS share is located on the same server as the backup proxy server. To work around this, create regular Windows based backup repository on the proxy server instead. Linux servers registered with Veeam Backup & Replication infrastructure must use "Password" authentication method and BASH shell. All registered server names must be resolvable into IPv4 address. NETBIOS names of backup servers must be resolvable on Enterprise Manager server. Sending SNMP traps fails with Unknown entity parameter error when receiver server is specified using DNS name. To work around this issue, use IP address instead. Due to NFS implementation specifics on certain NFS storage, backup 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. Windows Vista and Windows 7 based backup proxy servers support network processing mode only for populating replica disks with data during incremental replication passes and failback. To work around this, install backup proxy servers on other supported Windows versions. On Windows versions prior to 2008, the virtual backup proxy server using Microsoft iSCSI Software Initiator for 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, change the backup proxy VM virtual disks to IDE. Virtual backup proxy server cannot be used to backup, replicate or copy itself in virtual appliance (hot add) mode. Jobs configured to do this will automatically failover to Network processing mode. Virtual backup proxy server must have VMware Tools installed; otherwise it will be considered as not running, and will never be assigned any tasks. VMware vStorage API for Data Protection has some limitation preventing hot add process depending on VM configuration. For complete list of hot add limitations, refer to this support KB article. With the default proxy settings, should hot add operation fail, the job will failover to the network mode for specific virtual disk. Processing of vSphere Fault-Tolerant (FT) VMs is not supported. IDE VM disks are not supported for disk exclusion functionality. VM Copy jobs do not support disk exclusions functionality. VM Copy jobs to CIFS-based backup repository fail on non-default backup proxy. Hard Disk restore may fail with the Restore job failed Error: Controller with BusNumber 0 was not found error when SCSI controller is missing on the destination VM. To work around this, add SCSI controller (or SCSI disk) manually first by editing VM virtual hardware settings with vSphere Client. Disk mapping functionality is not supported for IDE disks in the Hard Disk Restore wizard. Restore and replication of VMs between different ESX(i) versions requires that VMs virtual hardware version is compatible with the target host.
VMware
Restoring VM with non-standard virtual disk layout (such as converted from VMware Workstation or VMware Server) as thin may fail. To work around this issue, restore these disks as thick. Instantly recovered VM with non-standard virtual disk layout (such as converted from VMware Workstation or VMware Server) and running on ESX(i) 4.x host and with change redirection to datastore enabled cannot be properly quick migrated. Quick Migration of vApp VMs is not supported. VM with virtual disks having the same name that had at least one snapshot created at the time of backup or replication requires manual adjustment of conflicting descriptors upon restore. Virtual disk placement and type cannot be customized during full VM restore when restoring backups produced by version earlier than 6.1. Virtual disk type customization does not work correctly in the Migration jobs. Replication jobs may fail if source or target datastore has specials symbols in its name. Network-less interaction with Microsoft Windows guests having UAC enabled (Vista or later) requires that Local Administrator (MACHINE\Administrator) or Domain Administrator (DOMAIN\Administrator) account is provided on Guest Processing step. Starting a replicated VM using means other than the products user interface (including Hyper-V Manager, SCVMM, PowerShell) makes all earlier restore points become unusable. CPU Type SCVMM parameter is not backed up and restored on Hyper-V VMs. Restoring VM with special symbols in its name fails with the Error: BackupDoc: Unexpected metadata format error. Virtual disks consisting of multiple files (such as from virtual machines originally created on Virtual Server 2005) are not supported for processing. Instant VM Recovery to the original location fails if the original VM was migrated to another host after backup, and still exists at the time of restore. To work around this, delete the existing virtual machine manually. Instant VM Recovery from backup with excluded disks is not supported. Instant VM Recovery for VMs on localized Hyper-V hosts is not supported for VMs with SCSI virtual disks. Changing the source VM disk size causes backup and replication job fail with the Client error: The requested capacity is not equal to the current capacity error. Failback to original location from replica of VM with differential disks fails with the "The process cannot access the file because it is being used by another process". Replica seeding from Linux-based backup repository is not supported. Replica mapping is not supported if source VM has differential disks. Starting a replicated VM using means other than the products user interface (including vSphere Client, Hyper-V Manager, SCVMM, PowerShell) disables advanced replication functionality such as Re-IP and failback. Backup Browser may show different drive letters than in the guest. File level restore may fail if a restored VM is lacking free space. Dynamic disks are not supported. Use multi-OS file level restore wizard instead. Legacy Logical Volume Manager version 1 (LVM1) volumes are not supported. Encrypted LVM volumes are not supported. Spanned, striped, RAID dynamic disks are not supported.
Hyper-V
Failover
Non-standard file system configurations support is limited (for example, configurations when file system journal is located on another volume, separately from actual file system are only supported for ext3 file system, but not for other file systems). Automatic virtual lab configuration is not supported for networks with non-private network addresses. Automatic virtual lab networking configuration process may fail with the Unable to resolve default network settings error. To work around this issue, go back in the wizard and try again. Automatic virtual lab networking configuration may fail in some case when DVS are present in virtual environment. In such cases, use advanced configuration mode to configure virtual lab networking manually. SureBackup job fails on VM with unsupported or excluded virtual disks which were not explicitly set to be removed from configuration (as a part of disk exclusion settings in the backup job), because test VM cannot find its disks and is unable to start. Automatic physical mode RDM disk exclusion in the backup job may lead to situation when test VM is able to connect RDM disk, and produce irreversible changes on the disk. To avoid this, always exclude physical RDM disk from backup job explicitly, selecting the option to remove the excluded disks from configuration. Some antivirus applications are known to cause BSOD on backup repository server when SureBackup job is started. To prevent this, exclude backup folders from monitoring. Non-Latin characters are not supported in the products installation path; in the backup target path and file names; in the Veeam Backup and Replication service account name; in the source or destination path of SSH-enabled file copy operations; in virtual machine properties; in VM file and folder names for multi-OS file level restore wizard. Unicode characters are not supported in the guest file names for 1-Click File Restore. A few UI controls may appear misplaced with the product installed on eastern locales. If your CIFS shares require authentication, edit settings for each backup repository created by upgrade process, and enter the share credentials before running the job. Guest file search and 1-Click FLR in restore points created prior to 6.0 is not supported for VMs with special symbols in their names. At least one successful backup job run is required after upgrade, before you can start moving backup files between repositories. First Hyper-V backup and replication job run after upgrade will not use the changed block tracking information, and thus may take longer than expected.
SureBackup
Globalization
7.
8.
9.
10. Once the installation is complete, launch the Veeam Backup product by clicking the Veeam Backup and Replication product icon on your desktop. 11. Repeat the procedure to install additional Veeam Backup servers if needed.
5.
6.
7. 8. 9.
3.
5.
Licensing
Veeam Backup is licensed per CPU Socket ("CPU Sockets") for each Managed Server. For more information, see www.veeam.com/eula.html. The trial license key is sent to you after registering the product with Veeam Software at: 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 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].
To install the new license file to a standalone backup server that is not connected to Enterprise Manager server: 1. 2. Select Help > License from the main menu. Click the Install license button to browse to the license file (.lic) that was sent to you after registration to install the license. To learn more, see the Licensing section.
To view the product help, press the F1 key or select Help > Help from the main menu.
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 export the log files, select Help > Support Information... from the main menu, and select all servers (backup proxies and repositories) involved in the job you are having issues with.
To submit your support ticket or obtain additional information please visit www.veeam.com/support.html Hint Before contacting technical support, you may be able to find a resolution to your issue by searching Veeam community forums at: www.veeam.com/forums.
Customer Support
For the most up to date information about our support practices, business hours and contact details, please visit www.veeam.com/support. You can also use this page to submit a support ticket and download the support policy guide.
Company Contacts
Office Address U.S. Headquarters 6479 Reflections Drive, Suite 200 Columbus, Ohio 43017 USA Phone Fax +1-614 339 8200 +1 614 675 9494 EMEA Headquarters 400 Thames Valley Park Thames Valley Park Drive Reading, Berkshire RG6 1PT UNITED KINGDOM +44 (0) 1276 804 501 +44 (0) 1276 804 676 +61 2 9977 0280 +61 2 8088 6899 APAC Headquarters Suite 2, 15 The Corso Manly, NSW 2095, AUSTRALIA Veeam Software Benelux Evert van de Beekstraat 310, 1118 CX Schiphol Centrum NETHERLANDS +31(0)20 654 1805 +31(0)20 654 1801