Netbackup 7.6 guide Bmr 1r2l4

[email protected]

\Addons\x86\BMRBS For 64-bit SRT, specify the source location of srd_x64.wim, which is as follows: \Addons\x64\BMRBS is the root folder on the NetBackup Windows installation DVD.

Path to the NetBackup client software image

Enter the path of the BMR client software image.

Edit an SRT This lets you edit SRT parameters. In certain scenarios, you may need to modify the SRT contents. For example, add a new binary to the SRT as part of applying a new release update to the existing BMR version. In such scenarios, you first need to mount the SRT and then modify its contents. The Explore SRT option automatically mounts the selected SRT and shows it in a file explorer view where you can add any new binaries or even modify existing ones. This option is particularly useful when would like to apply any engineering binary within the SRT. If you manually modify an SRT, it may not function properly. In this case, you need to follow the guidelines that Symantec provides with the release update content.

46

Shared resource trees Creating a shared resource tree

Figure 5-1

Edit a Shared Resource Tree

Select the SRT to modify its parameters: ■

Modify the SRT description.

■

Modify the contents in the SRT by clicking Explore SRT.

After modifying the SRT, click either of the following: ■

Click Save changes when clicked on Next.

■

Click Do not save changes when clicked on Next. If you select this option and click Next, the modifications to the SRT description or content is not saved.

Click Next to complete the SRT modification procedure.

Import an SRT This option lets you import an existing SRT. Typically after an upgrade, if there are some existing SRTs of previous version, importing will update the SRT version and recreate the SRT record. Perform the below steps in order to import an SRT: ■

Select the directory on the boot server where the existing SRT is located, which you want to import.

■

Enter the name for the new SRT.

Copy an SRT This option enables you to copy an existing SRT from one boot server to other. Copy operation is always preferred over re-creating a new SRT as it is faster.

47


Perform the below steps in order to copy an SRT: ■

Select the SRT to copy.

■

Enter a name for the new SRT. The SRT name should not contain more than eight alphanumeric characters.

■

Enter a description for the new SRT.

■

Enter a path to or browse to select the location to create the new the SRT.

Delete an SRT Select the SRT to delete, then click OK in the confirmation dialog box. Note: An SRT which is in the mounted state or opened for editing cannot be deleted.

Create a bootable CD or DVD image Bootable CD or DVD image for Fast Boot SRT The steps for creating bootable CD/DVD images from Fast Restore SRTs is as follows: ■

Select the shared resource tree. See “Select an SRT” on page 48.

■

Specify the location of ISO and client verification. See “Specify a location for the ISO image” on page 48.

The process ends with the Copy Progress and the Completing the Shared Resource Tree . Select an SRT Select the shared resource tree that you want to turn into a bootable CD or DVD image to be used for the restore. For legacy SRTs, you must run a prepare-to-restore operation on a client using the selected SRT. Specify a location for the ISO image You need to specify the location for the ISO image. Enter the path or browse to select the directory in which the ISO image is to be stored. The wizard does not create a CD or a DVD; it creates an image that you must burn onto a CD or a DVD. If any clients are listed on this page, they are automatically restored when booting this image.

48


Completing the Shared Resource Tree configuration Click Finish to complete the SRT configuration.

Bootable CD or DVD image for Legacy OS SRT Perform the following steps to create a bootable CD image for a legacy SRT.: ■

Select a shared resource tree See “Select an SRT ” on page 49.

■

Location of ISO image See “Location of ISO image ” on page 49.

The process ends with the Copy Progress and the Completing the Shared Resource Tree . Select an SRT Select the shared resource tree that you want to turn into a bootable CD or DVD image to be used for the restore. Note: For legacy SRTs, you must run a prepare-to-restore operation on a client using the selected SRT. Location of ISO image Enter the path or browse to select the directory in which the ISO image is to be stored. The wizard does not create a CD. It creates an image that you must burn onto a CD.

Add or update packages to an SRT Select the resource to add to the shared resource tree: ■

Add a Windows service pack to an SRT.

■

Update the NetBackup client software image in an SRT. An SRT must contain a NetBackup client image that is the same version as the system or systems to be protected.

■

Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT.

■

Add Symantec Veritas security services to an SRT.

Add a Windows service pack to an SRT This option is specific to Legacy OS-based SRT and is not applicable to Fast Restore SRT. Using this option you can update the Service Pack associated to the particular Windows version within the SRT. For example: You can add Service Pack 2 or

49


Service Pack 1 to a existing Windows 2003 Legacy SRT or add Service Pack 1 to Windows 2008 Legacy SRT. The steps for adding a Windows service pack to an SRT are as follows: ■

Select the legacy shared resource tree to which you want to add a service pack.

■

Select the service pack to add; all service packs available for the selected version of Windows are listed in the drop-down menu.

■

Enter the path to or browse to select the service pack executable (.exe) image.

If you create a legacy SRT with a Microsoft Installation CD that includes a service pack, the wizard recognizes the service pack, and creates a record of it. If you add a later service pack to an SRT that already has a service pack installed, the later one replaces the earlier one.

Add NetBackup Client to an SRT The steps to add NetBackup client software to the shared resource tree are as follows: ■

Select the shared resource tree to which you want to add the client image.

■

Enter the path name to the NetBackup client installation image (Symantec NetBackup Client.msi) or browse to select the image.

An SRT must contain a NetBackup client image that is the same version as the system(s) to be protected. If the SRT already contains a NetBackup client image, it is replaced. An SRT without a NetBackup client is in the Locked state. Ready state indicates a NetBackup client image is installed.

Add NetBackup Security Services to an SRT For NetBackup version 7.0 and later, separate installation of NetBackup Security Services in SRT is not required. Symantec Security Services get installed into an SRT as part of NetBackup client installation. For the SRTs containing an older version of NetBackup client, NetBackup security service should be installed separately into SRT. If you use NetBackup Access Management to ister access to your NetBackup environment, install the NetBackup Security Services (VxSS) software for NetBackup client older version. For more information about Access Management components and how to use Access Management, see the NetBackup Security and Encryption Guide . You would need to perform following steps to add NetBackup Security Services to an SRT:

50


■

Select the shared resource tree to which you want to add the NetBackup Security Services image.

■

Select the version of NetBackup security service.

■

Enter the path to the setup file (in .exe format) or browse to select the image.

Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT You can add maintenance packs or hot fixes that are associated with the installed version of SFW (Veritas Storage Foundation for Windows) to a legacy SRT. This option is not applicable to Fast Restore SRT Steps for adding a Veritas SFW image to a legacy SRT are as follows: ■

Select the legacy OS-based shared resource tree to which you want to add the SFW image.

■

Select the version of SFW.

■

Enter the path to the root of the SFW installation CD or browse to select the folder. Note: The SRT and the restoring client should contain the same base SFW version. For example: If you want to restore a 5.1 SP1 client, the SRT should contain 5.1 SP1 or later SP version. You cannot use SRT with SFW 5.1 to restore an SFW 5.0 client. This is because volume and disk group creation parameters may change across major releases and there may be license key conflicts.

To know the compatibility between the SFW versions of BMR clients and SRT, See Table 5-2 on page 52.. See “Add an SFW Maintenance Pack to an SRT” on page 53. See “Examples screen shots for SFW package installation into SRT” on page 55. During a restore, BMR installs SFW only if it was on the protected system. Therefore, you can use one SRT to protect clients with and without SFW. If you add a later SFW package to an SRT that already has one, the later version replaces the earlier one. Note: Using NetBackup Bare Metal Restore, you can protect clients that have SFW 5.0 and later versions installed. Once a base SFW package is added to the legacy SRT you need to further perform below steps: ■

Apply associated SFW Maintenance Pack to the SRT.

51


Select this option to directly go the Add a Veritas SFW Maintenance Pack Image to an SRT . See “Add an SFW Maintenance Pack to an SRT” on page 53. ■

Apply associated SFW Hot Fix to the SRT. Select this option to directly go the Add a Veritas SFW Hot Fix Image to an SRT . See “Add an SFW Hot Fix to an SRT” on page 53.

Table 5-2 lists the SFW versions that the SRT should have installed to restore clients with specific operating systems and SFW versions. Table 5-2

SRT contents to restore SFW clients

Operating System

SFW version on the client

Windows 2003

SFW 5.0, SFW SFW 5.0 5.0 RP1, SFW 5.0 RP2

RP2

None

SFW 5.1, SFW SFW 5.1 5.1AP1, SFW SP1, SFW SP2

AP1

Hotfix_5_1_01004_407_1974940b Yes

SFW 5.1, SFW SFW 5.1 5.1AP1

AP1

SFW 5.1 SP1

SP1

(32 or 64-bit) Windows 2003 (32 or 64-bit)

Windows 2008

Minimum base Maintenance pack Hot Fix required in the SRT SFW version in required in the the SRT SRT

SFW 5.1

(32 or 64-bit)

Hotfix_5_1_01004_407_1974940b None https://sort.symantec.com/patch/ detail/3354/0/ cGF0Y2gvc2VhcmNobWF0cml4LzIxLzIvMQ Hotfix_5_1_10012_584_1946291

None

https://sort.symantec.com/patch/ detail/3491/0/ cGF0Y2gvc2VhcmNobWF0cml4LzIxLzIvMQ

(32 or 64-bit)

Windows 2008

None

https://sort.symantec.com/patch hp tw /:wwm . cirosoc.tfom/ /detail/3354/0/ s/ cGF0Y2gvc2VhcmNobWF0cml4LzIxLzIvMQ en/detasli.aspx? Famylid I=993c0bc-f 3bcf4009b -e212 -7e85e1857b1 &dsipa lya lng=en

(32 or 64-bit)

Windows 2008

MSXML 6.0 required

SFW 5.1 SP2

SFW 5.1

SP2

None

None

52


Table 5-2

SRT contents to restore SFW clients (continued)

Operating System

SFW version on the client

Minimum base Maintenance pack Hot Fix required in the SRT SFW version in required in the the SRT SRT

MSXML 6.0 required

Windows 2008 R2

SFW 5.1 SP1

SFW 5.1

None

SP1


(32 or 64-bit)

Windows 2008 R2

SFW 5.1 SP1 AP1

SFW 5.1

SFW 5.1 SP2

SFW 5.1

SP1

Hotfix_5_1_10012_584_1946291

None


(32 or 64-bit)

Windows 2008 R2

Hotfix_5_1_10012_584_1946291

SP2

None

None

(32 or 64-bit)

Add an SFW Maintenance Pack to an SRT Using NetBackup Bare Metal Restore, you can protect clients that have SFW 5.0 and later versions installed with all available Maintenance Packs. To know the compatibility between the SFW versions of BMR clients and SRT, refer to the SRT contents to restore SFW clients table. See “Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT ” on page 51. See “Examples screen shots for SFW package installation into SRT” on page 55. The options for adding an SFW Maintenance Pack to a legacy SRT are as follows: ■

The selected SRT is displayed.

■

Select the appropriate Service Pack for the existing SFW version. All Service Packs that are associated with the existing SFW version are available in the drop-down list for selection.

■

Enter the path to the SFW Maintenance Pack installation image or browse to select the image.

Add an SFW Hot Fix to an SRT Using NetBackup Bare Metal Restore, you can protect clients that have SFW 5.0 and later versions installed with all available Maintenance Packs and Hot Fixes.

53


To know the compatibility between the SFW versions of BMR clients and SRT, refer to the SRT contents to restore SFW clients table. See “Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT ” on page 51. See “Examples screen shots for SFW package installation into SRT” on page 55. The options for adding an SFW Hot Fix to a legacy SRT are as follows: ■


■

Select the appropriate Maintenance Pack for the existing SFW version. All Hot Fixes that are associated with the existing SFW MP version are available in the drop-down list for selection.

■

Enter the path to the SFW Hot Fix installation image or browse to select the image.

Add a Windows Hot Fix to an SRT This option is used if the selected legacy SRT has the following configuration: ■

Windows 2003

■

SFW 5.1

To know the compatibility between the SFW versions of BMR clients and SRT, refer to the SRT contents to restore SFW clients table. See “Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT ” on page 51. See “Examples screen shots for SFW package installation into SRT” on page 55. Note: In case of Windows 2003, if you install SFW 5.1 AP1 Hot Fix, you need to also install MSXML 6.0 self-extractable .exe. You can this Windows Hot Fix from the following location http://www.microsoft.com/s/en/details.aspx? FamilyId=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en For Windows 2008 and later versions, MSXML .exe is included in the SFW Hot Fix that you install into the SRT. The options for adding a Windows Hot Fix to a legacy SRT are as follows: ■


■

Select the appropriate Service Hot Fix for Windows 2003, for example Microsoft XML Core Services 6.0.

54


■

Enter the path to the SFW Hot Fix installation image or browse to select the image.

Examples screen shots for SFW package installation into SRT This section provides a series of screen shots that help you understand the compatibility between the SFW package versions of the BMR clients and the SRTs. This section contains the example screen shots for installations of SFW 5.0 and SFW 5.1 versions into SRT. To know about the compatibility between all SFW versions of BMR clients and SRT, See Table 5-2 on page 52. See “Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT ” on page 51. ■

For SFW 5.0, See “Example screen shots for SFW 5.0 installation into SRT” on page 55.

■

For SFW 5.1, See “Example screen shots for SFW 5.1 installation into SRT” on page 58.

Example screen shots for SFW 5.0 installation into SRT Refer to this section while installing SFW 5.0 packages into the selected SRT. Select the SRT into which you want to install SFW 5.0 image.

Select the SFW 5.0 image.

55


Start SFW 5.0 installation.

Select the required SFW 5.0 Application Pack and Maintenance Pack.

56


Start the SFW 5.0 RP2 installation.

This completes the SFW 5.0 installation into the selected SRT.

57


Example screen shots for SFW 5.1 installation into SRT Refer to this section while installing SFW 5.1 packages into the selected SRT. Select the SRT into which you want to install SFW 5.1 image.

Select the SFW 5.1 image.

58


Start the SFW 5.1 installation.

Select the required SFW 5.1 Application Pack.

59


Select the SFW 5.1 SP1 Maintenance Pack.

Start the SFW 5.1 SP1 MP installation.

60


Select the required SFW 5.1 Hot Fix.

Select the required Windows Hot Fix.

61


This completes the SFW 5.1 installation into the selected SRT.

Add NetBackup Release Update or Maintenance Pack to an SRT Steps for adding NetBackup Release Update or Maintenance Pack to the shared resource tree are as follows

1


2

Enter the path name to the NetBackup Client installation image (Symantec Release Update.msi) or browse to select the image. An SRT must contain the base NetBackup client image for that particular version before you apply the relevant Release Update or Maintenance Pack. If the SRT already contains the NetBackup Release Update, it is replaced.

Add NetBackup Language Pack Steps for adding NetBackup Language Pack software to the shared resource tree are as follows:

1


2

Enter the path name to the NetBackup Client installation image (Symantec Language Pack.msi) or browse to select the image. If the SRT already contains a NetBackup Language Pack, it is replaced.

Creating an SRT for UNIX or Linux To create an SRT for UNIX or Linux OS client you need to use the bmrsrt command line.

62


To know the procedure of creating each client OS-specific SRT type, see the following:. ■

See “ Creating an AIX SRT” on page 63.

■

See “Creating an HP-UX SRT” on page 66.

■

See “Creating a Solaris SRT” on page 70.

■

See “Creating a Linux SRT” on page 74.

More information is available about how to copy an SRT to a bootable CD or DVD (create boot media). See “Creating boot media for UNIX and Linux” on page 91.

Creating an AIX SRT When you create an AIX SRT, you are guided through the installation process, as follows: ■

The operating system software

■

NetBackup client software

To create an AIX SRT

1

On the boot server where you want to create the SRT, change to the following directory: /usr/openv/netbackup/bin

2

Enter the following command: ./bmrsrt

63


3

When you are prompted, select the option to create a new SRT.

64


4

Complete the command prompts as indicated in following table. Enter the name of the SRT to create

The name of the SRT that is also used for the directory that contains it. Only alphanumeric characters and underscore (_) characters are allowed.

Enter the description of the new SRT

A description of the SRT.

Enter desired OS level of AIX Enter the levels you can create based on the operating system version of the boot server. Enter desired Architecture(32/64)

Enter whether 32-bit or 64-bit AIX operating system needs to be installed into SRT.

Note: This SRT operating system architecture type is not related to the client operating system architecture type. Instead, it is related to NetBackup client software going to be installed into SRT. If you want to install NetBackup client of the versions older than 7.0 into SRT, this OS architecture type should to be selected as 32-bit. For NetBackup 7.0, select 64-bit as OS architecture type. During the NetBackup client installation into SRT step, bmrsrt gives the appropriate error message if there is any incompatibility between SRT OS architecture type and NetBackup client version. Enter the directory in which to place the new SRT

The path to the directory in which to create the SRT. The root of the SRT (called the SRT path) is the path name to the SRT location, which includes the SRT name. The default is either /export/srt or the directory where an SRT was last created successfully. The directory must already exist.

65


Source of AIX install images

Enter the name of the device where the operating system installation program is inserted or enter the path to the installation image. After you enter the device name or host:/path, the operating system is installed into the SRT.

Enter the source of the NetBackup install images. Specify a device name or an NFS path (host:/path form), or a local directory

Enter the device name where the NetBackup client software installation program is inserted or enter the path to the installation image. After you enter the device name or path, the NetBackup client installation procedure installs the client software into the SRT.

Do you want to continue? [y,n] Enter y. (y) Do you want to install the Enter y. NetBackup client software for this client? [y,n] (y) Enter the name of the NetBackup server:

Enter any non-blank value. The server name is replaced at restore time with the correct values for the BMR client being restored.

Would you like to use servername as the configured name of the NetBackup client? [y,n] (y)

Accept the default or enter any non-blank value. The client name is replaced at restore time with the correct values for the BMR client being restored.

After you install the AIX and NetBackup software, the bmrsrt command provides options to install other software in the SRT. You can either add other software now or quit (you can add software later). During step NetBackup client installation into SRT you might get an error message if the operating system architecture type and NetBackup client version are incompatible. More information is available about how to add other software. See “Adding software to a shared resource tree” on page 78.

Creating an HP-UX SRT When you create an HP-UX SRT, you are guided through the installation process, as follows: ■

Ignite software

66


If the SRT is to be used to restore PA-RISC2-based clients, use Ignite-UX 5.3x or later to create the SRT. ■

Operating system software

■

Operating system patches: You need following HP OS patches: ■

PHCO_31903

■

PHSS_35381

■

PHCO_30544

■

PHSS_33901

■

PHSS_26946

■

PHCO_38279

PHCO_36006 For this patch, you need Dec_2009_11i_GoldPack patch bundle. You can this patch bundle from HP website. If you are recovering client based with VxVM 5.0 version, then you need to install VxVM 5.0 in HP-UX SRT. This requires patch PHCO_40961 to be ed from HP web-site. ■

■


To create an HP-UX SRT

1


2


3


4


The name of the SRT also is used for the directory that contains it. Only alphanumeric characters and the underscore (_) character are allowed.

67


Enter the description of the new A description of the SRT. SRT SRT OS level

The levels you can create based on the operating system version of the boot server.

Enter desired Architecture(32/64)

Enter whether 32-bit or 64-bit HP-UX operating system needs to be installed into SRT.

Note: This SRT operating system architecture type is not related to the client operating system architecture type. Instead, it is related to NetBackup client software going to be installed into SRT. In case you want to install NetBackup client of the versions older than 7.0 into SRT, this OS architecture type should to be selected as 32 bit. For NetBackup 7.0, select 64-bit as OS architecture type. During the NetBackup client installation into SRT step, bmrsrt gives the appropriate error message if there is any incompatibility between SRT OS architecture type and NetBackup client version. Enter the directory in which to The path to the directory in which to create the SRT. The root of the SRT (called the place the new SRT SRT path) is the path name to the SRT location, which includes the SRT name. The default is either /export/srt or the directory where an SRT was last created successfully. The directory must exist.

68


Location (device or directory path) of the Ignite install media.

BMR searches for the following directory (x.x is either 11.00 or 11.11): ■

Ignite-UX/FILE-SRV-x.x/opt/ignite/data/Rel_B.x.x/ (BOSdatapath)

If the BOSdatapath directory is found, BMR expects the Ignite installation image to be in one of the following directories. (Note that -PA indicates Ignite version B41.) ■

Ignite-UX/BOOT-KERNEL/opt/ignite/data

■

Ignite-UX/BOOT-KERNEL/opt/ignite/boot

■

Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data

■

Ignite-UX/BOOT-KERNEL-PA/opt/ignite/boot

If the BOSdatapath directory is not found, BMR looks for a file named INSTCMDS from the tar file supplied in one the following directories: (Note that -PA indicates Ignite version B41.) ■

Ignite-UX/BOOT-KERNEL/opt/ignite/data

■

Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data

If the file is not found, BMR cannot install Ignite. Enter the location (device or The variable x.x is the SRT operating directory path) of the HP-UX x.x system version. install media The following patches are required for this SRT: patch_list

If your version of Ignite requires a patch, you are prompted to provide the path to the specific patch that the version requires.

Note: To create SRT for HP-UX 11.11 They can be found on an HP plus media, or they can PARISC, a new patch PHCO_36006 is be ed from HP Web site. required. This patch is available in HP-UX 11.11 ‘Dec_2009_11i_GoldPack’ patch Location (device or path) of the bundle. You need to this patch media that contains patch_list: bundle and then install the patch PHCO_36006 by providing the location of Dec_2009_11i_GoldPack.

69


Location (device or path) of the Enter the name of the device where the Symantec NetBackup install media NetBackup client software installation media is inserted or enter the path to the installation image. After you enter the device name or path, the NetBackup client installation procedure installs the client software into the SRT. Do you want to continue? [y,n] (y) y

Enter y.

Do you want to install the NetBackup client software for this client? [y,n] (y)

Enter y.

Enter the name of the NetBackup Enter any non-blank value. The server name is replaced at restore time with the server: correct values for the BMR client being restored. Would you like to use servername Accept the default or enter any nonblank value. The client name is replaced at as the configured name of the restore time with the correct values for the NetBackup client? [y,n] (y) BMR client being restored.

After you install the HP-UX and NetBackup software, the bmrsrt command provides options to install other software in the SRT. You can either add other software now or quit (you can add software later). More information is available about how to add other software. See “Adding software to a shared resource tree” on page 78.

Creating a Solaris SRT When you create a Solaris SRT, you are guided through installing: ■

Operating system software

■

NetBackup Client software

You may want to consult the following additional information: ■

See “About installing patches and packages into Solaris SRTs” on page 82.

70


To create a Solaris SRT

1


2


71


3


72


4



Enter the description of the new A description of the SRT. SRT Enter desired level of Solaris/SunOS

Enter the levels you can create based on the operating system version of the boot server.

Enter the directory in which to The path to the directory in which to create the SRT. The root of the SRT (called the place the new SRT SRT path) is the path name to the SRT location, which includes the SRT name. The default is either /export/srt or the directory where an SRT was last created successfully. The directory must exist. Enter a [hostname:/]pathname containing a suitable Solaris x.x Boot CDROM or OS image location

Enter the following: the name of the device where the installation program is inserted OR the path where the OS installation image is extracted.

Note: For Solaris 11.0, SRT creation requires “Automated Installer” ISO path which can be ed from Oracle website containing latest Solaris 11.0 update ISOs. htp:/www.orace l .com/technetwork/server-storage/soa l rsi 11/downo l ads/n i dex.htm.l Make sure that the ISO path is provided when prompted and not the mounted location. After you enter the device name or path, the operating system is installed into the SRT.

73


Enter a [hostname:]/ pathname containing NetBackup client software

Enter the name of the device in which the NetBackup software installation media is inserted or enter the path to the installation program (named install). After you enter the device name or path, the NetBackup installation procedure installs the client software into the SRT.

Do you want to continue? [y,n] (y) y

Enter y.


Enter y.

Enter the name of the NetBackup Enter any nonblank value. The server name is replaced at restore time with the server: correct values for the BMR client being restored. Would you like to use servername Accept the default or enter any nonblank value. The client name is replaced at as the configured name of the restore time with the correct values for the NetBackup client? [y,n] (y) BMR client being restored.

After you install the Solaris and NetBackup software, the bmrsrt command provides options to install other software in the SRT. You can either add other software now or quit (you can always add software later). More information is available about how to add other software. See “Adding software to a shared resource tree” on page 78.

Creating a Linux SRT The first time you create an SRT on a Linux boot server, you are guided through installing the following software: ■

The operating system software.

■

BMR third-party products, the open source products that may not be included in the vendor Linux distribution. To a CD image at no charge, see the following: http://www.symantec.com/business//index?page=content&id=TECH37875

■

NetBackup client software.

74


During this process, the bmrsrt command copies files from BMR third-party installation program to the following directory: /usr/openv/netbackup/baremetal/server/data/media

Each time thereafter that you create an SRT on that boot server, bmrsrt uses those installation files. You do not have to enter the path to the third-party product image again. If you want to be prompted for the installation program or image location again, remove the media directory before running bmrsrt. The BMR third-party products CD is distributed as an ISO file system image. You can the image and use it as the source image or write it to CD media. To create a Linux SRT

1


2


75


3


76


4



Enter the description of the new A description of the SRT. SRT Enter the directory in which to The path to the directory in which to create the SRT. The root of the SRT (called the place the new SRT SRT path) is the pathname to the SRT location, which includes the SRT name. The default is either /export/srt or the directory where an SRT was last created successfully. The directory must exist. The following media is required: The Linux distribution (Red Hat or SUSE) and the required disk. Linux distribution - disk x of The bmrsrt command prompts you x for several of the Linux installation discs. Please load the media now. Some systems try to mount the media that Load media from: is loaded in the CD drive automatically (such as the Red Hat magicdev process). When you are prompted for media on those systems, do the following: load the media into the drive, close the drive tray, and wait for the drive light to stop flashing before pressing Enter. The following media is required: Enter the name of the device in which the BMR third-party products CD is inserted BMR third-party products CD or enter the path to the installation image. (3PPCD) This CD contains open source the Please load the media now. components that BMR uses on Linux systems. Load media from:

77

Shared resource trees Managing shared resource trees

The following media is required: Enter the name of the device in which the NetBackup client software installation NetBackup x.x Client media is inserted or enter the path to the Please load the media now. installation image. Load media from:

After you enter the device name or path, the NetBackup client installation procedure installs the client software into the SRT.

Do you want to continue? [y,n] (y) y

Enter y.


Enter y.

Enter the name of the NetBackup Enter any nonblank value. The server name is replaced at restore time with the server: correct values for the BMR client being restored. Would you like to use servername Accept the default or enter any nonblank value. The client name is replaced at as the configured name of the restore time with the correct values for the NetBackup client? [y,n] (y) BMR client being restored.

After you install the Linux and NetBackup software, the bmrsrt command provides options to install other software in the SRT. You can either add other software now or quit (you can always add software later). More information is available about how to add other software. See “Adding software to a shared resource tree” on page 78.

Managing shared resource trees You can import, copy or delete the existing SRTs and can also add softwares into an SRT.

Adding software to a shared resource tree Install additional software into an existing SRT only if it is required during a restore. Additional software may include an operating system patch or fileset that NetBackup client software requires. The software in an SRT is not installed on the restored system. It only brings the protected system to a state from which the original files can be restored. Therefore, you do not need to install the following: patches,

78


maintenance levels, Maintenance Packs, service packs, fileset, or drivers into an SRT that are in a protected system. Clustering software does not need to be installed into an SRT. After the local file systems are restored, the client res the cluster. More information is available on the following tasks: ■

See “Adding software to a UNIX or Linux SRT” on page 79.

■

See “Adding software to a Windows SRT” on page 83.

Adding software to a UNIX or Linux SRT The bmrsrt command provides options to install additional software in an existing UNIX or Linux SRT. The following options are available, although not all options are ed on all systems: ■

Symantec NetBackup Maintenance Pack

■

Veritas Volume Manager and Veritas File System

■

Symantec Security Service

■

Other software The name of the option depends on the operating system.

Note: Use only the specific options from this list to add products to an SRT. If you did not add required NetBackup software when you created the SRT, a prompt appears to add it when you select the modify option. After you add the NetBackup software when you create an SRT, the bmrsrt command provides options to install other software in the SRT. To add software to a UNIX or Linux SRT

1

On the BMR boot server where the SRT resides, change to the following directory: /usr/openv/netbackup/bin

2


3

When you are prompted, select the option to modify an existing shared resource tree.

79


4

Enter the name of the SRT to modify.

5

Select intended installation option. The bmrsrt command guides you through software installation. Usually, you have to enter the path to the installation program or image for the software. To continue, see the following information about the software you install: ■

See “About adding NetBackup Maintenance Packs” on page 80.

■

See “About adding Veritas Volume Manager and Veritas File System” on page 80.

■

See “About adding Symantec Security Services” on page 81.

■

See “About adding other software” on page 82.

About adding NetBackup Maintenance Packs If a NetBackup maintenance or feature pack is installed on the clients the SRT protects, install that Maintenance Pack or feature pack in the SRT. When you select the install option of Symantec Maintenance pack, you are prompted for the location of the installation program or image as follows::

Location (device or path) of the Symantec NetBackup Maintenance Pack media

Enter the full path to the location of the installation program or image.

About adding Veritas Volume Manager and Veritas File System The following information does not apply to Linux systems. If Veritas Volume Manager (VxVM) and Veritas File System (VxFS) are installed on the systems that the SRT protects, install them in the SRT. Then BMR can use them to partition disks and rebuild file systems. The VxVM and VxFS versions in the SRT must exactly match that of the client being restored. If the versions do not match, the restored client software is unable to access the file systems and volumes. If protected clients have different versions of VxVM or VxFS, create a separate SRT for each of those versions. However, SRTs that include VxFS and VxVM can be used to restore the clients that do not have VxFS or VxVM installed. If you need more than one SRT of the same operating system, create an SRT with only the operating system and NetBackup client software. (For example, if you want to restore the clients that have different versions of VxVM or different drivers.) Then make as many copies as you need and add the different versions of the other

80


software to the copies. To copy an existing SRT usually is faster than to create an SRT. Identify any prerequisites that VxVM and VxFS require, such as operating system patches. Install them in the appropriate order before you install VxVM and VxFS. Warning: On Solaris systems, that any patches the patchadd -C flag. Only install patches that the patchadd -C flag into the SRT. Most patches for VxFS and VxVM do not the patchadd -C flag. Test results show that the clients that use patched versions of VxFS and VxVM can perform a restore successfully. They perform restores successfully even when they use an SRT that contains unpatched versions. The Install Veritas Volume Manager and Veritas File System option in the bmrsrt command prompts you to:

Install Veritas License Software (prerequisite to below) Install Veritas Volume Manager Install Veritas File System

You do not have to untar and uncompress the packages before you install them in an SRT. When you are prompted for the path to each component, enter a path to the extracted packages. Or enter a path to the root directory of the installation program (the directory that contains the file_system and volume_manager directories). For more information about operating system dependencies for VxVM and VxFS, see OSCL matrix on http://www.symantec.com/business//index?page=content&id=TECH76648

About adding Symantec Security Services Bare Metal Restore version 7.6, does not require separate installation of Symantec Security Services in SRT. Symantec Security Services gets installed into SRT along with NetBackup client installation. For the SRTs containing an older version of NetBackup client, Symantec Security should be installed separately into SRT. If you use NetBackup Access Management to ister access to your NetBackup environment, install the Symantec Security Services (VxSS) software for NetBackup client versions earlier than 7.5. For more information about Access Management components and how to use Access Management, see the NetBackup Security and Encryption Guide.

81


About adding other software Use only the specific options to add software to an SRT. The following menu options for other software depend on the operating system of the SRT: AIX

Maintenance levels (MLs) or additional fileset

HP-UX

No other software is required; therefore, you cannot add software

Linux

Additional drivers

Solaris

Additional packages or patches

When you install other software, you are prompted for the following: the location of the installation program, image, package, patch, fileset, rpm, and so on (depending on operating system). See “About installing patches and packages into Solaris SRTs” on page 82. See “Installing device drivers into Linux SRTs” on page 82.

About installing patches and packages into Solaris SRTs Always use the bmrsrt command to install patches and packages into Solaris SRTs. The bmrsrt command prevents any damage from the packages that do not the pkgadd -R flag. Patches that are installed into the miniroot that do not the patchadd -C flag can damage BMR boot servers as well as JumpStart servers. Therefore, do not install the patches into an SRT that do not the patchadd -C flag.

Installing device drivers into Linux SRTs To add or update device drivers in a Linux SRT, use the following procedure.

82


To install device drivers into Linux SRTs

1

Select Modify an existing SRT option under the main menu and provide name of the SRT to be modified.

2

Choose the option Install additional patches/drivers. The following appears:

The following additional packages are available to install: 1. Install/update kernel drivers. 2. Install a Linux Update/Service Pack. 3. None of the above, leave unchanged. Enter your selection [3] :

Select the appropriate option. Choose option 1 to add additional Linux kernel drivers (.o, .ko) files into the SRT. This option can be used to add the drivers which are not present into the Linux installation media by default and need to be loaded during BMR restoration.

Adding software to a Windows SRT You can install the following into an existing Windows SRT: ■

Windows service pack (Legacy SRTs only)

■


■

Veritas Storage Foundation for Windows

■

NetBackup Security Services

To add software to a Windows SRT

1

On the Start menu on the Windows BMR boot server that hosts the SRT, click Programs > Symantec NetBackup > Bare Metal Restore Boot Server Assistant.

2

In the Bare Metal Restore Boot Server Assistant, click Shared Resource Tree istration Wizard.

3

In the Shared Resource Tree istration Wizard, click Next on the Welcome .

4

Select the option to update an SRT. ■

Add a Windows service pack to an SRT. See “Add a Windows service pack to an SRT ” on page 49.

83


5

■

Add or update NetBackup client software images in an SRT. An SRT must contain a NetBackup client image that is the same version as the system(s) to be protected. See “Add NetBackup Client to an SRT ” on page 50.

■

Add Veritas Storage Foundation for Windows to an SRT. See “Add Symantec Veritas Storage Foundation for Windows (SFW) to an SRT ” on page 51.

■

Add Symantec Security Services to an SRT. See “Add NetBackup Security Services to an SRT” on page 50.

Follow the prompts to add software to the shared resource tree. The Shared Resource Tree Wizard help pages provide additional information.

Importing a shared resource tree This section provides information on how to import a shared resource tree.

Importing an SRT on UNIX and Linux This topic provides the procedure to import a shared resource tree on UNIX and Linux. On UNIX and Linux boot servers, use the bmrsrt command to import an SRT. To import an SRT on UNIX and Linux

1


2

Select the option to import an existing shared resource tree.

3

Enter the required information, as follows: ■

The name for the new SRT

■

The path on the boot server where the existing SRT is located

Importing an SRT on Windows This topic provides the procedure to import a shared resource tree on Windows. Note: In NetBackup 7.0 and later versions, Windows Boot Servers do not importing SRTs of versions 6.X and 6.5.X. Windows 7.1 Windows Boot Servers do not import of old Legacy DOS-based SRT.

84


See “Import an SRT ” on page 47.

Copying a shared resource tree You can create a new SRT by copying another SRT. The new SRT is created on the boot server where you run the bmrsrt command (UNIX and Linux) or Shared Resource Tree istration Wizard (Windows). The existing SRT may reside on either a local or a remote boot server. NFS services are required to copy an SRT that resides on a remote boot server. The remote boot server must have NFS server services enabled. An SRT that is in the process of being modified cannot be copied. Usually, it takes several minutes to copy an SRT. However, it can take longer depending on the size of the source SRT and the network speed if you copy to a different boot server. See “Copying an SRT on UNIX and Linux” on page 85. See “Copying an SRT on Windows” on page 86.

Copying an SRT on UNIX and Linux On UNIX and Linux boot servers, use the bmrsrt command to copy an SRT. To copy an SRT on UNIX and Linux

1

Change to the following directory on the boot server where you want to create the SRT: /usr/openv/netbackup/bin

2


3

When you are prompted, select the option to copy an existing shared resource tree.

4

When you are prompted, enter the required information, as follows: ■

The name of an existing SRT to copy

■

The name for the new SRT

■

The path on the boot server in which to create the SRT

■

The description of the SRT

■

(Linux only). The path to the device in which the BMR third-party options CD is inserted or an installation image of the BMR third-party options CD

85


(Only if the SRT is copied to a Linux boot server where an SRT has not been created.)

Copying an SRT on Windows On Windows boot servers, use the Shared Resource Tree istration Wizard to copy an SRT. Caution: In NetBackup 7.0 and later versions, Windows Boot Servers do not copy of SRTs of versions 6.X and 6.5.X. See “Copy an SRT ” on page 47.

Deleting a shared resource tree You can delete an SRT by using the bmrsrt command (UNIX and Linux boot servers) or Shared Resource Tree istration Wizard (Windows boot servers). An SRT that is allocated to a restore task or being modified cannot be deleted.

Deleting an SRT on UNIX and Linux On UNIX and Linux boot servers, use the bmrsrt command to delete an SRT. To delete an SRT on UNIX and Linux

1

Change to the following directory on the boot server where the SRT resides: /usr/openv/netbackup/bin

2

Run the following command: ./bmrsrt

3

When you are prompted, select the option to delete an existing shared resource tree.

4

When you are prompted, type the name of the SRT and press Enter.

5

When you are asked if you want to delete the SRT, enter y to delete the SRT. If the SRT is locked, this operation fails. See “Breaking a stale shared resource tree lock” on page 88.

86


Deleting an SRT on Windows On Windows boot servers, use the Shared Resource Tree istration Wizard to delete an SRT. See “Delete an SRT” on page 48.

Enabling or disabling SRT exclusive use The following information applies only to UNIX and Linux clients. If you save custom files with the client configuration, you can copy those custom files into the SRT. They then are used in the temporary operating system environment on the client during the restore. To do so, enable the SRT for exclusive use by the client. Other clients cannot use that SRT until you disable it from exclusive use, which removes the custom files from the SRT. Enable exclusive use before you do any of the following: ■

Run a prepare-to-restore operation.

■

Run a prepare-to-discover operation.

■

Create a bootable CD or DVD (if you create a bootable CD or DVD that contains an SRT that has custom files).

Note: If you enable an SRT for exclusive use before custom files are saved for that client, the prepare-to-restore or prepare-to-discover process fails. You may want to consult the following additional information: See “Saving custom files on UNIX or Linux” on page 31. To enable or disable SRT exclusive use

1

On the boot server where the SRT resides, change to the following directory: /opt/openv/netbackup/bin

2


3

When you are prompted, select the option to modify an existing shared resource tree.

4

When you are prompted, enter the name of the SRT to modify.

5

When you are prompted, select the option to change exclusive use of the SRT.

6

When you are prompted, do either of the following: ■

To enable exclusive use, enter a client name.

87


■

To disable exclusive use, press Enter without entering anything.

Repairing a damaged shared resource tree The following information applies only to UNIX and Linux boot servers. If BMR places an SRT into a DAMAGED state, it may be possible to repair it to return it to a READY state. If an SRT is marked DAMAGED because a previous bmrsrt command is interrupted, recovery is likely. If you are unsure why an SRT was marked DAMAGED, delete it and create a new one from scratch. SRT states appear in the Shared Resource Trees view of the NetBackup istration Console. To repair a damaged share resource tree

1

Change to the following directory on the boot server on which the SRT resides: /usr/openv/netbackup/bin

2


3

Enter the number of the option to modify an existing shared resource tree.

4

When you are asked for the name of an SRT, enter the name of the damaged SRT.

5

When you are asked if you want to continue, enter y. The bmrsrt program attempts to repair the SRT. The program guides you through installation of any missing SRT components. If repair is successful, the bmrsrt modify menu appears. When you quit the program, the SRT is in a READY state.

Breaking a stale shared resource tree lock The following information applies only to UNIX and Linux boot servers. An SRT in the LOCKED_READ or LOCKED_WRITE state is busy and most operations are not allowed. To manage a locked SRT, you should wait for the process using the SRT to finish and release the lock before you proceed. (The one exception is that you can allocate an SRT in a LOCKED_READ state to a restore task.) In rare cases, an SRT may be left with a stale lock. For example, if a boot server crashes or is rebooted in the middle of an SRT operation, the SRT may be left locked. If you are sure that an SRT lock is stale, you can break the lock.

88

Shared resource trees Managing boot media

SRT states are displayed in the Shared Resource Trees view of the NetBackup istration Console. To break a stale SRT lock

1

Change to the following directory on the boot server on which the SRT resides: /usr/openv/netbackup/bin

2


3

When you are asked for a select, provide the number of the option to modify the Shared Resource. The following appears: Enter the name of an existing SRT :

4

When you are asked for the name of an existing SRT, enter the name of the locked SRT and press Enter. Warning: Do not attempt to break an SRT lock unless you are positive that the SRT is stale. If you break the lock of an SRT while it is in use, it may become corrupted.

5

When you are asked if you are sure that you want to break the lock, enter y to break the lock. The stale lock is broken. The bmrsrt command modify menu appears. When you quit the program, the SRT is in a READY state.

Managing boot media Boot media is used to boot a client and provide the shared resource tree or the resources to mount a shared resource tree. The boot media contains a small run-time environment that includes a kernel, a RAM file system, libraries, and programs. The client system firmware boots the kernel from the media. This boot media also contains a shared resource tree. If you use media to boot the client system, you must use BMR to prepare the appropriate boot media. You can prepare boot media at any time before the restore. However, a prerequisite is that the shared resource tree for the protected system must exist. Boot media is created from the resources that are stored in an SRT.

89


About the ed boot media on Windows for BMR 7.0.1 and later versions The BMR restore process begins by network booting the client from a BMR boot server or from BMR prepared boot media (CD or DVD). You can restore a client using Fast Restore SRTs or Legacy OS-based SRTs. Note: The Legacy OS-based Restore of Windows Server 2008 SP2 systems can be done with a Legacy OS-based SRT that is at Windows Server 2008 SP1 level. The Prepare To Restore step allows this special scenario. In BMR 7.0.1 and later versions, you can boot BMR clients only with the following options on Windows platform: ■

Network boot

■

CD/DVD Media boot

Note: In BMR 7.0.1 and later versions, floppy-based restore is not ed on Windows platform because of the elimination of PC-DOS. Therefore the Legacy Boot Floppy Wizard link on the Boot Server Assistant screen is removed.

About writing a CD or DVD The size of the media boot image that BMR produces depends on several factors. The structure of the installation program can change from one release to another and from one type of media (CD) to another (DVD). Therefore, sizes of the final images that are produced may be different under seemingly identical conditions. The size of the media boot image that BMR produces depends on the following: ■

The optional software packages on the SRT

■

The operating system version

■

The install media type used (where applicable) during media boot image creation.

In all cases, if the final media boot image that BMR produces fits on a CD, burn the image to a CD or a DVD. However, if the final image cannot fit on a CD, you must burn a DVD. CD/DVD media must be bootable by the system for which you create it. To determine the correct way to create a bootable CD/DVD for the specific system, see the instructions that are provided with your CD/DVD writing software. In addition, consider the following:

90


■

The CD/DVD image that is created for AIX, Linux, and Solaris uses ISO-9660 format. HP-UX uses a binary format that is different from ISO.

■

BMR does not contain CD/DVD writing software. Burn the CD/DVD image onto a disk using CD/DVD writing software that s the following: ■

ISO-format images for AIX, Linux, and Solaris

■

Binary images for HP-UX

The procedures for writing CDs/DVDs vary between applications; refer to the documentation for procedures. ■

The CD/DVD writing software may require that ISO-format or binary CD/DVD image files end in a .iso extension. If necessary, you can add a .iso extension to the CD/DVD image before you write it.

■

If the BMR boot server does not have CD/DVD writing hardware and software, transfer the CD/DVD image to a system that does. Ensure that the CD/DVD image file transmits as a binary file and transfers without errors; corrupted CD/DVD image files produce unpredictable results.

■

For the CD/DVD media that includes an SRT, the name of the SRT appears as the content of the root directory on the CD/DVD.

■

Label the CD/DVD for easy identification. Include the following information.

■

■

The client name (Windows clients)

■

The NetBackup version that is used

■

The operating system of the SRT that is installed

■

Any extra software installed

BMR does not use the CD/DVD image file after it is created. Therefore, you can move, rename, or delete the image file after you write the CD/DVD.

Creating boot media for UNIX and Linux On UNIX and Linux systems, use the bmrsrt command to create a bootable CD/DVD image that contains an SRT. After you create the CD/DVD image, you must use CD/DVD writing software to burn the image onto a CD/DVD. This process copies an existing SRT to the CD/DVD media; therefore, an SRT that s the client must exist. The following is the required information: ■

The name of the SRT you want to use.

91


■

The name to use for the SRT on the CD/DVD.

■

The path to a directory that has enough free space to store the CD/DVD image.

To create boot media for UNIX and Linux

1

On Solaris systems only, use the following command to that the vold process is not running on the boot server where the SRT resides: # ps -ef | grep vold

If it is running, do the following: ■

To eject any CD/DVD that may be loaded, run the following command # eject

■

To stop the vold process, run the following command # /etc/init.d/volmgt stop

2

On the boot server on which the SRT resides, change to the following directory: /usr/openv/netbackup/bin

3


4

When you are prompted, select the option to create a new CD/DVD image based shared resource tree.

5

Continue by referring to the information about the operating system. See “About boot media for AIX” on page 92. See “About boot media for HP-UX” on page 93. See “About boot media for Linux” on page 93. See “About boot media for Solaris” on page 93.

About boot media for AIX You must have the AIX installation program that created the SRT that you want to use to create the boot media. (You must have it even if you created the SRT from a network copy of the media.) You must enter the device name that contains the installation program. The directory for the CD/DVD image should not be a direct prefix of the directory that contains the SRT you intend to use.

92


For example, you can use the following for SRT /export/srt/aix433esm: ■

Do not specify /, /export, or /export/srt for the location.

■

You can specify /export/srt/mb because it is not a direct prefix of the SRT path.

About boot media for HP-UX HP-UX uses a binary format that is different from ISO. The CD/DVD image file is a binary image of the CD/DVD and does not contain an extension. However, you can add an .iso extension to the CD/DVD image if your CD/DVD writing software requires it. The CD/DVD recording programs that are known to work for HP-UX images are as follows: ■

Sony CD/DVD Extreme - Add an .iso extension to the image file name and use the Global Image or Other Image option from the File menu options.

■

Nero - Add an .iso extension to the image file name, and use the Burn Image to Disk option.

Note: The Roxio Easy CD/DVD Creator recording program does not work for HP-UX images.

About boot media for Linux For Linux, the bmrsrt command creates a bootable ISO image file by using the name of the SRT with an .iso extension. Any standard CD/DVD writing software can be used to write media from this file.

About boot media for Solaris You must have the Solaris installation media (Software 1 of 2) that created the SRT you copy to the CD/DVD. You must enter the device name that contains the installation media. After you enter the information about the SRT, the following information appears: ■

If Veritas Volume Manager (VxVM) is installed on the BMR boot server, the following appears: What do you want to use for temporary space? Select one of the following options: 1. Use a disk group.

93


2. Use a raw partition. Enter your selection (1-2) [1] :

Enter 1 or 2. Then enter the name of the disk group or the device file for the raw partition. If you use a raw partition for temporary storage, you are prompted to continue. ■

If Veritas Volume Manager (VxVM) is not installed on the BMR boot server, the following appears: Enter the name of a partition of size 103040 or more blocks

Enter the name of the device file for the raw partition. Then respond to the next prompt if you want to continue. After the CD/DVD image is created, restart the vold process (/etc/init.d/volmgt start) if you stopped it before running the command bmrsrt.

Creating boot media for a Windows client Windows systems may create a bootable ISO image which can be burned to either a CD or DVD. To create boot media for a Windows client

1

On the Windows BMR boot server, select Programs > Symantec NetBackup > Bare Metal Restore Boot Server Assistant from the Windows Start menu. The Bare Metal Restore Boot Server Assistant screen appears.

2

Click Shared Resource Tree istration Wizard.

3

Select the option for Create a Bootable CD/DVD from a Shared Resource Tree.

4

Follow the prompts to create the boot media.

94

Chapter

6

Restoring clients This chapter includes the following topics: ■

BMR restore process

■

Preparing a client for restore

■

BMR disk recovery behavior

■

About restoring BMR clients using network boot

■

About restoring BMR clients using media boot

■

About restoring to a specific point in time

■

About restoring to dissimilar disks

■

Restoring to a dissimilar Windows system

■

About restoring NetBackup media servers

■

About restoring BMR boot servers

■

About external procedures

■

About SAN (storage area network)

■

About multiple network interface

■

Port usage during restores

BMR restore process The process to restore a protected system depends on the type of restore you want to perform and the operating system of the client.

Restoring clients BMR restore process

Table 6-1

Restore types

Restore type

Procedures

To restore to the same client and use the most recent backup

See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

To restore to a specific point in time

See “About restoring to a specific point in time” on page 123.

To restore a client in which the disks are different

See “About restoring to dissimilar disks” on page 126.

To restore to a new target system (only on Windows systems)

See “Restoring to a dissimilar Windows system” on page 131.

To restore a NetBackup media server

See “About restoring NetBackup media servers” on page 136.

To restore a BMR boot server

See “About restoring BMR boot servers” on page 139.

To customize the restore process

See “About external procedures” on page 139.

To restore to hosts with Veritas Storage Foundation for Windows.

See “About legacy restores on Windows” on page 201.

Other information is available. See “Preparing a client for restore” on page 98. See “ BMR disk recovery behavior” on page 100. See “About SAN (storage area network) ” on page 149. See “Port usage during restores” on page 152. The NetBackup BMR master server manages the restore process, as follows: ■

The master server creates the necessary configuration files and restore scripts (on UNIX and Linux) or restore processes (on Windows) and allocates the boot server when the prepare-to-restore operation runs.

■

The client boots either by network boot or media boot.

■

The client accesses the shared resource tree, either from a boot server or from the boot media.

96

Restoring clients BMR restore process

■

The client runs a temporary operating system environment that is known as the restore environment. The restore environment starts from the shared resource tree.

■

The client restore environment retrieves the restore script and configuration files from the master server.

■

The client restore environment starts the customized restore process, which configures disks.

■

The client restore environment performs an automated restore using the NetBackup client software, which restores all required files and data from the NetBackup server.

■

The client reboots, which starts the restored operating system and de-allocates the boot server.

■

Dissimilar system restore tasks are completed (dissimilar system restore only).

Figure 6-1 shows a standard network restore. Figure 6-1

Network restore 2

1

3

UNIX Client Boot server NetBackup media server (backup image) Boot server SRT

Boots from a shared resource tree over the network

Windows Client

Accesses system files and client software from the SRT on the boot server

Boots from a BMR-prepared CD, DVD, or floppy disk

Figure 6-2 shows a media restore.

Restores files from the NetBackup backup image

97

Restoring clients Preparing a client for restore

Figure 6-2

Media restore 2

1

3

BMR Client NetBackup media server (backup image) CD-based SRT or DVD-based SRT Boots from a BMR prepared CD or DVD

Accesses system files and client software from the SRT on the CD media or DVD media

Restores files from the NetBackup backup image

Preparing a client for restore Before you restore a client, you must prepare to restore (PTR) the client. During a prepare-to-restore operation, the NetBackup master server does the following: ■

Retrieves the client configuration from the master server database.

■

Creates the restore script and the configuration files that are used to restore the client.

■

Allocates the boot server resources for the selected client recovery.

When you prepare to restore a client, you select the configuration to use for the restore, as follows: ■

For a standard restore (also known as a self restore, which is a restore to the same system), select the current configuration.

■

For other types of restores, select the configuration that you created for the restore.

To ensure that the restore includes the most recent data, Symantec recommends that you prepare to restore immediately before you restore a system. To prepare a client for restore

1

In the NetBackup istration Console, expand Bare Metal Restore Management > Hosts > Bare Metal Restore Clients.

2

Select a client or a client configuration.

98

Restoring clients Preparing a client for restore

3

Select Actions > Prepare to Restore.

4

In the Prepare to Restore Client dialog box, select the appropriate values for the restore. Some fields may be completed depending on whether you selected a client or a client configuration. If some other PTR options are selected, See “ BMR disk recovery behavior” on page 100.

5

Click OK. Bare Metal Restore runs all the processes to prepare for a restore.

6

After the processes finish, in the dialog box that appears, click OK. The client is listed in the Bare Metal Restore Tasks in Queued state. The Prepare-To-Restore step may take few minutes to complete.

99

Restoring clients BMR disk recovery behavior

To clean up the restore configuration

1

In the NetBackup istration Console, click Bare Metal Restore Management > Bare Metal Restore Tasks.

2

In the details pane, right-click the client for which you want to clean up the restore configuration.

3

Select Clean Up from the shortcut menu. The resources that the task uses are unallocated, the State is set to Done, and Status is set to 150, terminated by .

BMR disk recovery behavior BMR either restores or imports disks during a restore, as follows: ■

To restore a disk means that BMR formats the disk and restore files to it. No attempt is made to retain any data on the disk.

■

To import a disk means that BMR tries to reuse the volumes on it (that is, mount the file systems automatically after restore). BMR tries to reuse rather than format the disk and restore files to it.

BMR always restores the system disk. For other disks, the following two options on the Prepare to Restore Client dialog box control BMR behavior: ■

■

Restore system disks/volumes only. ■

On AIX and HP-UX, the root volume groups (rootvg and vg00) are restored.

■

On Solaris, all disks that have any of the root file systems (/, /swap, /var, /usr) are restored.

■

On Windows, all disks that have %SystemRoot%, %SystemBoot%, and %TEMP% are restored. On Active Directory servers, BMR also restores the disks that contain the Active Directory system, database, and log files.

■

On Linux, all disks that have /, usr/, /usr/local, /var, /opt, /tmp, and /boot are restored.

Make available volumes on non-restored disks after the system is restored. If you select this option, BMR imports the disks. Otherwise, the action depends on the disk class processing with prepare-to-restore options.

The following are the disk classes: ■

System disks contain the operating system files that are required to boot the system.

■

Nonsystem disks are all other disks, as follows:

100


■

Restorable disks are visible in the temporary restore environment and therefore can be restored.

■

Nonrestorable disks are not visible in the temporary restore environment and therefore cannot be restored. Typically these are SAN devices. You may not know that these disks cannot be restored until you attempt a restore. If these disks are required for a restore, you are forced to do a dissimilar disk restore (DDR).

■

Shared disks are shared with another system using clustering software. The client may not control them during or after the restore.

■

Missing disks may or may not have been used and are no longer attached to the system. These disks are in the restore configuration. More information is available about the actions to perform for missing disks. See “BMR disk class processing with prepare-to-restore options” on page 102.

■

New disks are attached to the system in previously unused locations and used by any volume or any volume group. New disks are not in the original configuration.

BMR also restricts some disks so they are not processed during a restore. For example, BMR restricts shared disks in a cluster and unused VxVM disks on Solaris systems. Additionally, you can restrict a disk manually so that BMR does not process it.

BMR disk processing with prepare-to-restore options Table 6-2 describes how BMR processes disks, depending on the two prepare-to-restore options. Note the following about the restore options column: ■

System only is the Restore system disks/volumes only option for prepare to restore.

■

Import is the Make available volumes on non-restored disks after the system is restored option for prepare to restore.

Table 6-2 Restore options

BMR disk actions System Disks

System only = true and Restore import = true

Nonsystem disks

Nonsystem disks

Restricted=false

Restricted=true

Import

No action

101


Table 6-2 Restore options

BMR disk actions (continued) System Disks

Nonsystem disks

Nonsystem disks

Restricted=false

Restricted=true

System only = true and Restore import = false

No action

No action

System only = false and Restore import = true

Restore if possible otherwise import

No action

System only = false and Restore import = false

Restore

No action

BMR disk class processing with prepare-to-restore options Table 6-3 describes the actions that BMR performs for system disks. Table 6-4 describes the actions that BMR performs for nonsystem disks and any action you should perform. Note the following about the Restore options columns of the tables: ■

System only is the Restore system disks/volumes only option for prepare to restore

■

Import is the Make available volumes on non-restored disks after the system is restored option for prepare to restore

To avoid conflicts with other cluster nodes that may use surviving shared disks during a restore, shared disks should remain restricted or be unmapped or remapped to alternate, non-shared restorable locations. Shared disks should only be unrestricted and restored in-place if other cluster nodes do not hold the share actively during the restore. Table 6-3

Actions for system disks

Restore options

Action

System only = true and import = true

Restore

System only = true and import = false

Restore

System only = false and import = true

Restore

System only = false and import = false

Restore

102


Table 6-4

Actions for nonsystem disks

Restore options Restorable Nonrestorable Shared

Missing

New

System only = Import true and import = true

Import

No action

Mark the restricted disk, remap to a Not restorable disk, or remove the disk from imported the restore configuration

System only = No action true and import = false

No action

No action

No action

System only = Restore false and import = true

Import

No action

Mark the restricted disk, remap to a Not restorable disk, or remove the disk from imported the restore configuration

System only = Restore false and import = false

Remove the disk No action from the restore configuration or mark the disk restricted

No action

Mark the restricted disk, remap to a No action restorable disk, or remove the disk from the restore configuration

Import actions for operating systems or volume managers Table 6-5 describes the import action for each operating system or volume manager. Note the following regarding import actions: ■

HP-UX logical volume manager is a virtual auto import. An HP system can have VxVM managed root disks and some LVM managed disks. In a system only restore, the LVM database (the /etc/lvmtab file) is restored. Without any action required by BMR, these disks and their volumes are available. If entries remain in the /etc/fstab file for the file systems, those file systems are available.

■

During a merge on Solaris systems or a merge on VxVM, BMR may remove entries in the /etc/fstab or /etc/vfstab files by commenting them out.

■

Veritas Volume Manager is an auto import. VxVM has the ability (a disk group option) to import disk groups automatically. If there are entries in the /etc/fstab and the /etc/vfstab files, the file systems are available without BMR having to take action.

■

Note the following for Windows imports: ■

Without import, only the drive letters that were recreated are assigned after restore.

103

Restoring clients About restoring BMR clients using network boot

■

With import, the drive letters assigned to volumes on Trusted disks are assigned to the same location after the restore. If the volume does not exist or has moved, you must edit the Mount Devices registry key.

Table 6-5

Import actions

OS and volume manager

What import means

AIX logical volume manager

Run importvg at restore time or during first boot.

HP-UX logical volume manager Merge lvmtab, merge fstab. Linux

Merge fstab.

Solaris

Merge vfstab.

Veritas Storage Foundation for Assign drive letter by MountedDevices, run vxdg import. Windows Veritas Volume Manager

Run vxdg import, merge fstab.

Windows

Assign drive letter by MountedDevices.

About restoring BMR clients using network boot Use these procedures for a standard restore (also known as a self restore, which is a restore to the same system and disks). Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. To restore BMR Windows or UNIX client, you MUST perform bpnbat -addmachine on master server before restoring the client. To restore using media boot requires that you first create bootable media.

See “Creating boot media for UNIX and Linux” on page 91. See “Creating boot media for a Windows client” on page 94.

Before you do a standard restore, you must run the prepare See “Preparing a client for to restore operation using the current, saved configuration. restore” on page 98.

104


The procedure for restoring the client system depends on the manufacturer and mode.

See “Restoring an AIX client with network boot” on page 105. See “Restoring a Solaris client with network boot” on page 114. See “Restoring an HP-UX client with network boot” on page 110. See “Restoring a Linux client with network boot” on page 113. See “Restoring a Windows client with network boot” on page 115.

Other information about restoring clients is available.

See “About external procedures” on page 139. See “About performing complete backups” on page 30. See “About performing a full backup after a restore” on page 30. See “Ensuring successful backups” on page 31.

Restoring an AIX client with network boot Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. An AIX boot (either network boot or media boot) may set the network interface configuration, speed, and duplex mode to auto-negotiate or 10 half duplex. This setting may cause the BMR restore to run much more slowly than expected. To achieve normal restore performance, manually set the network interface configuration through the firmware before a BMR restore. AIX system restore requires certain information and resources.

105


The information to be configured in the firmware varies according to architecture, but can include the following: ■

Network adapter type

■

BMR client IP address

■

BMR client subnet mask

■

BMR boot server IP address

■

BMR client gateway address

Here is sample screenshot showing the required entities configured in the target hardware firmware so that it can be BMR restored automatically upon a network boot.

106


Figure 6-3

Sample AIX firmware settings

107


108


After you perform the network boot procedure, the remainder of the restore process is automatic and requires no manual intervention. After the restore finishes and the client reboots itself, it is completely restored. You can network boot an AIX system that has AIX installed, which does the following: ■

Updates the NVRAM with the proper addresses for the BMR boot server, client, and gateway address.

■

Boots by bootp from the BMR boot server. If the boot server does not answer the bootp request, the computer boots from the hard drive.

The network boot only works when the BMR client is properly prepared for restore. Warning: Do not perform this procedure unless you intend to do a restore. When you prepare a client for restore, the process may result in a restore. To restore an AIX client with network boot

1

Prepare to restore the client. See “Preparing a client for restore” on page 98.

2

Boot from a network interface according to the procedures in the IBM hardware documentation.

109


Restoring an HP-UX client with network boot Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. HP-UX system restore requires certain information and resources. The information varies according to architecture, but can include the following: ■

BMR client IP address

■

BMR client gateway address

■

BMR client subnet mask

■

Ignite Server Address (usually, the BMR boot server).

After you perform the network boot procedure, the remainder of the restore process is automatic and requires no manual intervention. After the restore finishes and the client reboots itself, it is completely restored. To restore an HP-UX PA client with network boot

1


2

Boot the client to restore.

3

Press any key when the following message appears. To discontinue, press any key within 10 seconds.

4

In the Main Menu, do one of the following to begin the network boot process: ■

If only one Ignite server is on the subnet, enter the following boot command: boot lan

■

If there is more than one Ignite server on the subnet, specify the Ignite server to boot from by using the following command: (Replace x.x.x.x with the IP address of the Ignite server and y.y with the gateway.) boot lan.x.x.x.x.y.y

Use the same command if you use a boot helper to boot from an Ignite server on a different subnet.

5

Enter No when the prompt asks if you want to interact with IPL.

110


6

If the client is a workstation, select the operating system language by number. For example, US English is 61.

7

After you enter the language choice, press Enter twice to select and confirm the choice. The HP-UX Ignite menu opens.

8

Use the arrow key to scroll to Run a Recovery Shell. Wait while the DH search occurs and until the Network Configuration menu opens. If you interrupt a DH search, the BMR restore may fail.

9

Answer the following prompts: ■

Hostname:

■

Internet Protocol Address:

■

Subnet mask:

■

Ignite Server Address (typically the BMR boot server):

10 Use the arrow key to scroll to OK and press Enter. The system boots from the network.

111


To restore an HP-UX IA client with network boot

1


2


3

If the client is a workstation, select the operating system language by number. For example, US English is 61.

4

After you enter the language choice, press Enter twice to select and confirm the choice. The HP-UX Ignite menu opens.

5

Use the arrow key to scroll to Run a Recovery Shell. Wait while the DH search occurs and until the Network Configuration menu opens. If you interrupt a DH search, the BMR restore may fail.

6

Answer the following prompts: ■

Hostname:

112


7

■

Internet Protocol Address:

■

Subnet mask:

■

Ignite Server Address (typically the BMR boot server):

Use the arrow key to scroll to OK and press Enter. The system boots from the network.

Restoring a Linux client with network boot Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. To network boot Linux clients, BMR requires the following: ■

PXE

■

DH

■

TFTP

■

NFS

During the prepare-to-restore operation all the information is gathered that is required for a Linux network boot. For Linux client network based recovery, you need to make sure above listed services are configured on the BMR boot server and are running. You need to require to do any client specific settings in these services configuration files. BMR handles the required network boot services configuration for the selected client during prepare-to-restore operation. To know more on the required network services configuration, See “Network services configurations on BMR boot Server” on page 238. After the prepare-to-restore, boot the client to start the restore.

113


To network boot a Linux client

1


2

Ensure that no other DH service except the one running on BMR Boot server is running in the same subnet. Otherwise the client DH boot request may go to un-intended DH server and PXE network boot may fail. Note: This is the limitation with PXE, DH boot protocols where first DH reply failure stops network boot process. Hence recommendation is to keep only Linux DH service on the boot server running.

3


4

PXE Boot the client according to the hardware vendor instructions. On some systems, the BIOS displays a message that indicates that you can press a key to force a PXE Boot . On others, you may have to modify the settings in the BIOS to add the network card to the default boot order. Consult your hardware documentation for details.

5

When you are prompted, either press the Enter key or wait until the system boots. The system boots and the restore begins with no further intervention required.

6

Upon successful client recovery, BMR automatically cleans up any network boot settings added for the client in DH configuration during prepare-to-restore operation.

Restoring a Solaris client with network boot Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. To network boot Solaris clients, BMR requires the following: ■

PXE (In case of Solaris-x64 platform based client recovery)

■

DH

■

TFTP

■

NFS

114


To know more on the required network services configuration, See “Network services configurations on BMR boot Server” on page 238. Solaris system restore requires the name of the network device that directs the client to the correct BMR boot server. After you perform the network boot procedure, the remainder of the restore process is automatic and requires no manual intervention. After the restore finishes and the client reboots itself, it is completely restored. To restore a Solaris client with network boot

1


2

Ensure that no other DH service except the one running on BMR Solaris Boot server is running in the same subnet. Otherwise the client DH boot request goes to un-intended DH server and network boot may fail. Note: This is a limitation with DH, PXE boot protocols themselves where first DH reply failure stops network boot process. Hence recommendation is to keep only Solaris DH service on the boot server running.

3


4

Terminate the boot process by using the #.command to return to the sc> prompt and send break command from sc>prompt to get OK prompt.

5

Start the network boot by entering the following command (net[id] is the device that points to the BMR boot server): boot net[id] where [id] is 1,2,3 interface cards.

6

Start the network boot by entering the following command (net[id] is the device that points to the BMR boot server):boot net[id] where id is 1,2,3 interface cards.

Restoring a Windows client with network boot Note: If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. Windows systems network boot uses the PXE protocol. The BMR boot server provides and manages the PXE network services, but a DH service is required

115

Restoring clients About restoring BMR clients using media boot

in the environment. A DH service can exist on the same Boot server or anywhere in the subnet. To restore a Windows client with network boot

1


2

Ensure that PXE and TFTP services configuration on BMR Boot server is done once. I If BMR PXE configuration is not done ever on the boot server then run PXE Service Configuration Wizard available in BMR Boot server assistant which can be located in the Start menu on the Windows BMR boot server. For this, click Programs >NetBackup istration Console > Bare Metal Restore Boot Server Assistant. This BMR PXE service configuration needs to be done only once for a Windows boot server. If the DH server location changes later then this wizard needs to be run again. Note: Any other non-BMR PXE or TFTP service running on the same BMR Boot server cannot be used for BMR recovery. Make sure to stop these services while client network boots for recovery. Otherwise the client PXE boot request goes to un-intended server and PXE network boot may fail. This is a limitation with PXE, DH boot protocols, Symantec recommendation is to keep only correct PXE, DH, TFTP servers running while booting client for network based recovery.

3

Make sure BMR PXE and TFTP services are up and running.

4


5

PXE Boot the client according to the hardware vendor instructions. On some systems, the BIOS displays a message that indicates that you can press a key to force a PXE Boot . On others, you may have to modify the settings in the BIOS to add the network card to the default boot order. Consult your hardware documentation for details.

6

When you are prompted, press the Function 12 key and the system boots and the restore begins with no further intervention required.

About restoring BMR clients using media boot Use these procedures for a standard restore (also known as a self restore, which is a restore to the same system and disks).

116


To restore using media boot requires that you first create bootable media.

See “Creating boot media for UNIX and Linux” on page 91. See “Creating boot media for a Windows client” on page 94.

Before you do a standard restore, you must run the prepare See “Preparing a client for to restore operation using the current, saved configuration. restore” on page 98. The procedure for restoring the client system depends on the manufacturer and mode.

See “Restoring an AIX client with media boot” on page 117. See “Restoring an HP-UX client with media boot” on page 118. See “Restoring a Linux client with media boot” on page 121. See “Restoring a Solaris client with media boot” on page 122. See “Restoring a Windows client with media boot” on page 123.

Other information about restoring clients is available.

See “About external procedures” on page 139. See “About performing complete backups” on page 30. See “About performing a full backup after a restore” on page 30. See “Ensuring successful backups” on page 31.

Restoring an AIX client with media boot Note: If NetBackup access management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files.

117


An AIX boot (either network boot or media boot) may set the network interface configuration, speed, and duplex mode to auto-negotiate or 10 half duplex. This setting may cause the BMR restore to run much more slowly than expected. To achieve normal restore performance, manually set the network interface configuration through the firmware before a BMR restore. To restore an AIX client with media boot

1

Prepare to restore the client using the SRT you created on the bootable media. See “Preparing a client for restore” on page 98.

2

Boot the client from the boot media you created. For instructions on how to boot from a CD or from a DVD, see the IBM hardware documentation.

3

Enter the required information at the following BMR process prompts: ■

Client name (for a discovery boot, enter the client’s name as it appears in

the Tasks view from the prepare-to-discover operation) ■

Client IP address

■

Network mask

■

Default gateway

■

NetBackup master server name

■

NetBackup master server IP address

■

NetBackup master server gateway IP address

The restore begins.

Restoring an HP-UX client with media boot Note: If NetBackup access management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. To media boot an HP-UX client, do the following. To restore an HP-UX PA client with media boot

1


2

Insert the bootable CD or bootable DVD into the CD-ROM drive.

3


4

When you are prompted, press the Space bar to stop the normal boot process.

118


5

Search for the location and name of the CD-ROM drive. The search utility may be useful to determine this information.

6

Find the CD-ROM drive from the list of devices and boot the computer using that device with the boot command.

7

In response to the Interact with IPL prompt, type No.

8

In response to the Run a Recovery Shell prompt, type Yes.

9

In response to the Start Networking prompt, type Yes.

10 In response to the Choose

the Network Interface prompt, type the default

LAN device to boot from. You must enter the default LAN because the firmware uses this address for booting from the Ignite server. Note that any network interface card can be used for accessing the SRT or backups, but the default LAN must be used for booting.

11 Enter the following information when prompted: ■

Hostname

■

IP address

■

Default gateway

■

Subnet mask

12 At the Is

this network information temporary prompt, type No.

13 Use the arrow key to scroll to OK and press Enter. 14 Enter the required information at the following BMR process prompts: ■




■


■


The restore begins. To restore an HP-UX IA client with media boot

1


2


119


3


4

In response to the Run a Recovery Shell prompt, type Yes.

5

In response to the Start Networking prompt, type Yes.

6

In response to the Choose the Network Interface prompt, type the default LAN device to boot from. You must enter the default LAN because the firmware uses this address for booting from the Ignite server. Note that any network interface card can be used for accessing the SRT or backups, but the default LAN must be used for booting.

7

Enter the following information when prompted: ■

Hostname

■

IP address

■

Default gateway

■

Subnet mask

120


8

At the Is this network information temporary prompt, type No.

9

Use the arrow key to scroll to OK and press Enter.

10 Enter the required information at the following BMR process prompts: ■




■


■


The restore begins.

Restoring a Linux client with media boot Note: If NetBackup access management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. Use the following procedure for Linux clients. To restore a Linux client with media boot

1


2

Insert the bootable CD or bootable DVD into the CD-ROM drive. On some systems, you may have to modify the BIOS settings so that the system boots from the CD-ROM drive. Consult your hardware documentation for details.

3


4




Client IP address

■

Network mask

■

Default gateway

■


■


121


■


■

Additional gateway address to reach the NetBackup master server

The restore begins.

Restoring a Solaris client with media boot Note: If NetBackup access management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. Use the following procedure for Solaris clients. To restore a Solaris client with media boot

1


2


3


4

Terminate the boot process by pressing command #. to return to the sc> prompt and send break command from sc> prompt to get OK prompt.

5

Enter the following command: boot cdrom

The Solaris OS Installation prompts you for network identification.

6

Enter the network identification.

7





■


■


After you enter the required information, the restore begins.

122

Restoring clients About restoring to a specific point in time

Restoring a Windows client with media boot Note: If NetBackup access management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files. To restore BMR Windows client, you MUST perform bpnbat -addmachine on master server before restoring the client. To media boot a Windows client, do the following. To restore a Windows client with media boot

1


2

Create a bootable CD or bootable DVD from the SRT used during the Prepare to Restore.

3

Insert the bootable CD or bootable DVD into the CD-ROM drive. On some systems, you may have to modify the BIOS settings so that the system boots from the CD-ROM drive. Consult your hardware documentation for details.

4

Boot the client to restore. The following message appears: press any key to boot from CD

5

The system boot and the restore begin with no further intervention required.

About restoring to a specific point in time When NetBackup backs up a BMR client, it also backs up the currently saved configuration, and that configuration contains the information about the client on that specific date and time. So you can restore to any point in time for which you have a backup for a BMR client. For a point in time restore, you must create a restore configuration and specify the point in time to which you want to restore.

About the point in time restore process Normally, BMR restores from the most recent backup. In a point in time restore, BMR can restore the system to a state earlier than the last full backup. To restore the system to a previous point in time, you select the point in time backup for the restore when you create a restore configuration.

123


A point in time restore is useful when a recent software change has rendered the system unusable. Bare Metal Restore can restore the system to a previous known working state. Use the point in time restore feature in the following scenarios: ■

A hardware change has destabilized the system. There may be cases in which the software that is associated with the hardware cannot be removed completely. Instead of removing all the associated drivers and software, point in time restore can recover the system to a known working state.

■

A software addition has destabilized the system. Rather than uninstalling the software, which may not return the system to its state before the software was installed, point in time restore can recover the system.

■

A virus attacked the system.

■

Critical system or application files were deleted.

Creating a point in time restore configuration The following procedure creates the restore configuration for a point in time restore for any client type. Then follow the standard restore procedures for the client. To create a point in time restore configuration

1

In the NetBackup istration Console, expand Bare Metal Restore Management > Hosts > Bare Metal Restore Clients.

2

In the All Bare Metal Restore Clients pane, right-click the saved configuration for the client (the configuration labeled current), then select New from the shortcut menu.

124


3

In the New Configuration dialog box, enter a name for the new configuration. Below is a sample screenshot showing creation of Point-In-Time configuration for recovery.

4

Click Retrieve from NetBackup.

5

Select the Policy and End Date for the restore. If the backup policy uses multiple data streams to back up the client, all of the data streams for each backup job are shown in the End Date drop-down list. Select the most recent stream of the backup job on the date to which you want to restore. Normally backup jobs occur on separate days and data streams within the same backup job are separated by seconds or minutes.

125

Restoring clients About restoring to dissimilar disks

6

Click OK. The new configuration appears in the list of the client's configurations. The configuration is now ready for the prepare-to-restore operation.

7

Restore the client. See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

About restoring to dissimilar disks You can restore a protected client even if the disk drives were replaced. You also can perform a dissimilar disk restore (DDR) if you need to change the volume layout or size or restore only some of the disks or volumes.

About the dissimilar disk restore process In a standard restore, BMR uses the current client configuration to recreate the original system. Little or no intervention is required because the original system is moved onto the original disk configuration. In a dissimilar disk restore, intervention is required because you have to map the volume configuration from the protected client to the new disks. (Disk refers to a physical disk and volume refers to a logical division of disk space on one or more physical disks.) Mapping occurs as follows: ■

■

Before the restore: You can create a configuration you can edit (an editable restore configuration) and initialize that configuration with the new disk layouts. Then map the original volume configuration to the new disks. After you finish mapping, you restore the client using the restore configuration. ■

Layouts of the new disks on the client, which is necessary, for example, when you perform a discovery operation.

■

Whether another protected client has the same disks.

During the restore: You perform a standard restore and BMR detects that the disks are different. BMR enters DDR mode and creates an editable restore configuration so you can map the disks. ■

For UNIX and Linux clients, use the BMR disk mapping utility in the NetBackup istration Console on the master server.

126


■

For Windows clients, you can map on the client during recovery or on the master server using the BMR disk mapping utility in the NetBackup istration Console.

You should use dissimilar disk restore in the following circumstances: ■

A physical disk is replaced.

■

The size of one or more disks has decreased and cannot contain the same volume arrangement.

■

The location of one or more disks changes.

■

The number of disks has decreased and the required volume arrangement cannot be restored.

■

You need to change the layout and volumes for the restored system.

■

You want to restore only some of the disks in a system.

Warning: Changes in disk locations may prevent a clustered resource from going online after a restore. BMR does not attempt to adjust clustered resource attributes to for a dissimilar disk restore.

Creating a restore configuration for DDR Table 6-6 is an overview of the process to create an editable restore configuration and perform disk mapping before you begin the restore. In case of Windows client recovery, you do not have to create a DDR configuration before you begin the restore. You can begin a restore and perform disk mapping during the restore itself. BMR windows recovery opens disk mapping GUI automatically in case it fails to map original disks to the disks available during recovery time. While in case of Unix/Linux client case, if disks matching fails then recovery process goes into target hardware discovery mode. See “Restoring a client to dissimilar disks” on page 128. Table 6-6

To create a restore configuration

Step

Task

Procedure

Step 1

Discover the configuration of the new disks. See “Discovering a configuration” on page 159.

Step 2

Create an editable restore configuration by See “Copying a copying the current configuration. configuration” on page 158.

127


Table 6-6

To create a restore configuration (continued)

Step

Task

Procedure

Step 3

Open the Change Configuration dialog box See “Modifying a for the restore configuration. configuration” on page 162.

Step 4

Initialize the restore configuration with the disk information from the discovered configuration and then map the original volume configuration to the new disks.

Step 5

After you finish mapping, perform the DDR See “Restoring a client to restore procedure. dissimilar disks” on page 128.

See “About Volumes properties” on page 176.

Restoring a client to dissimilar disks Table 6-7 is an overview of the process to restore to dissimilar disks. If you did not prepare a restore configuration in advance, BMR automatically creates an editable restore configuration during this process. Note the following for UNIX and Linux DDR: ■

Shared disks in a cluster are marked restricted.

■

Unused VxVM disks on Solaris clients are marked restricted and should remain restricted.

■

You cannot map Linux LVM volume groups with the physical volumes that were created on top of multi devices with the same configuration. The physical volumes are mapped to either disks or partitions but not to a multi device.

Table 6-7

To perform a dissimilar disk restore

Step

Task

Procedure

Step 1

Prepare to restore the client.

If you prepared a restore configuration in advance, select that configuration during the prepare operation. See “Preparing a client for restore” on page 98.

128


Table 6-7

To perform a dissimilar disk restore (continued)

Step

Task

Procedure

Step 2

Begin the restore by booting the client using either network boot or media boot.

If you use a configuration where the protected system’s volume configuration is already mapped to the new disks, the restore proceeds as a standard restore. No intervention is required. If BMR detects that the disks are different and are not already mapped, BMR enters DDR mode. In case of Windows, you can map volumes to recovery time disks at this point by using auto popped-up BMR configuration mapping GUI. See “BMR restore process” on page 95.

Step 3

Save the editable restore configuration.

Non-editable configuration only. If you use a configuration that cannot be edited, BMR creates an editable restore configuration. It copies the current configuration and prompts you to enter a name for it, as follows: Current configuration name for restore is 'current'. Please enter the name for a new editable configuration:

129


Table 6-7


Step

Task

Procedure

Step 4

Save the discovered configuration.

To obtain the layouts of the new disks, BMR discovers the hardware of the client. BMR prompts you for a name for the discovered configuration, as follows: Please enter the name for a new discovered configuration: BMR saves the discovered configuration. Later, you import the disk layouts from this discovered configuration into the restore configuration by using Initialize option on BMR configuration mapping GUI (as described in step-6).

Step 5

Open the Change Configuration dialog box .

After the discovered configuration is saved, in the NetBackup istration Console on the master server, open the Change Configuration dialog box for the restore configuration. See “Modifying a configuration” on page 162.

Step 6

Initialize the restore configuration.

Initialize the restore configuration with the new disk layout from the discovered configuration. And then map the original volume configuration to the new disks. See “About Volumes properties” on page 176.

130

Restoring clients Restoring to a dissimilar Windows system

Table 6-7


Step

Task

Procedure

Step 7

Prepare to restore and then restore the client, using the edited restore configuration.

See “Preparing a client for restore” on page 98. See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

Step 8

If the disk mapping in the restore See “About Volumes configuration is incomplete, BMR enters properties” on page 176. DDR mode again so you can continue to map volumes to disks.

Restoring to a dissimilar Windows system Microsoft Windows systems only. Table 6-8 describes the process to restore to a dissimilar system. If the target system disk(s) are different than the protected system disks, disk and volume mapping (as performed with a dissimilar disk restore) are required. Table 6-8

Dissimilar system restore overview

Step

Task

Procedure

Step 1

Learn about dissimilar system restore.

See “About dissimilar system restore” on page 132.

Step 2

Discover the configuration of the target system.

See “About discovering the configuration of the new system” on page 133.

Step 3

Create a configuration to use for the restore.

See “Creating an editable DSR configuration” on page 133.

Step 4

Add NIC drivers and the MSD See “About adding NIC and MSD drivers to the restore configuration drivers” on page 133. system.

131


Table 6-8

Dissimilar system restore overview (continued)

Step

Task

Procedure

Step 5

Change the network interfaces and See “About changing network network identities in the restore interfaces” on page 134. configuration.

Step 6

Map disks in the restore configuration.

See “About mapping disks in the restore configuration” on page 135.

Step 7

Create boot media.

See “About creating boot media” on page 135.

Step 8

Restore the client.

See “About restoring the client” on page 136.

Step 9

Complete the DSR changes at the See “Logging on for the first time first logon to the restored system. after system restore” on page 136.

About dissimilar system restore Microsoft Windows systems only. A dissimilar system restore (DSR) restores a protected Windows client to a new system that has a different hardware configuration. Note: Changes in the hardware configuration may prevent clustered resources from going online after a restore. BMR does not attempt to adjust clustered resource attributes to for a dissimilar system restore. A DSR is useful in the following situations: ■

You change the preferred vendor for a class of systems in your enterprise.

■

You migrate an application from older hardware to the newer hardware.

■

Your system experiences critical hardware failure and similar hardware is not available for replacement.

■

Your disaster recovery provider does not have identical hardware to yours at the disaster recovery site.

■

You stage and an application at a test site with different hardware from the production site. (You can migrate the application from test to production.)

Use DSR when any of the following conditions apply: ■

The target system has a disk controller that the protected system does not have.

132


■

The target system has a network card that the protected system does not have.

■

The target system requires a different hardware abstraction layer (HAL) or kernel than the protected system.

■

The target system has different T/IP settings than the protected system has. (Only T/IP properties are restored. Other networking properties, such as Internetwork Packet Exchange (IPX), are not restored and must be configured after the restore.)

About discovering the configuration of the new system The first step in restoring to dissimilar hardware is to discover the hardware that is contained on the new system. See “Discovering a configuration” on page 159.

Creating an editable DSR configuration You must create a configuration to use for the restore of the protected client. The following table lists the step to create the configuration. Table 6-9

Process for creating an editable DSR configuration

Step

Action

Related topic

Step 1

Create the DSR configuration by copying an existing configuration of the protected client.

See “Copying a configuration” on page 158.

For example, to restore client protected to system target, create a configuration named dsr_to_target by copying the current configuration of client protected. Step 2

After you create the DSR See “Client configuration configuration, open the Change properties” on page 164. Configuration dialog box to modify the configuration as described in the following sections.

About adding NIC and MSD drivers The DSR configuration must include the NIC drivers and the MSD drivers that the target system requires.

133


The target system drivers were added to the packages pool when you performed one of the procedures to discover configurations. See “Discovering a configuration” on page 159. The drivers are available to add to the DSR configuration. To add drivers, select them in the Available drivers window of the configuration’s Drivers dialog box. Then add them to the Drivers to be used during restore window. See “Devices and drivers properties” on page 166. If you have added the drivers to the packages pool using the following methods, the driver description includes the name of the target system: ■

By saving the target system’s configuration

■

By extracting the drivers from the target system

The driver description helps identify which drivers are required for the target system. Also, remove any drivers from the DSR configuration that the protected system uses and the target system does not. Note: Only T/IP properties are restored. Other networking properties, such as Internetwork Packet Exchange (IPX), are not restored and must be configured after the restore.

About changing network interfaces You must change the network interfaces and network identities in the DSR configuration. For the changes to work properly you must back up the target system in compliance with the procedures that are part of discovering a configuration. See “Discovering a configuration” on page 159. If you installed the client on the target system and backed it up in compliance with the procedures above, you can do the following: ■

Import the NIC information from that configuration.

■

Map the network identifiers (IP address, netmask, and domain name) from the protected client to the NICs in the target system.

If you did not save the target system’s configuration, you must determine the MAC addresses of the NICs in the target system. Then add the network interface information manually to the DSR configuration.

134


More information is available on procedures to import and map interfaces or change them manually. See “Network interfaces properties” on page 170.

About mapping disks in the restore configuration A dissimilar system restore may also be a dissimilar disk restore. If the target system has different disks than the protected client, you must map the volume configuration from the original system to the new disks. (You map as in a dissimilar disk restore.) You can also shrink or extend the size of the system partition or volume. You do not have to map the vendor partition (if one exists) from the protected client to the target system’s disks. For the changes to work properly, you must back up the target system in compliance with the procedures that are part of discovering a configuration. See “Discovering a configuration” on page 159. If you installed the client on the target system and backed it up in compliance with the procedures above, you can do the following: ■

Import the disk layouts from that configuration.

■

Map disks before the restore.

Symantec recommends that you map disks before the restore, especially when the protected client’s system partition cannot fit on the target system’s system disk. If you did not save the target system’s configuration, you must do the DDR mapping during the restore. More information is available about dissimilar disk restore. See “About restoring to dissimilar disks” on page 126. During Windows client recovery, if BMR recovery process finds vendor partition on target machine disk where client operation system is going to be recovered, then BMR prompts the giving option to save the found vendor partition.

About creating boot media If you use media to start the target system, create that media if it is not available already. See “Managing boot media” on page 89.

135

Restoring clients About restoring NetBackup media servers

About restoring the client Prepare to restore the client and initiate the dissimilar system restore process using the DSR configuration. See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

Logging on for the first time after system restore After the system is restored, a local is required to complete the DSR changes. The bmrcleanup utility runs and displays a status box that describes the actions being performed. While the status box is visible, Windows may display a number of New Hardware Found Wizards. To logon for the first time after system restore, perform the following actions, depending on which wizard or message screen appears: ■

In the Digital Signature Not Found , click Yes or Continue.

■

In the Found New Hardware Wizard , click Cancel.

■

In the New drivers are installed, do you want to reboot? , click No.

Note: Do not reboot the system until the bmrcleanup status box completes. Windows XP and Windows Server 2003 systems may require product activation after a DSR.

About restoring NetBackup media servers You can restore NetBackup media servers if they are protected as BMR clients (exception: you cannot restore a media server that is co-located with a NetBackup master server). The following options exist for restoring NetBackup media servers: ■

If you back up a media server to a different media server, restore the protected media server as you restore any protected client. See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

■

A media server can back up its own data using SCSI-attached storage devices or SAN-attached storage devices. If this is true for you, use BMR to restore the media server by first configuring NetBackup to use an alternate media server.

136


More information is available. See “About configuring an alternate media server” on page 137. See “Restoring the media server” on page 138.

About configuring an alternate media server Two methods exist to configure an alternate media server in NetBackup. You must do one of the following: ■

Configure the automatic media server failover. This method redirects the restore only if the media server is not available. This method is most useful if the library that contains the media is connected both to the failed media server and the alternate media server. Normally, you configure automatic media server failover before the failure, which results in less time and effort during the restore.

■

Override the original media server manually. This method forces restores to the alternate server, regardless of the state of the original media server. ■

You did not configure automatic media server failover before the failure.

■

You want to perform a temporary media server reassignment to restore the original media server.

All backup and restore requests (not only BMR restores) are directed to the alternate media servers. More information is available. See “Overriding the original media server manually” on page 138. See “Enabling automatic media server failover to an alternate server” on page 137. More detailed information about how to configure NetBackup to use an alternate media server is available. See the NetBackup ’s Guide for UNIX, Windows and Linux, Volume I.

Enabling automatic media server failover to an alternate server Normally, automatic media server failover is configured before the original media server fails. On UNIX and Linux systems, when you configure this option, it sets the FAILOVER_RESTORE_MEDIA_SERVERS parameter in the bp.conf file.

137


To enable automatic failover to an alternate server

1

In the NetBackup istration Console, open the Restore Failover host properties for the master server.

2

Add an entry in the Alternate Restore Failover Machines list; name the media server and failover restore server(s).

3

Stop and restart the NetBackup Request Manager daemon or service on the master server.

Overriding the original media server manually If necessary, before you physically override the media server, move the media to a library that is attached to the new media server. Then update the Enterprise Media Manager database to reflect the move. After you perform the restore, reverse the NetBackup configuration changes by removing the alternate server entry from the Media Host Override list. The original server performs the NetBackup and restore requests again. On UNIX and Linux systems, when you configure this option, it sets the FORCE_RESTORE_MEDIA_SERVER parameter in the bp.conf file. To override the original server for manual restores

1

In the NetBackup istration Console, open the General Server host properties for the master server.

2

Add an entry in the Media Host Override list; name the original backup server and the restore server.

3

Click OK.

4

Stop and restart the NetBackup Request Manager daemon or service on the master server.

Restoring the media server If you configured an alternate media server before the media server failure (which is most likely with the automatic failover method), the alternate media server is saved as a host in the original media server’s BMR client configuration. Now you can perform a standard restore. If you did not configure the NetBackup alternate media server before the failure, create and modify a restore configuration to use during the restore.

138

Restoring clients About restoring BMR boot servers

Table 6-10

Restore media server process

Step

Task

Procedure

Step 1

Create a restore configuration.

See “Copying a configuration” on page 158.

Step 2

Add an alternate media server as a host.

See “Modifying a configuration” on page 162. See “Hosts properties” on page 169.

Step 3

After you create and modify the restore configuration, perform a standard restore.

See “About restoring BMR clients using network boot” on page 104. See “About restoring BMR clients using media boot” on page 116.

About restoring BMR boot servers You can restore BMR boot servers if you protect them as BMR clients. First, back them up. Then use a shared resource tree on another boot server or BMR media-based shared resource tree that contains the resources to rebuild the protected boot server. If a boot server is installed on the same system as the NetBackup master server, you cannot protect it as a BMR client. You can recover the NetBackup catalogs (which include the BMR databases) on the NetBackup master server. However, you must reinstall the NetBackup and BMR software on the master server. For more information, see the disaster recovery procedures in the NetBackup Troubleshooting Guide.

About external procedures External procedures are the scripts that interact with the restore process during exits. Using external procedures, you can minimize the interaction that is required for restores that are not automatic. The following are the external procedure types: ■

Client-specific for a specific client

■

Operating system specific for all clients of that operating system type

Client-specific procedures take precedence over operating system procedures. External procedures start only if you do one of the following:

139

Restoring clients About external procedures

■

Select Run External Procedures on the Prepare to Restore Client or Prepare to Discover dialog box.

■

Specify external procedures by using the bmrprep -runep command.

External procedures operate in the restore environment (a limited operating system environment during the restore process). Many of the commands and capabilities that are available with a complete operating system are not available in the restore environment. UNIX external procedures execute as root. Windows external procedures execute as . External procedures are stored in the BMR database on the NetBackup master server. Use the bmrep command on the master server to manage external procedures. Note: Using external procedures requires a general knowledge of scripts.

External procedure points and names BMR can run external procedures at the following exit points during the restore process, in the following sequence: prediscover

Before discovery of hardware is reported to the BMR server (UNIX clients only).

preformat

Before disks are formatted and partitioned. On Windows systems, the preformat takes place after the system drive is formatted but before any nonsystem drives are formatted.

prerestore

Before files begin to restore.

postrestore

After files are restored.

first boot

After the restore is complete and at the first boot of a restored client. On Windows systems, the first boot external procedure operates as the first to log on after a client is restored.

An external procedure point name is used as part of the name of each external procedure script that you create. The naming convention for client-specific external procedures is different than for operating system-specific external procedures. Note: Do not add a .cmd extension for the external procedures that are intended for Microsoft Windows systems. BMR adds the appropriate file name extension when it generates the scripts during the prepare-to-restore process.

140


Client-specific external procedure names Client-specific external procedure names are in the following format: clientname_externalprocedure For example, the sol123_prerestore external procedure is started before files are restored on client sol123. (The procedure starts if Run External Procedures is specified during restoration.) Operating system-specific external procedures names

Operating system-specific external procedure names are in the following format: externalprocedure.ostype The ostype is one of the following: ■

aix

■

AIX hp

■

HP-UX systems linux

■

Linux systems sol

■

Solaris systems win Windows systems

For example, the preformat.linux external procedure is started on Linux clients before drives are formatted. (The procedure starts if Run External Procedures is specified during restoration.)

About managing external procedures Use the bmrep command to do the following: ■

Add an external procedure so it is available during a restore.

■

Delete an external procedure from the database.

■

Extract an existing procedure from the database.

■

List all the external procedures in the database.

For example, to add a prerestore external procedure for a client named sol123, use this command on the NetBackup master server with a BMR license:

141


bmrep -add sol123_prerestore

The bmrep command does not validate client names (that is, you can add an external procedure for a nonexistent client). For another example, to add an external procedure auxiliary file named ListStorageGroups.vbs, use the following command: bmrep -add -data ListStorageGroups.vbs

For more information about the bmrep command, see the NetBackup Commands Reference Guide.

Specifying external procedures You must specify during the prepare-to-restore operation that you want to run external procedures. The BMR master server then creates the appropriate external procedure scripts and uses them during the restore. Note: External procedures should be in the BMR database before the prepare-to-restore or prepare-to-discover operation is started. To specify external procedures, ■

Select Run External Procedures in a Prepare To Discover or Prepare to Restore Client dialog box. See “Discovering a configuration” on page 159. See “Preparing a client for restore” on page 98.

■

Alternatively, use the bmrprep command -runep option to specify external procedures.

About external procedure data transfer You can use the bmrc command to transfer files from the BMR master server to a client during a restore. On UNIX systems, store data in the /tmp file system or in the file systems that are mounted under /tmp. All other file systems are read only during a restore. On Windows systems, transferred files are stored in the current directory by default. The directory is %SystemDrive%\ during restore. The directory is %HOMEPATH% during the first boot procedure. You can specify other path names or file names on the command line.

142


The following is an example of using the bmrc command to transfer a file from the master server to the client: bmrc -operation pull -resource procedure -client clientName -source file_on_server -destination /tmp/filename

When you start the bmrc command in an external procedure, specify the full path in the restore environment, as follows: ■

On UNIX and Linux clients: /usr/openv/NetBackup/bin

■

On Microsoft Windows clients: %SystemDrive%\BMR\NBU\bin At the first boot external procedure point, the path to the bmrc command is install_path\NetBackup\bin on Microsoft Windows clients.

For more information about the bmrc command, see the NetBackup Commands Reference Guide.

About interaction with external procedures UNIX and Linux systems

You can enter commands and interact with an external procedure during restore time. To do so, start the bmrShell function from within the external procedure script. The bmrShell function allows input from the default console keyboard and outputs to the console monitor. You can also use redirection to send output to the screen from an external procedure by redirecting output to the special device. To do so, use /dev/console (as in echo "Hello World" >> /dev/console). On UNIX and Linux systems, the bmrShell is not available during first boot.

Windows systems

You can enter commands and interact with an external procedure during restore time. To do so, start the Windows command interpreter cmd from within the external procedure script. On Windows systems, the limited restore environment may not contain DLLs or the same version of DLLs that were used with the original client system. Use bmrc to transfer these DLLs during the restore to the C:\BMR\WINNT\SYSTEM32 directory. Alternatively, add the location of that DLL to the path environment variable.

External procedure logging examples The following logs are created on the BMR master server during the restore process: /usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX) install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)

143


144

On UNIX and Linux systems, the BMR restore process writes external procedure begin and end messages to the logs. (On Windows systems, the BMR restore process does not perform begin and end logging.) You can use the bmrc command in your external procedure scripts to write messages to the logs also. External procedures write messages when they start and finish. A message includes the date and time that the procedure began, the client name, and a description that includes the external procedure name. See the following examples: 2005/08/02 12:10:38.180 w2k200,sol157 INFO: Executing External Procedure: sol123,sol123_prerestore. 2005/08/02 12:10:38.350 w2k200,sol157 INFO: Completed executing External Procedure: sol123,sol123_prerestore.

You can use the bmrc command to write messages to the restore log. The following is an example of a bmrc command that writes a message during a restore of client sol123: bmrc -operation create -resource message -client sol123 -msg " message text to log"

Alternatively, you can pipe data to the bmrc command, as in the following example: echo "Hello World" | bmrc -operation create -resource log -client sol123

The following is the log entry from the previous command: Restoration log start time: 2005/03/28 10:59:27 Hello World. Restoration log end time: 2005/03/28 10:59:27

When you start the bmrc command in an external procedure, specify the full path in the restore environment, as follows: ■

On UNIX and Linux clients: /usr/openv/netbackup/bin

■

On Microsoft Windows clients: %SystemDrive%\BMR\NBU\bin At the first boot external procedure point, the path to the bmrc command is install_path\NetBackup\bin on Microsoft Windows clients.

For more information about the bmrc command, see the NetBackup Commands Reference Guide.

External procedure operational states During the operation of an external procedure, the following operational states appear in the Tasks view:


Discovery External Procedure

An external procedure runs during the prediscovery phase.

First Boot External Procedure

An external procedure runs during the first boot phase.

Post-restore External Procedure

An external procedure runs during the postrestore phase.

Pre-format External Procedure

An external procedure runs during the preformat phase.

Pre-restore External Procedure

An external procedure runs during the prerestore phase.

About external procedure exit codes Ensure that external procedures exit with a return code of 0. If an external procedure exits with a non-zero code, the restore pauses for input. If it is acceptable for an external procedure to fail during the restore (that is, not vital to system functionality), ensure that you exit 0 from the external procedure.

About external procedure error handling By default, external procedures halt the restore process and await action if the procedure returns a non-zero return code. For UNIX and Linux restores, the following menu appears: What do you want to do next? Choices are: a) Abort the restore. r) Retry the external procedure again. I) Ignore the error and continue the restore. s) Escape to shell prompt, return here when done.

If you retry, a prompt asks if you want to transfer the external procedure again from the BMR server before you run it. The prompt lets you edit the external procedure on the master server before you run it again. Note: When a UNIX first boot external procedure is started with no terminal defined and the procedure returns non-zero, the Bare Metal Restore process ends. For Windows restores, a dialog box appears with the following choices: ■

Cancel halts the restore.

145


■

Try Again starts the external procedure again.

■

Continue ignores the error and continues with the restore.

If you try again, a prompts asks if you want to transfer the external procedure again from the BMR server before you run it. The prompt lets you edit the external procedure on the master server before you run it again.

About external procedure environment variables BMR sets and exports certain environment variables during the restore process. Some are general environment variables; others are specific to BMR.

UNIX and Linux environment variables The following environment variables are exported on all UNIX and Linux systems: Table 6-11

UNIX and Linux environment variables

Variable

Description

$BMRC

Path name to the bmrc executable file (/usr/openv/NetBackup/bin/bmrc)

$bootServerAddress

Boot server IP address

$clAddress

The IP address of the client

$clAddressHex

Client IP address that is converted to hex

$client_firstboot

Name of client-specific, first boot external procedure

$client_postrestore

Name of client-specific, post-restore external procedure

$client_prediscover

Name of client-specific discover external procedure

$client_preformat

Name of client-specific preformat external procedure

$client_prerestore

Name of client-specific prerestore external procedure

$clName

The name of the client.

$clOs

BMR abbreviated OS specification

$configName

The name of the configuration

146


Table 6-11

UNIX and Linux environment variables (continued)

Variable

Description

$default_firstboot

Name of OS default first boot external procedure

$default_postrestore

Name of OS default postrestore external procedure

$default_prediscover

Name of OS default prediscover external procedure

$default_preformat

Name of OS default preformat external procedure

$default_prerestore

Name of OS default prerestore external procedure

$defaultGateway

The name of the default gateway

$extProcName

Current external procedure name

$importNonRootVgs

Import nonsystem volume and disk groups

$logging

Log restore; yes=yes, no=no

$newConfig

Name of the configuration to discover

$onEpError

Restore behavior on External Procedure Error: 0=cancel 1=prompt 2=ignore

$runEp

Start external procedures if found 0=no, 1=yes

$runMode

Mode of BMR process discover or restore

$serverAddress

NetBackup server IP address

$serverGateway

Gateway to the NetBackup server

$serverName

NetBackup server name

AIX environment variables $BMR_BOSINST_DATA $RC_CONFIG

$MNT $ROUTES

The following exported operating system environment variables are set at restore: $BIDATA $LIBPATH $NIM_HOSTS

$HOME $NIM_HOSTNAME $NIM_NAME

147


$NSORDER $PATH $SHOWLED $SYSCFG_PHASE

$ODMDIR $PWD $SPOT

HP-UX environment variables The following exported operating system environment variables are set at restore: $DEFAULT_RELEASE_DIR $ENV $FCEDIT $HOME $INST_CLIENT_DIR $INST_IS_BOOTP_SYSTEM $INST_NOT_TEST_MODE $MAILCHECK $OPTIND $PPID $PS2 $PS4 $RANDOM $SHELL $SOURCE_LIF_FILE $SOURCE_TYPE

$EDITOR $ERRNO $HISTFILE $IFS $INST_CUR_PRIMARY_PATH $INST_LOG_FILE $LINENO $OPTARG $PATH $PS1 $PS3 $PWD $SECONDS $SOURCE $SOURCE_NET_DIR $TMOUT

Solaris environment variables The following exported operating system environment variables are set at restore: $IFS $OPTIND $PS1 $PWD $_DVFS_RECONFIG

$MAILCHECK $PATH $PS2 $TZ

Windows environment variables CMD is used to start the Windows command-line interpreter during restore. The following exported operating system environment variables are available during the restore:

148

Restoring clients About SAN (storage area network)

%ALLSPROFILE% %CommonProgramFiles% %ComSpec%

%APPDATA% %COMPUTERNAME% %HOMEDRIVE%

About SAN (storage area network) Bare Metal Restore (BMR) can restore a system that is attached to a Storage Area Network (SAN). On Windows, AIX, Linux, Solaris, and HP-UX systems, if the host bus adapter (HBA) drivers are available, BMR automatically restores the SAN-attached volumes. Note: During BMR recovery, can either avail BMR DDR (dissimilar disk restore) where may want to restore operating system on the same SAN LUNs to make the machine SAN bootable again or the can move operating system volumes on local disk so that machine is bootable from the local disk. Same logic is applicable while restoring machine having local disk-based systems. Using DDR, can map operating system volumes to SAN LUN and can make restored machine SAN bootable. See “Restoring Solaris SAN-attached volumes if they are left unmapped” on page 149. See “About SANs and dissimilar system restores on Windows clients” on page 150.

Restoring Solaris SAN-attached volumes if they are left unmapped The following information applies only to Solaris clients. After a Solaris system is recovered using the dissimilar disk restore feature, you may need to perform the following procedure for SAN-attached volumes that were left unmapped (marked not to restore). To restore Solaris SAN-attached volumes if they are left unmapped

1

Determine the differences between the current and previous vfstab files: % diff /etc/vfstab /etc/vfstab.old.bmr.dmr

2

Review the differences.

3

Copy the entries about the SAN devices from the /etc/vfstab.old.bmr.dmr file. Add them to the /etc/vfstab file or uncomment the corresponding lines that are commented out when vfstab was merged.

149

Restoring clients About multiple network interface

4

Mount the file systems that are on the SAN.

5

Manually restore the SAN file systems using the NetBackup Backup, Archive, and Restore interface.

About SANs and dissimilar system restores on Windows clients The following information applies only to Windows clients. If you perform a dissimilar system restore on Windows and you want to restore to a SAN disk, you must do the following: ■

Add the HBA drivers to the restore configuration. The HBA drivers can be added the same way as any other mass storage device driver.

■

Reconfigure your SAN so that the HBA in the target system sees the same devices as the HBA that existed in the source system.

More information is available on adding drivers. See “About adding NIC and MSD drivers” on page 133.

About multiple network interface BMR recovery occurs in two major stages: boot stage and restore files stage. The boot stage uses a single network interface to talk to the BMR boot server. Once the restore environment is loaded from the boot server, BMR configures and activates all network interfaces for the restore files stage. Note: Systems with multiple network interfaces are also known as multihomed systems. BMR fully multihomed clients. Figure 6-4 illustrates a configuration that can occur with multihomed clients. For this configuration, specify the network interface for Network 1 when you network boot the client.

150

Restoring clients About multiple network interface

Figure 6-4

Simple multihomed example

Network 1 1.1.1.0

BMR boot server

BMR client Network 2 2.2.2.0

NetBackup BMR master server

About client configuration using gateways BMR clients can use gateways to communicate with BMR and NetBackup servers during a restore operation. Table 6-12 describes gateway attributes that are used during a restore. Table 6-12

Network gateways

Gateway

Description

Default Gateway

Defines the default network gateway for the client during the restore.

Master Server Gateway Defines the gateway from the client to the NetBackup master server. Media Server Gateway Defines the gateway from the client to the NetBackup media server used to restore the files.

You may not have to specify all gateways. If the client can communicate with all hosts through the default gateway, you only have to specify the default gateway. For network boots, specify the following: ■

The gateways for the NetBackup master and media servers in the Hosts dialog box of the restore configuration

■

The default gateway in the Network Routes dialog box

For media boots, you are prompted for these values when you create the boot media or during the restore.

151

Restoring clients Port usage during restores

Figure 6-5 shows how gateways can be used during a BMR client restore. Gateway example

Figure 6-5

NetBackup master server (network 3) G2 Master server gateway BMR client (network 1) G1

G3 Media server gateway

Default gateway (network 2)

(network 4)

NetBackup media server

BMR boot server

The client in this diagram cannot communicate with all of the servers it needs to by using only the default gateway. For such a configuration, you should specify the default gateway as G1, the master server gateway as G2, and the media server gateway as G3.

Port usage during restores During restores, clients communicate with BMR master, BMR boot, and NetBackup master-media servers through specific services and ports. If the boot servers are behind a firewall, communication between the client server and boot servers must be allowed through these ports. Table 6-13 lists the ports and services that are used during restores. Table 6-13

Port usage during restores

Service

Port

bootp/DH

67, 68

UNIX

Linux

Windows

X

X

X

152

Restoring clients Port usage during restores

Table 6-13 Service

Port usage during restores (continued) Port

UNIX

Linux

Windows

X

ping lockd

Unreserved

X

X

mountd

Unreserved

X

X

nfsd

2049

X

X

portmapper

111

X

X

X (for bootpararm on Solaris only)

rpcbind

statd

Unreserved

X

X

tftp

69

X

X

X

vnetd

13724

X

X

X

bpcd

13782

X

X

X

Windows File Sharing

445

X

153

Chapter

7

Managing Windows drivers packages This chapter includes the following topics: ■

About Windows drivers packages

■

Adding a Windows driver package

■

Deleting a Windows driver package

About Windows drivers packages Windows packages are network interface card (NIC) drivers and mass storage device (MSD) drivers. Packages are stored in the BMR database on the NetBackup master server. The packages pool comprises of the packages that are stored in the database. The packages pool is the common pool of packages that can be added to restore configurations. Packages may be required when you restore to a different system, in which case you add packages to the restore configuration. If the Packages window does not contain a driver that is required for a dissimilar system restore, add it to Bare Metal Restore. Do not add it to the restore configuration if a driver is on the Windows installation media that created the SRT. If a package required for a dissimilar system restore already appears in the Packages window, add it to the restore configuration. See “Client configuration properties” on page 164. See “Devices and drivers properties” on page 166.

Managing Windows drivers packages Adding a Windows driver package

Adding a Windows driver package Add a package, as follows: ■

Use the Driver Package Wizard on any Windows boot server to add a network interface card (NIC) driver or mass storage device (MSD) driver.

■

Alternatively, install NetBackup client software on the target system and perform a full BMR backup. The drivers are saved in that client’s configuration and available for use during a dissimilar system restore.

Before you can add a package, you must have the installation files for the package. Obtain the files from the vendor’s Web site, the installation program that is provided with the NIC device or MSD device, or another BMR Windows client in your environment. Note: You can add only NIC and MSD drivers. All other types of drivers (audio, video, modem, and so on) must be installed on the system after the restore is complete. See “Finding the correct driver if Windows is already installed” on page 155. To add a driver package by using the Driver Package Wizard

1

On the Start menu on any Windows boot server, click Programs > Symantec NetBackup > Bare Metal Restore Boot Server Assistant.

2

In the Bare Metal Restore Boot Server Assistant, click Driver Package Wizard.

3

In the Driver Package Wizard, step through the prompts as follows to add the software package: ■

Path to the installation files for the package

■

Description of the package

■

Version of Windows that the package can be used with

■

The specific driver from the package installation files (installation files may include more than one driver)

Finding the correct driver if Windows is already installed A driver information file (.inf or txtsetup.oem) may contain information about more than one driver. Therefore, when you add a mass storage device (MSD) or network interface card (NIC) driver, you may have to select from more than one option.

155

Managing Windows drivers packages Deleting a Windows driver package

The devices should be documented in the materials that come with the computer. If not, the manufacturer for the driver option. Alternatively, use the following procedure to determine the correct name for the driver if Windows is installed. To find the correct driver if Windows is already installed

1

On the computer that contains the mass storage device adapter, open the Windows device manager.

2

Expand the category for the adapter (for example, network adapters).

3

Note the device name that appears here. The option name in the .inf file should be the same or similar to this device name.

Deleting a Windows driver package The following procedure deletes a driver package. Warning: Do not delete any drivers that are required for a restore. To delete a Windows driver package

1

In the NetBackup istration Console on the NetBackup master server, click Bare Metal Restore Management > Resources > Packages.

2

In the details pane, right-click the driver you want to delete.

3

Select Delete on the shortcut menu.

4

In the confirmation , click Yes. The selected package is deleted.

156

Chapter

8

Managing clients and configurations This chapter includes the following topics: ■

About clients and configurations

■

Copying a configuration

■

Discovering a configuration

■

Modifying a configuration

■

Deleting a configuration

■

Deleting a client

■

Client configuration properties

About clients and configurations Logically, a BMR client is a collection of configurations. A configuration is a collection of information about the system to be used as a template to rebuild a protected system. It includes the following: ■

Number of disk drives

■

Volume information

■

File system information

■

Number and type of network adapters

■

Network properties

Managing clients and configurations Copying a configuration

■

Drivers

■

Other system software components.

Most BMR operations are performed on configurations. When a BMR protected client is backed up, the configuration of the client is saved and named current. Every time a client is backed up, the new saved configuration replaces the previously saved configuration. The saved, current configuration is read-only. Use the current configuration to restore the original protected system to its state at the most recent backup (a standard or a self restore). To restore to a different point in time, to different disks, or to a different system, create a restore configuration by copying a current configuration. Then modify the restore configuration.

Copying a configuration Copy a configuration so that you can do the following: ■

Restore a client to a state that was saved in a backup before the last backup. See “About restoring to a specific point in time” on page 123.

■

Restore a client in which the disks have changed. See “About restoring to dissimilar disks” on page 126.

■

Restore a Windows client to a different system. See “Restoring to a dissimilar Windows system” on page 131.

■

Restore a client to the same hardware but with different network properties.

A copied configuration that is used for a restore is called a restore configuration. After you create the restore configuration, modify it so it matches the target hardware properties. To copy a configuration

1

In the NetBackup istration Console, click Bare Metal Restore Management > Hosts > Bare Metal Restore Clients.

2

In the All Bare Metal Restore Clients tree pane, expand the view of the client that contains the configuration you want to copy.

3

Right-click the configuration you want to copy.

158

Managing clients and configurations Discovering a configuration

4

On the shortcut menu, select New.

5

On the New Configuration for Bare Metal Restore Client dialog box, complete the fields.

6

Click OK.

7

If necessary, modify the configuration. See “Modifying a configuration” on page 162.

Discovering a configuration You can discover the configuration of a new system; the system does not have to be a NetBackup client. A discovered configuration contains the hardware and the software information of a host. Hardware discovery is mainly required when you are recovering a client onto different target machine than the original. In this case, as target machine differs in hardware details like NIC (network interface card), disk details than original, BMR needs to understand those details before restore begins. Therefore needs to perform hardware discovery of target hardware using BMR prepare-to-discover operation and map original client configuration with the discovered configuration. When you discover a configuration, BMR adds it to the discovered configurations pool. The elements of the configuration (such as disk layout) can then be used when you perform operations such as dissimilar disk restore.

159


When the discovery operation ends, the following changes appear on the client, and the configuration appears in the Discovered Configurations view: ■

AIX clients display B55 on the LED display.

■

HP-UX, Linux, and Solaris clients display the following message: The Bare Metal Restore hardware discovery boot has concluded.

■

Windows clients display a popup box stating that the discovery is finished and that you can click OK to reboot the system.

160


To discover a configuration

1

In the Bare Metal Restore Management node, click Actions > Prepare to Discover.

2

In the Prepare to Discover dialog box, complete the fields and enter data as necessary. If you select a client in the Hosts > Bare Metal Restore Clients view, the values for that client are included in the dialog box. Note: If a client is the target of a dissimilar disk restore (DDR) and VxVM manages the protected client’s disks, specify an SRT with VxVM installed.

161

Managing clients and configurations Modifying a configuration

3

Click OK.

4

Boot the client to start the hardware discovery operation. If you use media boot, when BMR prompts for the client name, enter it as it appears in the Tasks view from the prepare-to-discover operation. Target machine discovery will be done automatically and you get a notification upon discovery completion. Upon successful discovery operation, you can see the discovered configuration with the given name under Bare Metal Restore Management > Resources > Discovered Configurations menu.

Modifying a configuration Modify a configuration so you can do the following: ■

Restore a client to a state that was saved in a backup before the last backup. See “About restoring to a specific point in time” on page 123.

■

Restore a client in which the disks have changed. See “About restoring to dissimilar disks” on page 126.

■

Restore a Windows client to a different system. See “Restoring to a dissimilar Windows system” on page 131.

■

Restore a client to the same hardware but different network properties.

■

Restore a client by skipping intended non-OS data volumes or disks.

■

Make client SAN bootable by mapping its OS volumes onto SAN LUNs.

You cannot modify the configuration named current; you must create a configuration you can edit. See “Copying a configuration” on page 158. To modify a configuration

1

In the NetBackup istration Console, click Bare Metal Restore Management > Hosts > Bare Metal Restore > Clients.

2

In the All Bare Metal Restore Clients pane, expand the view of the client that contains the configuration you want to modify.

3

Right-click the configuration you want to modify.

4

On the shortcut menu, select Change.

5

In the Change Configuration dialog box, modify properties as needed. See “Client configuration properties” on page 164.

162

Managing clients and configurations Deleting a configuration

Figure 8-1

Change Configuration Dialog Box

Deleting a configuration You cannot delete a current configuration as it is read-only. Only custom created configurations can be deleted. To delete a configuration

1


2

In the All Bare Metal Restore Clients pane, expand the view of the client that contains the configuration you want to delete.

3

Right-click the configuration you want to delete.

163

Managing clients and configurations Deleting a client

4

On the shortcut menu, select Delete.

5

In the confirmation dialog box, click Yes.

Deleting a client When you delete a client, it removes only the client and its BMR configurations from the BMR database. It does not remove the NetBackup software on the client, nor remove it from NetBackup, nor delete the backups of the client. You can delete a client but not remove it from the NetBackup policy that backs it up. If you do, the client is reed with BMR the next time it is backed up and appears in the Bare Metal Restore Clients view. (The NetBackup policy that backs it up is the policy that collects BMR information.) To delete a client

1


2

Right-click the client you want to delete.

3

On the shortcut menu, select Delete.

4

In the confirmation dialog box, click Yes.

Client configuration properties Use the Change Configuration dialog box to map the attributes of the client configuration on the protected system to the restore configuration. Map the configurations to enable point-in-time restore, dissimilar disk restore, or dissimilar system restore. The Change Configuration dialog box contains multiple property sheets. See “Configuration Summary properties” on page 165. See “Devices and drivers properties” on page 166. See “Hosts properties” on page 169. See “Network interfaces properties” on page 170. See “Network routes properties” on page 174. See “About Volumes properties” on page 176. Configuration changes are saved differently depending on which of the following NetBackup istration interfaces you use:

164

Managing clients and configurations Client configuration properties

■

In the Windows-based istration Console, changes occur when you click OK or Apply.

■

In the Java-based istration Console, changes occur when you make them.

Configuration Summary properties Use Configuration Summary property sheet of the Change Configuration dialog box to do the following: ■

View a summary of the configuration.

■

Change a license key for software on the protected system that requires a license key.

■

Determine the components of the restore configuration so you can select a shared resource tree that has the appropriate software for the restore.

Figure 8-2

Configuration Summary

Table 8-1 describes the actions you can initiate regarding license keys.

165


Table 8-1

License key actions

Action

Description

Add License Key

Opens a dialog box in which you can add the license key for the selected software.

Change License Key

Opens a dialog box in which you can change the license key for the selected software.

Remove License Key Deletes the selected license key.

Table 8-2 describes the client fields that are displayed in the dialog box. Table 8-2

Client items

Field

Description

Name

The name of the client.

Operating system

The operating system of the client.

Service pack

(Windows clients only.) The service pack version on the client.

Architecture

(UNIX and Linux clients only.) The architecture of the client.

NetBackup version

The NetBackup software version on the client.

Veritas Volume Manager version

The version of Veritas Volume Manager or Veritas Storage Foundation for Windows (if any).

Table 8-3 describes the configuration fields that are displayed in the dialog box. Table 8-3

Configuration fields

Field

Description

Name

The name of the configuration.

State

The state of the configuration. Saved indicates a configuration that cannot be edited. Copied indicates that the configuration can be edited.

Last modification The date and time when the configuration was last modified. Version

The version of the configuration.

Devices and drivers properties The Devices & Drivers property sheet applies only to Microsoft Windows clients. The Device Drivers mapping changes are required when a Windows client is being

166


restored to a different hardware than the original system, and target hardware has different mass storage device (MSD) drivers and/or network interface card (NIC). Use the Devices & Drivers property sheet of the Change Configuration dialog box to perform the following actions: ■

Initialize the devices in this configuration from a new hardware discovered configuration or from another client's configuration.

■

Automatically select the correct mass storage device (MSD) drivers and network interface card (NIC) drivers for the listed devices.

■

Manually add MSD and NIC drivers to the configuration.

You can also specify whether to use only BMR discovered drivers. Figure 8-3

Devices & Drivers dialog box

Table 8-4 describes the options available and the actions they initiate.

167


Table 8-4

Device and driver options

Option

Action

Initialize Devices...

Prompts you for another configuration from which to import the devices. You may select a discovered configuration or one from another client. The initialize operation updates the Drivers packages to be used during restore window to include the necessary drivers for this hardware.

Map Drivers

Automatically matches drivers to devices without drivers. If drivers are added to BMR after the last initialize operation, repeat this action. Sometimes, it may be useful to override the driver that is selected automatically by using the Add option to select a specific driver manually. Devices without a driver are identified in the Devices window by No matching driver in the Enabled column. These devices are not available during the restore.

Add

Moves the selected driver from the Available driver packages window to the Driver packages to be used during restore window.

Remove

Moves the selected driver from Driver packages to be used during restore window to the Available driver packages window.

Change

Lets you change the following attributes of the selected driver: ■

■

The Force installation of this driver instead of Windows supplied or newer driver checkbox controls whether the selected driver is to be used forcefully. For MSD drivers, the Bootable driver to be used during text mode portion of the installation checkbox only applies to Windows 2003 legacy restore method. It determines if the driver is used during the installation phase of the Windows 2033 legacy restore. It has no effect for a Fast Windows Restore.

Force installation of this driver instead of Windows supplied or newer driver When BMR saves third-party drivers from a protected system, the driver g is lost. (Third-party drivers are those that are not part of the Windows distribution.) During the BMR restore, the installation process installs the standard drivers into the temporary repair environment because the drivers from the protected system are unsigned. You can edit the configuration so that the discovered drivers are forcefully installed onto the temporary repair environment rather than the standard Windows drivers. This option also helps to select particular driver version.

168


To use discovered Windows drivers during a restore

1

In the Devices & Drivers property sheet, select the desired driver from the list of drivers in the bottom window, and click Change.

2

Select the Force installation of this driver instead of Windows supplied or newer driver checkbox.

3

Click OK.

Hosts properties Use the Hosts property sheet of the Change Configuration dialog box to add, remove, or change the attributes of any host that has a role in the restore process. You can change attributes so you can restore on a network with a different configuration, such as at a disaster recovery site. Figure 8-4

Hosts property sheet

Table 8-5 describes the actions you can initiate from the property sheet.

169


Table 8-5

Hosts mapping actions

Action

Description

Add

Opens a dialog box in which you can add a new host, specify its role, and enter its IP address and gateway.

Change

Opens a dialog box in which you can change properties for the selected host.

Remove

Removes the selected host. If you don’t want to remove the host, click Cancel to exit the Change Configuration dialog box without applying the changes.

Table 8-6 describes the Client Information fields in the Hosts property sheet. Table 8-6

NetBackup Client Information fields in Hosts dialog box

Field

Description

Client Name

The name by which NetBackup knows the client. The specified client name must match the client name in the NetBackup policy that backs up the client.

IP address

The IP address of the client. All IP addresses defined in the network interfaces are in the drop-down list.

NetBackup version

The NetBackup software version on the client.

Network interfaces properties Use the Network Interfaces property sheet of the Change Configuration dialog box to add or remove interfaces or change the network identity that is associated with an interface.

170


Figure 8-5

Network interfaces property sheet

The Original Network Information is read-only. The New Network Information shows the values that are used for the restore. If the configuration was not edited, the top panes and bottom panes show the same information. Table 8-7 describes the actions you can initiate from the dialog box. Table 8-7

Network interface mapping actions

Action

Description

Initialize

Opens a dialog box from which you can select a configuration to import. Only the hardware information from the configuration is imported, not the network identity. The interfaces from the imported configuration replace the interfaces in the New Network Information window.

171


Table 8-7

Network interface mapping actions (continued)

Action

Description

Unmap All

Unmaps all mapped interfaces in the New Network Information window and changes all interfaces in the Original Network Information window to Unmapped. The unmapping removes the name, IP addresses, network masks, gateways, and DH and bootable attributes. MAC addresses are not removed.

Map

Right-click an interface in the Original Network Information window and select Map from the shortcut menu. In the Map Interface dialog box, select an interface in which to map the IP address, netmask, and domain name from the source network card. The MAC address of the original interface is not mapped to the target interface.

Unmap

Right-click an interface in the New Network Information window and select Unmap from the shortcut menu. The unmapping of an interface removes the name, IP addresses, network masks, and DH and bootable attributes. MAC addresses are not removed.

Change

Right-click an interface in the New Network Information window and select Change from the shortcut menu.

Importing and mapping network interfaces If you restore to a dissimilar system and you save the target system’s configuration by backing up the target system, you can do the following: ■

Import the network interface card (NIC) information from the target system into the restore configuration.

■

Map the network identify from the NICs in the original configuration to the NICs in the restore configuration.

To import and map interfaces

1

Click Initialize.

2

In the Import configuration dialog box, select the client configuration to import.

3

Click OK. The network hardware information is imported into the New Network Information window and replaces the interfaces that were in the window. The network identity (IPs, routes, and so on) is not imported.

172


4

Right-click an interface in the Original Network Information window and select Map from the shortcut menu.

5

In the Map or Change Interface dialog box, select an interface from the Map to Interface drop-down list.

6

Click OK. The IP address, netmask, and fully qualified domain name are applied to that interface on the restored system.

Changing network interfaces manually If you restore to a dissimilar system and do not discover or save the target system’s configuration, you can manually change original configuration interface properties for a restore. You must first determine the MAC addresses of the NICs in the target system. To change an interface manually

1

Right-click an interface in the New Network Information window and select Change from the shortcut menu.

2

In the Map or change interface dialog box, select Use DH (if using DH). Because this action is an interface change, the dialog box includes the Hardware MAC Address field. Go to step 5.

3

Select a row of attributes in the Attributes for Network Interface window and click Change.

4

In the Add Network Identity dialog box, enter the IP address, netmask, and fully qualified domain name from the interface on the protected system. Then click OK.

5

Enter the hardware MAC address of the NIC in the target system.

6

Click OK. The MAC address and network identity are changed. The name of the interface is not changed, but it does not affect the restore.

Specifying the UNIX and Linux boot interface UNIX and Linux clients must use a single network interface to boot from and to restore through. The Bootable column in the Network Interfaces dialog box shows the interface that is configured as the boot interface. If your restore configuration includes more than one network interface, you can specify which one to use for the restore.

173


Table 8-8 helps you to determine the correct interface. Table 8-8

Bootable network interfaces

Platform or hardware type Bootable network interface(s) AIX

Integrated Ethernet, Ethernet card, or Token Ring Note the following about the network interfaces on AIX: ■

Only chrp hardware is ed.

■

Booting the RS/6000 from a network adapter requires in the system firmware.

HP-UX

Integrated Ethernet only

Linux

Any Ethernet device

Solaris

Any Ethernet device

To specify the UNIX and Linux boot interface

1

In the New Network Information window of the Network Interfaces property sheet, right-click the interface that you want to use as the boot interface.

2

Select Change from the shortcut menu.

3

In the Map or Change Interface dialog box, click Bootable.

4

Click OK.

Note: In case target hardware is booted using different network Interface for recovery than the one shown as Bootable in BMR client configuration, then recovery may result info failure.

Network routes properties Use the Network Routes property sheet of the Change Configuration dialog box to add a network route to use during the restore.

174


Figure 8-6

Network routes property sheet

You may need to add a route if an existing route in the configuration is not sufficient to reach the NetBackup or BMR servers. This situation can occur during disaster recovery at a different location when you move servers from one subnet to another. It also can occur when any routers that intervene are changed. For example, client 10.10.5.12 and NetBackup master server 10.10.6.23 have a router (10.10.5.254) between them because they are on different subnets. When you prepare to restore, the restore process configures the route to the NetBackup master server as 10.10.5.254, and the restore is successful. However, if the IP address of the router between them changes, the client may not be able to reach the master server. The client cannot reach the server because the configuration does not include the correct route to it. Therefore, you must add a network route to the master server before you perform the prepare-to-restore operation. BMR attempts to reach hosts in the following order: ■

Host routes (specified on the Hosts property sheet)

■

Network routes that are specified on this property sheet

175


■

The default route that is specified on this property sheet

Table 8-9 describes the fields and options in the property sheet. Table 8-9

Network routes mapping fields

Action

Description

Default gateway

The gateway to use if no other route reaches a host.

Add

Opens a dialog box in which you can enter the properties for a new network route.

Change

Opens a dialog box in which you can change the properties for the selected route.

Remove

Removes the selected route.

About Volumes properties Use the Volumes property sheet of the Change Configuration dialog box to map the volume configuration from the protected client to the new disks of the restore configuration.

176


Figure 8-7

Volumes property sheet

You can perform the following operations for mapping volumes and for changing configurations: ■

Change the disks that make up a disk group.

■

Control the file systems that are restored.

■

Control the logical volumes that are created.

■

Change the attributes of either a file system, a logical volume, or a disk.

■

Restrict a disk to prevent it from being used as a target for mapping.

■

Make a discovered disk available for mapping (remove restriction).

Given enough space on the target disk, you can map all the logical volumes and their file systems. Or you can map specific logical volumes and file systems. You do not have to restore all your logical volumes and file systems. Primary partitions and simple volumes require only one disk. Striped, mirror, and RAID-5 volumes require multiple disks.

177


About Native Disk Objects A new Native Disk node appears under the Volumes node in the Change Configuration dialog box. The following example shows information about the Native disks that are available with the total size, used space, and free space.

You can map the Solaris Native disk resource by using the disk mapping wizard. To map a disk using the mapping wizard, right-click a volume in the list and click map. The following is an example of Disk Mapping Wizard.

178


A Partition node appears under the Native Disks node. The following example shows the information regarding the partition name, partition state, partition length (size).

You can map the partition by using the mapping wizard. Right-click the Volume to launch the mapping wizard. You can map the source partition to destination disk and specify the percentage space of the destination disk to use for creating the partition.

179


About mapping and unmapping volumes The wizard that appears for mapping volumes depends on what you select to map. These wizards guide you through the mapping process. The mapping is saved between sessions, so you can stop mapping and then resume later. (If you map during a dissimilar disk restore process and you click OK to close the Change Configuration dialog box, the DDR restore process continues.) If an element is mapped or unmapped, all the elements that are contained in it are mapped or unmapped. The main options are as follows:

180


Initialize

Opens a dialog box where you can select a configuration to import into the New Volume Layout window. Only the disk information from the configuration is imported. Use this option to initialize the configuration with the layout of the new disks so you can begin mapping.

Unmap All

Removes all mapped elements in the New Volume Layout and changes all elements in the Original Volume Layout window to Unmapped.

Note: The mapping wizards do not let you reduce the size of a volume or partition to less than the required space to restore files. The following notes apply to UNIX and Linux DDR: ■

Shared disks in a cluster are marked restricted.

■

Unused VxVM disks on Solaris clients are marked restricted.

■

You cannot map Linux LVM volume groups with the physical volumes that are created on top of multi-devices with the same configuration. The physical volumes are mapped to either disks or partitions but not a multi device.

The following notes apply to Windows DDR: ■

The system drive is always mapped and cannot be moved; however, you can resize it if you map disks before the restore.

■

Original disks and their volumes that were clustered cannot be mapped.

■

The discovered disks that have the same disk signature as an original disk that was clustered cannot be mapped.

Table 8-10 describe possible volume mapping actions. Table 8-10

Volume mapping actions

Action

Description

Initialize

Opens a dialog box from which you can select a configuration to import into the New Volume Layout window. Only the disk information from the configuration is imported.

Fast Map

Evaluates the original configuration and maps source disks to disks in the target configuration that have the necessary attributes.

Unmap All

Removes all mapped elements in the target configuration and changes all elements in the original configuration to Unmapped.

181


Table 8-10

Volume mapping actions (continued)

Action

Description

Map

Right-click an element in the Table View of the Original Volume Layout window and select Map from the shortcut menu. The mapping wizard starts for the selected element (except main element Disk Group, Disks, Volumes, Volume Sets, and so on).

Map Volume

Right-click a volume in the Disk View of the Original Volume Layout window and select Map Volume from the shortcut menu. The mapping wizard starts for the selected element.

Map Volume Group

Right-click a volume group in the Disk View of the Original Volume Layout window and select Map Volume Group from the shortcut menu. The mapping wizard starts for the selected element.

Map Disk

Right-click a disk in the Disk View of the Original Volume Layout window and select Map Disk from the shortcut menu. The mapping wizard starts for the selected element.

Map Disk Group

Right-click a disk group in the Disk View of the Original Volume Layout window and select Map Disk Group from the shortcut menu. The mapping wizard starts for the selected element.

Restrict

(Veritas Cluster Server only.) Right-click an element in the Original Volume Layout window and select Restrict from the shortcut menu.

Remove Restriction

(Veritas Cluster Server only. ) Right-click an element in the New Volume Layout window and select Restrict from the shortcut menu to map the disk.

Mapping volumes Use the following procedures to map volumes from the protected client to the restore configuration. To initiate mapping for individual elements

1

In the Table View or Disk View, right-click the element in the Original Volume Layout window.

2

Choose the appropriate map option on the shortcut menu (the map options are context-sensitive ). The Mapping Wizard starts with one of the following contexts, as appropriate:

182


Map

The Mapping Wizard starts for the selected element (except main element disk groups, disks, volumes, volume groups, and so on).

Map Volume

The Volume Mapping Wizard appears.

Map Volume Group

The Volume Group Mapping Wizard appears.

Map Disk

If the element is a disk in a disk group or a volume group, the disk group or volume group wizard appears. Then the volume mapping wizard for each volume appears (the required properties are set). The Disk Mapping Wizard appears if the element is as follows: ■

A disk that is not in a disk group

■

Not part of a volume group (AIX)

■

None of its volumes span other disks (mirrors, stripes).

Then all the volumes and the file systems are populated into the target disk. The mapped state are set for both source elements and target elements (disks, volumes, and file systems) Map Disk Group

The Disk Group Mapping Wizard appears.

To unmap an element

1

In the Table View or Disk View, right-click the element you want to unmap in the New Volume Layout window.

2

Click the unmap option on the shortcut menu. The unmap options are context-sensitive and include Unmap, Unmap Disk, Unmap Volume, and others. The element is unmapped, and the values of used and free space change accordingly.

To change the system volume size on Windows

1

In the Table View or Disk View, right-click the volume in the New Volume Layout window.

2

Click Change Size on the shortcut menu.

3

In the Windows System Volume Size Change dialog box, change the size of the volume.

4

Change the size of the volume.

183


To restrict a disk or remove restriction

1

In the Table View or Disk View, right-click the disk in the New Volume Layout window.

2

Click either Restrict or Remove Restriction on the shortcut menu to specify the following: ■

Restrict prevents a disk to be used as a target for mapping. Also, it is not formatted, and the volume groups or volumes on it are not created or restored.

■

Remove Restriction removes the restriction so the disk can be used as a target. If the disk is mapped, it is formatted and its volumes and volume groups are created and restored.

To promote a disk to dynamic on Windows

1

In the Table View or Disk View, right-click the disk in the New Volume Layout window.

2

Click Promote to Dynamic on the shortcut menu.

To add or remove a Windows system mirror

1

If the disk is a basic disk, promote it to a dynamic disk

2

In the Table View or Disk View, right-click the element in the New Volume Layout window.

3

Click either Add Mirror or Remove Mirror on the shortcut menu.

4

If you add a mirror, in the Windows Add Mirror to System Volume dialog box, select the disk to use for the mirror.

5

If you add a mirror, select the disk to use for the mirror.

Volumes views The tree view (the left pane) shows the elements that are part of the disk layout. The elements in the tree change depending on the operating system of the client and the volume managers that are enabled. The tree view filters the details pane on the right. Select an element to display its attributes in the right pane and to filter other elements so they do not appear in the details pane. The following indicators show an element’s state throughout the mapping process: Unmapped

The element is not mapped into the new configuration.

Mapped

The element is mapped into the new configuration.

184


Restricted

The disk is or was shared or manually restricted and cannot be used.

The details pane on the right contains the following views: ■

The Table View shows the elements in an ordered list.

■

The Disk View shows how every disk is organized. A colored bar indicates the type of storage layout. For extended partitions, the primary partition color appears in the top color bar and the extended color in a bottom bar. For soft partitions, the top bar shows the underlying volume or slice on which the soft partition was created.

■

The Pool View shows how every file system and volume of ZFS pool is organized. Note: The pool view is added in NetBackup 7.5 to ZFS-managed storage pools.

■

The Original Volume Layout (the top window) shows the volume layout and the source elements (disks, disk groups, or volumes) in the original system. The amount of space that is used and the size of the disk appears. To view the properties for an element, right-click the element and select Properties on the shortcut menu.

■

The New Volume Layout (the bottom window) shows the volume layout and elements for the target system. If you initialize the configuration with the layout from a discovered configuration, map elements from the Original Volume Layout to the New Volume Layout.

The following is the hierarchy for volume information: ■

A disk group, volume group, or disk set contains disks.

■

A disk contains volumes and partitions.

■

A volume or a partition contains file systems.

All volume managers may not use all of these logical concepts. For example, a Solaris slice does not belong to a disk group and has only a file system. The following tables show the various elements in the tree view and what appears in the Table View tab and Disk View tab. Table 8-11 lists details about the selected Windows elements.

185


Table 8-11

Windows elements

Node

Appears in Table View

Appears in Disk View

Windows Disk Management

Disk and volumes

Not applicable.

Disks

All disks in the system.

All disks in the system.

Volumes

All the volumes that are Disks that contain volumes, defined in the system, both regardless of which volume managed or unmanaged. manager created them.

One specific volume

Disks that the volume spans.

Disks that the volume spans.

Table 8-12 lists details about the selected Veritas Volume Manager elements. Table 8-12

Veritas Volume Manager and Storage Foundation for Windows elements

Selected element



Veritas Volume Manager

Disk groups, volume sets, and volumes.

Not applicable.

Disk groups

Disk groups in the configuration. Disks that are part of any disk group.

A specific disk group

Disks that are part of that disk group.

Disks that are part of that disk group.

Volumes

All the volumes that Volume Manager manages.

Disks that contain Volume Manager volumes (ordered by disk group)

A specific volume

Disks that contain that volume.


Table 8-13 lists details about the ZFS Manager elements. Note: In NetBackup 7.5, BMR can also restore Solaris 10 clients that have ZFS storage pool attached.

186


ZFS Manager elements

Table 8-13 Selected Element


Appears in Pool View

ZFS Manager

Not applicable Not applicable

ZFS pools Not applicable Details of File systems and Volumes on each ZFS Pool

Appears in Disk View Not applicable

Details of disks associated with each ZFS Pool

ZFS file systems

Not applicable Pool space consumption Not applicable details of each selected ZFS File system

ZFS volumes

Not applicable Pool space consumption Not applicable details for each selected ZFS volume

Table 8-14 lists details about the selected Solaris Volume Manager elements. Table 8-14

Solaris Volume Manager elements

Selected Element



Solaris Volume Manager

Disk sets and volumes.

Not applicable.

Disk sets

All named (nonlocal) sets.

Disks that are part of a named (nonlocal) set (ordered by disk set).

A specific disk set

Disks that are part of that disk set.

Disks that are part of that disk set.

Volumes

All SVM volumes.

Disks that have SVM volumes.

A specific volume

Disks that include that volume.

Disks that include that volume.

Table 8-15 lists details about the selected non-managed Solaris elements. Table 8-15

Non-managed Solaris elements

Selected element



Non-managed

Disks and partitions.

Not applicable.

Disks

All disks that VxVM does not All disks that VxVM does not manage and all disks that are not manage and all disks that are not in an SVM disk set. in an SVM disk set.

187


Table 8-15

Non-managed Solaris elements (continued)

Selected element



Slices

All slices that are not managed and not used as SVM meta devices.

All disks that contain nonmanaged slices.

Table 8-16 lists details about the selected empty disks elements. Table 8-16

Empty disks elements

Selected element



Empty disks

Disks that are not used.

Disks that are not used.

Table 8-17 lists details about the AIX and HP-UX logical volume manager elements. Table 8-17

AIX and HP-UX logical volume manager elements

Selected Element



Logical volume manager

Volume groups and volumes.

Not applicable.

Volume groups

Volume groups in the configuration.

Disks that are part of any volume group (ordered by volume group).

A specific volume group

Disks that are part of that volume Disks that are part of that volume group. group.

Volumes

All the volumes that the LVM manages.

Disks that have LVM volumes.

A specific volume



188

Chapter

9

Managing BMR boot servers This chapter includes the following topics: ■

About boot servers

■

Boot server requirements

About boot servers Boot servers provide the environment that is required to rebuild a protected client, including system recovery needed resources such as shared resource trees (SRT). Boot servers also provide the resources that are used to boot the client system when it performs a network boot before restore. This temporary operating system environment known in the NBU-BMR language as an SRT or Shared Resource Tree, needs to be created and hosted according to the peculiar requirements of a host’s operating system and that of NBU-BMR as well. An SRT is a collection of OS Files, NBU Client Software and other required software like the Veritas Volume Manager. An SRT is NOT an image of the client and a single SRT can be used for recovering multiple clients. Many of the operations required to be carried out for creation and modification of a SRT are dependent on the target host’s operating system. Hence, NBU-BMR needs a Boot Server of the same operating system as that of the hosts that are to be recovered. Boot server software is installed from the NetBackup installation media. The general deployment including the BMR Boot Server appears as follows: Refer chapter Configuring BMR to understand BMR boot server setup.

Boot server requirements More information is available about the SRT requirements that are related to boot servers.

Managing BMR boot servers Boot server requirements

See “About shared resource trees” on page 38. Table 9-1

Boot server requirements

Type of server

Requirements

General boot server

You must have a boot server for each type of client that you want to protect. For example, a Solaris client requires a Solaris boot server, a Windows client requires a Windows boot server, and so on. For UNIX, Linux, and legacy Windows restores, a boot server at a particular operating system version can only host SRTs of the same operating system version or lower. For example, a Solaris 9 boot server can host Solaris 8 and Solaris 9 SRTs, but not Solaris 10 SRTs. For UNIX, Linux, and legacy Windows restores, a client at a particular operating system version requires an SRT of the same operating system version. Refer appendix Network services configurations on BMR Boot Server to know details about network-based recovery pre-requisite setup for different platforms.

AIX boot server

AIX boot servers do not have any special requirements. An AIX boot server can reside on the same subnet as the subnet of the client, or on a different subnet. However, AIX boot servers at a specific operating system version can only host SRTs of the same or earlier operating system version. For example, a 5.3.0.10 boot server can only host 5.1.x.x, 5.2.x.x, 5.3.0.0, and 5.3.0.10 SRTs, but not 5.3.0.20 SRTs. Likewise, a 5.2.x.x boot server cannot host 5.3.x.x SRTs. Also, in order to recover 5.3.0.10 client, you need to create 5.3.0.10 SRT. You cannot use 5.3.0.11 or 6.1.0.1 SRT to recover this client.

HP-UX boot server Each network segment with HP-UX clients must have an HP-UX boot server that can the clients. On an HP-UX boot server, the Ignite version of an SRT must match the Ignite version that is installed on the boot server. Linux boot server

Each network segment that has Linux clients must have a Linux boot server. Though in case of VLAN (Virtual Local Area Network) setup case, you can configure your switch settings to route network boot requests packets to server located at other VLAN than where client exists. This way a single Linux boot server can recover Linux clients belonging to different VLANs.

190

Managing BMR boot servers Boot server requirements

Table 9-1 Type of server

Boot server requirements (continued)

Requirements

Solaris boot server Each network segment with Solaris clients must have a Solaris BMR boot server that can the clients. However, you can use the following to minimize the effect of this requirement: ■

■

■

■ ■

When necessary, you can install BMR boot server software on a Solaris computer in the network segment. Then create an SRT after the client has failed and needs to be restored. The Solaris BMR boot server can be defined on a Solaris computer that has a physical IP presence on multiple networks. That is, you can use a single Solaris BMR boot server with multiple network interfaces for Solaris BMR clients on each network segment. Configure a relay boot server to allow Solaris computers on remote subnets to boot from a BMR boot server using a network gateway. Refer following technote that describes the procedure to setup relay boot server. http://www.symantec.com/business//index?page=content&id=TECH92038 You can also representative to get more information on this. The BMR boot server for Solaris10_x64 requires the following software installed: ■ TFTP Server ■

DH server

■

NFS Server

SRTs for carrying out a bare metal restore of a Solaris10_x64 client can only be created and hosted on a Solaris10_x64 Boot server. The OS and Kernel level should be greater than or the same of the client to be restored. If you want to use bmrsrt Media Creation to generate BMR-ISO SRTs, you must install the SUNWmkcd package on the boot server. ■

Windows boot server

Windows boot server requirements are as follows: ■

■

The network boot services on the boot server require a DH server somewhere on the network. The boot server must not run a PXE service or a TFTP service.

191

Chapter

10

Troubleshooting This chapter includes the following topics: ■

Problems booting from CD or DVD

■

Long restore times

■

Solaris media boot network parameters issue

■

How to recover client when BMR configuration is deleted accidentally

■

First boot after BMR restore fails on UNIX platforms

■

Client network based boot issue

■

backup failure while recovering Windows client

■

The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS

■

BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform

■

Troubleshooting issues regarding creation of virtual machine from client backup

Problems booting from CD or DVD AIX, Linux, and Solaris platforms use a common bootable CD or DVD format (ISO-9660). HP-UX uses Logical Interchange Format (LIF). If a system cannot boot from the CD or DVD, place it in a system that has a CD drive and examine the contents. (Either UNIX or Windows platforms can read ISO format.) Do the following: ■

If the CD or DVD contents consist of a single file, the CD or DVD was written as a data CD or DVD instead of an ISO-9660 CD or DVD image. Repeat the

Troubleshooting Long restore times

burning procedure but use the options that are required to burn an ISO image file. ■

If the CD or DVD is blank or unreadable, remove it from the drive and examine it closely to determine if it has been written to. Some CD or DVD burning software by default simulates the burning of a CD or DVD to test the capabilities of the CD or DVD burning hardware. It does not burn the CD or DVD until the test-only option is turned off. Repeat the burning procedure with the test-only option disabled.

■

If the boot was partially successful, or if it appears that some files are not present or some are corrupted, then one of the following occurred: ■

The burning process failed. A partially burned CD may be bootable but may not contain significant portions of its content. Lower the CD writing speed to allow a successful burn. Use the test after writing or use the option to that some CD writing software offers may help detect unsuccessful CD writes.

■

The file transfer from the BMR boot server to the computer with the CD writer failed. A common cause of corruption occurs when the file is transferred with FTP in ASCII transfer mode rather than binary mode.

■

If the CD boots successfully on another similar computer, the drive on the restore system may be damaged or dirty. Similarly, the CD itself may be easily damaged or made unreadable by surface contamination after writing. Examine the physical media and the environment in which it is read.

■

that you use the correct procedures to boot the client computer from CD.

■

Try booting the client from the installation media to ensure that the computer does not have a hardware problem when it boots from the CD.

Long restore times If a restore takes an unusually long time (for example 20 hours instead of 2 hours), the media speed between the adapter and the switch or hub where it connects may not match. For example, the media speed is set to 100 MB full duplex, but the restore slows down because the hub uses half duplex. Change the media speed to match the hub speed or switch speed, or change the hub-switch setting to match that of the client.

Solaris media boot network parameters issue In a media boot of a Solaris client, the Solaris code polls the local subnet. The code polls to determine if any computer on the local subnet has a record of the network

193

Troubleshooting How to recover client when BMR configuration is deleted accidentally

parameters for the booting client. If a JumpStart server has network parameters for the client in the /etc/ethers or /etc/bootparams file, those parameters are used for the boot process. The parameters are used even if they are different than the network parameters for the boot interface that are configured in BMR. If network parameters for the client exist, the restore may fail. To work around this issue, do one of the following: ■

Remove all references to the client system from the following files in all other computers in the subnet of the client:

/etc/ethers file /etc/bootparams ■

Unplug the booting client from the network until the media boot configures the network parameters for the restore.

How to recover client when BMR configuration is deleted accidentally If you delete a client and its current configuration, the next time the client is backed up, its configuration is saved. The client appears again in the Bare Metal Restore Clients view. If the client and configuration are deleted after a client fails (before it is restored), use the bmrs command to retrieve the client’s previous configuration. (You cannot perform a point in time restore because a deleted client does not appear in the Bare Metal Restore Clients view.) The following is the format of the bmrs command to use on the master server:

bmrs -resource config -operation retrieve -client clientName -destination newConfigname -enddate dateFormat -policy policyName

For more information about the bmrs command, see NetBackup Commands.

First boot after BMR restore fails on UNIX platforms After BMR restore, first boot may fail at Grub if root disk that is originally mirrored across two disks is changed to concatenate layout. In the system setup, root disk was mirrored across 2 disks say c3t0d0 and c4t0d0. In BIOS settings, c3t0d0 is the first disk in boot sequence. During DDR configuration, root disk is changed from

194

Troubleshooting Client network based boot issue

mirror to concatenate and mapped on c4t0d0. In BIOS, this disk is the second disk in boot sequence. So, after BMR restore, when system boots for the first time, as c3t0d0 is the first disk in boot sequence AND as "grub signature is still present on this disk as it was mirrored earlier", system tries to boot from the grub on c3t0d0 and then fails to boot as it does not get root file system and other bootable files which are now on c4t0d0. After BMR restore, during system boot, change the BIOS settings and choose the correct disk for system to boot.

Client network based boot issue Different operating systems use different network protocols for network boot. BMR leverages this protocol/s for starting network-based client recovery. For example, Windows, Linux and Solaris-x86 uses PXE based network boot which comprises DH, TFTP protocols. In case of, Windows: BMR has PXE and TFTP services running on the BMR boot server. DH can be any server in the same subnet. Linux: DH, TFTP services needs to be running on the boot server providing client network boot. (Note: Once services are deployed and running on boot server; BMR automatically /de- them to enable client network boot.) Sometimes it happens that in the same subnet where client recovery is being done has multiple network boot protocol servers running. One of them is correct PXE/DH/bootp servers which can assign IP_address to BMR client upon network boot. In such environment when client boots over network for BMR recovery, its network boot request gets broadcasted and it can be reached to unintended network boot server (PXE/DH/BOOTP) first. In such case it can return failure and BMR recovery may fail. So ensure that no other network boot services except the valid one providing BMR client network boot is running in the same subnet. Note that this is limitation with PXE, DH, BOOTP boot protocols themselves where first DH reply failure stops network boot process.

backup failure while recovering Windows client During the Bare Metal Restore (BMR) restore process, the restoring client will attempt to that it has a valid backup image to complete the restore. This validation process is failing. The probable causes are ■

The backup images have expired.

195

Troubleshooting backup failure while recovering Windows client

■

The client was backed up with the wrong policy type. As an example, a Windows client was backed up with a Unix Standard policy.

■

The backup image is missing critical files required for a proper system restore.

■

The client is not authorized to perform list/restore operations on the Master Server.

■

The restore configuration used for the restore has invalid/missing networking information.

■

The NetBackup Master Server is not able to perform proper reverse lookup of the client.

The best methodology for debugging this error message involves the following steps:

1

Perform a Prepare-to-restore operation from the NetBackup istration Console or via command line. If an error is encountered, then one of the below listed causes is at fault. Use normal NetBackup catalog query information to that a backup image is available using the correct policy type. Also, that the System State/ Shadow Copy Components were backed up properly. Also that the Bare Metal Restore software directory on the client was also backed up. If the Prepare To Restore operation is successful, the backup image information is valid. This in turn points to a problem in the BMR restore environment on the client or a network setting on the Master Server. Items that need to be verified as good in the restore configuration: ■

Check the 'Network Interfaces' section and ensure that the MAC address is correct and is the one being used during the restore. that a network cable is attached to correct port on both the client NIC and the switch.

■

Check the "Hosts" section and that valid entries (host name and ip-address) exist for the NBU Master Server and Media Server, as required.

■

Look in the bmrrst log on the Master Server to see the progress of the restore. To determine the root cause on the restoring client:

2

Cancel and exit from the restore wizard. This should place you in the main menu.

3

Move the mouse to a location in the upper left hand corner of the mains screen, near the gear shape icon. When the mouse pointer changes from an arrow to a hand, right click the mouse. This will open a command line window.

4

Change directory to X:\BMR\NBU\bin.

5

Execute the command, bpclimagelist -client $CLNT_NAME -T echo %ERRORLEVEL%

196

Troubleshooting The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS

The 'echo' command will display the return code of the command. The bpclimagelist command will fail to gather catalog backup image information for the following reasons: ■

Could not the Master Server (rc=25) This will happen if the client has the connected on the wrong interface port or has invalid/incomplete host name and ip-address information for the Master Server. The fact that the client could initially access the client configuration is not relevant. At the time of the failure, the client network interfaces were modified to match what was in the restore configuration specified for the restore. The values entered on the first input page have been modified to match the configuration values.

■

The Master Server could not respond back to the client port (rc=23) Possible causes are missing client reverse lookup information, either in the Server's DNS entries or hosts file or invalid routing back to the client

■

The Master Server does not see the restoring client as a valid client (rc=131, 133, 135) The ip-address used by the client resolved to a different name than in the configuration, or the client does not have permission to perform list/restore requests. One way to resolve this is to place a temporary entry in the 'hosts' file of the Master Server and Media Server. This entry must match the data information found'Network Interfaces' section of the restore configuration used for the restore. Also check the "Host Properties -> Master Server -> Client Attributes" of the istration Console to ensure that the client has permissions to perform list and restore operations

■

The NBU Master Server does not have a valid backup image (rc=227)

As a general, best practices rule, all BMR restores should make use of fixed ip-address information and not make use of DH or DNS during the restore. This can be reset after the BMR restore has completed, if so desired.

The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS During VM boot up time, post-, Windows pops up New Hardware Found and Configuration window. It prompts to configure device driver for SAS Controller Base System Device. This windows dialog gives two options for new device configuration, which are, Auto search and configure and Skip prompting for these devices. If you select any one of these options then Windows makes error in SAS controller VMWare PVSCI device driver configuration. Due to this problem next boot may result in BSOD.

197

Troubleshooting BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform

Do not take any action for the New hardware configuration dialog. Close this dialog window by using the Window cross button. You can ignore this dialog. This process may need to be done every time during VM boot up.

BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform This issue shows job failure with error code 12. This means that the Virtual Instance Converter or NetBackup recovery host fails to mount file systems on the created VM. Restart NetBackup recovery host so that VMWare mounter service gets ed correctly and then get started. It is always recommended to reboot NB Recovery host once upon NB Client installation.

Troubleshooting issues regarding creation of virtual machine from client backup Following sections provide details about the troubleshooting steps that you might use while using the feature Direct Virtual Machine creation from client backup.

Client name is not visible under virtual machine conversion clients list To debug the cause, follow these steps:

1

Check whether the client BMR backup is successful. See “Pre-requisites to create VM creation from backup ” on page 213.

2

Refer bmrd and bmrsavcfg logs to get more details about the failure.

3

If BMR backup is successful, check whether the client hostname is enlisted under the tab Bare Metal Restore Clients. If the client hostname is enlisted under Bare Metal Clients list, but not under VM conversion Clients list, refer the matrix to validate whether the client meets the specified criteria. Refer Table 10-1 for logs location.

Failure during submitting the job of virtual machine creation To find the reason for failure of job of virtual machine creation, follow these steps: ■

On UI wizard window, if the intended Netbackup Recovery Host (Virtual Instance Convertor) is not visible under Recovery Host drop-down list, make sure that

198

Troubleshooting Troubleshooting issues regarding creation of virtual machine from client backup

the Virtual Instance Convertor (VIC) is ed with the Netbackup master server. See “Pre-requisites to create VM creation from backup ” on page 213. ■

On UI wizard window, if you are not able to view the intended Hypervisor (vCenter or ESX) Server, follow these steps: ■

If your intended server is vCenter server or a standalone ESX server, make sure that it is ed with the master server. See “Pre-requisites to create VM creation from backup ” on page 213.

■

If Hypervisor is already ed, validate its connectivity with VIC as follows: ■

Open the target Hypervisor entry under the node Media and Device Management > Credentials > Virtual Machine Servers.

■

Select the intended recovery host under the tab For Backup Host.

■

Click OK.

Completing the process will validate the connectivity of Hypervisor server through the selected Netbackup recovery host. ■

If you are not able to view the datastores or resource pool/vApp or folder of hypervisor, check the connectivity of the Hypervisor as mentioned earlier in this section. If connectivity exists, but you are still not able to get the entries, refer the bpVMutil and bpVMreq logs with verbose level 6. Refer Table 10-1 for logs location.

Job of creating virtual machine failed To refer the error codes, See “Monitoring VM Creation jobs” on page 233. Check the bmrb2v, bmrb2vrst and bmrd logs with verbose level 6. Refer Table 10-1 for logs location. Table 10-1 Component

Log directory

Resides on

bpVMutil

install_path\NetBackup\logs\bpVMutil Virtual Instance Convertor Recovery Host

bpVMreq

install_path\NetBackup\logs\bpVMreq Master server from where conversion job is submitted.

bmrb2v

install_path\NetBackup\logs\bmrb2v Master server from where conversion job is submitted.

bmrb2vrst

install_path\NetBackup\logs\bmrb2vrst Virtual Instance Convertor Recovery Host

199

Troubleshooting Troubleshooting issues regarding creation of virtual machine from client backup

Table 10-1

(continued)

Component

Log directory

Resides on

bmrd

install_path\NetBackup\logs\bmrd Master server from where conversion job is submitted.

bmrsavcfg

install_path\NetBackup\logs\bmrsavcfg Client whose BMR backup is taken.

200

Chapter

11

Restoring Windows using legacy methods This chapter includes the following topics: ■

About legacy restores on Windows

■

Changes in the Legacy Restore function in BMR 7.0.1 and later versions

■

Creating a legacy shared resource tree

■

Creating CD boot media for a Windows client

■

About restoring a system with legacy procedures

About legacy restores on Windows This section provides details about the Legacy Restore process in NetBackup Bare Metal Restore. Note: NetBackup Bare Metal Restore 6.5 introduced a Fast Restore process for Windows systems. This new simplified and faster process covers most system restores. Legacy restore is typically preferred when the client to be restored is using Veritas Storage Foundation for Windows (SFW). Installation, deployment, and backup operation remain unchanged for systems requiring the legacy restore procedure. The legacy process differs from normal operation in the following ways: ■

A different SRT type See “Creating a legacy shared resource tree” on page 203.

Restoring Windows using legacy methods Changes in the Legacy Restore function in BMR 7.0.1 and later versions

■

A different type of boot media See “Creating CD boot media for a Windows client” on page 207.

■

Completely different approach to the restore process

During the legacy restore process, the boot media boots into Windows PE and performs an automated installation of Windows onto the hard drive. This new temporary installation of Windows is automatically booted into and the recovery process begins. From initial boot of the boot media to final reboot, the legacy restore procedure requires between five and eight system reboots.

Changes in the Legacy Restore function in BMR 7.0.1 and later versions In BMR 7.0.1 and later versions, the Legacy Restore function is modified with the following changes: ■

PC-DOS is no longer required to run a Legacy Restore. In BMR 7.0.1 and later versions, the legacy restore function boots from a Windows PE boot image. This change in the boot process of the legacy restore option reduces maintenance and overheads. BMR 7.0.1 and later versions, you do not need to do the following tasks: ■

and store DOS extensions.

■

Maintain the floppy disks, which are now outdated as media.

■

and maintain DOS-compatible drivers.

■

Maintain Floppy Disk Drives (FDDs) for BMR purpose.

■

As a result of PC-DOS elimination, you do not need to create boot floppy. Therefore the Legacy Boot Floppy Wizard link on the Boot Server Assistant screen is removed.

■

PC-DOS is replaced with Windows PE, therefore the legacy restore can boot with the PXE-based network option.

■

Unlike PC-DOS, Windows PE does not require a 16-bit Windows Installer binary. Therefore, BMR 7.0.1 and later versions provide the legacy restore also for the 64-bit editions of Windows.

■

PC-DOS-based legacy restore requires approximately eight reboots during the restore. With Windows PE-based legacy restore, the number of reboots is reduced to approximately five.

202

Restoring Windows using legacy methods Creating a legacy shared resource tree

Note: With Windows PE in place of PC-DOS, the legacy restore requires an additional free space of 2 GB to 4 GB in the system’s boot partition. The boot partition is the one that contains the operating system.

Creating a legacy shared resource tree Before a system can be restored with the legacy restore procedures, you must create a legacy SRT.

203


To create a legacy shared resource tree

1

From the Start menu on the Windows BMR boot server which hosts the SRT, select Programs > Symantec NetBackup > Bare Metal Restore Boot Server Assistant.

204


2


3

Select the option to create a shared resource tree.

205


4

Select the type of SRT as Legacy OS-based SRT.

5

Follow the prompts to create a shared resource tree. You must provide the following information: Name

The name of the SRT is also used for the directory that contains it. Only alphanumeric characters and the underscore (_) character are allowed

Description

Enter the description of the SRT. For example: Windows 2008 SRT

Architecture

Enter the architecture of the SRT (32bit / 64 bit)

Windows Install Image

Select the Windows OS image depending on the client to be restored. For example if you want to restore Windows 2008 client then specify the path to Windows 2008 Install Image. If restoring Windows 2003 Client, you will require Windows 2003 Legacy SRT and so provide the Windows 2003 install path. You can apply appropriate service pack later. See Add a Windows service pack to an SRT for details.

Windows License Key

Enter the license key required for the respective Windows install.

Location for the SRT

Enter the path where the SRT needs to be created. When you configure the 32-bit or 64-bit SRT for the first time, you need to specify the source location of SRD. For 32-bit SRT, specify the source location of srd.wim, which is as follows: \Addons\x86\BMRBS For 64-bit SRT, specify the source location of srd_x64.wim, which is as follows: \Addons\x64\BMRBS where is the root folder on the NetBackup Windows installation DVD.

Path to the NetBackup client software image

Enter the path of the BMR client software image.

206

Restoring Windows using legacy methods Creating CD boot media for a Windows client

If the SRT is hosted by boot server that is also an Active Directory Server, set the following security parameters to allow the legacy restore method to share SRTs with restoring clients: ■

Microsoft network server: Digitally sign communications (always) - Set to Disabled

■

Microsoft network server: Digitally sign communications (if client agrees) - Set to Enabled

Creating CD boot media for a Windows client Before you begin a restoration of a Windows system using the legacy procedures, you must first create a boot CD. The boot media automatically installs Windows from the SRT onto the hard drive of the system. The boot CDs access a copy of the CD that is copied to the CD itself. To create a media type, a legacy Windows SRT must already exist. Note: In BMR 7.0.1 and later versions, floppy-based restore is not ed on Windows platform. Before creating a bootable CD, that you have done the following: ■

You have created a legacy SRT that matches the OS version to be restored. If you restore a Windows 2003 Server, you need a Windows 2003 Legacy SRT. To , navigate to the Bare Metal Restore Management > Resources > Shared Resource Trees tab on the NetBackup istration Console. Legacy SRTs are flagged (Legacy) in the Name Column. Note: BMR 7.0.1 also s Windows 2008 legacy restore.

■

You have done a Prepare-To-Restore for the system to be restored. A legacy boot CD is customized for a specific BMR Client system to allow full automation. See “Preparing a client for restore” on page 98.

To create CD boot media for a Windows client

1

On the Windows BMR boot server, select Programs > Symantec NetBackup > Bare Metal Restore - Boot Server Assistant from the Start menu. The Bare Metal Restore - Boot Server Assistant screen appears.

2


3

Click Next on the Welcome .

207

Restoring Windows using legacy methods About restoring a system with legacy procedures

4

Select the Create a Bootable CD/DVD from a Shared Resource Tree option and click Next.

5

Select an SRT that is marked (Legacy).

6

Select the Client and Configuration to be restored.

7

Follow the prompts to create the boot media.

About restoring a system with legacy procedures Before you start a restore, make sure that you have done a prepare-to-restore, created an SRT, and created the boot media.

About restoring to dissimilar disks for Windows clients To restore a system whose disks are different, you may edit a configuration on the server first, which may cause a fully automated restoration. Or, you may start a restore and allow BMR to detect the different disks. If the new disks do not the original disk layout, BMR automatically launches the Dissimilar Restore Mapping utility during the restore process. For procedures to edit a configuration before starting a restore, see Modifying a configuration.

Loading only the boot partition driver during the boot phase Windows 2003 systems often use more than one mass storage device (MSD) driver. However, only one of them is associated with the boot partition of the drive where Windows is installed. By default, BMR loads all MSD drivers during the boot phase of the restore. You can edit the configuration so that only the driver that is associated with the boot partition is loaded. Do so if loading all MSD drivers interferes with the boot process of the restore. The system drive is always mapped and cannot be moved. However, you can resize it if you map disks before the restore. To load only the boot partition driver during the boot phase

1

In the Device & Drivers dialog box, select the correct driver from the bottom box, and click Change.

2

Check that the box labeled Bootable driver to be used during text mode portion of the installation.

3

Click OK.

208

Chapter

12

Creating virtual machine from client backup This chapter includes the following topics: ■

About creating virtual machine from backup

■

BMR physical to virtual machine creation benefits and use cases

■

Deployment diagram for virtual machine creation

■

Client-VM conversion process flow

■

Pre-requisites to create VM creation from backup

■

Virtual machine creation from backup

■

Virtual Machine Creation CLIs

About creating virtual machine from backup NetBackup BMR s direct virtual machine (VM) creation (Physical to Virtual) from FULL, SYNTHETIC, INCREMENTAL, and PIT (point-in-time) backups. This VM creation does not require BMR Boot server and Shared Resource Tree setup. For more information on platform matrix, refer appendix section to See “BMR Direct VM conversion matrix” on page 246. This feature s easy wizard-based or single CLI-based disaster recovery (DR) to virtual machine. VM creation is even possible at DR domain using NetBackup Auto Image Replication (AIR) . The feature aids a non-technical person to perform server level DR as the need not create virtual machine layout or do dissimilar system recovery using BMR method. Run physical to virtual machine creation wizard or single command line to find the created client virtual machine and to boot it automatically.

Creating virtual machine from client backup BMR physical to virtual machine creation benefits and use cases

Note: For information on matrix See “BMR Direct VM conversion matrix” on page 246. Currently, the deployment on Windows client having SFW-enabled or having EFI or GPT partitioning cannot be converted to VM using this client to VM conversion utility.

BMR physical to virtual machine creation benefits and use cases Client to VM creation process provides following major benefits and use-cases. ■

Can be used as instant temporary DR mechanism.

■

Lowers OPEX by leveraging virtual machines for recovery.

■

Provides quick recovery of primary domain clients at DR domain by enabling NetBackup Auto Image Replication (AIR). Refer NetBackup 's Guides for more details on enabling Auto Image Replication.

■

Reduces Recovery Time Objective (RTO) with easy-to-use VM conversion wizard as well as not requiring any system recovery pre-requisites preparation.

■

Can be used to do compliance and fire-drill testing.

■

s create VM from FULL, INCREMENTAL, and synthetic backup image.

■

s create VM from Point-In-Time backup image.

■

Provides VM creation flexibility by providing different preferences like: ■

System-only restore: Provides option to create VM with OS volumes only.

■

Overwrite existing VM: Any existing VM with the same name can be automatically overwritten.

■

Auto boot VM after creation: When selected, VM creation process automatically boots VM, post creation.

■

Flexibility to map individual virtual disk to required virtualization storage entity.

■

Network stripping: Option to remove original client network interfaces and IP configuration in VM.

■

Provides option to create VM with only selected disks.

■

Provides a single command-line facility to trigger client VM creation.

Note: The incremental data restore is not currently ed, however, fresh VM creation from an incremental backup is possible.

210

Creating virtual machine from client backup Deployment diagram for virtual machine creation

Deployment diagram for virtual machine creation Following is a general deployment diagram for BMR client to virtual machine conversion.

Master server: NetBackup master server that takes BMR enabled backup of client. Note: Refer following sections and for more details on configuring BMR master server and enabling BMR client protection. See “Configuring BMR Master Server” on page 20. See “Configuring policies to back up BMR clients” on page 28. Media server: NetBackup media server which contains client's BMR enabled backup image on disk-based storage unit. Virtual Instance Convertor (VIC): This host is NetBackup recovery host which has configured NetBackup client. BMR client to VM conversion requires VIC operating system, belonging to same family as client’s operating system, which is required to be converted to virtual machine. For example, Windows 2008 based VIC can create VMs of Windows 2003, 2008, 2008 R2, and Windows 7 based clients.

211

Creating virtual machine from client backup Client-VM conversion process flow

Hypervisor Server: The destination virtualization server where client VM is created. You need to select the intended Hypervisor server while running virtual machine conversion wizard. Note: You do not need extra hardware for VIC host. VIC host can be optionally configured over a virtual machine. VIC can also be configured over master or media server if server OS is of same OS family as that of client being converted. Though it is not recommended to set up VIC on NetBackup master or media server as VM creation process consumes resources and it can slow down NetBackup server Performance. For details on currently ed Hypervisor servers for virtual machine conversion operation See “BMR for virtual environment” on page 245.

Client-VM conversion process flow Following diagram shows the process flow of client to VM conversion process at high level.

212

Creating virtual machine from client backup Pre-requisites to create VM creation from backup

Pre-requisites to create VM creation from backup Following are the prerequisites to create virtual machine from backups. ■

Configured BMR Master Server First, you need to enable the BMR server on your NetBackup master server. For details on how to enable BMR server, See “Configuring BMR Master Server” on page 20.

■

Client's BMR enabled backup Configure NetBackup policy for BMR. Enable check box for BMR for the Collect disaster recovery information option in backup policy attributes. For details, See “Configuring policies to back up BMR clients” on page 28.

■

BMR backup policy requires at least OS volumes added as part of backup selection. In case of Windows, Boot, System Volume, System State needs to be added under backup selection list. Note: For convenience, in the backup selection, ALL_LOCAL_DRIVES option is made available by default that considers all the client volumes during backup. After enabling BMR in backup policy, take an initial FULL backup.

■

Hypervisor-specific tools ISO file VM creation process requires hypervisor-specific tools ISO file so that during VM creation it configures required device drivers into VM system. Usually Hypervisor vendor provides their tools ISO file on their website and hypervisor server. For example, in case of VMWare ESX server 5.0, the associated tools ISO can be located on your ESX server as well as can be ed from VMWare website. See following examples given. Tools ISO path on ESX server: /vmimages/tools-isoimages/windows.iso Website location: http://packages.vmware.com/tools/esx/5.0latest/windows/x86_64/index.html It is MUST to have this tools ISO file on VIC host. Virtual machine creation wizard prompts for full directory path of this ISO available on VIC.

■

Hypervisor server name registration in NetBackup You need to your Hypervisor server with NetBackup where VM needs to be created. This registration requires Hypervisor server credentials. Refer following sample GUI of VMWare vCenter server registration.

213

Creating virtual machine from client backup Pre-requisites to create VM creation from backup

■

VIC (NetBackup recovery host) name registration in NetBackup For VMWare type Hypervisor, Virtual Image Converter host name needs to be ed in NetBackup master server property named “VMWare Access Host”. Refer following sample GUI of VMWare Access Host registration.

214

Creating virtual machine from client backup Virtual machine creation from backup

Virtual machine creation from backup Following sections details about client’s VM creation process from backup.

Virtual Machine Conversion Clients In NetBackup istration Console, in tab Bare Metal Restore Management > VM Conversion Clients enlists all the clients available to be converted to virtual machines (VMs). You can see various details of the clients like operating system type, U, RAM, Hosts, and network-related information.

215


Converting client backup to VM You can convert BMR-enabled backups to virtual machine using Virtual Machine Conversion wizard.

216


To initiate operations related to conversion of client backups to virtual machines, perform following actions:

1

Navigate to VM Conversion Clients on NetBackup console.

2

Right-click on intended client configuration to get a pop-up menu with conversion operation options.

Optionally, you can create a custom client configuration or PIT (Point-In-Time) configuration for VM creation. In such case, use New Client Configuration option to either create a PIT configuration or copy the existing client configuration. For details on how to change client configuration, See “Creating custom configurations” on page 225.

3

On conversion operations pop-up menu, click Convert to Virtual Machine to start conversion process wizard. This wizard prompts you the details about destination Hypervisor server parameters and conversion options.

217


VMWare based VM Conversion Wizard Flow The wizard first page prompts for information about VMWare server parameters, VIC host details etc. Table 12-1

Conversion to Virtual Machine

Parameter

Parameter Details

NetBackup recovery host:

This is NetBackup client host-name which to be used as VIC (Virtual Instance Converter). or recovery host. This host prepares VM on intended VMWare server.

Note: VIC OS has a rule that if client that is being converted to VM has Windows-based family, then you Must set Windows-based VIC . VIC can be set on physical or virtual machine if this OS rule is satisfied. However, it is not recommended to set up VIC on NetBackup master or media server as Virtual Machine creation process consumes resources and it can slow down NetBackup server Performance. VMWare Tools ISO files:

Enter the absolute path where the VMWare .iso file is located on VIC host that is entered earlier in this dialog box. For details See “Pre-requisites to create VM creation from backup ” on page 213.

vCenter server:

Select vCenter server name if applicable.

ESX Server:

Select or Enter ESX server name.

VMWare Folder:

The folder where the destination virtual machine to be created.

Display Name:

Enter a display name for the virtual machine to be created.

Resource Pool:

Select the intended resource pool name from the drop-down menu.

Datastore/Datastore Cluster:

These are storages connected to ESX server. If you select option Use the same datastore/datastore cluster for all VMDKs then all V-disks belonging to the VM will be created on the same datastore or datastore cluster. If this option is not selected, then later screen of this wizard will provide option to map individual V-disk to the datastore.

Refer following sample dialog snapshot showing earlier described parameters populated. Refer following screenshot for more details.

218


Virtual Machine Options The next wizard page prompts you to provide VM conversion options and allows selection of virtual disk types. Following table enlists all the required options related to VM and disk types. Table 12-2

Virtual Machine Options

Virtual Machine Options

219


Table 12-2

Virtual Machine Options (continued)

Over-write existing VM:

Select this option to enable deletion of existing virtual machine in case of duplication of display name. If a virtual machine with the same display name exists at the destination, that virtual machine will be automatically deleted before the restore begins; otherwise, the restore fails. If you do not select this option, you need to manually delete the duplicate VM name.

Remove network interfaces:

If this option is selected then original client network interfaces will not be configured on the destination. If this option is not selected, then same number of network interfaces and their details existing on source client configuration will be configured on the VM.

Power-on virtual machine after recovery:

Select this option to have the recovered virtual machine automatically turned on when the recovery is complete.

Restore System disks and volumes only:

Select this option to restores the OS disk volumes only in case where only OS needs to be recovered on VM.

Virtual Disk Types Thin Provisioning:

Select this option to configure the restored virtual disks in thin format. Thin provisioning saves disk space through dynamic growth of the vmdk file. The vmdk files are no larger than the space that the data on the virtual machine requires. The virtual disks automatically increase in size as needed.

Thick Provisioning:

Select this option to configure the restored virtual disks in thick format. It creates virtual disk length that is equivalent to physical disk length on the VM. Creation of the virtual disks may take more time with this option.

Refer following sample snapshot showing VM options.

220


Virtual machine conversion storage destination VM Conversion storage destination wizard lists all the disks belonging to client being converted to virtual machine. It lets you select datastore to be mapped with the individual disks where recovery process creates equivalent VMDK file on the correspondent datastore. Note: In case you have checked the option Use the same datastore/datastore cluster for all VMDKs in the Conversion to VM wizard, then the storage destination is already selected. Refer following sample screenshot with destination details.

221


Network connection selections You can select VMWare network connection name in order to create VM Network interface belonging to virtual network. The wizard lists all the available network connections. Refer following sample screenshot showing network names to select from.

222


Virtual machine conversion summary The summary page displays all the details related to client conversion that are configured through VM Conversion wizard. Execute a pre-check to confirm that the environment details are intact. The validation tests show status as ed if all the environment configurations are intact. Click Convert to Virtual Machine to create tasks for VM creation process through NetBackup master server. Check the tasks listed in VM Conversion Tasks under Bare Metal Restore Management tab and refer task status and operation to know the progress status. Refer chapter Monitoring bare metal restore tasks for more details about tasks and status information. Refer following sample summary screen.

223


Virtual Machine Conversion Tasks On Virtual Machine Conversion wizard, when you click Convert to Virtual Machine it creates a task for virtual machine creation process. You can check the status of this task in Virtual Machine Conversion Tasks tab and can check tasks operation to know the progress status. Refer chapter Monitoring bare metal restore tasks for details about tasks and status information.

224


Restore Task Properties Restore Task Properties dialog summarizes all parameters for client-VM conversion viz. general configuration and recovery options. The summary also includes virtual machine conversion configurations such as VM name, vCenter server, VMWare Tools ISO file location, and datacenters for VMDKs. It also lists configured network parameters and restores disk types. Refer chapter Monitoring bare metal restore tasks for details about tasks and status information.

Creating custom configurations When creating new client configuration, you can either copy an existing client configuration or a Point-in-time (PIT) configuration policy to have PIT VM creation. Customized configuration creation is required for the following: ■

Create a copy configuration: You can copy existing client configuration for conversion customizing original configuration. You can customize client properties viz. RAM size, allocated U units, disks to be created on VM, and network parameters. This customization provision helps in some cases like you may not want to recover all original disks or volumes on VM. In this case, you can mark unwanted disks as restricted so as to avoid creating VM conversion process create corresponding virtual disk/s during VM creation. Note: Make sure that you are not restricting OS disk/s. Otherwise created VM will not boot.

■

Point-in-time (PIT) VM creation from PIT backup: You can retrieve PIT configuration for a backup image.

225


226

Creating virtual machine from client backup Virtual Machine Creation CLIs

Refer chapter Managing clients and configurations for more information.

Virtual Machine Creation CLIs You can use command line interface to perform various operations related to VM creation from client backup. ■

Submitting a job for VM creation from backup Submit a job for VM creation using command nbrestorevm from master server or any client with istrative privilege. In case you fire nbrestorevm without any parameter, following help is displayed. For VM restore: nbrestorevm -bmr {-vmw|-vmhv} -C vm_client [-S master_server] [-O] [-R rename_file (must be an absolute path)] [-L progress_log [-en]] [-k "keyword phrase"] [-disk_media_server media_server] [-s

227


mm/dd/yyyy [HH:MM:SS]] [-e mm/dd/yyyy [HH:MM:SS]] [-w [hh:mm:ss]] [-vmtm vm_transport_mode] [-vmserver vm_server] [-vmproxy vm_proxy] [-vmpo] [-vmtd] [-vmfd] [-vmbz] [-vmdrs] [-vmpdrs] [-vmvxd] [-vmkeephv] [-vmid] [-vmsn] [-vmrb] [-force] [-vcd] [-vcdred] [-vcdovw] [-vcdrte] [-vcdtemplate] [-vcdlfree] [-vcdremv] [-ir_activate] [-temp_location temp_location_for_writes] [[-ir_deactivate | -ir_reactivate | -ir_done] instant_recovery_identifier] [-ir_reactivate_all [-vmhost vm_host] [-media_server media_server_activate_vm]] [-ir_listvm]

For BMR VM Conversion: nbrestorevm -bmr {-vmw|-vmhv} -C vm_client [-S master_server] [-O] -vmserver vm_server -vmproxy vm_proxy -veconfig ve_config_file_Path (must be an absolute path) [-config bmr_config_name] [-vmpo] [-vmsn] [-systemOnly]

Where, -vmw : VMWare -C : Name of the client to be converted to VM -S : Name of the master server -O : Option to overwrite VM if already exists with the same name -vmserver : vCenter or ESX server name -vmproxy : Virtual Image Converter or NB-Proxy name -veconfig : File full path containing virtual environment details -vmpo : [optional] If provided VM will be automatically powered On Example: nbrestorevm -bmr -vmw -C d1950-17.punbmr.com -vmserver bmrrh10.vxindia.veritas.com -vmproxy ix3650-21.punbmr.com -veconfig C:\B2V\veconfig-vmw1.txt -config current -O -vmpo [Info] V-433-32 Successfully submitted job. For more details please see VM Conversion Tasks

Details for -veconfig file. For example, C:\B2V\veconfig.txt contains below information in parameter = value manner. esxhost="bmrvmw1.vxindia.veritas.com" name="Test_NBRestoreVM" network="VM Network" diskformat="ThinVdisk" toolsIsoPath="C:\B2V\windows_esx5.iso" datacenter="/TestFolderAboveDC/Public Datacenter" folder=[optional]"/TestFolderAboveDC/Public Datacenter/vm"

228


resourcepool= [optional]"/TestFolderAboveDC/Public Datacenter/host/bmrvmw1.vxindia.veritas.com/Resources" harddisk=0:"B2V_4TB" harddisk=1:"storage1 (2)" harddisk=2:"storage2 (1)" ■

Tracking VM creation jobs You can track submitted VM creation jobs using following CLIs. On master server, to list submitted jobs which are in running state, fire: bmrs -operation list -resource B2VrestoreTask

On master server, to list VM creation jobs history (successfully completed or failed), fire: bmrs -operation list -resource B2VrestoreTaskLog ■

Deleting VM creation related task logs On master server, to clean-up logs from the database, fire: bmrs -o delete -resource b2vrestoretasklog -id

You can get p2vRestoreTaskLogId by using command in the list operation for task log keyword. For more information, refer NetBackup Commands Reference Guide.

229

Chapter

13

Monitoring Bare Metal Restore Activity This chapter includes the following topics: ■

Monitoring BMR restore tasks

■

Monitoring backup jobs

■

Monitoring VM Creation jobs

■

BMR logs

Monitoring BMR restore tasks The Tasks window shows the status and the resource allocation for the prepare-to-restore and prepare-to-discover operations.

Monitoring Bare Metal Restore Activity Monitoring BMR restore tasks

To monitor BMR restore tasks

1

In the NetBackup istration Console, select Bare Metal Restore Management > Bare Metal Restore Tasks. Use the Refresh option to update the details pane with new information retrieved from the master server. If an item is highlighted, only that item is updated. Following screenshot shows a restore task created for client post PTR (prepare-to-restore operation). The task status indicates that the client is ready for BMR recovery.

2

To display details about a task, right-click a task in the Details pane and then select Properties. You also can select one of the following other options to manage tasks: Clean Up

The resources that are used by the task are unallocated, the State is set to Done, and Status is set to 150 (terminated by ). You can clean up the tasks that are in an Active or Waiting state.

Delete

You can delete the tasks that are in a Done state.

231

Monitoring Bare Metal Restore Activity Monitoring backup jobs

Monitoring backup jobs You can monitor the jobs that back up the protected clients by using the Jobs tab in the Activity Monitor of the NetBackup istration Console. You can see information about a job by double-clicking the job, which opens the Job Details dialog box. The tabs display job information, as follows: ■

The Job Overview tab contains general information about the job.

■

The Detailed Status tab contains detailed information about the job and about the agent that runs on the client. It collects the client configuration information and sends it to the BMR master server. On the protected systems that have uncomplicated configurations (one or a few disks), the agent only takes a few seconds. The more complex systems that have disk or volume groups may take a few minutes. Complex storage area network environments may take up to an hour.

If the Allow Multiple Data Stream attribute is enabled in the backup policy, NetBackup may divide backups for each client into multiple jobs. Each job backs up only a part of the backup selection list. The jobs are in separate data streams and can occur concurrently. For each client, only one of the jobs initiates the agent that collects the client bare metal recovery required configuration (normally, the job with the lowest job ID).

232

Monitoring Bare Metal Restore Activity Monitoring VM Creation jobs

Investigate nonzero status of a backup job and resolve problems so backups occur and the agent collects and sends the configuration to the master server. Note: In case BMR configuration backup job fails (normally, the job with the lowest job ID), the file system data backup completes successfully. In this case, after successful file system data backup, BMR configuration backup job is marked as Partially Completed highlighted in yellow.

Monitoring VM Creation jobs On Virtual Machine Conversion wizard execution, when you click Convert to Virtual Machine button, NetBackup creates a task for VM creation process. You can check the status, selected hypervisor environment details and VM conversion options under this task tab.

233

Monitoring Bare Metal Restore Activity Monitoring VM Creation jobs

To monitor VM conversion tasks, perform the following tasks:

1

In the NetBackup istration Console, navigate to Bare Metal Restore Management > VM Conversion Tasks.

2

Use the Refresh option to update the details pane with new information retrieved from the master server. Only the update item is highlighted. Following screenshot shows a VM conversion task created upon execution of VM conversion wizard.

3

To display details about a task, right-click a task in the Details pane and then select Properties. Note: You cannot cleanup or cancel submitted VM conversion task similar to BMR restore or discover tasks. You can see selected clients file system data recovery jobs under NetBackup Activity Monitor.

Following table shows different task status codes related to VM conversion, with description. Status Code

Description

0

VM conversion task completed successfully.

3

Resource allocation failed.

4

Uned client configuration for VM creation. Some unidentified exception has been thrown during VM creation process execution.

6

Failure while loading client configuration.

7

Failure while creating VM node for the selected client configuration.

8

Failure while preparing for client physical machine object.

9

Failure while constructing VM conversion metadata.

12

Failure while mounting file systems on the created VM.

13

Failure while loading windows registry on the created VM.

15

Failure while configuring network settings.

16

Failure while auto-rebooting created VM. Sometimes if the hypervisor server is fully loaded then this task may fail. You can try booting VM manually in such case.

17

Failure while handling device driver configuration.

234

Monitoring Bare Metal Restore Activity BMR logs

Status Code

Description

18

Failure while handling MSD device driver configuration.

19

An unidentified exception has been thrown during VM conversion process execution

BMR logs You can monitor BMR activity by viewing the messages that are generated by BMR. BMR activity log files are stored in the following directories on the master server: ■

/usr/openv/logs directory (UNIX and Linux)

■

install_path\NetBackup\logs folder (Windows)

BMR uses a standardized naming format for log files. The following is an example log file name: 51216-119-3892578826-050225-0000000000.log

The following are the components of this example log file name: ■

51216 is the product ID for NetBackup.

■

119 is the originator ID of the process that wrote the log (bmrd or bmrbd, the Bare Metal Restore master or boot server service).

■

3892578826 is a decimal ID for the host that created this log.

■

050225 is the date in YYMMDD format.

■

0000000000 is the rotation number indicating the instance of this log file. If the file reaches maximum size and a new log file is created for this originator, the file rotation number increases by 1.

The following types of messages can appear in unified logging files: ■

Application log messages. These include informational, warning, and error messages.

■

Diagnostic log messages. The amount of information that is logged depends on the logging level.

■

Debug log messages. These are primarily for Symantec and engineering. The amount of debug information that is logged depends on the logging level that is specified for the NetBackup master server.

235


BMR logging originator IDs Following are the originator IDs for the BMR processes that perform logging: 119

bmrd and bmrbd. Bare Metal Restore master and boot server services. The bmrbd boot server process runs on a BMR boot server.

121

bmrsavecfg. Bare Metal Restore the agent that runs on client systems, collects the client configuration, and saves the client configuration to the master server.

122

bmrc. Bare Metal Restore the utility that clients use to communicate with the BMR master server during a restore. Runs on the restoring client.

123

bmrs. The Bare Metal Restore command line interface for the various activities that are performed by the GUIs.

125

bmrsrt. Bare Metal Restore utility that creates and manages shared resource trees and creates bootable CD media or DVD media for restores. Runs on a BMR boot server.

126

bmrprep. Bare Metal Restore utility that prepares BMR for a client restore or discovery. Runs on the master server.

127

bmrsetupmaster and bmrsetupboot. Bare Metal Restore master server and boot server configuration utilities.

128

Miscellaneous programs and Bare Metal Restore libraries.

129

bmrconfig. Bare Metal Restore utility that modifies a client's configuration.

130

bmrcreatepkg.exe. Bare Metal Restore utility to add Windows drivers, service packs, and hotfixes to the BMR master server so they can be used in a restore. Runs on Windows boot servers.

131

bmrrst.exe and bmrmap.exe (Windows systems only). Utilities that restore Windows Bare Metal Restore clients. Run on the restoring client.

142

bmrep. A utility that manages Bare Metal Restore the external procedures that are used during restores. Runs on the master server.

152

bmrovr. A utility that manages custom override functions for Bare Metal Restore.

248

bmrlauncher. A utility that prompts for IP information in the new Windows Fast Restore environment.

433

bmrb2v: This is BMR backup to VM creation command-line interface.

434

bmrb2vrst. A utility that does VM creation on VIC (NetBackup recovery) host.

236


Commands to manage unified logging and log files The amount of information that is collected and the retention period for that information is configured on the NetBackup master server in the Host Properties Logging properties and Clean-up properties. See the NetBackup ’s Guide for UNIX, Windows and Linux, Volume I. For information ing and managing logs, see the NetBackup Troubleshooting Guide. BMR activity log files are in a special format that requires you to use commands for viewing and managing. The following commands manage unified logging and log files: vxlogview

Use this command to view the logs that are created by unified logging.

vxlogmgr

Use this command to manage unified logging files (for example, to move or delete log files).

vxlogcfg

Use this command to configure logging settings.

These commands are located in the following directories: ■

/usr/openv/NetBackup/bin directory (UNIX)

■

install_path\NetBackup\bin folder (Windows)

BMR restore logs The BMR restore process writes messages to restore logs on the master server if logging option is selected during Prepare-To-Restore step. Following is the location and naming convention for the log files: /usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX) install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)

On UNIX and Linux systems, the messages include external procedure begin and end messages (begin and end logging is not performed by the BMR restore process running on Windows systems). Unlike BMR activity logs, the restore log files are text files.

237

Appendix

A

NetBackup BMR related appendices This appendix includes the following topics: ■

Network services configurations on BMR boot Server

■

About the for Linux native multipath in BMR

■

BMR for multi-pathing environment

■

BMR multipath matrix

■

BMR for virtual environment

■

BMR Direct VM conversion matrix

■

About ZFS storage pool

■

Solaris zone recovery

■

BMR client recovery to other NetBackup Domain using Auto Image Replication

Network services configurations on BMR boot Server For Network boot based recovery, BMR leverages OS specific NW boot protocols to start recovery. Different NW configurations like PXE, bootp, DH, or TFTP, would need to be done for network boot recovery depending on the type of OS. Following sections provide the details for specific platforms.

NetBackup BMR related appendices Network services configurations on BMR boot Server

Common Unix network configuration The TFTP service must be available. On some of the operating systems, this service is commented out of the /etc/inetd.conf file. They must be uncommented and inetd needs to be refreshed for the BMR boot server to function. The NFS service must be available and nfsd daemon must be running. /etc/exports contain the filesystem entries which are exposed to other clients over NFS protocol. Make a note that no /etc/exports configuration is required to be done manually. BMR handles this configuration automatically.

Redhat Enterprise Linux network configuration The following system prerequisites apply only to Red Hat Linux systems: ■

■

Install the following RPM packages (unless already installed): ■

compat-libstdc++

■

tftp-server

■

dh

Enable the tftp service as follows: ■

Edit the /etc/xinetd.d/tftp file and change disable = yes to disable = no.

■

Start the service by running the following command: /etc/init.d/xinetd restart

■

Create a /etc/dhd.conf file and configure it to define the networks it serves. You do not have to define host information; hosts are added and removed as needed by the BMR software. The following is an example configuration: log-facility local7; ddns-update-style none; ignore unknown-clients; subnet 10.10.5.0 netmask 255.255.255.0 { default-lease-time 600; max-lease-time 7200; option domain-name "example.com"; option broadcast-address 10.10.5.255; option domain-name-servers 10.10.1.4,10.88.24.5; option routers 10.10.5.1; }

To the /etc/dhd.conf file syntax, restart the daemon and ensure that it starts successfully by running the following command:

239


/etc/init.d/dhd restart

SUSE Linux Network configuration The following system prerequisites apply only to SUSE Linux systems: ■

■

Install the following RPM packages (unless they are installed already): ■

nfs-utils

■

dh-base

■

dh-server

■

inetd

■

tftp

Enable the tftp service by doing the following: ■

Edit the /etc/inetd.conf file and uncomment the tftp line.

■

Start the service by running the following command: /etc/init.d/inetd restart

■

Modify the /etc/dhd.conf file to define the networks it serves. You do not have to define host information; hosts are added and removed as needed by the Bare Metal Restore software. The following is an example configuration: log-facility local7; ddns-update-style none; ignore unknown-clients; subnet 10.10.5.0 netmask 255.255.255.0 { default-lease-time 600; max-lease-time 7200; option domain-name "example.com"; option broadcast-address 10.10.5.255; option domain-name-servers 10.10.1.4,10.88.24.5; option routers 10.10.5.1; }

To the /etc/dhd.conffile syntax, restart the daemon and ensure that it starts successfully by running: /etc/init.d/dhd restart

240


Note: DH server needs to be configured on Linux BMR boot server. Any existing DH server in the network cannot be used for Linux BMR network-based boot recovery. It is recommended to shut down any other DH server while Linux client is network booting over BMR boot server. In case client DH boot requests goes to the other DH server then network boot recovery fails. This is not a BMR limitation and instead the way this boot protocol works.

Solaris Network configuration The network configuration boot strategy that is used in Oracle Solaris comprises TFTP, NFS and BOOTP OR Dynamic Host Configuration Protocol (DH) NW services. TFTP and NFS services configuration is same as explained in earlier section. See “Common Unix network configuration” on page 239..

Network boot service configuration for Solaris version 10 No specific DH configuration is required on Solaris-10 SPARC architecture as BMR internally handles the required network configurations on boot server while preparing the client for restore. Solaris 10 x64 architecture requires DH and TFTP services configuration to be done on the boot server manually. To configure DH services, perform following steps: ■

Run dhconfig command to initialize dh: dhconfig -D -r SUNWfiles -p /var/dh

■

Add network table entry. pnt -C E.g. : pnt –C 10.209.4.0

■

Configure subnet/route details. dht -A -m -d < ':option=value:option=value:option=value:'>

Example: dht -A -m 10.209.4.0 -d ':Subnet=255.255.252.0'':Router=10.209.4.1'':DNSdmain=" .com"'':DNSserv=10.216.16.101 10.217.160.131:' ■

Enable DH server using following command. svc -v enable dh-server.

To configure TFTP services, perform following steps: ■

Create TFTP base directory. mkdir /tftpboot

241


■

If the TFTP entry is not present in file /etc/inetd.conf file, add the following line. tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

■

Import the configuration changes. /usr/sbin/inetconv

■

Restart TFTP. svcs network/tftp/udp6 svc restart network/tftp/udp6

Note: For Solaris, BMR does not Solaris WAN-based boot protocol. Though in case of cross subnet network-based boot recovery is intended then Relay Boot server can be used.

Network boot service configuration for Solaris version 11.0 and later Both x64 and SPARC architecture platforms require DH service configuration to be done on BMR boot server. A GUI-based utility, DH Manager is required to configure DH server on boot server. This utility is wizard-based guiding the required setup steps. Note: Do not use dhconfig command-line utility to setup DH server in case of Solaris 11.0 and later versions. IP lease time-line related issues have been observed with command-line usage.

HPUX and AIX NW configuration In addition to common network services configuration, enable BOOTP service for both HPUX and AIX platforms. Make sure TFTP, NFS and BOOTP services are running on your BMR boot server.

Windows Network configuration Windows BMR Boot server registration enables below three services. ■

BMRBD (BMR BOOT server) service

■

BMR TFTP Service

■

BMR PXE Service

BMR TFTP and PXE services are used in case of network-based boot recovery. Apart from these services, DH service is also required.

242

NetBackup BMR related appendices About the for Linux native multipath in BMR

DH service requirements: DH server can exist on the same Boot Server host or somewhere on the network. BMR PXE and TFTP service requirement and configuration: ■

Make sure that there is no other PXE server running in the same subnet while BMR NW boot is happening. This restriction is more due to the way this network protocol works. In case client NW boot request goes to un-intended PXE server then client NW boot fails. It does not re-direct the request to other valid PXE server in the network. Hence recommendation is to keep only valid BMR PXE service running while NW booting your client for BMR recovery.

■

Post BMR boot server registration, navigate to BMR PXE Configuration Wizard available on Windows boot server. This wizard can be located in Start > Programs > NetBackup. This wizard prompts for DH server location. Depending upon your DH server location (either same boot server machine or any other machine in the network), the wizard prompts to run netsh command-lines on your DH server.

■

Finish the wizard for successful PXE, TFTP and DH server configuration.

If the Windows boot server is to be installed on an Active Directory Server, let the legacy (DOS) restore method to share SRTs with restoring clients. Set the following security settings: Microsoft network server Digitally signed communications (always) – Disabled

Microsoft network server Digitally signed communications (if client agrees) -- Enabled

About the for Linux native multipath in BMR In the data storage domain, multipathing is the ability of a server to communicate with its mass storage devices using more than one physical path; through the buses, controllers, switches, and bridge devices connecting them. Multipathing protects against the failure of paths but not from the failure of a specific storage device. Another advantage of using multipath connectivity is the increased throughput by way of load balancing. NetBackup BMR 7.5 and earlier versions ed EMC Powerpath solution. However to cater the demand for native multipath which is a platform-independent technique, NetBackup BMR has introduced for native multipath for BMR versions 7.5 and later for the Linux platform. Once the System has configured the Linux native multipath on the client systems, no additional installation, un-installation, or configuration steps are

243

NetBackup BMR related appendices BMR for multi-pathing environment

required from the BMR side to enable the native multipath. The native multipathing ability is already integrated with BMR 7.5. For details about general BMR for multipath environment, See “BMR for multi-pathing environment” on page 244.

BMR for multi-pathing environment BMR has compliance for multi-pathing environments. What this means is, during client’s BMR backup which has BMR known multi-pathing environments setup; BMR automatically marks the multi-pathed disk/s restricted in that client’s captured BMR configuration. This restricts to use those disks during recovery. Though any file systems running over the multi-pathed disk/s can be recovered to alternate non-multipathed disk/s. For example, if client setup has EMC PowerPath enabled over SAN Luns then BMR backup will mark those SAN Luns as restricted. can recover file systems on top of them to either local disks or other SAN Luns not having multi-path enabled.

Why this restriction is? BMR recovery environment has no multi-path software setup and configured (like EMC PP). Hence BMR recovery environment cannot identify multi-path enabled disks on given target hardware. Currently ed Multi-pathing environments are: ■

EMC PowerPath on Unix/Linux/Windows ed platforms

■

Linux Native Multi-pathing ( started with NetBackup BMR 7.5 release)

The details of environment is as below.

What does it mean BMR ed multi-pathing environments? BMR s only above mentioned multi-pathing environment setups. If the client being BMR backed-up has any one of these multi-pathing enabled; then while capturing client’s BMR configuration, BMR resolves multi-paths to exact unique physical disk and shows it in BMR config. Also as mentioned above, BMR marks them restricted and avoids recovery time failure.

What if client has any different multi-pathing environments than above? BMR backup will fail to identify unique disk names and BMR captured configuration will show multiple-disk names as shown by multi-path software. Also it will not be able to mark the disks restricted automatically. Here you need to copy BMR configuration using GUI (Refer chapter Managing client configurations

244

NetBackup BMR related appendices BMR multipath matrix

from NetBackup BMR 's Guide)and identify MP disks and mark them restricted manually. If file systems on top of these MP disks need to be recovered then map them to other non-MP disks. If you ignore MP based file systems recovery and restore only operating system then post BMR recovery if the Multi-Pathed disks are attached to the target host then file systems on top of them may come online automatically. Refer tables Actions for nonsystem disks and Import Actions for more details. In case client setup has Operating System Volumes based on multi-pathing environment then BMR will not be able to recover this system.

BMR multipath matrix Following table describes platform matrix for BMR multipathing. Platform

EMC Power Path Version

Native Multipath

SF Version

Windows

EMower.5.5.SP1

N/A

SFW 5.1SP1 & SP2

HPUX

EMower.HPUX.5.1.SP2.GA N/A

SF 5.0 MP3

AIX

EMower.AIX.5.5.GA

SF 6.0, SF 6.0RP1

Solaris

EMower.SOLARIS.5.5 Not ed

SF 5.1

RHEL

EMower.LINUX.5.6.GA ed

Not ed

SUSE

EMower.SUSE_LINUX.5.5.GA ed

Not ed

OEL

EMower.LINUX.5.7.GA ed

Not ed

N/A

BMR for virtual environment Following table lists BMR Boot server and Client versions ed on virtualization technologies. Hypervisor Type and Version OS Version on Guest VM ESX 4.1

Windows, RHEL-Linux, SuSE-Linux

ESX 5.0

Windows, RHEL-Linux, SuSE-Linux, Solaris x64

ESX 5.1

Windows, RHEL-Linux, SuSE-Linux, Solaris x64

Xen 6.0


245

NetBackup BMR related appendices BMR Direct VM conversion matrix

Hypervisor Type and Version OS Version on Guest VM IBM VIO AIX 7.1

AIX 6.1 and 7.1 versions

Hyper-V


Note: Solaris Zones recovery is ed by protecting host operation system. Refer See “Solaris zone recovery ” on page 248. For information: Following OS recoveries on their ed virtual platforms have not been officially tested or ed but some of the customers have tried them successfully. ■

AIX recovery on LPAR

■

HPUX recovery of vPar, nPar

■

Solaris recovery on LDOM instance

BMR Direct VM conversion matrix Following table lists ed OS versions for clients whose backup image can be converted to virtual machine using direct virtual machine conversion feature of NetBackup BMR 7.6. Note: Currently, the direct conversion of backup image to virtual machine is not ed for UNIX/Linux clients. Hypervisor Type and Version Client OS Version VMware ESX/vCenter 4.1

Windows 2003, 2008, 2008R2 and Win7

VMware ESX/vCenter 5.0


VMware ESX/vCenter 5.1


About ZFS storage pool Zettabyte File System (ZFS) is a combined file system and logical volume manager, which is part of Solaris operating system. ZFS is available on both SPARC and x86-based systems. for ZFS is added in Solaris 10 6/06 (“U2”). When you install Solaris 11.0 ZFS is also installed and set as the default file system.

246

NetBackup BMR related appendices About ZFS storage pool

Starting with NetBackup 7.5, Bare Metal Restore can protect Solaris 10 Update 8 and later clients that are attached to ZFS storage pools. The ZFS in NetBackup 7.5 and later versions ensures that the Solaris clients with ZFS storage pools are protected. BMR 7.6 s backup and restore of Solaris 10 Update 8 and later clients with the following configurations: ■

ZFS Root Pool and Data Pools

■

ZFS storage pools on slice

■

ZFS file system with zones

■

ZFS with SAN boot

■

ZFS storage pools along with VxVM and SVM disk groups

Note: All above features are ed on Solaris SPARC and Solaris x86_64 architectures. BMR 7.6 does not Solaris clients with the following configurations: ■

UFS to ZFS migration

■

Different file system on ZFS volumes

To view the ZFS Manager elements and its parameters, do the following: ■

In the NetBackup istration Console, click Bare Metal Restore Management > Hosts > Bare Metal Restore Clients. Open the Change Configuration dialog box for the client for which you want to view all associated volumes.

Figure A-1 shows the ZFS Manager GUI screen.

247

NetBackup BMR related appendices Solaris zone recovery

Figure A-1

ZFS Manager UI

Solaris zone recovery When using BMR to back up and restore Solaris Zones, you need to address some unique considerations. Bare Metal Restore can restore a Solaris system running Zones. Although BMR cannot restore individual non-global zones, all non-global zones in a system are re-created as part of the global zone restoration. If global and non-global zones are based upon ZFS filesystems, then does not require to do the 'vfstab' configuration."

248


To restore all non-global zones in a dissimilar disk restoration scenario

1

Remap the file system that hosts the zone (also known as zone path) to restore the zone files. If a non-global zone imports slices from the global zone that are not remapped, BMR removes the slices from the zone configuration. If a non-global zone imports slices from the global zone that are remapped to different disks, BMR readjusts the zone configuration and any zone vfstab (ZONEPATH/root/etc/vfstab) entries to use the new device names. If a non-global zone imports systems from the global zone file that are not remapped, BMR removes any references to them in the zone configuration.

2

Test

You may have to re-create and restore all file systems imported or used by a non-global zone after BMR restoration. These file systems usually don't appear in the global zone vfstab (/etc/vfstab). BMR relies on entries in /etc/vfstab to document the file systems that are subject to restoration. Dynamically-created and mounted file systems that do not appear in /etc/vfstab (even if backed up by NBU) do not automatically restore. The easiest way to force BMR to restore such file systems is to add an entry to /etc/vfstab that documents the devices and mount points used, with the Mount at boot field set to No. Then, the dynamic file systems can continue to be used as before. BMR is aware of them, recreates them unless unmapped in DDR, and restores their contents if backed up by NBU. Zone features cause dynamically mounted file systems to appear, as follows: ■

FS entries that involve devices in the global zone.

■

Device entries imported from the global zone but mounted either by the /etc/vfstab of the non-global zone, or dynamically by the zone itself.

To automate BMR zone restoration, Add entries to the global zone /etc/vfstab that cause BMR to restore them (unless unmapped by DDR), as follows: ■

For FS entries, the global zone devices are used as special and raw values with a mount point that appears under the root of the non-global zone. The entry to add to the global zone's /etc/vfstab should use the global zone's device paths with the full path to the non-global zone mount point, including the zone path. For example, if the zone looks like:

zonepath=/export/zone1 fs: dir=/export

249


250

special=/dev/dsk/c0t9d0s6 raw=/dev/rdsk/c0t9d0s6 type=ufs

Then the global zone entry in /etc/vfstab should be as follows: /dev/dsk/c0t9d0s6 /dev/rdsk/c0t9d0s6 /export/zone1/root/export ufs - no ■

For device entries mounted by the non-global zone, the following issues must be dealt with when you configure for BMR restoration: ■

The dynamic mount that is used involves the imported device path under the zone path. For a device that is mounted by /etc/vfstab inside a non-global zone, there are one or more device entries in the zone, such as the following:

zonepath=/export/zone2 device: match=/dev/*dsk/c0t0d0s4

The devices that are listed are in the non-global zone's /etc/vfstab as follows: /dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /local ufs - yes -

This command causes the global zone to dynamically mount. /export/zone2/dev/dsk/c0t0d0s4 on mount point /export/zone2/root/local. However, to make BMR automatically recreate

the file system, you should add the documenting entry to the global zone /etc/vfstab instead as follows: /dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /export/zone2/root/local ufs - no -

(If you use the device paths relative to the zone path, BMR only recreates the mount point instead of restoring the whole file system.) ■

The device match should not use wildcards to allow BMR to edit if DDR is used. When the device specification involves a wildcard, if DDR mapping is done that affects the zone (for example, if you unmap or move a file system from one disk to another), BMR is not able to edit the entry. The affected zone's /etc/vfstab is edited, but the device match entries are edited only if the match does not include a wildcard. For example, change the following entry:

NetBackup BMR related appendices BMR client recovery to other NetBackup Domain using Auto Image Replication

match=/dev/*dsk/c0t0d0s4

The entry must use two device entries, as follows: match=/dev/dsk/c0t0d0s4 match=/dev/rdsk/c0t0d0s4

If the entries are changed as the example shows, BMR DDR correctly updates the zone definitions and vfstab file.

BMR client recovery to other NetBackup Domain using Auto Image Replication This appendix explains how BMR and Auto-Image-Replication (AIR) can be leveraged together to do bare metal recovery of primary domain clients onto other clients or disaster recovery domain. NetBackup AIR feature helps duplicating clients backup image onto defined destination or DR domain NetBackup setup. The feature performs fast backup import automatically providing primary data recovery readiness at DR site. Refer NetBackup 's Guide to know more about AIR and how to enable it. In NetBackup 7.5 release, BMR has been added to AIR ing primary domain side client’s bare metal recovery onto DR domain end. For this dual-domain dual-site protection requirement, you need to enable Bare Metal Restore option in Auto Image Replication enabled backup policy. When Auto Image Replication and BMR enabled backup image gets imported at DR domain; NetBackup server checks if the image being imported is BMR enabled. If NetBackup server finds the image is BMR enabled then it automatically imports client BMR configuration as well. You can see client’s bare metal restore configuration node appears under UI menu NetBackup istration Console > Bare Metal Restore Management > Hosts > Bare Metal Restore Clients. During BMR configuration import at DR site, BMR master server automatically tunes client configuration for DR site entities like NetBackup master and media server host name and their IP-addresses. It updates older domain entries with new server details so that BMR recovery environment can approach to DR domain NetBackup servers while recovering client’s data. Optionally, you can add or update required host entries manually by copying or editing client’s imported BMR configuration. To manually edit client configuration refer chapter Managing clients and configurations. Without any manual backup import or configuration change, client can be completely recovered at DR domain using BMR network or media based recovery procedure.

251

NetBackup BMR related appendices BMR client recovery to other NetBackup Domain using Auto Image Replication

You can also create client VM onto DR domain Virtual Environment Server using feature Direct VM creation from backup. Refer chapter Creating virtual machine from client backup. Note: It is recommended to list client short names in NetBackup backup policy at primary domain. If FQDN of DR domain is different than primary domain then client data recovery at DR domain may fail due to mismatch in client domain name. Primary domain Primary domain > backup selection must enlist minimum OS file systems where NetBackup client is installed. In case of Windows, system state should be listed as well. If these points are not listed, then BMR configuration import at DR site may fail. Refer chapter Protecting Clients for more details about defining BMR backup policy.

Note: Make sure BMR master server on DR domain is enabled; otherwise BMR configuration import at DR site fails.

252

Index

A Active Directory Windows 100 activity viewing BMR logs 235 add client resources 36 adding license key 166 adding new driver 155 adding to packages pool 155 AIX boot interface 174 external procedure environment variables 147 media boot 117 network boot 105

B backups back up the client 27 configuring policies to back up BMR clients 28 job status 232 monitoring 232 perform complete 30–31 save custom files 31 use the same client name in multiple policies 30 BMR 178 boot interface AIX 174 client 173 HP-UX 174 Linux 174 Solaris 174 specifying 174 UNIX and Linux 173 boot media creating for AIX 92 creating for UNIX and Linux 91 for HP-UX 93 for Linux 93 for Solaris 93 overview 89

boot server about 189 network segment 190 requirements 189 restoring 139 breaking a stale shared resource tree lock 88

C CD ISO format 90 writing 90 changing license key 166 client deleting 164 deleting accidentally 194 cluster environments 19 clusters and dissimilar disk restore 128 configuration changing 162 collecting and saving during backup 232 copying 158 creating restore 158 current 158 deleting 163 deleting accidentally 194 discovering 159 editing 162 modifying 162 modifying a restore 162 restore 158, 162 saved 158 Configuration Summary dialog 165 copying a client configuration 158 creating a restore configuration 158 creating boot media 37

D DDR seedissimilar disk restore 126 deleting a client 164

Index

dialog Configuration Summary 165 Drivers 166 Hosts 169 Network Interfaces 170 Network Routes 174 discovering a configuration 159 discovery boot 159 disk recovery behavior overview 101 overviewbsx0d 100 dissimilar disk restore and clusters 128 introduction 126 Linux notes 128 mapping before the restore 126 mapping during the restore 126 overview 126 SAN 149 UNIX notes 128 when to performing mapping 126 dissimilar system restore adding MSD drivers 133 adding NIC drivers 133 creating boot media 135 creating restore configuration 133 first logon 136 mapping disks 135 restoring the client 136 SAN 150 when to use 132 drivers bootable Windows 208 finding the correct 155 Drivers properties 166 dynamic disk promoting in Windows 184

E external procedures adding to database 141 client-specific names 141 data transfer 142 environment variables 146 AIX 147 HP-UX 148 Linux 146 Solaris 148 UNIX 146

external procedures (continued) environment variables (continued) Windows 148 error handling 145 exit codes 145 interaction with 143 logging 143 names 140 operating system specific names 141 operational states 144 points 140 running 142 using 139

H hosts adding to configuration 169 changing in configuration 169 removing from configuration 169 Hosts properties 169 hotfixes 155 HP-UX boot interface 174 external procedure environment variables 148 media boot 118 network boot 110

I identifying the systems to protect 19 importing SRT on UNIX and LINUX 84 SRT on Windows 84 installation BMR boot server in a UNIX cluster 23 boot server prerequisites for UNIX and Linux 22 Configuring BMR Master Server 20 Internetwork Packet Exchange 134 IPX 134

J job status 232

L license key adding 166 changing 166 Linux boot interface 174

254

Index

Linux (continued) boot server location 190 dissimilar disk restore notes 128 external procedure environment variable 146 installing device drivers in SRT 82 media boot 121 network boot 113 logging configuring and using 237 external procedures 143 log file location 235 log filenames defined 235 originator IDs 236 restore log locations 237 viewing logs 235 vxlogcfg command 237 vxlogmgr command 237 vxlogview command 237

M mapping disk groups 180 disk sets 180 disks 180 network interfaces in configuration 170 volume groups 180 volumes 180 mapping and unmapping volumes dissimilar disk restore mapping and unmapping volumes 180 mass storage device adding drivers to configuration 166 adding drivers to packages pool 155 bootable Windows drivers 208 finding correct drivers 155 media boot AIX 117 HP-UX 118 Linux 121 Solaris 122 Microsoft Active Directory 100 modifying a restore configuration 162 modifying client configuration 162 monitoring backups 232 multiple network interface (multihomed) 150

N native disk 178 native partition 178 network boot AIX 105 HP-UX 110 Linux 113 Solaris 114 Windows 115 network interface card adding driver to configuration 170 adding drivers to configuration 166 adding drivers to packages pool 155 finding correct drivers 155 Network Interfaces properties 170 network routes adding to configuration 174 configuring in configuration 174 removing from configuration 174 Network Routes properties 174

O one-button restore external procedures 139 originator IDs 236

P packages adding new driver 155 adding to packages pool 155 packages pool defined 154 pkgadd 82 point in time restore creating configuration for 124 introduction 123 overview 123 prepare to restore client 98 protection domain overview 13

R restore BMR boot servers 139 dissimilar system creating configuration for 133 log locations 237

255

Index

restore (continued) overview 95 point in time creating configuration for 124 overview 123 process overview 95 restore tasks monitoring 230 restoring to a dissimilar system 131 to a specific point in time 123 using media boot 116 using network boot 104 restrict a disk 184

S SAN coexistence 149 dissimilar disk restores 149 dissimilar system restores 150 149 save custom files 31 setup BMR boot server on UNIX or Linux 22 shared disks and dissimilar disk restore 128 shared resource tree breaking stale lock 88 creating AIX 63 HP-UX 66 introduction 40 Linux 62, 74 Solaris 70 UNIX 62 installing Linux device drivers 82 overview 38 repairing a damaged 88 states 88–89 using exclusively 87 Shared Resource Tree istration Wizard 42 Add a Package to an Existing Shared Resource Tree 49 Add a Service Pack to an existing Shared Resource Tree 49 Add a Symantec NetBackup Client Image to an Existing Shared Resource Tree 50 adding NetBackup Security Services to an existing Shared Resource Tree 50

Shared Resource Tree istration Wizard (continued) adding SFW Hot Fix to a Shared Resource Tree 53 adding SFW Maintenance Pack to a Shared Resource Tree 53 adding Windows Hot Fix to a Shared Resource Tree 54 copying an SRT 47 creating a bootable CD image for a legacy SRT 49 location of ISO image 49 selecting an SRT 49 creating a bootable CD image for fast restore 48 selecting an SRT 48 specifying a location for ISO image 48 creating a bootable DVD image for fast restore 48 deleting an SRT 48 Edit SRT 46 importing an SRT 47 Solaris boot interface 174 boot server requirements 191 external procedure environment variables 148 media boot 122 network boot 114 pkgadd 82 unused VxVM disks marked restricted 128 Solaris 11 in NetBackup 7.6 17 space requirements of SRTs 39 SRT seeshared resource tree 40 for direct creation of backup instance on virtual machine 17

T troubleshooting deleting a client accidentally 194 different service pack level warning 193 long restore times on HP-UX 193 problems booting from CD 192 Solaris media boot network parameters issue 193 UNIX boot from CD 192

U uninstalling BMR boot server from a UNIX or Linux system 26 using external procedures 139 using the NetBackup Activity Monitor 232

256

Index

V client protection 37 Veritas Cluster Server 79 viewing BMR logs 235 Volumes properties 176 vxlogcfg command 237 vxlogmgr command 237 vxlogview command 237

W Windows Active Directory 100 adding drivers to configuration 166 adding drivers to packages pool 155 bootable mass storage device drivers 208 dynamic disk promoting 184 external procedure environment variables 148 finding correct drivers 155 network boot 115 writing a CD 90

Z ZFS storage pool 246

257

Netbackup 7.6 guide Bmr 1r2l4

Overview 6h3y3j

More details h6z72

Related Documents 543cg

Netbackup 7.6 guide Bmr 1r2l4

Veritas Netbackup Bmr Installation 3z6v6a

Plexis-guide 1d4824

Bmr Nih x502

Rumus Bmr 3z2t4w

Bmr Answers 2p406h

More Documents from "Rashmi Vishal Yagnik" 1x5y70

Netbackup 7.6 guide Bmr 1r2l4

Estimation Of Degree Of Calcination 6f4m3r

Unit-5 Chapter - 8 Resource Allocation.ppt 1t4m

Cloud Computing Nutshell 5h1w65

Tantra Books 70703g

Format Of Ccsu Result u2e14