EMC HomeBase. Agent Recovery and Migration Guide. Version 6.6 P/N REV 03

Transcription

1 EMC HomeBase Version 6.6 Agent Recovery and Migration Guide P/N REV 03

2 Copyright EMC Corporation. All rights reserved. Published in the USA. Published October, 2012 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. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support ( 2 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

3 CONTENTS Preface Chapter 1 Chapter 2 Chapter 3 Chapter 4 Appendix A Recovery and Migration Introduction... 9 HomeBase Base profile Extended profile Profile transport options Profiling the source server Preparing for recovery and migration Recovery Checklist Unsupported applications and components during HomeBase recovery 16 Virtual host Before you begin Changing the virtual host configuration Provisioning for Windows recovery Preparing for Red Hat Enterprise Linux recovery Recovering a Windows Server An overview of the Windows recovery process Provision the server operating system Enhanced Server Recovery process Automatic selection of recommended backup manager Using NetWorker to select multiple savesets Multiple recovery sessions Enhanced Server Recovery using the wizard Initialize a recovery session Options to initialize a recovery session Manual Server Recovery process Base Profile recovery Extended Profile recovery Recovering a Red Hat Enterprise Linux Server An overview of the Red Hat Enterprise Linux recovery process Enhanced Server Recovery using the wizard Initialize a recovery session Options to initialize a recovery session Manual Server Recovery process Manually provision the operating system Manually prepare the operating system Manually finalize operating system Command Line Recovery Options Recovery commands EMC HomeBase Agent Version 6.6 Recovery and Migration Guide 3

4 Contents Recovery command options Appendix B Appendix C Appendix D Storage Recovery General storage recovery considerations Recovery support for Veritas storage Requirements for storage space Ensuring sufficient disks are available Issues affecting recovery performance Disk group recovery Volume recovery File system recovery Windows Application Recovery Active Directory recovery Authoritative domain recovery Multidomain recovery Seizing FSMO roles Member server recovery Microsoft SQL Server 2000 recovery Pre-recovery Step 1: Rebuild the master database Step 2: Restore databases Step 3: Open SQL Enterprise Manager Step 4: Restore the master database Step 5: Restore other databases Microsoft SQL Server 2005 recovery Microsoft Exchange Server 2000 and Exchange Server exceptions Post-extended recovery steps Troubleshooting NetWorker Client is not correctly configured on the NetWorker Server Failure of controlled recovery Failure at Deployment Phase Failure at Base Recovery Phase Failure at Controlled Data Restore Phase Failure at Extended Recovery Phase NetWorker remote access list error NetWorker Data Restore Error: Failed to recover.dll file Index 4 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

5 PREFACE As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC representative if a product does not function properly or does not function as described in this document. Note: This document was accurate at publication time. Go to EMC Online Support ( to ensure that you are using the latest version of this document. Purpose Audience Related documentation This document describes how to perform a recovery or migration. This document is intended for the host system administrator, system programmer, and operator who will be involved in managing HomeBase. The following EMC publications provide additional information: EMC HomeBase Version 6.6 Release Notes EMC HomeBase Version 6.6 Non-EMC Software Copyrights Readme EMC HomeBase Version 6.6 Enhanced Server Recovery Getting Started Guide EMC HomeBase Version 6.6 Enhanced Server Provisioning Getting Started Guide EMC HomeBase Version 6.6 Enhanced Server Provisioning Product Guide EMC HomeBase Server Version 6.6 Installation and Configuration Guide EMC HomeBase Agent Version 6.6 Installation and Configuration Guide EMC HomeBase Server Version 6.6 Administration Guide Conventions used in this document EMC uses the following conventions for special notices: NOTICE is used to address practices not related to personal injury. Note: A note presents information that is important, but not hazard-related. EMC HomeBase Agent Version 6.6 Recovery and Migration Guide 5

6 Preface IMPORTANT An important notice contains information essential to software or hardware operation. Typographical conventions EMC uses the following type style conventions in this document: Normal Bold Italic Courier Courier bold Courier italic Used in running (nonprocedural) text for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, and utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus What the user specifically selects, clicks, presses, or types Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis, for example, a new term Variables Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for specific user input, such as commands Used in procedures for: Variables on the command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values Vertical bar indicates alternate selections the bar means or { } Braces enclose content that the user must specify, such as x or y or z... Ellipses indicate nonessential information omitted from the example Where to get help EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at: Technical support Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. 6 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

7 Preface Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your comments regarding this document to: EMC HomeBase Agent Version 6.6 Recovery and Migration Guide 7

8 Preface 8 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

9 CHAPTER 1 Recovery and Migration Introduction This chapter contains the following information: Introduction... 9 Profiling the source server The HomeBase suite can capture and store the configuration state of a server. This information can be used to recover the system's operating system and configuration state. The HomeBase product suite must be used in conjunction with a backup storage manager solution, such as the EMC Avamar product or EMC NetWorker product. To fully restore a server s functionality, the following components are required: HomeBase Server HomeBase profile from the source system Appropriate operating system installation media HomeBase compliant file system backup Together these components will support the recovery or migration of a server into a different environment. The recovery process has four steps. These steps are the same for all supported operating systems. These steps are shown in Figure 1 on page 10. Recovery and Migration 9

10 Recovery and Migration Figure 1 Recovery steps HomeBase The configuration data that HomeBase collects into a profile varies across operating systems and the operating system installations. The data also depends on the configuration of the server. A HomeBase profile captures major areas of the server configuration such as the hardware, operating system, services, and the applications 10 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

11 Recovery and Migration installed. The operational window required for profiling is typically less than five minutes and there is no need to degrade or offline server services or applications. Servers containing hundreds of volume groups or large active directory installations may require increased profiling time. When a server generates a HomeBase profile, it will generate a base profile isil file and an extended profile isil file. Base profile Extended profile Base profile The base profile contains the key operating system elements needed to recover or migrate a server. The base profile is typically transported offsite to where the server recovery or migration is to be performed. The base profile is required in the initial stages of the recovery or migration process. The base profile file is used to restore basic system settings and configuration of the original server, including the following: Network interface settings Services configuration Security settings Storage structures Routing tables Local settings Name service settings Swap configuration Detailed kernel settings User and group settings Extended profile For Windows Servers, the extended profile contains additional information needed to re-establish a Windows system. It contains the elements of the Windows Registry from the original server that are needed to enable application binaries within the backup media on the target server. In a domain controller recovery, the extended profile contains all the information required to restore Active Directory. Note: For a Windows Server, the extended profile is always required for recovery. For Linux systems, the extended profile contains optional operating system services configuration information. For example, the extended profile contains NIS database information. Introduction 11

12 Recovery and Migration Note: For Red Hat Enterprise Linux servers, the extended profile is typically optional for recovery. By default, the HomeBase Agent writes the extended profile to the local file system after generation, where it should be included as part of any regular system backup. Note: The HomeBase Agent can be configured to transport the extended profile to the HomeBase Server. The EMC HomeBase Agent Version 6.6 Installation and Configuration Guide provides detailed information on this configuration. Table 1 on page 12 describes the size and use of the base and extended profiles. Table 1 Profile size and use Name Common size Use Base profile Less than 5 MB Used during Provision the server operating system on page 25 for Windows and Manually prepare the operating system on page 40 for Linux. Extended profile Between 40 and 50 MB Used during Provision the server operating system on page 25 for Windows and Manually prepare the operating system on page 40 for Linux. The actual size depends on server role. Profile transport options The base profile is a subset of the data contained in the extended profile. Only if an extended profile is available, then it can be used in place of the base profile. The HomeBase Agent can be configured to transport the extended profile to the HomeBase Server. The EMC HomeBase Agent Version 6.6 Installation and Configuration Guide provides detailed information on this configuration. You can configure the profile transport options from the HomeBase Web Console. When specifying transport options, you can specify whether the base profile is sent alone or with an extended profile, and whether the profiles can be sent to multiple HomeBase Servers. The HomeBaseSSL protocol is used when the Agent profile is sent to a HomeBase Server. The primary target list defines the order in which the HomeBase Agent will attempt to send its profile to a HomeBase Server for storage. IMPORTANT The profiles can be sent to two HomeBase Servers only and not more. There is the capability to send the profile to a second HomeBase Server location. The agent will attempt to send a copy of the profile to all designated secondary locations on the list. As with primary locations, multiple secondary locations can be specified. However, the profile will only be sent to the first available secondary location. 12 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

13 Recovery and Migration The HomeBase Servers can reside in a number of geographically remote locations and the configuration can be such that the profile always get through to at least one of the destinations. Additionally, the HomeBase Servers can be configured to replicate between servers. The transport options provide resilience, redundancy, and flexibility. Within the specification, the Agent will first attempt to send the profile to the specified HomeBase Server. This is achieved through the primary and secondary basetransportlist options by configuring the same in the HomeBase Web Console under Agent Configuration: The primary basetransportlist defines a list of methods for transferring the base profile. This will be worked through until a method is successful. Multiple primary locations can be specified. Irrespective of the number of primary locations specified, the profiles will be sent only to the first available primary location. The secondary basetransportlist defines a second list of transfer methods. This is in addition to the primary list. Profile storage By default, the extended profile is not sent to the HomeBase Server for storage. The extended profile is stored on the file system of the profiled server and is expected to be included in the normal file system backup for that server. During recovery, the extended profile is required to be available after the data recovery is completed. This default setting minimizes the storage capacity required on the HomeBase Server. However, if required, it is possible to specify that the extended profile be sent to a HomeBase Server. Profiling the source server To successfully recover a source server, you need an up-to-date profile of that source server. Profiles should be run on a regular basis. Profiles can be generated in the following ways: HomeBase Web Console : The EMC HomeBase Server Version 6.6 Administration Guide provides more information on using the HomeBase Web Console to schedule and generate profiles. Command line: Using the hba profile command on the source server. The EMC HomeBase Agent Version 6.6 Installation and Configuration Guide provides detailed information on the hba profile command. Scheduling options: HomeBase Agents generate profiles based on a schedule configured during the Agent installation or from the HomeBase Web Console. The EMC HomeBase Server Version 6.6 Administration Guide provides more information on how to schedule profile generation. You can also configure the NetWorker savesets to execute the BMR profile creation. Profiling the source server 13

14 Recovery and Migration 14 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

15 CHAPTER 2 Preparing for recovery and migration Recovery Checklist This chapter contains the following information: Recovery Checklist Virtual host Provisioning for Windows recovery Preparing for Red Hat Enterprise Linux recovery Before starting any recovery or migration of a server, make sure that all required components are available and that the recovery environment has been fully commissioned. This requires that a number of tasks be carried out in the HomeBase Server environment to ensure that it is ready for the restore. To assist in the validation, HomeBase provides a Recovery Checklist. This Recovery Checklist provides all the configuration information necessary to provide a suitable server environment in order to successfully recover that profile. The Recovery Checklist can be viewed by: Viewing the source server profile creation output in the HomeBase Web Console or the command line interface. Actively gathering a source server profile Selecting a profile in the HomeBase Web Console for the source server and then selecting View Profile > View Run Log task. Generating the Server Checklist report in the HomeBase Web Console. Hardware - The hardware section of the Recovery Checklist can be used to ensure the target hardware, physical or virtual hardware, is adequate to recover the source server. Software - The software section can be used to ensure that appropriate operating media is available for the target recovery server. Make sure that the following conditions are met: The new target host is provisioned with enough disk space to restore all partitions detailed in the profile. Not providing enough disk space to the new host will result in failure of the original storage configuration restore. This is especially relevant when some storage is required to be basic and the other storage is dynamic. Appendix B, Storage Recovery, provides additional information on storage recovery. The new target host has enough network adapters to restore all IP addresses detailed in the profile. Not providing enough network interfaces to the new host may result in failure of the original network configuration restore. Preparing for recovery and migration 15

16 Preparing for recovery and migration All NetWorker Adapters are configured for maximum speed and duplex on the VLAN. Communication between the new host and the HomeBase Server is critical for all operating systems recoveries. Stable and dedicated VLANs will provide the best opportunity for successful results. The time set on the new host is synchronized with the HomeBase Server time. Failure to do so may confuse the HomeBase Server and Agent and prevent the selected profile from being usable. This typically generates an error message saying that the profile was not licensed. Ensure that processors have the same type of architecture on the source and target servers. Ensure that the operating system edition and maintenance levels are the same on the target server. Unsupported applications and components during HomeBase recovery There are specific applications and components that HomeBase was not designed for. Table 2 Unsupported applications and components during HomeBase recovery Application or Component Citrix Metaframe Citrix XenApp Windows Hyper-V NIC teaming IPV6 configuration Cluster configuration PowerPath Workaround, if any No workaround No workaround No workaround Must be manually reconfigured on the target after the recovery. Must be manually reconfigured on the target after the recovery. The standalone node is recovered but it must be reconfigured and added back to the cluster configuration manually. It must be manually installed and configured to view the external storage. EMC HomeBase does not support recovering Windows clusters directly. In a disaster recovery situation, each node must be recovered as a standalone server, which can be joined together later as a cluster, manually. Provision the server operating system on page 25 provides information on performing a recovery manually. If each cluster member has a separate system drive and accesses the shared data from another drive, it is recommended that you recover the first node instead of recovering additional nodes with the shared drive omitted. Later, rebuild the cluster manually from the first recovered system. In Windows 2008 and Windows 2008 R2, HomeBase does not necessarily restore the currently active network profile from source to target since Windows uses a Network Location Awareness (NLA) service algorithm to determine where a server is and which is the ideal network profile for that server. The currently active network profile dictates the behavior of the Windows firewall and the policies that are enforced. If you are not a domain member or are restoring to a different subnet, Windows might assume that 16 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

17 Preparing for recovery and migration you are in a different network location and is likely to default your profile to public network profile. Even if you are restoring to the same subnet, you might be considered to be in a different location. The public profile is the most restricted profile and this may result in the recovered server not allowing remote desktop connectivity. This happens if the source server has its firewall set to allow RDP when in the private location, but not in the public. The solution is to log in to the server locally and choose an appropriate network location when prompted. Virtual host A virtual host tries to approach the best match for the source profile and the local settings. A virtual host is created during a recovery process. This virtual host is then set as the target of the recovery. This is one of ways by which a user can recover a server. This is explained in Create a virtual host on page 20. The other methods are explained in Recover the source server on page 29 HomeBase version 6.6 introduces new target types when creating a recovery session. The new type of target types are: Virtual Create new virtual host Use existing empty virtual host Use existing virtual host with clean operating systems and agents Physical Use bare physical objects Use physical host with clean operating system and agents In HomeBase version 6.5, these target types are known as Base Server or Bare Virtual Machine and Preinstalled Server or Preinstalled Virtual Machine. Information on using these target types are available at Create a virtual host on page 20 and Recover the source server on page 29. Before you begin Before creating a virtual host: Set up IP pools in vsphere Create a virtual host Set up IP pools in vsphere HomeBase sets as default the most suitable networks compatible with the IPs found in the source profile. Servers that are provided IP addresses from this pool will only be able to talk to other servers within the calculated IP range configured in the vsphere. HomeBase 6.6 enables you to set up IP pools in vsphere to manage the connections. To set up IP pools in vsphere: 1. Open the vsphere Client. Virtual host 17

18 Preparing for recovery and migration The vsphere tree panel appears. 2. Select the Data Center(s) for which you want HomeBase to create the virtual machine. Figure 2 on page 18 shows the data centre from where you can create the virtual machine. Figure 2 Data center used to create the virtual machine 3. Navigate to the IP Pools tab then, click Add. 4. Enter the IP Pool Name and Subnet details. Note: The rest of the fields in this screen are not used by HomeBase. Figure 3 on page 19 shows the IP Pools table where you type the IP Pool name and the subnet details. 18 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

19 Preparing for recovery and migration Figure 3 Adding the IP Pool 5. Navigate to the Associations tab. 6. Select the Network(s) that should use this IP Pool. Each network that you want to use should have an associated IP Pool for HomeBase to automatically assign the right network. Figure 4 on page 19 shows adding a network to use the IP Pool. Figure 4 Associating the network to use the IP pool Virtual host 19

20 Preparing for recovery and migration Note: If IP Pools are not defined, HomeBase still creates the virtual machine with as many Network Interface Cards (NIC) found in the source profile, but each NIC will be attached to the first available network rather than the most suitable network. However, you can manually change this by editing the virtual machine settings when creating the recovery session. Proceed to create a virtual host after you have successfully set up IP pools in vsphere. Create a virtual host IMPORTANT A virtual host must be created before you start a recovery session because the virtual host creation does not start until you click Continue from the View Session page, which is part of the recovery session creation process. To create a new virtual host: 1. Log in to the HomeBase Web Console. 2. Browse to Recovery > Create Session. The Select Source Server page appears. 3. Select the source server to which you want to recover. 4. Click Done. The default values are automatically chosen predicting the most likely recovery to be attempted. 5. After you select the recovery source, select the target type. From Target Host, select Create new virtual host. 6. (Optional) Click Change to customize the settings. If not, accept the default values. 7. Click Create. The View Sessions page appears. This page gives a summary of the configuration of the new virtual host. On this page, an action required message prompts you to continue when you are ready to start the recovery session, which also creates the virtual host. 8. Click Continue when you are ready to initiate the recovery. The virtual machine creation starts. If the virtual host creation process is successful, the status in the View Session page turns from Creating VM to Created VM. If an error occurs during the virtual host creation, you are prompted to retry the process. Repeat the process to successfully create a virtual host. Changing the virtual host configuration To change the configuration of the virtual host: 20 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

21 Preparing for recovery and migration 1. Click Change against Virtual Machine. The Select Virtual Host Configuration page appears. 2. On this page, you can specify the following options: Table 3 Virtual host configuration options Options Name vsphere Description Name of the virtual host. The name of the virtual host is set to the hostname from the source profile. Name of the vsphere connection. The selected vsphere is the first one available in the HomeBase Server. Note: The vsphere connection must be created before starting to create a recovery session. Location ESX Host Data Store Location of the datacenter and the folder path. This is the default location specified when creating the selected vsphere. Name of the ESX host. Represented with values from one to eight. The maximum number of hosts supported by VMware is eight. This depends on the selected ESX host and changes according to the value of the host. Virtual Hardware - Under virtual hardware, you can configure the following: Memory CPUs Disk Size Options Adapter Type Network Memory to be consumed. To be specified in gigabytes. This is the same as specified in the source profile. Denotes the number of CPUs. The maximum number of CPUs supported by VMware is eight. This is the same as specified in the source profile. The size of the provisioning disk. Represented in giga bytes. HomeBase creates the first disk with enough capacity to accommodate the system volume and other system specific volumes such as the boot volume. HomeBase also creates one virtual disk per volume in the source profile for volumes larger than 150 MB. Smaller volumes are accommodated in the first disk. The capacity of each disk is the sum of the size of all volumes that the disk accommodates plus an additional disk space as recommended in Recovery Checklist on page 15. The type of disk provisioning Thin Clustering By default, thin provisioning is selected. The type of adapter used in the virtual host configuration. You can also add and remove adapters. The available network for the virtual host. The network attached to each network is the first one available for the selected host. If the networks are not available, the warnings explained in Non-availability of network adapters on page 23 appear. This varies depending on the selected ESX host and changes according to the value of the host. Virtual host 21

22 Preparing for recovery and migration Table 3 Virtual host configuration options Options IP Address Description The IP Address to be set as the primary IP in the NIC. This lists the static IP addresses found in the profile and two other options - DHCP and Disconnected. DHCP - If DHCP is selected, then NIC is set to obtain an IP address automatically. Disconnected - If Disconnected is selected, then NIC is not connected when the virtual hosts starts although the enhanced recovery still attempts to appropriately configure the NIC based on the NIC configuration in the source profile. Note: The operating system displayed on this page is based on the profile. This is not editable. 3. After you have made the required changes, click Done. Example of virtual host configuration Figure 5, Sample of a virtual host configuration specifications, presents an example of a virtual host configuration. Figure 5 Sample of a virtual host configuration specifications 22 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

23 Preparing for recovery and migration Non-availability of network adapters When creating a virtual host, if HomeBase detects that none of the virtual network adapters are connected to the HomeBase server's network despite the network being available on the default host, then an additional network adapter connected to the HomeBase server's network is added to the virtual host configuration. In addition, if the network pools are not configured in the vsphere, then HomeBase defaults to connecting all the adapters to the first available network in the host. In this context, HomeBase displays the following warnings: Context Reason Warning displayed IP Pools are not configured. The network IP Pools are not configured in the vsphere. Network adapters not connected to HomeBase Server. None of the network adapters are connected to the HomeBase Server. TFTP channel is not configured. The IP address set when configuring the TFTP is channel is used to find out whether there is at least one adapter connected to the HomeBase server's network. Provisioning for Windows recovery Make sure that the following conditions are met: Make sure that you have a minimum of 1GB RAM for 32-bit operating systems and 2GB RAM for 64-bit operating systems. Make sure that your HomeBase server has the correct Windows operating system install media loaded including any required service packs into the software repository. HomeBase requires that for each operating system to be recovered or migrated, that exact operating system is available within the HomeBase Server. IMPORTANT HomeBase Server requires that service packs are integrated with the operating system install media. HomeBase cannot automate standalone service pack upgrades. If the precise installation media is not available directly, manual operating system provisioning is required. Make sure that the new host is recognized from a hardware perspective. The new target hardware may require new drivers to be installed that are not part of the standard Microsoft operating system install media. These additional drivers must also Provisioning for Windows recovery 23

24 Preparing for recovery and migration be loaded into the HomeBase Server. If these drivers are not available, any recovery or migration process stops as if there is a failure in communication with a hardware device. For example, not having the correct network drivers available results in failure of the HomeBase Server to communicate with the new host. Make sure that Microsoft WAIK Toolkit is installed. The WAIK toolkit is used to prepare the HomeBase boot image Again, any non-standard drivers (for example, RIS or monolithic drivers) that are required for network communication must be provided when creating the HomeBase boot image. For Windows 2003 Servers, it is recommended that you recover to a similar type of media license. Recovering to dissimilar Windows media license might require activating the server after recovery. For instance, if you create the source server operating system with Windows 2003 retail license media then, recover it to a target operating system created with a Windows 2003 retail media license server. Do not recover to a target operating system created with Windows 2003 volume license media. Preparing for Red Hat Enterprise Linux recovery Make sure that the following conditions are met: Make sure that you have a minimum of 1GB RAM for 32-bit operating systems and 2GB RAM for 64-bit operating systems. Make sure that the HomeBase Server has the correct Red Hat Enterprise Linux operating system install media loaded into the software repository. Make sure that the new host for your server is recognized from a hardware perspective as the new target hardware might require new drivers to be installed that are not part of the standard Red Hat Enterprise Linux operating system install media. Additional drivers must be loaded into the HomeBase Server. Make sure that the HomeBase software repository is validated and that it contains the required Red Hat Enterprise Linux operating systems and packages. You can do this by creating a HomeBase Server report called the Missing Packages report, using the profile that you intend to recover or migrate. This report will identify any missing packages that should be uploaded into the HomeBase Server software repository before starting. Once missing packages, if any, have been loaded, the report should be run once again to ensure that any required packages for the newly loaded packages are present. Note: Failure to provide all the packages identified will result in manual correction during recovery. 24 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

25 CHAPTER 3 Recovering a Windows Server This chapter contains the following information: An overview of the Windows recovery process Provision the server operating system Enhanced Server Recovery process Enhanced Server Recovery using the wizard Manual Server Recovery process An overview of the Windows recovery process The Windows recovery procedure closely follows the generic four-step process listed in Figure 1 on page 10. If correctly followed, this will recover the full functional capability of the server as captured in the profile being used. Additional instructions are provided in Appendix A, Command Line Recovery Options, for restoring certain types of applications, such as Microsoft Exchange and Microsoft SQL Server. Running a system recovery and restoring binaries recovers all standard applications except those that were backed up online. In order to recover these services, an application-specific recovery procedure is required. This involves creating a blank dataset, starting the application service, and restoring data into it. While HomeBase will restore the running applications, the data related to those applications will need to be re-imported. These procedures are application specific and normally provided by the software vendor. Provision the server operating system IMPORTANT Manual provisioning is required only if the operating system is not automatically provisioned. Complete the following steps to manually deploy the Windows operating system: 1. The target server must be provisioned with the matching base operating system and service pack level for the profile being recovered. Ensure that the operating system image is compatible with the hardware devices on the target server and that network and storage communication is possible. 2. Ensure that the total disk space required, as specified in the selected profile, is available to the operating system. 3. For all supported Windows versions, all empty disks should be configured to be basic type and will then be converted to dynamic as necessary when restoring the base profile. Disks already containing volumes, such as the system disk, will need manual conversion to the profiled types prior to recovery. Recovering a Windows Server 25

26 Recovering a Windows Server 4. Ensure that the operating system on the new server is installed in the same location as the original server, typically C:\Windows. Enhanced Server Recovery process Once the operating system has been successfully installed, the preparation stage for recovery can start. To support this stage, two items need to be installed: The HomeBase Agent An appropriate backup manager client The enhanced server recovery process consists of: Automatic selection of recommended backup manager Using NetWorker to select multiple savesets Multiple recovery sessions Automatic selection of recommended backup manager By default, the HomeBase Server automatically recommends backups depending on the backup manager that is being used. Recovery using Avamar requires a single backup. So, when Avamar is used as a backup manager, only one backup is recommended. The recommendation rules for Avamar backup are: If the profile creation date is before the first known backup of the volume, then the earliest available backup of the volume is added to the recommended backups list. If the profile creation date is after the last backup of the volume, then the latest backup of the volume is added to the recommended backups list. If the profile creation date is within a range of backups of the volume, then the latest backup of the volume after the profile created date is added to the recommended backups list. HomeBase recoveries using NetWorker require a backup (also known as a saveset) per volume to be selected. So, when NetWorker is used as a backup manager, one or more backups are recommended. The backups recommended are the ones deemed most appropriate to ensure a successful recovery. The recommendation rules for each volume are: If the profile creation date is before any known backup with a labelled as Label, then the earliest backup for the label is added to the recommended backups list. If the profile creation date is after any known backup with a labelled as Label, then the latest backup for the label is added in to the recommended backups list. If the profile creation date is within a range of known backups with a labelled as Label, then the backup after the profile created date is added to the recommended backups list. 26 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

27 Recovering a Windows Server Using NetWorker to select multiple savesets Manual backups are not recommended when using NetWorker backups. Unlike Avamar, NetWorker can handle multiple backups. In the Select Backup screen, select at least one saveset for the recovery session. For easier selection, the screen contains a filter option on the top which allows the user to filter the savesets on basis of product, backup server, backup client ID, start date and end date. The backups table contains a Recommended column which indicates whether the saveset is recommended for the recovery. The color: Green indicates recommended selection. Yellow indicates that the selection is within the recommended savesets, but the elapsed time between the saveset and the profile is less than 18 hours (warning period). Red indicates that the selection is not within the recommended savesets and is beyond the warning period. HomeBase Server does not recommend using these savesets, but you can still use them for the recovery. Multiple recovery sessions To select multiple savesets: 1. Select NetWorker as the backup manager. 2. Select the Backup Server to use. The name of the backup server is set on Administrator > Backup Managers at the time of creating server. 3. Fill the Backup Client Id. In case of NetWorker, it is the name of the NetWorker Client installed on the target machine. 4. Use Start Date and End Date to select a time period. The savesets created in this period will be displayed in the filtered result. 5. Select one or more savesets for the recovery session. Consider the following while selecting the savesets: The best option is to select the savesets that are recommended by HomeBase Server, that is, the ones with green color in the Recommended column. The following savesets should be avoided: The savesets that are not recommended by HomeBase Server, that is, the ones with red color in the Recommended column. Manual savesets. These savesets can be recognized by their Type or Level which is manual. When multiple recovery sessions are being conducted concurrently, the progress of all recovery sessions may be viewed in summary form in the Recovery Sessions screen. Establishing connectivity to a HomeBase Server without DHCP configured When booting a Windows server from a CD or a USB drive, the DHCP service provides the IP address of the HomeBase Server. If DHCP is not configured, the Network Settings page is displayed. Enhanced Server Recovery process 27

28 Recovering a Windows Server Note: If DHCP is configured for the HomeBase Server but connectivity for some reason was not able to be established, click Renew to attempt to connect to the HomeBase Server. If that does not work, complete the procedure below. If any required network or storage drivers were not included when the HomeBase boot image was created, use the Load button to add them. Use the Network Settings page to establish connectivity to the HomeBase Server: 1. On the IP Settings panel, select the network card to use, and set the IP address, subnet mask, and default gateway for the HomeBase Server. 2. On the Connection Settings panel, set the HomeBase Server URL, username, and password. 3. Click Set IP. 4. Click Ping or Trace to verify that connectivity to the HomeBase Server has been established. 5. Click OK to continue with Windows deployment. Enhanced Server Recovery using the wizard To perform an enhanced server recovery using the wizard: Initialize a recovery session Options to initialize a recovery session Initialize a recovery session You can initialize a recovery session using four methods. You can initialize a recovery using four methods. Of these, two of are from the Agents section and two are from the Recovery section. Note: If a profile that contains errors is selected for recovery, a warning message is displayed. It is recommended that you do not recover such profiles because the results are unpredictable and the profiles may not be recovered correctly. Through the Agents section: Select an agent and then select the task Recover Agent. This leads to the latest profile from that agent that is being used as the source profile in the new recovery session. When viewing the agent, either select the task Recover Agent or select a profile and then the task Recover Profile. This leads to the latest profile from that agent being used as the source profile in the new recovery session. Through the Recovery section: Select the task Create Session. This prompts for the source agent and then by default selects the latest available profile for use in the new recovery session. 28 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

29 Recovering a Windows Server Recover the source server In the Recovery section, select the task Copy Session. This copies the details of an existing recovery session into a new recovery session. The details of the new session can then be changed if required. 1. Log in to the HomeBase Web Console. 2. Navigate to the Recovery page. 3. From Related Tasks on the left pane, select Create Session. The Select Source Server page appears. 4. Select the source server to which you want to recover. 5. Click Done. IMPORTANT The default values are automatically chosen predicting the most likely recovery to be attempted. If the source server is being backed up to Avamar or NetWorker and the HomeBase server is aware of the backup servers, the most suitable backup is automatically selected. If one or more unsuitable backups are selected, warnings appear in the Create Session screen. The following types of warnings are issued: Strong warning: A strong warning is displayed under the following conditions: The oldest profile was taken 24 hours or more before or after the profile date. The oldest selected backup was taken more than 24 hours after the first profile backup. Regular warning: A regular warning is displayed under the following conditions: The oldest profile was taken six hours or more before or after the profile date. The oldest selected backup was taken more than six hours after the first profile backup. Ignore the warning message and continue the recovery. These warnings are indicators of the profile backup status. The recovery session is not affected by this. 6. From the Target Host list, select Use existing empty virtual host or Use bare physical host. You can also select Existing virtual host with clean operating system and agents or Physical host with clean operating system and agents. If you select, Use existing empty virtual host - or - Use bare physical host Action Proceed with Step 7 on page 30. The process is the same for both the options. Enhanced Server Recovery using the wizard 29

30 Recovering a Windows Server If you select, Existing virtual host with clean operating system and agents - or - Physical host with clean operating system and agents Action Proceed with Step 7 on page 30. The process is the same for both the options. The option Use existing empty virtual host is used for demonstration purpose in documentation. 7. Specify a target server MAC address. Only one session in a Configured or Unconfigured state is allowed in HomeBase server for the same MAC address. If a configured or unconfigured session for the same MAC address exists for a session, HomeBase warns the user about the sessions and provides an option to replace it. 8. (Optional) If the default choice of operating system is incorrect or needs additional configuration, click Change to customize the settings. Table 4 on page 30 describes the fields on the Choose OS page. Table 4 Choose OS page (Windows) Field Operating System Media Key Install this Agent Hostname and Organization Name Password and Confirm Password System Root and Size Description Operating system to install during this recovery. The operating system must have been previously uploaded to the HomeBase Server software repository. The EMC HomeBase Server Version 6.6 Administration Guide describes this process. Media key for the selected operating system. If you have previously uploaded the media key when editing the operating system entry after uploading the operating system, this field is automatically populated when you choose the operating system. Version of the HomeBase agent to install on the target server during this recovery. The agent must have been previously uploaded to the HomeBase repository. Hostname and organization of the target server. These fields are automatically populated. Temporary password for the target server while the operating system is deployed. System root and size of the system disk. These fields are automatically populated. If you do not want to change the default configurations, proceed to next step. 9. Click Create. A summary page with the configuration details of the new virtual host appears. On this page, an action required message prompts you to initiate the deployment using the boot CD or PXE. 10. Click Continue to initiate the recovery. 30 EMC HomeBase Agent Version 6.6 Recovery and Migration Guide

31 Recovering a Windows Server If booting from PXE, select the BIOS setting (if required), and then power on or reboot the target server. Note: Alternatively, if the target is configured to use Wake-on-LAN and PXE, then click Wake in the Related Tasks. If booting from a CD or USB device, insert it into the target server and then reboot. An address is served by DHCP to the target server and the deployment begins. HomeBase installs the operating system on the target server, installs the HomeBase Agent, announces it to the HomeBase Server, and installs the Backup Client. Hint: A progress bar on this page indicates the progress of the recovery session. 11. Ensure that you have met the requirements specified for recovery. When the recovery is in progress, the recovery wizard pauses before starting the base recovery to allow you to: Check if you need to install any additional hardware drivers. Check if you have sufficient disk space and disks. Check if you need to configure any external storage. 12. Click Continue when you are sure that you have met all the requirements. The recovery is initiated and after the base recovery, the target server reboots to allow the backup client to be used to restore the data. The server is now fully recovered. Options to initialize a recovery session After the server is restarted, a local administrator account is enabled to allow login to the server for installation of the backup manager client. This account can be used if the administrative account is not known. Account username: indigostone Account password: H0meBase Install the backup manager client on the new host. The backup manager is used to restore the application binaries and data from the original server. The following restore instructions are to be performed on any disk drives that contain the operating system or application binaries. Any hard disk restorations performed containing just data files do not need to follow the restore instructions. Restore instructions During the restore of the base profile, the HomeBase Agent automatically generates an exclude list for the backup clients installed on the source server during profiling. Each exclude list presents data in a format suitable for each backup manager to import. IMPORTANT Failure to adhere to this exclude list can result in catastrophic server failure at the time of reboot. The validated backup managers are: EMC Avamar Enhanced Server Recovery using the wizard 31