VEEAM BACKUP & REPLICATION RELEASE NOTES

Transcription

1 VEEAM BACKUP & REPLICATION RELEASE NOTES This Release Notes document provides last-minute information about Veeam Backup and Replication 4.1.2, 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 and Replication is available for download at: starting from August 4, See next: New Features Resolved Issues System Requirements Known Issues Installing Veeam Backup Uninstalling Veeam Backup Upgrading Veeam Backup Upgrading Veeam Backup Enterprise Manager Licensing Updating Veeam Backup License Technical Documentation References Technical Support Contacting Veeam Software Page 1

2 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 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 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 for added reliability. Page 2

3 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 installations only. Page 3

4 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 yourinfrastructure-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

5 System Requirements VMware Infrastructure Platforms Hosts vsphere 4 Infrastructure 3 (VI3) 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 OS 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. 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

6 Software VMware Tools Veeam Backup Server Hardware CPU: x86/x64 (4 cores recommended for optimal backup performance). Memory: 1024MB RAM (2048MB RAM when using local SQL Express installation). Hard Disk Space: 200MB Network: 1Gbit/sec recommended due to backup performance considerations. OS Both 32-bit and 64-bit versions of the following operating systems are supported: Microsoft Windows XP SP3 Microsoft Windows 2003 SP2 Microsoft Windows Vista SP2 Microsoft Windows 2008 SP2 Microsoft Windows 2008 R2 Microsoft Windows 7 Software Microsoft SQL Server 2005 or 2008 (SQL 2005 Express is included in the setup) Microsoft.NET Framework 2.0 SP1 (included in the setup) Microsoft PowerShell 1.0 or later (PowerShell 1.0 included in the setup) VMware Player 2.5 (optional, for multi-os file level restore wizard only) Veeam Backup Enterprise Manager Hardware Processor: x86/x64. Memory: 1024MB RAM (2048MB RAM when using local SQL Express installation). Hard Disk Space: 100MB. Network: 1Gb or faster recommended for optimal backup performance. OS Both 32-bit and 64-bit versions of the following operating systems are supported: Microsoft Windows XP SP3 Microsoft Windows 2003 SP2 Microsoft Windows Vista SP2 Microsoft Windows 2008 SP2 Microsoft Windows 2008 R2 Microsoft Windows 7 Software Microsoft SQL Server 2005/2008 (SQL 2005 Express Edition is included in the setup) Microsoft Internet Information Services 5.1 or later ( IIS 6.0 Management Compatibility and Windows Authentication components are required for IIS 7.0) Microsoft.NET Framework 2.0 SP1 (included in the setup) Page 6

7 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

8 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

9 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. File Level Restore Backup Browser may show different drive letters than in the actual VM. If a VM has snapshots, FLR mounts the VM file system to the earliest snapshot. File level restore may fail if a restored VM is lacking free space. Only first partition on dynamic disk is visible during file level restore. Multi-OS File Level Restore Legacy Logical Volume Manager version 1 (LVM1) volumes are not supported. 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). Globalization Non-latin characters are not supported in the product s installation path; in the backup target path; in the Veeam Backup and FastSCP 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. A few UI controls may appear misplaced when Veeam Backup is installed on eastern locales. This issue does not affect product s functionality. Page 9

10 Installing Veeam Backup To install Veeam Backup server and management console: 1. Download the 32-bit or 64-bit package of the latest version of Veeam Backup from: 2. Extract the downloaded archive and run the Veeam_Backup_Setup.exe setup file. 3. Accept the terms of Veeam Backup and FastSCP License Agreement to install the product. 4. Provide setup program with your license file. 5. Specify the installation folder. 6. Select existing Microsoft SQL server instance to create Veeam configuration database in, or have setup install local Microsoft SQL Server 2005 Express Edition to host the database. Setup will install a named (VEEAM) instance of SQL Express. 7. Specify the administrative credentials to run the Veeam Backup service, and port to be used by the service. The account must have Local Administrator privileges on the computer where you are installing Veeam Backup. 8. Click Install to start the installation. 9. Once the installation is complete, launch the Veeam Backup product by clicking the Veeam Backup and FastSCP product icon on your desktop. 10. Repeat the procedure to install additional Veeam Backup servers if needed. If you want to manage one or more Veeam Backup servers with centralized management and reporting web UI, install Veeam Backup Enterprise Manager. You only need one Enterprise Manager installation per your environment. To install Veeam Backup Enterprise Manager: 1. Run the Veeam_Backup_Enterprise_Manager_Setup.exe setup file. 2. Accept the terms of License Agreement to install the product. 3. Specify the installation folders leaving both components selected for the installation. 4. Select existing Microsoft SQL server instance to create Veeam configuration database in, or have setup install local Microsoft SQL Server 2005 Express Edition to host the database. Setup will install a named (VEEAM) instance of SQL Express. 5. Specify the administrative credentials to run the Veeam Backup Enterprise Manager service, and port to be used by the service. The account must have Local Administrator privileges on the computer where you are installing Veeam Backup Enterprise Manager. 6. Depending on operating system you are installing on, you may be present with step allowing you to customize web site ports for HTTP and HTTPs connections. 7. Click Install to start the installation. 8. Once the installation is complete, access the Veeam Backup Enterprise Manager Web UI by clicking the Veeam Backup Enterprise Manager product icon on your desktop. Uninstalling Veeam Backup 1. From the Start menu, select Control Panel > Add or Remove Programs. 2. In the programs list, select Veeam Backup and FastSCP and click the Remove button. 3. In the programs list, select Veeam Backup Enterprise Manager (if it was installed) and click the Remove button. Page 10

11 Upgrading Veeam Backup To perform upgrade to Veeam Backup 4.1.2, you must be running version 4.x or 3.x. 1. Ensure that the latest run for all existing jobs completed successfully. If some jobs have failed, re-run the failed jobs. Otherwise, job upgrade procedure may fail. 2. Download the required x86 or x64 package of the latest version of Veeam Backup from: 3. Extract the downloaded archive and run the Veeam_Backup_Setup.exe setup file. 4. Setup will detect the existing installation and will ask you to confirm the upgrade. 5. Click Yes and follow the upgrade wizard steps as outlined above. Be sure to select the same SQL database and instance that was used by the previous Veeam Backup version. To perform upgrade to Veeam Backup from version 2.x, you must do the following: 1. Ensure that you are running version If you are running earlier version, please upgrade to You may contact Veeam support to obtain the distributive. 2. Perform upgrade from version to version You may contact Veeam support to obtain the distributive, license key and Release Notes document with the upgrade instructions for version Perform upgrade to version as outlined above. Upgrading Veeam Backup Enterprise Manager To perform upgrade to Veeam Backup Enterprise Manager 4.1.2: 1. Download the latest version of Veeam Backup Enterprise Manager from: 2. Extract the downloaded archive and run the Veeam_Backup_Enteprise_Manager_Setup.exe setup file. 3. Setup will detect the existing installation and will ask you to confirm the upgrade. 4. Click Yes and follow the upgrade wizard steps as outlined above. Be sure to select the same SQL database and instance that was used by the previous Veeam Backup Enteprise Manager version. Page 11

12 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: 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 The full license includes a one-year maintenance plan. To renew your maintenance plan, please contact Veeam Customer Support at: support@veeam.com. Updating Veeam Backup License To install the new license file: 1. Select Help > License Information... from the main menu. 2. 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. After the license is installed, you will be able to use all features which require a valid license such as backup and replication. Page 12

13 Technical Documentation References If you have any questions about Veeam Backup 4.1.2, you may use the following resources: Product web-page: User Guide: Community forum: To view the product help, press the F1 key or select Help > Help from the main menu. Technical Support We offer 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 Hint: Before contacting technical support, you may be able to find a resolution to your issue at Veeam community forums at: Page 13

14 Contacting Veeam Software At Veeam Software we pay close attention to comments from our customers. It is important to us not only to quickly help you with your technical support issues we make it our mission to listen to your input, and to build our products with your suggestions in mind. Should you have a Customer Support issue or question, please feel free to contact us. We have qualified English speaking technical and customer support staff in the USA and Europe who will help you with any inquiry that you may have. Office U.S. Headquarters EMEA Headquarters APAC Headquarters Veeam Software Benelux Address 6479 Reflections Drive, Suite 200 Columbus, Ohio Thames Valley Park Thames Valley Park Drive Reading, Berkshire RG6 1PT Level 21 & 22, 201 Miller Street North Sydney NSW 2060, Australia Evert van de Beekstraat 310, 1118 CX Schiphol Centrum The Netherlands Phone (0) Fax (0) (0) (0) Page 14