VEEAM BACKUP & REPLICATION RELEASE NOTES

Transcription

1 VEEAM BACKUP & REPLICATION RELEASE NOTES This Release Notes document provides last-minute information about Veeam Backup & Replication 5.0.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 April 11, See next: New Features Resolved Issues 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 Page 1

2 New Features The following is a list of new features introduced in version 5.0.2: Internet access from virtual lab. SureBackup virtual labs now provide an optional internet access from fenced-off environment. This enables using On-Demand Sandbox for additional use cases, such as more streamlined patch or software upgrade testing. Internet access is disabled by default, and must be configured through new registry parameters on the Veeam B&R server. Automated retention for removed and deleted VMs. Data belonging to removed or deleted VMs will now be automatically cleaned up from backup files according to new UI retention setting in days. Previously, it was necessary to remove such VMs from backup manually to explicitly confirm that VM data is no longer needed. Optional catalog import. Guest file system catalog import was made optional to reduce the time required to import backup in cases when importing catalog data is not required. The corresponding option has been added to the Import Backup dialog. Date Modified attribute preservation. Instant file level restore for Microsoft Windows guests now preserves Date Modified attribute on all restored files. Microsoft Windows Storage Server support. You can now install backup server and Enterprise Manager servers directly on your Microsoft Windows Storage Server. The following is a list of new features introduced in version 5.0.1: Distributed Virtual Switches (DVS) support. Veeam Backup & Replication now supports configuring virtual labs in virtual environments with DVS. Improved virtual lab auto-configuration logic. Automatic virtual lab networking configuration now supports more scenarios and should work more reliably. SQL Server Role. New SQL Server role and corresponding application verification script was added to SureBackup roles. Automatic failover for Veeam Backup server. Attempting to backup Veeam Backup server in Virtual Appliance mode now automatically fails over the job to Network mode for Veeam Backup VM. Multi-OS File Level Restore DHCP requirement removed. FLR helper appliance no longer requires DHCP to be present in the environment, and can be configured to use static IP address instead. Multi-OS File Level Restore via FTP. FTP server can now be optionally enabled on FLR helper appliance for scenarios when faster bulk recovery of thousands of guest files is needed. This functionality also enables self-user restores capabilities. Page 2

3 Resolved Issues The following is a list of issues resolved in version 5.0.2: General Windows Storage Server is not supported for backup server and Enterprise Manager servers. Backup and Replication Failed or terminated transformation of previous full backup chain causes the following transform attempts to fail with the Patch failed error. Backup job fails with the There is an item with the specified name and another type error. Backup job fails with the Failed to execute stored procedure. Name: [[Backup.Model.DeleteBackup]] error. Replication job fails with the Index was outside the bounds of the array error. Replication job fails with the Failed to parse "" error. Replication job fails with the Cannot delete nvram error Virtual Appliance mode jobs fail with the Unknown transport type when Encrypt LAN traffic option is enabled. Running multiple jobs on continuous schedule may cause the jobs to crash with the Failed unexpectedly error. Application-aware image processing Failover to network less operation should now be performed more reliably in scenarios when network connection to processed guest can be established, but other reasons still prevent network based operation. Under rare circumstances, application-aware processing failure may cause the job to hang forever. Guest agent fails to start with The process cannot access the file because it is being used by another process error. Microsoft SQL Server log truncation does not work for default SQL instances. Guest file system indexing Under rare circumstances, guest file system indexing process may hang causing the job to hang waiting for indexing to complete. SureBackup Period is incorrectly restricted as allowed symbol in a virtual switch name. Enterprise Manager wizards on Requests page may not show a list of available backups, preventing virtual lab request approval. Restore Importing backups made on backup server with some non-english locales may fail with the String was not recognized as a valid DateTime. Unknown VBK format error User interface User interface can become irresponsive for extended periods of time when selecting certain management tree nodes, such as Backups or Replicas. Remove excluded disks from VM configuration checkbox state cannot be changed for replication jobs. Remove from replicas command fails with the This backup file is locked by job, and cannot be deleted. when failover is active. Automatic backup integrity checks are performed during each job run, ignoring a value of the corresponding checkbox. Page 3

4 The following is a list of issues resolved in version 5.0.1: Backup and Replication Veeam Backup server cannot backup itself in any processing mode. Windows 2008 server with Veeam Backup & Replication installed hangs for extended periods of time during OS boot up. Failed or terminated Virtual Appliance mode jobs may leave the drive mounted inside the backup VM, which prevents correct snapshot removal. Renaming processed VMs may result in backup job failing with the Last backup must be full, oibid {GUID} error. Database owner (dbo) rights on Veeam Backup configuration database were not sufficient due to xp_regread procedure use by logging component. Retry operation does not handle failed synthetic backup processing correctly in the incremental backup mode. Synthetic full backup transform operation does not start if last retry operation was started on the next day after backup job was started. Backup file statistics is not updated after synthetic full backup transform. Backup job with WAN storage optimization mode fails when backup file size reaches 2.2TB with the Banks pool is full error. Replication job may fail with the AddThinDiskToVm failed.cannot complete the operation because the file or folder already exists error. Replication of thin disks fails with the Required disk size differ from the actual error if thin disk size is not a multiple of 1KB. Such disk can only be replicated as thick. Starting jobs from command line leaves Veeam.Backup.Manager.exe running after the job completes. This can result in multiple Veeam.Backup.Manager.exe processes appearing and persisting until Veeam Backup server is rebooted. reports are not being sent to global notification recipients (super administrators) specified under Tools > Options when job-specific notifications list is disabled under Advanced job settings. Backup job running in reversed incremental backup mode fails with Failed to execute stored procedure error if retention policy set to 1. Under rare circumstance, backup job may fail with the There is no FIB [summary.xml] in the specified restore point error. backupjobresult field in SNMP notifications always contains string "None" regardless of the actual job outcome. A number of enhancements and fixes in backup import functionality. Processing virtual machine with special characters in its name or backup file path fails with the XML parsing: illegal name character error. Job session results do not report automatic failover from Virtual Appliance to Network processing mode. Application-aware image processing Guest processing fails with No such host is known or The requested name is valid, but no data of the requested type was found if DNS is configured incorrectly or is missing reverse lookup zone. Guest processing agent crashes when attempting to truncate logs on Microsoft SQL Server 2000 (or MSDE 2000). SureBackup Virtual lab creation fails on ESX hosts that are a part of cluster with VMware DRS turned off due to inability to create resource pool. Virtual lab may not be configured correctly when production network is connected to DVS (distributed virtual switch) on ESX(i) host virtual lab is created on. It is recommended to use ESX host with standard virtual switch until this issue is resolved in future update. Page 4

5 Recovery verification may fail for Windows 2008 R2 and Windows 7 VMs using VMXNET3 adaptor and static IP address due to guest network adaptor resetting to DHCP. For more information, refer to VMware support KB article In some cases, SureBackup jobs are unable to reach virtual lab VMs due to using proxy server specified in the Internet Explorer settings. If source VM has CPU reservation settings set, and this reservation exceeds virtual lab ESX limit, the VM will fail to start during SureBackup job. Multi-OS file level restore Restore points are sorted from oldest to newest, instead of showing most recent first. Backup explorer cannot browse through ext4 guest file system. Search Search Server 2008 installed on Windows OS with non-english locale may fail to return search results for certain VMs. User interface Size of VMs with thin disks is calculated using provisioned storage versus used storage versus on virtual machine selection wizard step, and for Check Space functionality. Under certain circumstances, clicking the Jobs node fails with the "Index was outside the bounds of the array. (System.IndexOutOfRangeException)" error. Incorrect or corrupted Veeam Backup configuration results in the "Specified cast is not valid" error when opening Veeam Backup user interface. Multiple concurrent user access to Veeam Backup console is restricted, while this was possible to do with v4 (although this was not supported). Registry key was added that enables v4 style behavior, however its use is not recommended. Contact support for more information and to obtain the registry key. Upgrade Synthetic full backup transform operation fails with Value cannot be null error on v4 backup job which had its backup mode changed (against recommendations). Importing backups with some restore points produced with previous version (before upgrade) does not pick up restore points created before upgrade. Page 5

6 System Requirements VMware Infrastructure Platforms Hosts vsphere 4.x Infrastructure 3.x (VI3) ESX(i) 4.x ESX(i) 3.x Software vcenter Server 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). Unsupported disk types are skipped from processing automatically. All operating systems supported by VMware are supported. Microsoft VSS integration is supported for Windows XP (32bit only), Windows 2003, Windows Vista, Windows 2008, Windows 2008 R2 and Windows 7. Native file level restore supports Microsoft Windows file systems only. Multi-OS file level restore wizard supports the following file systems: OS Supported File Systems Linux ext ext2 ext3 ext4 ReiserFS JFS XFS Unix JFS XFS UFS Solaris ZFS 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. Software VMware Tools (optional) Page 6

7 Veeam Backup Server Hardware CPU: modern x86/x64 processor (minimum 4 cores recommended). Using faster processors improves data processing performance. Memory: 2048MB RAM. Using faster memory (DDR3) improves data processing performance. Hard Disk Space: 200MB for product installation. 1 GB per 100 VM for guest file system catalog folder. Sufficient free space for Instant VM Recovery cache (non-persistent data, at least 10GB recommended). 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 SP1 Microsoft Windows 7 SP1 Software Microsoft SQL Server 2005/2008 (SQL 2005 SP3 Express included in the setup) Microsoft.NET Framework 2.0 SP1 (included in the setup) Microsoft PowerShell 2.0 or later Veeam Backup Enterprise Manager Hardware Processor: x86/x64 processor. Memory: 2048MB RAM Hard Disk Space: 100MB for product installation. Network: 1Mb/sec or faster connection to Veeam Backup servers. 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 SP1 Microsoft Windows 7 SP1 Server Software Microsoft Internet Information Services 5.1 or later ( IIS 6.0 Management Compatibility and Windows Authentication components are required for IIS 7.0) Microsoft SQL Server 2005/2008 (SQL 2005 SP3 Express included in the setup) Microsoft.NET Framework 2.0 SP1 (included in the setup) Client Software Microsoft Internet Explorer 6.0 or later, or Mozilla Firefox 3.0 or later. Microsoft Excel 2003 or later (to view Excel reports) Veeam Backup Search Server Hardware Refer to Microsoft Search Server system requirements. Page 7

8 OS Refer to Microsoft Search Server system requirements. Software Microsoft Search Server 2008 (including Express Edition). Microsoft Search Server 2010 (including Express Edition). Backup Target Backup can be performed to the following targets: Storage Area Network devices (Veeam Backup server must be connected directly into SAN fabric via HBA or software iscsi initiator, 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 CPU: x86/x64 processor. Memory: according to OS requirements. Hard Disk: Using faster local storage (fast high-rpm hard drives, striped RAID configurations) improves data processing performance. Hard Disk Space: Sufficient disk space required to store the backup files according to the selected retention policy. Network: 1Mb/sec or faster connection to target storage supported. 1Gb/sec recommended due to performance considerations. OS o o o o Microsoft Windows (via CIFS share) All major Linux distributions (via agent) ESX 3.x (via agent) ESX 4.x (via agent) Replication Target Hosts ESX(i) 3.x ESX(i) 4.x Page 8

9 Known Issues General 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. Only "Password" authentication method is supported for Linux servers added to Veeam Backup console. Backup and Replication VMware Tools quiescence is not supported for Windows 2008 R2 and Windows 7 running on ESX(i) 4.1 hosts. To work around this, enable application-aware processing in the Veeam job settings to leverage Veeam VSS integration. 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. 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. 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. Changing replica processing mode by adjusting target ESX data transfer engine (agent-based / agentless) is not supported. 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. The connections limit has been increased significantly in ESX(i) 4.1 VM that were connected to DVS (distributed virtual switch) require manual VLAN settings adjustment upon restore or failover. Restoring VM with non-standard disk sizes (such as converted from VMware Workstation or VMware Server) as thin may fail. To work around this issue, restore disks as thick. Restore and replication of VMs from ESX 4.x to earlier versions of ESX is not supported due to incompatible virtual hardware versions. Native File Level Restore Backup Browser may show different drive letters than in the actual VM. File level restore may fail if a restored VM is lacking free space. Dynamic disks support is limited. Only first partition on dynamic disk is visible during file level restore. To work around this, use multi-os file level restore instead. MBR disk partition table is required for file-level restore, GPT disks are not supported. Multi-OS File Level Restore Legacy Logical Volume Manager version 1 (LVM1) volumes are not supported. Page 9

10 Encrypted LVM volumes are not supported. Spanned, striped, RAID5 dynamic disks are not supported. MBR disk partition table is required for file-level restore, GPT disks 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). Application-aware image processing Connection-less operation with Microsoft Windows versions having UAC enabled (Vista or later) requires that Local Administrator (MACHINE\Administrator) or Domain Administrator (DOMAIN\Administrator) account is provided on Guest Processing step. Virtual Appliance mode Virtualized Veeam Backup server cannot be used to backup, replicate or copy itself in virtual appliance mode. Jobs configured to do this will automatically failover to Network processing mode. Virtual Appliance mode fails with the insufficient disk space error if ESX datastore hosting Veeam Backup VM has less free space than biggest processed virtual disk. Virtual Appliance mode fails if ESX datastore hosting Veeam Backup VM has different VMFS block size than datastore where backed up virtual disk is located. Virtual Appliance mode does not support processing VMs with IDE virtual disks. vpower NFS Using volume root (e.g. D:\) as vpower NFS root folder is not supported. To workaround, create and use path with at least one subfolder (e.g. D:\NFS). SureBackup 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. 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. Upgrade Changing backup mode for existing v4 jobs is not recommended. If you want to use new backup mode, please create the new job instead. Some PowerShell SDK commands have been updated to reflect new functionality. Existing PowerShell scripts may need to be adjusted before they can be used with v5. Page 10

11 Installing Veeam Backup & Replication Veeam Backup & Replication Server To install Veeam Backup & Replication server and management console: 1. Download the 32-bit or 64-bit package of the latest version of Veeam Backup & Replication from: 2. Extract the downloaded archive and run the Veeam_Backup_Setup.exe setup file. 3. Accept the terms of Veeam Backup and Replication 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 services, and port to be used by the job management service. The account must have Local Administrator privileges on the computer where you are installing Veeam Backup. 8. Specify the location for guest file system catalog and vpower NFS root folder. Be sure to use the volume with sufficient amount of free disk space, according to the System Requirements. 9. Click Install to start the installation. 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. Veeam Backup & Replication Enterprise Manager If you want to manage one or more Veeam Backup servers with centralized management and reporting web UI, install Veeam Backup & Replication Enterprise Manager. You only need one Enterprise Manager installation per your environment. To install Veeam Backup & Replication 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 all 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. Specify the location for guest file system catalog folder and port to be used by catalog service. Be sure to use the volume with sufficient amount of free disk space, according to the System Requirements. 7. 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. 8. Click Install to start the installation. 9. 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. Page 11

12 Veeam Backup & Replication Search Server If you want to be able to search for guest OS files of backed up VMs in the Enterprise Manager, install Microsoft Search Server and apply Veeam Search Server integration components. You can have more than one Search Server in your environment depending on amount of virtual machines with indexing enabled. Note that you do not need to install Search Server in order to be able to simply browse guest OS file system of specific restore points in the Enterprise Manager. It is recommended that you install Microsoft Search Server on a separate computer. To install Microsoft Search Server: 1. Download the 32-bit or 64-bit package of the Microsoft Search Server. To download free version of Microsoft Search Server, use the following links: Microsoft Search Server 2008 Express Edition: x86 package, x64 package Microsoft Search Server 2010 Express Edition: x64 package. 2. Install Microsoft Search Server using the default settings. At the end of installation, select the checkbox to launch SharePoint configuration wizard. 3. Go through the SharePoint configuration wizard, accepting the default settings. 4. Go to the Start menu, locate link to Search Server Administration page and launch it. Make sure the account specified under Default content access account has Read access rights to the catalog share on your Veeam Backup Enterprise Manager server, as well as NTFS permissions on the folder backing this share. To install Veeam Backup Microsoft Search Server Integration: 1. Run the Veeam_Backup_Search_Setup.exe setup file. 2. Accept the terms of License Agreement to install the product. 3. Specify the installation folder. 4. For service account, specify any account who is Local Administrator on this computer. To add newly installed Search Server to Veeam Backup Enterprise Manager: 1. Open Veeam Backup & Replication Enterprise Manager user interface. 2. Open Configuration section, select Search Servers tab, and add the newly installed search server there. Note that you cannot add the same Search Server to more than one Enterprise Manager server. 3. Give the Search Server some time to crawl catalog, and use the Files tab in the Enterprise Manager web UI to test search for guest files. Make sure you have performed backup of at least one VM with guest indexing option enabled. Uninstalling Veeam Backup & Replication 1. From the Start menu, select Control Panel > Add or Remove Programs. 2. In the programs list, select Veeam Backup & Replication and click the Remove button. 3. In the programs list, select Veeam Backup & Replication Enterprise Manager (if installed) and click the Remove button. 4. In the programs list, select Veeam Backup Catalog and click the Remove button. 5. In the programs list, select Veeam Backup & Replication Search Server Integration (if installed) and click the Remove button. Page 12

13 Upgrading Veeam Backup & Replication If you are currently using multiple v4 licenses in your deployment, please contact your Veeam representative or to request a consolidated license key before upgrading. Veeam Backup & Replication Server To perform upgrade of Veeam Backup & Replication server to version 5.0.2, you must be running version 4.x, 5.0 or 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 & Replication 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 & Replication from earlier versions, please contact support. Veeam Backup & Replication Enterprise Manager To perform upgrade of Veeam Backup Enterprise Manager to version 5.0.2, you must be running version 4.x, 5.0 or 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 setup wizard steps as outlined above. Be sure to select the same SQL database and instance that was used by the previous Veeam Backup Enterprise Manager version. Page 13

14 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. For more information, see 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 & Replication License Starting from Veeam Backup & Replication 5.0, license is managed centrally by Enterprise Manager server. You should not update license on individual backup servers directly, as Enterprise Manager forces its license to all connected backup servers. To install the new license file to a backup server connected to Enterprise Manager server: 1. Open Configuration > Licensing tab in Enterprise Manager UI, and click Change License. 2. Browse to the license file (.lic) that was sent to you after registration to install the license. To learn more, see the Licensing section. 3. The provided license file will be automatically propagated and applied to all Veeam Backup servers connected to this Enterprise Manager server. To install the new license file to a standalone backup server that is not connected to Enterprise Manager server: 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. Page 14

15 Technical Documentation References If you have any questions about Veeam Backup & Replication, 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 by searching Veeam community forums at: Page 15

16 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. Phone Support Company Contacts United States +1 (614) UK +44 (845) Germany France +33 (1) Spain +34 (91) New Zealand +64 (9) Australia +61 (26) Netherlands +31 (858) Norway +47 (85) Denmark +45 (78) Belgium +32 (78) Sweden +46 (10) Office U.S. Headquarters EMEA Headquarters APAC Headquarters Veeam Benelux Software Address 6479 Reflections Drive, Suite 200 Columbus, Ohio USA 400 Thames Valley Park Thames Valley Park Drive Reading, Berkshire RG6 1PT UNITED KINGDOM Level 21 & 22, 201 Miller Street North Sydney NSW 2060, AUSTRALIA Evert van de Beekstraat 310, 1118 CX Schiphol Centrum THE NETHERLANDS Phone (0) (0) Fax (0) (0) Page 16