Technical Note P/N REV A01 June 2012

Transcription

1 EMC NetWorker Backup and Recovery Support for vcenter Server Technical Note P/N REV A01 June 2012 This technical note describes how to use the NetWorker software to backup and recover a vcenter Server based on the type of vcenter deployment. It also provides best practices for protecting a vcenter Server. The following topics are covered: Overview... 2 Backing up vcenter Server with the NetWorker Software... 2 Restoring vcenter Server with the NetWorker Software

2 Overview Overview This technical note describes how to use the NetWorker software to backup and recover a vcenter Server based on the type of vcenter deployment. It also provides best practices for protecting a vcenter Server. The vcenter Server is a virtualization management solution from VMware that provides centralized control of the entire virtual infrastructure. The vcenter Server offers core services related to resource management for ESXi hosts and VMs, VM and template management, VM deployment, scheduled tasks and alarms, event management, statistics, and logging. The vcenter Server uses a database for storing its configuration, permissions, statistics, and other data. Without a proper backup of the vcenter database, you might be required to rebuild the entire virtual infrastructure from scratch in the case of a disaster. It is recommended to backup the host that runs the vcenter Server in addition to backing up the vcenter database that resides either on the same host or on a different host. This technical note assumes that you have a working knowledge of VMware vsphere vcenter configuration. Backing up vcenter Server with the NetWorker Software There are multiple ways in which a vcenter Server can be deployed in an environment. The recommended method of protecting the vcenter Server depends on the type of deployment. This table illustrates the various deployment types with their recommended backup method. vcenter Server Deployment Type vcenter Server with embedded SQL Express database that runs on a Windows 2008 or 2008R2 platform vcenter Server that runs on a Windows 2008 or 2008R2 platform and a vcenter database server that is hosted on separate machine vcenter Server Backup Method: Perform a backup of the vcenter Server by using either of the following methods: Windows Disaster Recovery BareMetal Recovery (BMR) enabled backup Backup Scenario 1: vcenter Server with the bundled SQL Express database on page 3 provides more information. Perform the following steps: 1. Use the appropriate NetWorker Module software to backup the database. 2. Backup the vcenter Server by using either of the following methods: Windows Disaster Recovery BareMetal Recovery (BMR) enabled backup Backup Scenario 2: vcenter Server hosted on Windows with a remote database on page 6 provides more information. 2

3 Backing up vcenter Server with the NetWorker Software vcenter Server Deployment Type vcenter Server that runs on a Windows 2008 or 2008R2 platform and a vcenter database server that is hosted on separate machine Note: The recovery involves fresh vcenter installation. vcenter Server Appliance with an embedded database vcenter Server Appliance and the vcenter database server are hosted on a separate machine vcenter Server Backup Method: Perform the following steps: 1. Use the appropriate NetWorker Module software to backup the database. 2. Perform a filesystem backup of the required folders in the vcenter Server. Backup Scenario 4: vcenter Server hosted on Windows with remote database (non-dr backup) on page 10 provides more information. Note: When recovering the vcenter Server from this backup method, you must manually reinstall the vcenter Server application in a different machine. Perform a VADP backup of the vcenter Server appliance. vcenter Server Appliance (vcsa) with a bundled database on page 8 provides more information. Perform the following steps: 1. Use the appropriate NetWorker Module software to backup the database. 2. Perform a VADP backup of the vcenter Server appliance. vcenter Server Appliance (vcsa) with remote database on page 9 provides more information. Note: For vcenter Servers that are hosted on Windows platforms that run as a virtual machine, it is recommended to either use a Windows Disaster Recovery or BMR procedure to backup the vcenter Server. Do not use the VADP to backup the vcenter Server VM because: VMware recommends shutting down the vcenter services before the backup. VADP recovery has a limitation that requires a vcenter Server to be up and running prior to recovering any VM. This imposes a restriction that a standby vcenter Server is available for disaster recovery purposes. Backup Scenario 1: vcenter Server with the bundled SQL Express database For all vcenter Servers that are hosted on Windows with a bundled database, VMware recommends to shutdown all vcenter and database services before performing a backup. Since this will cause a downtime for the vcenter Server, schedule a backup at the least disruptive time. provides more information on this limitation. The following procedure uses the savepnpc backup command to shutdown the vcenter services, perform backup, and to bring the vcenter online again. 3

4 Backing up vcenter Server with the NetWorker Software To backup vcenter Server with bundled SQL Express database, perform these steps: Task 1: Configure the vcenter Server client on the NetWorker server To configure a vcenter Server client on the NetWorker server: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter Server. 3. Type the following value in the Backup command attribute in the Client resource of the vcenter Server: savepnpc 4. Create and save the following script as group-name.res in the following location on the vcenter Server: NetWorker_install_path\res where group-name is the same name that was used in the Group resource and was selected for the client that is running the vcenter Server. If the vcenter Server belongs to multiple backup groups, create a separate group-name.res file for each group to which it belongs. group-name.res type: savepnpc; precmd: "C:\\Windows\\System32\\cmd.exe /c C:\\<path-toscripts>\\stop-services.bat"; pstcmd: "C:\\Windows\\System32\\cmd.exe /c C:\\<path-toscripts>\\start-services.bat"; timeout: "12:00pm"; abort precmd with group: Yes; 5. On the vcenter Server, save the following script as stop-services.bat in the <path-to-scripts> folder: net stop "VMware VirtualCenter Server" /y PING n 20 > nul net stop VMwareVCMSDS PING n 20 > nul net stop "SQL Server (VIM_SQLEXP)" PING n 20 >nul 4

5 Backing up vcenter Server with the NetWorker Software 6. Create and save the following script as start-services.bat in the same <path-to-scripts> folder on the vcenter Server: start-services.bat net start "SQL Server (VIM_SQLEXP)" PING n 20 > nul net start "VMware VirtualCenter Server" PING n 20 > nul net start "VMware VirtualCenter Management Webservices" PING n 20 > nul Note: This script waits for 20 seconds before starting or stopping each service. If the vcenter services take longer to start or stop, increase the wait duration by changing the value passed to the -n parameter. Task 2: Customize the save set field as per the type of backup The procedure to customize the save set field of the NetWorker client differs if you are performing the following two different types of backup: Windows Disaster Recovery In the save set field of the vcenter Server client resource, set the value to All. The 7.6 Service Pack 2 Administration Guide or later provides information on how to configure a client for Windows Disaster Recovery backups and includes the related prerequisites. BMR If using HomeBase BMR: 1. In the save set field of the vcenter Server client resource, set the value to: All 2. In the Save operations attribute of the vcenter client, set the value to: VSS:DISASTER_RECOVERY=off The 7.6 Service Pack 2 Administration Guide or later provides information on how to configure a client for BMR enabled backups and includes the related prerequisites. Task 3: Customize the backup level and schedule To customize the backup level and schedule: 1. Schedule backups of the vcenter client. 2. Ensure that the backup level is set to Full for all of the scheduled backups of the vcenter Server. This step is required because Windows Disaster Recovery and BMR only support level full backups. 5

6 Backing up vcenter Server with the NetWorker Software The backup level is determined by the level of the NetWorker client or group. The backup level can be defined explicitly or through the schedule. The Backup Groups and Schedules chapter in the EMC NetWorker 7.6 Service Pack 2 Administration Guide or later provides information on how to set the schedule and backup level. Backup Scenario 2: vcenter Server hosted on Windows with a remote database To backup vcenter Server with a remote database server, perform the following steps: Task 1: Configure the vcenter Server client on the NetWorker server To configure a vcenter Server client on the NetWorker server: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter Server. 3. The procedure to customize the save set field of the NetWorker client differs if you are performing the following two different types of backup: For Windows Disaster Recovery In the save set field of the vcenter Server client resource, set the value to All. The 7.6 Service Pack 2 Administration Guide or later provides information on how to configure a client for Windows Disaster Recovery backups and includes related prerequisites. For HomeBase BMR: a. In the save set field of the vcenter Server client resource, set the value to: All b. In the Save operations attribute of the vcenter client, set the value to: VSS:DISASTER_RECOVERY=off The 7.6 Service Pack 2 Administration Guide or later provides information on how to configure a client for BMR enabled backups and includes the related prerequisites. 6

7 Backing up vcenter Server with the NetWorker Software Task 2: Customize the backup level and schedule of the vcenter Server client To customize the backup level and schedule: 1. Schedule backups of the vcenter client. 2. Ensure that the backup level is set to Full for all of the scheduled backups of the vcenter Server. This step is required because Windows Disaster Recovery and BMR only support level full backups. The backup level is determined by the level of the NetWorker client or group. The backup level can be defined explicitly or through the schedule. The Backup Groups and Schedules chapter in the 7.6 Service Pack 2 Administration Guide or later provides information on how to set the schedule and backup level. Task 3: Configure the vcenter database module client on the NetWorker server To configure the vcenter database module client on the NetWorker server: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter database server. For example, use the NetWorker Module for Microsoft Applications to back up the vcenter database that runs in a SQL Server 2008 database server. 3. Truncate the vcenter database transaction logs after each backup. Truncating database transaction logs ensures that logs will not grow too large which might lead to increased backup time. The appropriate NetWorker Module documentation provides information on how to: Configure a client for database backups and related pre-requisites Truncate logs Task 4: Customize the backup level and schedule of the vcenter database client Schedule the backups of the vcenter database server by using a NetWorker group. Ensure that the database server backup is scheduled to run either before or in parallel with the backup of vcenter Server. This maintains consistency of the vcenter database in case of disaster recovery. The Backup Groups and Schedules chapter in the 7.6 Service Pack 2 Administration Guide or later provides information on how to set the schedule and backup level. 7

8 Backing up vcenter Server with the NetWorker Software Backup Scenario 3: vcenter Server Appliance (vcsa) When using a vcenter Server that runs as a Linux appliance, use VADP to perform backup of the appliance. For disaster recovery purposes, there should be a standby vcenter Server available. The VADP backup image of the original vcenter Server can only be restored if the standby vcenter Server is up and running prior to the restore operation. vcenter Server Appliance (vcsa) with a bundled database To backup vcenter Linux appliance with a bundled database, perform the following steps: Task 1: Configure the vcenter Server client on the NetWorker server for VADP backup To configure a vcenter Server client on the NetWorker server for a VADP backup: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter Server. 3. In the vcenter Server client resource: a. Set the save set value to *FULL*. b. Select appropriate VADP proxy host. The Configuring NetWorker Clients for VADP Backup chapter in the 7.6 Service Pack 2 VMware Integration Guide provides information on how to configure a client for VADP backups and includes information on the related pre-requisites. Task 2: Customize the schedule of the vcenter Server client Use a NetWorker group to schedule the backups of the vcenter client. The Backup Groups and Schedules chapter in the 7.6 Administration Guide provides information on how to set the schedule and backup level. 8

9 Backing up vcenter Server with the NetWorker Software vcenter Server Appliance (vcsa) with remote database To backup vcenter Linux appliance with a remote database, perform the following steps: Task 1: Configure the vcenter Server client on the NetWorker server for VADP backup To configure a vcenter Server client on the NetWorker server for a VADP backup: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter Server. 3. In the vcenter Server client resource: a. Set the save set value to *FULL*. b. Select appropriate VADP proxy host. The Configuring NetWorker Clients for VADP Backup chapter in the EMC NetWorker 7.6 Service Pack 2 VMware Integration Guide provides information on how to configure a client for VADP backups and includes information on the related pre-requisites. Task 2: Customize the backup level and schedule of the vcenter Server client Use a NetWorker group to schedule the backups of the vcenter client. The Backup Groups and Schedules chapter in the 7.6 Administration Guide provides information on how to set the schedule and backup level. Task 3: Configure the vcenter database module client on the NetWorker server To configure the vcenter database module client on the NetWorker server: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter database server. For example, use the NetWorker Module for Databases and Applications to back up the vcenter Oracle database. 3. Truncate the vcenter database transaction logs after each backup. Truncating database transaction logs ensure that logs will not grow too large which might lead to increased backup time. The appropriate NetWorker Module documentation provides information on how to configure a client for database backups and related pre-requisites and how to truncate logs. 9

10 Backing up vcenter Server with the NetWorker Software Task 4: Customize the backup level and schedule of the vcenter database client Schedule the backups of the vcenter database server by using a NetWorker group. Ensure that the database server backup is scheduled to run either before or in parallel with the backup of vcenter Server. This maintains consistency of the vcenter database in case of disaster recovery. The Backup Groups and Schedules chapter in the 7.6 Administration Guide provides information on how to set the schedule and backup level. Backup Scenario 4: vcenter Server hosted on Windows with a remote database (non-dr backup) If the vcenter is connected to a remote database server, you can back up the vcenter management infrastructure components at the filesystem level. This type of backup is faster as compared to a full backup of the vcenter Server. However, the backup will not be DR-enabled, and you must manually recreate the target machine with a fresh operating system image prior to performing recovery of the vcenter. To perform a non-dr backup of vcenter that is hosted on Windows with remote database server, perform the following steps: Task 1: Configure the vcenter Server client with required save sets on the NetWorker server Create a client resource of the vcenter Server client and mention the following paths as save sets. SSL certificates The location of the SSL certificates varies according to the Windows version, but typically it is in one of the following folders: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL C:\ProgramData\VMware\VMware VirtualCenter\SSL License files: The location of the license files varies according to the Windows version, but typically it is in one of the following folders: C:\Program Files(x86)\VMware\Infrastructure\VirtualCenter Server\licenses C:\ProgramData\VMware\VMware VirtualCenter\licenses 10

11 Backing up vcenter Server with the NetWorker Software Audit logs: The location of the audit logs varies according to the Windows version, but typically it is in one of the following folders: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs C:\ProgramData\VMware\VMware VirtualCenter\Logs Windows guest customization (sysprep) files: The location of the Windows guest customization (sysprep) files varies according to the Windows version, but typically it is in one of the following folders: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep C:\ProgramData\VMware\VMware VirtualCenter\sysprep The Backing up Data chapter in the 7.6 Administration Guide provides information on how to configure a client for filesystem backups Task 2: Customize the backup level and schedule of the vcenter Server client Use a NetWorker group to schedule the backups of the vcenter client. The Backup Groups and Schedules chapter the 7.6 Administration Guide provides information on how to set the schedule and backup level. Task 3: Configure the appropriate vcenter database module client on the NetWorker server To configure the vcenter database module client on the NetWorker server: 1. Open the NetWorker Management Console (Console) and then connect to the NetWorker server. 2. Create a Client resource for the vcenter database server. For example, use the NetWorker Module for Microsoft Applications to back up a vcenter database that runs in a SQL Server 2008 database server. 3. Truncate the vcenter database transaction logs after each backup. Truncating database transaction logs ensures that logs will not grow too large which might lead to increased backup time. The appropriate NetWorker Module documentation provides information on how to: Configure a client for database backups and related pre-requisites Truncate logs 11

12 Restoring vcenter Server with the NetWorker Software Task 4: Customize the backup level and schedule of the vcenter database client Schedule the backups of the vcenter database server by using a NetWorker group. Ensure that the database server backup is scheduled to run either before or in parallel with the backup of vcenter Server. This maintains consistency of the vcenter database in case of disaster recovery. The Backup Groups and Schedules chapter the 7.6 Administration Guide provides information on how to set the schedule and backup level. Restoring vcenter Server with the NetWorker Software The method of restoring a vcenter Server depends on the type of backup performed by using the NetWorker software. This section outlines the different vcenter Server recovery methods based on the backup type: Recovery Scenario 1: vcenter Server with the bundled SQL Express database on page 12 Recovery Scenario 2: vcenter Server hosted on Windows with a remote database on page 13 Recovery Scenario 3: vcenter Server Appliance with a bundled database on page 13 Recovery Scenario 4: vcenter Server Appliance with a remote database on page 14 Recovery Scenario 5: vcenter Server (fresh installation) hosted on Windows with a remote database on page 15 Recovery Scenario 6: vcenter Server Appliance (fresh installation) with a remote database on page 16 Recovery Scenario 1: vcenter Server with the bundled SQL Express database Restoring this type of backup is a one-step process where the entire vcenter Server is restored to the point where it was at the time of the backup. Depending on the backup type, refer to following documentation: For Windows Disaster Recovery The Windows Disaster Recovery operations section in the 7.6 Service Pack 2 or later Administration Guide provides more information. For HomeBase BMR The Recovering with BMR section in the EMC NetWorker 7.6 Service Pack 2 Administration Guide or later provides information on recovering with BMR. 12

13 Restoring vcenter Server with the NetWorker Software Recovery Scenario 2: vcenter Server hosted on Windows with a remote database Restoring this type of backup is a two-step process where the database is recovered and then the vcenter Server recovery is initiated. Perform the following steps in order: Task 1: Use the appropriate NetWorker Module software to perform the recovery of the database Use the appropriate NetWorker Module recovery steps to restore the vcenter database. For example, if the vcenter database is Oracle, perform a restore of Oracle as described in the NetWorker Module for Databases and Applications Administration Guide. Note: This step is only required if the vcenter database is no longer available. Task 2: Perform a Disaster Recovery of the vcenter Server After the database is up and running, recover the vcenter Server according to the backup type. Depending on the backup type, refer to following documentation for detailed information: For Windows Disaster Recovery The Windows Disaster Recovery operations section in the 7.6 Service Pack 2 or later Administration Guide provides more information. For HomeBase BMR The Recovering with BMR section in the EMC NetWorker 7.6 Service Pack 2 Administration Guide or later provides information on recovering with BMR. Recovery Scenario 3: vcenter Server Appliance with a bundled database Restoring this type of backup is a two-step process where the standby vcenter Server is brought online and then the vcenter Server recovery is initiated by using VADP. Perform the following steps in order: Task 1: Bring the standby vcenter Server online To bring the standby vcenter Server online: 1. Turn on the standby vcenter Server. 2. Ensure that the vcenter Server is up and running. 3. Attach the appropriate ESX or ESXi to the standby vcenter Server. 13

14 Restoring vcenter Server with the NetWorker Software Task 2: Perform a disaster recovery of the vcenter Server Appliance Perform the VADP image recovery of the vcenter Server Appliance by using the standby vcenter Server as the destination. The Recovering VADP Backups chapter in the 7.6 Service Pack 2 VMware Integration Guide provides information on how to perform image level recovery from VADP backups and includes information on the related pre-requisites. Recovery Scenario 4: vcenter Server Appliance with a remote database Restoring this type of backup is a three-step process where the database is recovered, a standby vcenter Server is brought online, and then the vcenter Server recovery is initiated. Perform the following steps in order: Task 1: Use the appropriate NetWorker Module software to perform a recovery of the database Use the appropriate NetWorker Module recovery steps to restore the vcenter database. For example, if vcenter database was Oracle then perform restore of Oracle as described in the NetWorker Module for Databases and Applications Administration Guide. Note: This step is only required if the vcenter database is no longer available. Task 2: Bring the standby vcenter Server online To bring the standby vcenter Server online: 1. Turn on the standby vcenter Server. 2. Ensure that the vcenter Server is up and running. 3. Attach the appropriate ESX or ESXi to the standby vcenter Server. Task 3: Perform a Disaster Recovery of the vcenter Server Appliance After the standby vcenter Server is online with the required ESX or ESXi attached to it, perform the VADP image recovery of the vcenter Server Appliance by using the standby vcenter Server as the destination. The Recovering VADP Backups chapter in the 7.6 Service Pack 2 VMware Integration Guide provides information on how to perform image level recovery from VADP backups and includes information on the related pre-requisites. 14

15 Restoring vcenter Server with the NetWorker Software Recovery Scenario 5: vcenter Server (fresh installation) hosted on Windows with a remote database Restoring this type of backup requires that a user create a fresh target machine as well as perform a reinstall of vcenter application. This type of restore is also used to migrate the vcenter Server to a different higherend machine. Perform the following steps in order: Task 1: Use the appropriate module to perform recovery of database Use the appropriate NetWorker Module recovery steps to restore the vcenter database. For example, if vcenter database was Oracle then perform a restore of Oracle as described in the NetWorker Module for Databases and Applications Administration Guide. Note: This step is only required if the vcenter database is no longer available. Task 2: Create a target machine with fresh operating system image To create a new machine with fresh operating system image: 1. Create a new machine with a fresh operating system image. This machine can either have the same hostname/ip as the original vcenter Server or a different hostname/ip. 2. Install the NetWorker client package on the target machine. 3. If assigning a different hostname/ip for the target machine, ensure that the target machine is configured as a client on the NetWorker server. Task 3: Use the NetWorker User program to restore the vcenter filesystem backups To restore the vcenter filesystem backups: 1. Perform a recovery of the vcenter filesystem backups onto the target machine. Note: Recover all of the save sets that were backed up as part of Backup Scenario 4: vcenter Server hosted on Windows with remote database (non-dr backup), Task 1: Configure the vcenter Server client with required save sets on the NetWorker server on page Ensure that the backups are restored to the same location in the target machine. 3. If the destination machine uses a different hostname/ip from the original vcenter Server, use the directed recovery feature to recover the save sets. 15

16 Restoring vcenter Server with the NetWorker Software 4. If a different hostname/ip is assigned for the target vcenter Server machine, the ESX/ESXi hosts will show up in disconnected state. This is because the ESX hosts must be made aware of that change, otherwise the ESX hosts will continue to send their heartbeats to the original IP address of vcenter Server and appear as not responding or disconnected. The following VMware kb article provides more information The 7.6 Administration Guide provides information on: How to recover data by using NetWorker User program. How to perform directed recovery Task 4: Prepare a DSN pointing to vcenter database Prepare a DSN that points to the database. The vsphere Upgrade Guide at provides more information. Task 5: Reinstall the vcenter Server application on the target machine To reinstall the vcenter Server application on the target machine: 1. Perform vcenter Server installation onto the destination machine. 2. Select the following option during installation: Do not overwrite, leave my existing database in place Note: Ensure that the new vcenter Server is of the same version as the original vcenter Server. If the version is different, you might face issues when connecting to the recovered database. Recovery Scenario 6: vcenter Server Appliance (fresh installation) with a remote database Restoring this type of backup requires that you create a fresh vcenter Server Appliance and then point it to the vcenter database. Perform the following steps in order: Task 1: Use the appropriate NetWorker Module software to perform a recovery of the database Use the appropriate NetWorker Module recovery steps to restore the vcenter database. For example, if vcenter database was Oracle then perform a restore of Oracle as described in the NetWorker Module for Databases and Applications Administration Guide. Note: This step is only needed if the vcenter database is no longer available. 16

17 Restoring vcenter Server with the NetWorker Software Task 2: Deploy a fresh vcenter Server Appliance and then point it to the recovered database To deploy a fresh vcenter Server Appliance: 1. Deploy a fresh vcenter Server appliance with either the same hostname/ip as the original vcenter Server or a different hostname/ip. 2. After deployment, point the new appliance to the recovered database server. 3. Do not to select the following option when configuring the remote database server settings in the vcenter Server Appliance: Reset DB contents If the new vcenter Server Appliance has the same hostname/ip as the original vcenter Server To recover a new vcenter Server Appliance with the same hostname/ip, where the SSL certificates changes, and the ESX/ESXi hosts displays as disconnected in the vsphere client: 1. Right-click Disconnected hosts> Connect. 2. Provide the root login credentials. 3. Follow the prompts to reconnect the ESX hosts. If the new vcenter Server Appliance has a different hostname/ip as the original vcenter Server If a different hostname/ip was assigned for the target vcenter Server Appliance, the ESX/ESXi hosts will show up in a disconnected state in the vsphere Client. This is because the ESX hosts must be made aware of that change, otherwise the ESX hosts will continue to send their heartbeats to the original IP address of vcenter Server and appear as not responding or disconnected. For more information, refer the below VMware kb article at To recover a fresh vcenter Server Appliance with a different hostname/ip as the original the vcenter Server: 1. Right-click Disconnected hosts> Connect. 2. Provide the root login credentials. 3. Follow the prompts to reconnect the ESX hosts. Note: Ensure that the new vcenter Appliance is of the same version as the original vcenter Server. If the version is different, you might face issues when connecting to the recovered database. 17

18 Restoring vcenter Server with the NetWorker Software Copyright 2012 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 18