NetVault : Backup. User s Guide for the VaultDR System Plugins

(1)

VOG-101-5.6-EN-03 12/22/10 VaultDR Offline Plugin ver. 5.6 (VaultOS)

VaultDR Online Plugin for Windows ver. 3.5 VaultDR Online Plugin for Linux ver. 3.1 VaultDR Server ver. 2.6

NetVault

®:

Backup

(2)

BakBone Software

9540 Towne Centre Drive, Suite 100 San Diego, California 92121 866.484.2663 NetVault: Backup User’s Guide for the VaultDR System Plugins

This software product is copyrighted and all rights are reserved. The distribution and sale of this product are intended for the use of the original purchaser only per the terms of the License Agreement. All other product trademarks are the property of their respective owners.

The NetVault: Backup User’s Guide for the VaultDR System Plugins is copyrighted and all rights are reserved.

This document may not, in whole or part, be copied, photocopied, reproduced, translated, reduced or transferred to any electronic medium or machine-readable form without prior consent in writing from BakBone Software.

THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR

NON-INFRINGEMENT.

THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED INTO NEW EDITIONS OF THE PUBLICATION. BAKBONE SOFTWARE MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.

logo®_{, Integrated Data Protection}™_{, SmartDisk}™_{, Asempra}®_{, and FASTRecover}™_{are all}

(3)

Section 1: Introduction & Overview

Chapter 1: Introducing NetVault: Backup for the VaultDR

System Plugins

9

• NetVault: Backup for the VaultDR System Plugins – At a Glance ... 9

• Key Benefits ... 9

• Feature Summary ... 10

• Target Audience ... 11

• Recommended Additional Reading ... 11

• Open Source Code Availability ... 11

• Technical Support ... 11

• Documentation Updates ... 12

Chapter 2: Deploying VaultDR

13

• VaultDR Components ... 13

- VaultDR Offline Plugin ... 14

- VaultDR Online Plugin for Windows ... 14

- VaultDR Online Plugin for Linux ... 14

- VaultDR Server ... 14

- VaultOS Operating System ... 14

• VaultDR Deployment Scenarios ... 15

- VaultDR for Offline Only x86/x86-64 Clients with Windows NVBU Server ... 16

- VaultDR for Offline Only x86/x86-64 Clients with Linux NVBU Server ... 17

- VaultDR Client for Windows with Windows NVBU Server ... 18

- VaultDR Client for Windows with Linux NVBU Server ... 19

- VaultDR Client for Linux with Linux NVBU Server ... 20

- VaultDR Client for Linux with Windows NVBU Server ... 21

- VaultDR Client for Windows and VaultDR Client for Linux with Linux NVBU Server ... 22

(4)

Section 2: The VaultDR Offline Plugin

Chapter 3: Using VaultDR Offline Plugin

27

• VaultDR Server – An Overview ...27

- VaultDR Server Environment Overview ... 28

• Installing and Removing VaultDR Server ...28

- Prerequisites ... 28

- Installing VaultDR Server ... 29

- Removing VaultDR Server ... 30

- Upgrading VaultDR Server ... 30

• Configuring VaultDR Server ...31

- Creating a VaultOS Boot System ... 31

- Adding a VaultDR Client to the VaultDR Server ... 33

• Booting a VaultDR Client with VaultOS ...35

- Booting with VaultOS ... 35

• Backing Up Data with VaultDR Offline Plugin ...44

- Backing Up Data ... 47

• Restoring Data ...50

- Restoring to a Physical Machine ... 50

- Restoring as a VMDK Image ... 54

- Recovery to a Standby VaultDR Client ... 67

Section 3: The VaultDR Online Plugin

Chapter 4: Using VaultDR Online Plugin for Windows

71

• VaultDR Online Plugin for Windows – An Overview ...72

- VaultDR Online Plugin Environment Overview ... 73

• Configuring VaultDR Server ...74

- Creating a VaultOS Boot System ... 74

• Booting a VaultDR Client with VaultOS ...77

- Booting with VaultOS ... 78

• Installing and Removing VaultDR Online Plugin for Windows ...84

(5)

- Installing VaultDR Online Plugin for Windows ... 85

- Upgrading VaultDR Online Plugin for Windows ... 86

- Removing VaultDR Online Plugin for Windows ... 87

• Backing Up Data with VaultDR Online Plugin for Windows ... 89

• Restoring Data ... 97

- Restoring to a Physical Machine ... 98

- Restoring as a VMDK Image ... 103

Chapter 5: Using VaultDR Online Plugin for Linux

117

• VaultDR Online Plugin for Linux – An Overview ... 117

• Installing and Removing VaultDR Online Plugin for Linux ... 118

- Installing VaultDR Online Plugin for Linux ... 122

- Removing VaultDR Online Plugin for Linux ... 125

• Generating a DR Image ... 127

• Creating the Required Bootable CD ... 129

- Creating the CD and Saving it for Future Use ... 130

- Creating the CD at the Time of Recovery ... 131

• Recovering a DR Image ... 132

- Restoring Data ... 134

- Booting the Target VaultDR Client with the Appropriate OS and Drivers ... 137

- Monitoring Job Progress and Finalizing a Recovery ... 148

- Completing Post-Restore Requirements ... 150

Section 4: Appendix

Appendix A: VaultDR Physical to Virtual Recovery

155

• VaultDR Physical to Virtual Recovery – An Overview ... 156

• Offline Backup Procedure ... 156

- Installing SCSI/IDE Device Drivers ... 157

- Booting a VaultDR Client with VaultOS ... 157

- Configuring VaultDR Server ... 162

(6)

• Online Backup Procedure ...163

- Adding VaultDR Online Plugin Clients ... 164

- Installing VaultDR Online Plugin for Windows ... 164

- Installing SCSI and IDE Device Drivers ... 164

• Offline Recovery to a Virtual Machine ...166

- Configuring the Virtual Machine ... 167

- Booting a Virtual Machine with VaultOS ... 170

- Verifying Access to the Target VaultDR Client ... 170

- Restoring Data ... 170

- Installing the VM Tools ... 173

• Example ...173

- Backing Up the Physical Machine Using VaultDR Online Plugin ... 173

- Creating the Virtual Machine ... 177

- Booting a Virtual Machine with VaultOS ... 179

- Verifying Access to the Target VaultDR Client ... 180

- Recovering Data ... 181

- Installing VMware Tools ... 182

• Installing SCSI and IDE Device Drivers on a Physical Machine ...183

(7)

(8)

(9)

Chapter 1:

I

NTRODUCING

N

ET

V

AULT

: B

ACKUP

FOR

THE

V

AULT

DR S

YSTEM

P

LUGINS

NetVault: Backup for the VaultDR System Plugins – At a Glance Key Benefits

Feature Summary Target Audience

Recommended Additional Reading Open Source Code Availability Technical Support

Documentation Updates

1.1.0 NetVault: Backup for the VaultDR System

Plugins – At a Glance

NetVault: Backup (NVBU) for the VaultDR System Plugins (VaultDR) significantly reduces the time required to recover a failed disk drive and restore operations. Online full partition backups and offline block-level backups can be scheduled as an extension to your existing backup routine. In the event of a server crash, the provided minimal operating system (OS) or LiveCD may be used to recover a system that has no functioning OS. After it is in a state to be restored, the NetVault: Backup (NVBU) Console is used to restore the most recent system image. VaultDR improves your ability to meet aggressive Recovery Time

Objectives (RTOs) and service-level agreements (SLAs) by eliminating much of the manual intervention and guesswork commonly associated with the task of rebuilding a disk. By automating system recovery — including recovery of OSs, network settings, system settings, applications, disk partitions and data — VaultDR ensures that the disk rebuild will be done correctly the first time.

1.2.0 Key Benefits

Speeds Bare Metal Recovery to Minimize Downtime

(10)

minimizing downtime and improving user productivity. VaultDR provides protection for OSs, network settings, systems settings, application binaries, disk partitions and data. Providing protection down to the partition level, VaultDR allows you to choose between online backups, allowing a protected system to remain online and available to your users and offline block-level backups. Using the VaultOS minimal OS which is provided or LiveCD, VaultDR enables you to recover a system that has no functional OS. VaultDR substantially reduces the time consuming manual steps typically required to rebuild the disk and restore operations and enables you to meet aggressive RTOs.

Reduces Risk by Reducing Manual Intervention

One problem inherent to bare metal recoveries is the amount of information required to ensure success on the first attempt. A typical manual bare metal recovery may include sixteen or more steps, with each requiring input of values that must be correct to minimize the impact on users. By providing protection down to the partition level during regularly scheduled online or offline backups, VaultDR manages these steps for you, eliminates guesswork and keeps you current with changes and modified server configurations.

Ensures Business Continuity

VaultDR provides an added level of protection in the fight to ensure business continuity. VaultDR uses NVBU which provides automatic integration with a wide range of backup devices. Not only can you be assured that your critical system settings are being captured on a regular basis, but you can also take comfort in the fact that your bare metal recovery images are being stored off-site. When combined with NetVault: FASTRecover and NVBU Application Plugin Modules (APMs), VaultDR ensures a complete and comprehensive data protection strategy.

1.3.0 Feature Summary

Online full partition backups

Offline block-level backups Windows VSS-based backups

Protects boot and system Images on Linux platforms Recovers machines with no functional OS

(11)

1.4.0 Target Audience

System administration experience is recommended when using the VaultDR Offline Plugin or the VaultDR Online Plugin. Although it is not necessary to have this level of experience to perform routine backups with either plugin, the initial configuration of each plugin, the configuration of a target Client and the restore procedure will require administrator knowledge.

1.5.0 Recommended Additional Reading

NetVault: Backup Installation Guide – This guide provides complete details

on installing the NVBU Server and Client software.

NetVault: Backup Administrator’s Guide – This guide describes how to use

NVBU and provides comprehensive information on all NVBU features and functionality.

You can download these guides from the BakBone web site at the following address:

http://www.bakbone.com/documentation

1.6.0 Open Source Code Availability

The VaultOS component software used with the VaultDR System Plugins was created using open source, Linux kernel source code. To obtain a copy of this open source code, make a written request to:

BakBone Software, Inc. Attn: Product Management 9540 Towne Centre Drive, Suite 100

San Diego, CA 92121

1.7.0 Technical Support

BakBone Software is dedicated to providing friendly, expert advice to its

customers. BakBone’s highly trained professionals are available to answer your questions, offer solutions to your problems and generally help you make the most of any BakBone software purchase. Log on to the web site for more information.

(12)

1.8.0 Documentation Updates

For late-breaking documentation updates, refer to the BakBone Software Knowledge Base. BakBone’s Knowledge Base articles for VaultDR System Plugins can be found at the following links:

VaultDR Offline Plugin v5.6:

http://kb.bakbone.com/5808

VaultDR Online Plugin for Windows Clients v3.5:

VaultDR Online Plugin for Linux Clients v3.1:

VaultDR Server v2.6:

(13)

Chapter 2:

D

EPLOYING

V

AULT

DR

VaultDR Components VaultDR Offline Plugin

VaultDR Online Plugin for Windows VaultDR Online Plugin for Linux VaultDR Server

VaultOS Operating System VaultDR Deployment Scenarios

VaultDR for Offline Only x86/x86-64 Clients with Windows NVBU Server VaultDR for Offline Only x86/x86-64 Clients with Linux NVBU Server VaultDR Client for Windows with Windows NVBU Server

VaultDR Client for Windows with Linux NVBU Server VaultDR Client for Linux with Linux NVBU Server VaultDR Client for Linux with Windows NVBU Server

VaultDR Client for Windows and VaultDR Client for Linux with Linux NVBU Server

VaultDR Client for Windows and VaultDR Client for Linux with Windows NVBU Server

2.1.0 VaultDR Components

The VaultDR System is comprised of two key components, or plugins, each of which provides its own form of disaster recovery backup, and a third component that serves as a basic OS that is used to prepare a target DR Client for backup/ restore.

VaultDR includes the following technical components:

VaultDR Offline Plugin for x86/x86-64 Clients

VaultDR Online Plugin for Windows VaultDR Online Plugin for Linux

VaultDR Server VaultOS

(14)

2.1.1 VaultDR Offline Plugin

The VaultDR Offline Plugin implements a block-by-block backup and restore technique to fully recover a system. This block-by-block operation takes the target system offline and makes it unavailable. This is done to either:

Backup – An Offline Backup fully backs up all aspects of a target system

(OS, applications, system settings, and so on). This is ideal for new systems that have been configured for use.

Restore – An Offline Restore recovers a machine that has no functional OS to a previously configured state.

2.1.2 VaultDR Online Plugin for Windows

The VaultDR Online Plugin for Windows makes it possible to back up a full Windows system while it remains online and active. When a recovery is required, the VaultDR Offline Plugin operating system (VaultOS) is used to boot the target DR client to allow for a complete recovery of data (that is, an Offline Restore is required).

2.1.3 VaultDR Online Plugin for Linux

The VaultDR Online Plugin for Linux makes it possible to back up a full Linux system while it remains online and active. The VaultDR Online Plugin for Linux uses Storix, a third party DR boot utility, to boot the target DR client to allow for a complete recovery of data (that is, an Offline Restore is required).

2.1.4 VaultDR Server

The VaultDR Server resides on the NVBU Server and enables backup and recovery of a target client’s data via the VaultDR Offline Plugin or the VaultDR Online Plugin.

2.1.5 VaultOS Operating System

The VaultDR Offline Plugin includes a component known as VaultOS. The VaultOS is a minimal OS that is used to boot a target disaster recovery client system to prepare it for either backup or restore (depending on the VaultDR System Plugin in use). This minimal OS will start the target client, load all applicable device drivers, and leave its hard drive in a state suitable for either backup or restore.

(15)

backups.

If you created backup jobs using VaultDR Server version 2.6.1, you must re-create the jobs using a later version.

VaultDR Server version 2.6.8 requires VaultOS version 5.6.4 to perform backups (restores from previous versions will work).

2.2.0 VaultDR Deployment Scenarios

This section details deployment scenarios for the following VaultDR products:

VaultDR for Offline Only x86/x86-64 Clients with Windows NVBU Server VaultDR for Offline Only x86/x86-64 Clients with Linux NVBU Server VaultDR Client for Windows with Windows NVBU Server

VaultDR Client for Windows with Linux NVBU Server VaultDR Client for Linux with Linux NVBU Server VaultDR Client for Linux with Windows NVBU Server

VaultDR Client for Windows and VaultDR Client for Linux with Linux NVBU Server

(16)

2.2.1 VaultDR for Offline Only x86/x86-64 Clients with

Windows NVBU Server

This scenario is deployed when the user wants to perform offline or cold backups of Intel x86 Clients and has a Windows NVBU Server deployed.

The VaultDR Server for Windows component is installed on the Windows NVBU Server and the VaultDR Offline Plugin for Intel x86 Clients, VaultOS, is installed on each Intel x86 Client that you want to protect with offline or cold backups.

In this scenario, VaultOS is used to perform the backup and recovery of the Intel x86 Clients. Figure 2-1: VaultDR for Offline Only x86/x86-64 Clients with Windows Server

(17)

2.2.2 VaultDR for Offline Only x86/x86-64 Clients with Linux

NVBU Server

This scenario is deployed when the user wants to perform offline or cold backups of Intel x86 Clients and has a Linux NVBU Server deployed.

The VaultDR Server for Linux component is installed on the Linux NVBU Server and the VaultDR Offline Plugin for Intel x86 Clients, VaultOS, is installed on each Intel x86 Client that you want to protect with offline or cold backups.

In this scenario, VaultOS is used to perform the backup and recovery of the Intel x86 Clients. Figure 2-2: VaultDR for Offline Only x86/x86-64 Clients with Linux Server

(18)

2.2.3 VaultDR Client for Windows with Windows NVBU

Server

This scenario is deployed when the user wants to perform online or hot backups of Windows Clients and has a Windows NVBU Server deployed.

The VaultDR Server for Windows component is installed on the Windows NVBU Server and the VaultDR Online Plugin for Windows is installed on each Windows Client that you want to protect with online or hot backups.

In this scenario, VaultOS is used to perform the recovery of the Windows Clients.

Figure 2-3:

VaultDR Client for Windows with Windows Server

(19)

2.2.4 VaultDR Client for Windows with Linux NVBU Server

This scenario is deployed when the user wants to perform online or hot backups of Windows Clients and has a Linux NVBU Server deployed.

The VaultDR Server for Linux component is installed on the Linux NVBU Server and the VaultDR Online Plugin for Windows is installed on each Windows Client that you want to protect with online or hot backups.

Figure 2-4:

VaultDR Client for Windows with Linux Server

(20)

2.2.5 VaultDR Client for Linux with Linux NVBU Server

This scenario is deployed when the user wants to perform online or hot backups of Linux Clients and has a Linux NVBU Server deployed.

The VaultDR Online for Linux, Linux Server Component is installed on the Linux NVBU Server and the VaultDR Online Plugin for Linux, Linux Client Component is installed on each Linux Client that you want to protect with online or hot backups.

Figure 2-5:

VaultDR Client for Linux with Linux Server

(21)

2.2.6 VaultDR Client for Linux with Windows NVBU Server

This scenario is deployed when the user wants to perform online or hot backups of Linux Clients and has a Windows NVBU Server deployed.

The VaultDR Online for Linux, Windows Server Component is installed on the Windows NVBU Server and the VaultDR Online Plugin for Linux, Linux Client Component is installed on each Linux Client that you want to protect with online or hot backups.

Figure 2-6:

VaultDR Client for Linux with Windows Server

(22)

2.2.7 VaultDR Client for Windows and VaultDR Client for

Linux with Linux NVBU Server

This scenario is deployed when the user wants to perform online or hot backups of both Linux and Windows Clients and has a Windows NVBU Server deployed. The VaultDR Online for Linux, Windows Server Component is installed on the Windows NVBU Server and the VaultDR Online Plugin for Linux, Linux Client Component is installed on each Linux Client that you want to protect with online or hot backups.

Additionally, the VaultDR Server for Linux component is installed on the Linux NVBU Server and the VaultDR Online Plugin for Windows is installed on each Windows Client that you want to protect with online or hot backups.

Figure 2-7:

VaultDR Client for Windows and Client for Linux with Linux Server

(23)

2.2.8 VaultDR Client for Windows and VaultDR Client for

Linux with Windows NVBU Server

This scenario is deployed when the user wants to perform online or hot backups of both Linux and Windows Clients and has a Windows NVBU Server deployed. The VaultDR Online for Linux, Windows Server Component is installed on the Windows NVBU Server and the VaultDR Online Plugin for Linux, Linux Client Component is installed on each Linux Client that you want to protect with online or hot backups.

Additionally, the VaultDR Server for Windows component is installed on the Windows NVBU Server and the VaultDR Online Plugin for Windows is installed on each Windows Client that you want to protect with online or hot backups.

Figure 2-8:

VaultDR Client for Windows and VaultDR for Linux with

Windows Server

(24)

(25)

(26)

(27)

Chapter 3:

U

SING

V

AULT

DR O

FFLINE

P

LUGIN

VaultDR Server – An Overview

VaultDR Server Environment Overview Installing and Removing VaultDR Server

Prerequisites

Installing VaultDR Server Removing VaultDR Server Upgrading VaultDR Server Configuring VaultDR Server

Creating a VaultOS Boot System

Adding a VaultDR Client to the VaultDR Server Booting a VaultDR Client with VaultOS

Booting with VaultOS

Backing Up Data with VaultDR Offline Plugin Prerequisites

Backing Up Data Restoring Data

Restoring to a Physical Machine Restoring as a VMDK Image

Recovery to a Standby VaultDR Client

3.1.0 VaultDR Server – An Overview

(28)

3.1.1 VaultDR Server Environment Overview

The processes required to set up and use the VaultDR Server must be followed in a specific order. The following table outlines how to establish a VaultDR Server environment.

3.2.0 Installing and Removing VaultDR Server

This section covers the steps required to install (and upgrade) the VaultDR Server.

3.2.1 Prerequisites

Prior to installing (or upgrading) the VaultDR Server, the following points must be reviewed, and applicable actions must be taken:

VaultDR Server Component Compatibility – For the VaultDR Server to function properly, all of its associated components must be the proper

version (that is, version “X” of the VaultDR Server will only work with its

appropriate version of VaultOS). For complete compatibility information, refer

The VaultDR Server Environment Setup Components Required:

VaultDR Server

VaultOS Operating System

Installation

Install the VaultDR Server on the NVBU Server.

Configuration

Configure the VaultDR Server:

1. Create a VaultOS Boot System (for example, to a writable CD).

2. Add the target VaultDR Clients to the VaultDR Server on the NVBU Server.

Backup

Perform an offline backup of the desired Client machine. 1. Boot the target VaultDR Client system with VaultOS.

2. From the NVBU Server, administer backup of the Client by selecting data to be backed up (for example, partitions, drives, volumes, and so on).

Restore

Perform an offline restore to the target VaultDR Client. 1. Boot the target VaultDR Client system with VaultOS.

(29)

to the NetVault: Backup VaultDR Supported Platforms at www.bakbone.com/ compatibility.

Existing VaultDR Server Backups (upgrades only) – It is important to note

that backups performed with earlier versions of this plugin may not be compatible with the newest release of the plugin. Prior to performing an upgrade to the newest version, refer to NetVault: Backup VaultDR Supported

Platforms at www.bakbone.com/compatibility for complete compatibility information.

Before installing the VaultDR Server, make sure that the following requirements have been met:

The Server version of the NVBU software must be installed on at least one

machine.

The VaultDR Client machine (the target of the backup/restore) must have a supported Intel x86-based OS installed.

3.2.2 Installing VaultDR Server

The NVBU VaultDR Server must be installed on an NVBU Server. It is installed and removed via the NVBU Client Management window. To install this plugin, perform the following steps:

1. From the machine acting as the NVBU Server, open the NVBU Client Management window (via either of the toolbar buttons or by clicking Administration > Client Management).

2. On the Clients tab, right-click the applicable machine (the NVBU Server), and select Install Software from the pop-up menu.

Figure 3-1:

Install Software option

3. On the dialog that appears, navigate to the location of the “.npk” installation file (for example, the NetVault: Backup APM Installation CD or the directory to which the file was downloaded from the BakBone web site).

(30)

Note: Based on the OS in use and the location of this file, the directory path may vary, but the file required for installation of this plugin should be entitled

“drcxxxx.npk” (where xxxx represents the platform and version number). 5. When the Install Software dialog appears that indicates the software was

successfully installed, click OK to dismiss it. The plugin is now ready for use.

3.2.3 Removing VaultDR Server

To remove the VaultDR Server, perform the following steps:

1. From the NVBU Console, open the NVBU Client Management window (via either of the toolbar buttons or by clicking Administration > Client

Management).

2. On the Clients tab, right-click the NVBU Server or the applicable NVBU Heterogeneous Client, and select Remove Software from the pop-up menu. 3. On the Remove Software dialog, select the applicable plugin for removal (for

example, VaultDR APM or VaultDR Online APM), and click Remove.

Figure 3-2:

Remove Software dialog

4. When the next Remove Software dialog appears, click OK to proceed (or Cancel to abort).

5. When the confirmation message appears that indicates the software was removed, click OK to close the dialog and return to the NVBU Client Management window.

3.2.4 Upgrading VaultDR Server

To upgrade VaultDR Server, perform the following steps: 1. Uninstall the previous version of the VaultDR APM.

For details, see Removing VaultDR Serveron page 30. 2. Install the new version of the VaultDR APM.

(31)

3.3.0 Configuring VaultDR Server

The second phase of setting up the VaultDR Server involves environment configuration, which is divided into two steps:

Creating a VaultOS Boot System

Adding a VaultDR Client to the VaultDR Server

The following sections illustrate the procedures that must be followed to complete these steps.

3.3.1 Creating a VaultOS Boot System

Prior to using the VaultDR Server, you must create a VaultOS Boot System. This minimal OS loads to a target machine’s memory, rather than to its hard drive. This leaves the hard drive(s) inactive (offline) and in a suitable state for backup or restore. The VaultOS is created on a writable CD. You can also boot from a LiveCD with the VaultOS binaries on a separate device, such as a USB stick. This is described in Creating a Rescue Device for Use with a LiveCDon page 32.

3.3.1.a Creating a Bootable VaultOS CD

The VaultDR Server allows you to create a bootable CD that can be used to prepare a Client machine for the backup and restore process.

Requirements

The following items are required for this procedure:

Installation ISO image (obtained via download). A writable CD-ROM drive

A blank CD

CD-generation software

Creation Procedure

Note: BakBone recommends that all applications running on the machine performing this operation be shut down before starting this procedure.

1. Download VaultDR Offline Plugin, VaultOS from the BakBone web site via the following link:

http://www.bakbone.com/downloads

2. Follow the instructions on the Download Software page to download the VaultOS component for your OS.

3. Note the name and location of this file (for example,

(32)

4. Insert a blank CD in the writable drive.

5. Create a new CD with CD-generation software using the VaultOS “.iso” file. For details on this procedure, see the relevant documentation for the CD-generation software in use.

3.3.1.b Creating a Rescue Device for Use with a LiveCD

A LiveCD is an OS that boots from a CD without the necessity of installing to a hard drive. This allows you to initiate disaster recovery without the OS on disk. VaultDR supports booting from a LiveCD with VaultOS on a separate device, such as a USB stick (RescueUSB) or another CD (RescueCD). For a list of supported OS LiveCDs, refer to NetVault: Backup VaultDR Offline Plugin Supported

Platforms at www.bakbone.com/compatibility.

Requirements

The following items are required to create a RescueCD or RescueUSB device:

The “drdaemon” and “vaultdr_client.sh” files (obtained via download).

A USB port and a USB device with enough space to hold the “drdaemon” and

“vaultdr_client.sh” files (1MB is sufficient), or

A writable CD-ROM drive and a blank CD.

Note: You will need two CD-ROM drives on the target system to use a RescueCD with a LiveCD.

Creation Procedure

1. Download VaultDR Offline Plugin, VaultOS from the BakBone web site via the following link:

http://www.bakbone.com/downloads

2. Note the name and location of this file (for example,

“/home/vaultos_x86_vxxx.zip” where xxx represents the software version number).

3. Extract “drdaemon” and “vaultdr_client.sh” from the “.zip” file, and copy them to your blank media (for example, a USB stick or CD-R disc).

(33)

3.3.2 Adding a VaultDR Client to the VaultDR Server

To properly access a VaultDR Client machine for backup and restore, you must add it to the VaultDR Server. To accomplish this, perform the follow steps:

1. From the NVBU Console, open the NVBU Backup window (via either of the toolbar buttons or by clicking Operations > Backup).

2. On the Selections tab, locate the machine acting as the NVBU Server (that is, the machine with the VaultDR Server installed), and double-click it to open it.

Figure 3-3:

Open option on Selections tab

3. In the list of available APM/plugins, locate the VaultDR Server (labeled “VaultDR APM”), and open it by double-clicking it or right-clicking it and selecting Open from the pop-up menu.

4. When the Add VaultDR Client dialog appears, complete the following fields to add a VaultDR Client:

Figure 3-4:

Add VaultDR Client dialog

Client Name – The name of the applicable Client. NVBU scans the

network, looking for available systems that can be added as VaultDR Clients, and displays them in the drop-down list.

Address(es) – A comma-separated list of addresses that can either be IP

addresses or resolvable network names (for example, 10.55.55.1, Server_1, 10.55.55.2, and so on) that refer to the machine to be added.

Port Number – The port used to invoke drdaemon (for example, 15555).

(34)

Important: If you specify a port number other than the default 10000, you must manually enter the new port number when you boot the VaultDR Client. For details, see Step 16on page 44.

3.3.2.a Adding Additional VaultDR Clients

After you have added an initial VaultDR Client to the NVBU Server, you must perform the following steps to add additional Clients:

1. Open the NVBU Backup window (via either of the toolbar buttons or by clicking Operations > Backup), and double-click the NVBU Server (with the VaultDR Server installed on it) to open it.

2. Double-click the VaultDR Server to open it.

3. Right-click the plugin, and select Add Client from the pop-up menu.

4. When the Add VaultDR Client dialog appears, enter the values as explained in Step 4 of Adding a VaultDR Client to the VaultDR Serveron page 33.

Figure 3-5:

Add Client option

5. Repeat these steps as required until all VaultDR Clients have been added.

3.3.2.b Editing an Existing VaultDR Client

With a VaultDR Client added to the NVBU Server, the settings made during the original addition process can be edited, if necessary. To accomplish this, perform the following steps:

1. On the Selections tab, expand the VaultDR APM icon, right-click the applicable VaultDR Client, and select Edit Client.

2. When the Edit Client dialog appears, update the applicable values:

Figure 3-6:

(35)

Client Name – This field contains the current name for the selected client.

Changing this value updates the name of the Client in NVBU.

Address(es) – This field contains the IP address originally set for this

client. You can change this value or add additional, comma-separated addresses.

Port Number – This field contains the port used to invoke drdaemon (for

example, 15555). The default value is 10000.

Important: If you specify a port number other than the default 10000, you must manually enter the new port number when you boot the VaultDR Client. For details, see Step 16on page 44.

3. Click OK to close the dialog and commit the changes.

3.3.2.c Removing an Existing VaultDR Client

If you need to remove an existing VaultDR Client from the NVBU Server, perform the following steps:

1. On the Selections tab, expand the VaultDR APM icon, right-click the applicable VaultDR Client, and select Remove Client.

2. When the confirmation dialog appears, click Yes to remove it (or No to abort).

3.4.0 Booting a VaultDR Client with VaultOS

To use the VaultDR Server to back up or restore a target VaultDR Client, you must first take the system offline and boot it with the required components. This is accomplished by booting the Client machine with the VaultOS Boot System (the media created in the processes explained in the section, Creating a VaultOS Boot Systemon page 31). Rather than installing software to the Client’s hard drive, this boot system will load a minimal OS to the VaultDR Client’s memory, leaving the hard drive completely inactive (offline) and in a suitable state for either backup or restore.

3.4.1 Booting with VaultOS

This process entails the configuration of network equipment installed on the target VaultDR Client (that is, loading driver software for the system’s network interface card or small computer system interface (NIC/SCSI) card to memory to use the device and access the system).

The overall boot process with VaultOS can be broken down into two phases:

Gathering VaultDR Client Network Information

(36)

Important: Before beginning this procedure, you must verify the boot order of the target VaultDR Client. The machine’s CD-ROM drive must be the first source of a boot for this process to work.

3.4.1.a Gathering VaultDR Client Network Information

In this first phase of the process, you must gather specific network-related information from the VaultDR Client for use in the boot process (for example, NIC and SCSI interface values). This includes the following values:

IP Address Network Mask Gateway

Important: If the target VaultDR Client is configured with multiple NIC/SCSI devices for access, BakBone recommends that you gather the preceding information for each device. The VaultOS boot process will recognize all these devices and request that you configure each, individually, with this information (but only one of the devices actually needs to be successfully configured for use). The following sections offer sample procedures that you can use to obtain these required values, based on the OS in place on the target VaultDR Client.

Linux VaultDR Client

1. Log in locally to the Linux VaultDR Client, and initiate a Terminal Session. 2. At the prompt, type the following command:

ifconfig

3. In the content that is revealed, locate and record the IP Address and the Network Mask values.

Figure 3-7:

Result of ifconfig command

(37)

4. At the prompt, type the following command: route

5. In the content that is revealed, locate and record the Gateway value (when the command is issued, this value will be revealed as the default value).

Figure 3-8:

Result of route command

Windows VaultDR Client

1. Log in locally to the Windows VaultDR Client, and launch a Command Prompt session.

2. At the prompt, type the following command: ipconfig

3. In the content that is revealed, locate and record the IP Address, Subnet Mask (Network Mask), and Default Gateway values.

Figure 3-9:

Results of ipconfig

With all relevant networking information noted, you can boot the target VaultDR Client. If you are booting from a LiveCD, follow the steps outlined in the next section, Booting the VaultDR Client from a LiveCD. Otherwise, proceed to Booting the VaultDR Client with VaultOSon page 40.

The Gateway

(38)

3.4.1.b Booting the VaultDR Client from a LiveCD

If you are booting the VaultDR Client from a LiveCD, perform the following procedure. If you are booting the VaultDR Client from a standard VaultOS CD, proceed to Booting the VaultDR Client with VaultOSon page 40.

Requirements

The following items are required for this procedure:

A LiveCD containing the desired OS. Note the following important points:

The LiveCD must mount the loop-back device to perform backup and restore with NVBU.

Some LiveCDs automatically mount all partitions for devices, which can

lead to restore failure if the file system is mounted prior to a backup or restore job. If you boot with a LiveCD, ensure that the file system is unmounted before performing a backup or restore.

Some LiveCDs automatically use the swap partition for swap operations, which can lead to restore failure if the swap partition is used prior to a backup or restore job. If you boot with a LiveCD, ensure that the LiveCD does not use the swap partition before performing a backup or restore.

A Rescue device (see Creating a Rescue Device for Use with a LiveCDon page 32).

A USB port (for a RescueUSB device) or a secondary CD-ROM drive (for a RescueCD) on the target system.

If you are using a RescueCD, you will need two CD-ROM drives on the target

system — one for the LiveCD and one for the RescueCD.

Procedure

1. Insert the LiveCD in the CD-ROM drive on the target system, and reboot. 2. After the OS launches, plug in the USB stick or load the RescueCD.

In most cases, the LiveCD automatically mounts the USB/CD drive and shows an icon on the desktop.

3. If the LiveCD automatically mounted the USB/CD drive, use the “mount -l” command to find the path where the device is mounted.

Example:

# mount -l ...

(39)

4. If the LiveCD does not automatically mount the USB drive, mount it manually: Note: Follow the same procedure to use a RescueCD by mounting a CD instead of a USB device.

a. Use the “ls -l /dev/disk/by-id/usb*” command to find the USB devices on the system.

Example:

b. Mount the first partition on the device. Example:

5. To launch drdaemon, run the “vaultdr_client.sh” command. Example:

6. If you configured VaultDR to use a port other than the default “10000,” exit the VaultDR Daemon dialog, and enter the new port number manually. a. To exit the VaultDR Daemon dialog, press <Ctrl+C>.

b. At the command prompt, type the following command, and press Enter:

where port_number is the port you specified in Adding a VaultDR Client to the VaultDR Serveron page 33 or Editing an Existing VaultDR Clienton page 34.

Note: If you want to relaunch VaultDR Daemon from the command prompt without changing the port number, type drdaemon and press Enter.

7. If you want to enable multipath support, type the following at a command prompt, and press Enter:

Note: You can enter the -o mpath and -p port_number options together. # ls -l /dev/disk/by-id/usb*

root 9 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl -> ../../sdb

root 10 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl-part1_-> ../../sdb1 root 10 2007-09-26 8:16 /dev/disk/by-id/usb-JetFl-part2 -> ../../sdb2

# mount /dev/sdb1 /mnt/usb

# cd /mnt/usb

# sh vaultdr_client.sh

drdaemon -p port_number

(40)

3.4.1.c Booting the VaultDR Client with VaultOS

To boot from a standard VaultOS CD, perform the following steps. (If you are booting from a LiveCD, refer to Booting the VaultDR Client from a LiveCDon page 38.

1. Power down the VaultDR Client, and insert the VaultOS CD.

On reboot, there will be a 60-second delay after the boot prompt appears. 2. Press Enter to start the sequence immediately.

A series of dialogs will launch as various applications are loaded to system memory. The initial load sequence may take several minutes, during which time the screen may appear blank.

Important: This process only continues if VaultOS can locate the appropriate NIC/ SCSI driver components for the networking hardware available on the VaultDR Client. If no drivers can be found, you must manually load the device drivers.

3. When the Setup Networking dialog appears, highlight the Yes button (using either the Arrow keys or the Tab key), and press Enter to begin.

Figure 3-10:

Setup Networking dialog

4. If only one NIC card is present in the client machine, select Yes to configure the network interface when the Configuration Network Interface dialog appears, and skip to Step 6.

Figure 3-11:

(41)

5. If multiple NIC cards are present in the client machine, highlight the NIC card to be configured when the Network Configuration dialog appears, and select Edit.

Figure 3-12:

Network Configuration dialog

6. When the Network Configuration for <Device Name> dialog appears for the selected device, press the Spacebar to enable IPv4 support, use the Tab key to highlight the OK button, and press Enter to continue.

Figure 3-13:

Network Configuration for eth0 dialog

(42)

8. Press the Tab key to place the cursor in the IP Address field, and input this value (as recorded during Gathering VaultDR Client Network Informationon page 36).

Figure 3-14:

IPv4 Configuration for eth0 dialog

9. Press the Tab key again to access the Netmask field and input the appropriate Network Mask (as recorded during Gathering VaultDR Client Network Informationon page 36).

10.Use the Tab key to highlight the OK button, and press Enter to continue. 11. If an additional NIC/SCSI card exists on the target VaultDR Client, select the

appropriate device from the Network Configuration dialog, and repeat Step 5 through Step 9.

Figure 3-15:

Network Configuration dialog

(43)

12.Use the Tab key to highlight the OK button, and press Enter to continue. 13.When the Miscellaneous Network Settings dialog appears, use the Tab

key to highlight the Gateway field, and input the appropriate value (as recorded during Gathering VaultDR Client Network Informationon page 36).

Figure 3-16:

Miscellaneous Network Settings dialog

14.Use the Tab key to skip through the two DNS-related fields and highlight the OK button, and then press Enter to continue.

15.When the Network Interfaces dialog appears, select the OK button.

Figure 3-17:

Network Interfaces dialog

After selecting OK, the VaultDR Daemon dialog launches automatically, awaiting commands from the NVBU Server. The Client is now prepared for backup or restore.

Figure 3-18:

(44)

16.If you configured VaultDR to use a port other than the default “10000,” exit the VaultDR Daemon dialog, and enter the new port number manually. a. To exit the VaultDR Daemon dialog, press <Ctrl+C>.

b. At the command prompt, type the following command, and press Enter:

where port_number is the port you specified in Adding a VaultDR Client to the VaultDR Serveron page 33 (or Editing an Existing VaultDR Clienton page 34).

Note: If you want to relaunch VaultDR Daemon from the command prompt without changing the port number, type drdaemon and press Enter.

17.If you want to enable multipath support, type the following at a command prompt, and press Enter:

Note: You can enter the -o mpath and -p port_number options together.

3.5.0 Backing Up Data with VaultDR Offline Plugin

The VaultDR Server makes it possible to back up full systems. In addition, the plugin provides granular backup capabilities allowing for the selection of individual disk partitions for backup. This includes the following items:

Operating System

Applications

Specific User Information

From the NVBU Backup window, the VaultDR Server plugin can select the following items for backup:

Disk Partitions – All (or individual) partitions can be selected for backup.

Mounted Volumes (Linux/UNIX) – All of which are backed up as individual

partitions.

Note: The Master Boot Record (MBR) and the Partition Table items will be backed up automatically when a partition (all or individual) is backed up using the VaultDR Server. Therefore, these items are not available to select for a backup.

drdaemon -p port_number

(45)

3.5.1 Prerequisites

Prior to initiating a backup with the VaultDR Server, review the following sections for details on prerequisites that must be met.

3.5.1.a Booting the VaultDR Client with VaultOS

It is first necessary to boot the target VaultDR Client with the VaultOS to prepare it for the backup. To accomplish this, review all the steps covered in Booting with VaultOSon page 35.

3.5.1.b Verifying Disk Geometry and Device Size

Prior to performing a backup of any portion of a VaultDR Client’s hard drive, BakBone recommends that the Disk Size as well as the Disk Geometry of the selected drive be noted. When restoring previously backed up data, if these items are not taken into account, a restore could fail.

Example of How to Note the Drive Disk Size and Disk Geometry

A Client drive is divided into three partitions. The primary partition is 10 gigabytes (GB), the first logical partition is 7GB and the second is 3GB. A backup of the first logical partition is performed with the VaultDR Server. On restore of the system after a hard drive crash, if the first logical partition was restored, it would need to be restored to the proper partition (that is, the first logical partition), or the restore would fail.

The preceding information, including the Disk Size and Disk Geometry of a selected Client, can be determined via the NVBU Server as follows:

1. With the VaultDR Client booted using VaultOS (as outlined in Booting a VaultDR Client with VaultOSon page 35), access the NVBU Server, and launch the NVBU Console.

2. Open the NVBU Backup window, and double-click the NVBU Server (that is, the system containing the VaultDR Server) to open it.

3. Open the VaultDR Server by double-clicking it.

(46)

5. To determine the Disk Geometry, right-click the applicable disk, and select Disk Geometry from the pop-up menu.

The Display Device Geometry dialog displays details about the partition structure of the selected disk.

Figure 3-19:

Display Device Geometry dialog

Partitions – Each individual partition is listed here by number and the partition type.

Active – Displays the current activity state of the partition (“Yes” or “No”). Start Cyl – Displays the origination point (cylinder) for the various

partitions.

End Cyl – Displays the partition’s end point (cylinder). Size – Displays the size of each partition.

Type – Displays the type of partition.

6. With sufficient information noted, click OK to close this dialog.

7. To determine the overall size of a disk, right-click the applicable disk in the NVBU Backup window, and select Disk Size from the pop-up menu. The Device Size dialog displays details about the size of the selected disk.

Figure 3-20:

Device Size dialog

Device – The number and type of the disk.

Size – The size of the selected disk.

(47)

3.5.2 Backing Up Data

Before performing a VaultDR backup, consider the following important points:

The VaultDR Client machine must be booted with the VaultOS software prior

to each operation of the VaultDR Server (backup or restore). If this procedure is not completed properly, the VaultDR Client will be inaccessible from the NVBU Server. For details on this process, see Booting a VaultDR Client with VaultOSon page 35.

The Linux kernel supports only 15 partitions per SCSI disk and 63 partitions per IDE disk. Because of this limitation, VaultOS detects only 15 partitions per SCSI disk and 63 partitions per IDE disk, regardless of the target OS. If you exceed the maximum supported partitions, an error message will appear on the NVBU Server.

When Raw Mode is selected, not only will the media in use be backed up, but

the entire disk will be as well (for example, if 6GB are in use on a 30GB partition, 30GB of media will be used to back up the partition). The Raw Mode option should only be used when a complete hard drive is selected for a VaultDR Server backup (that is, not an individual partition).

Dynamic disks must be backed up via Raw Mode to maintain partition information.

VaultDR Offline Plugin does not support DR backup spanning multiple

libraries. Attempting to restore a backup job that spans multiple libraries will fail.

To perform a VaultDR backup, perform the following steps:

1. With the VaultDR Client booted with VaultOS, access the NVBU Server, and launch the NVBU Console.

2. Open the NVBU Backup window (via either of the toolbar buttons or by clicking Operations > Backup).

3. On the Selections tab, locate the machine acting as the NVBU Server (that is, the machine with the VaultDR Server installed), and double-click it to open it.

4. In the list that appears, locate the VaultDR Server (labeled “VaultDR APM”), and double-click it to open it and display the hard disks located on the Client system.

5. Select one of the following:

To select the entire disk for a backup, click the box to the left of the disk title.

To select specific items, double-click a disk to open it. Individual partitions

(48)

that you want to back up. Selected items will contain a green check, items that are not selected will be blank, and omitted items will contain a red cross. Figure 3-21: Selections tab on NVBU Backup window

Primary Partition – Each hard disk can contain up to four different

“true partitions”. They are referred to as the primary partitions, and can be individually selected for backup.

Extended Partition – This is the space on the hard disk not allocated

to the primary partition(s). This type of partition cannot be selected for a backup. To add it, the entire drive must be selected.

Figure 3-22:

Partition Types

Logical Partition – Logical partitions allow multiple system images to

run in one machine. This can be multiple instances of the same OS or different OSs. Logical partitions can be individually selected for a backup.

Figure 3-23:

(49)

6. Select the Backup Options tab, and then select Raw Mode, Zlib Compression, or both.

Figure 3-24:

Backup Options

Raw Mode – Select this option if you want all partition information for a

selected hard drive to be ignored and a “bit-by-bit” backup of the entire disk image to be performed. This bit-by-bit form of data transfer occurs during the restore of this backup as well, thereby eliminating the need to format the target drive.

Cases in which Raw Mode is desired include:

The selected hard drive does not have a partition table. VaultDR cannot recognize the partition table.

You are backing up data outside the MBR and partitions (for example,

dynamic disks).

Zlib Compression – Select this option to compress data on the VaultDR

Client prior to transfer during backup. This reduces overall network traffic during data transfer and also requires less media space to accommodate the VaultDR backup. This option is useful for partitions that contain a large amount of unused space and that would otherwise need 1:1 space on the backup medium.

7. Set the additional options on the remaining tabs (for example, Schedule, Target, and Advanced Options), as required.

These options are not unique to the VaultDR Server. For more information, refer to the NetVault: Backup Administrator’s Guide.

8. In the Job Title field, enter a suitable name for the job.

Specify a detailed name that lets you identify the job easily for monitoring its progress or restoring data.

9. Click the Submit button.

(50)

3.6.0 Restoring Data

The following sections describe how to restore backups to a variety of configurations, such as a physical machine or a Virtual Machine Disk Format (VMDK) image.

Important: Before attempting to recover to the same disk that you backed up, make sure that all existing partitions have been removed; otherwise, recovery to the same disk might fail.

Restoring a SATA disk with 15 partitions fails and the drdaemon presents an error when using Ubuntu 6.1 LiveCD.

3.6.1 Restoring to a Physical Machine

This option allows you to recover backups of the client to a physical machine that has the same hardware specification as the machine that was used for backup.

3.6.1.a Prerequisites

A DR restore procedure is a delicate operation. Prior to setting up and running a DR restore, the prerequisites covered in the following sections must be met.

Ensure that Device File Names Match

The target device name on the VaultDR Client (for example, Disk 0 (IDE)) must be the same as it was at the time of backup.

Important: When relocating a DR backup, ensure that the hard disk installed on the new relocation target has the same name as the hard disk that existed in the original target machine.

Boot the VaultDR Client with VaultOS

It is first necessary to boot the target VaultDR Client with the VaultOS to prepare it for the restore of a DR image. To accomplish this, perform the steps covered in

Booting a VaultDR Client with VaultOSon page 35.

Gather Noted Device Size and Disk Geometry Information

(51)

Verify Access to the Target VaultDR Client

The VaultDR Client machine that is to serve as a target for the restore must be accessible to the VaultDR Server. To check access, perform the following steps:

1. With the VaultDR Client booted with VaultOS, access the NVBU Server, and launch the NVBU Console.

2. Access the NVBU Backup window to verify that the applicable Client machine has been added as a VaultDR Client.

a. Open the VaultDR Server to reveal existing Clients.

b. Locate and right-click the applicable VaultDR Client, and select Edit from the pop-up menu.

c. When the Edit VaultDR Client dialog appears, verify that the data is correct or change it as required.

d. If the VaultDR Client is added properly, continue to the next section,

Restore Procedure; otherwise, proceed to the following step. 3. Add the applicable VaultDR Client.

For detailed instructions, see Adding a VaultDR Client to the VaultDR Server on page 33.

4. Close the NVBU Backup window of the VaultDR Server, and continue to the

Restore Procedure section.

3.6.1.b Restore Procedure

The following procedure illustrates how to perform a DR restore to a physical machine.

1. On the NVBU Server, use the NVBU Console to open the NVBU Restore window (via either of the toolbar buttons or by clicking Operations > Restore).

2. On the Selections tab, locate and double-click the applicable Client in the list of VaultDR Server backups.

3. Locate the VaultDR Server (labeled “VaultDR APM”), and double-click it to open it.

4. In the list of backup savesets that appears (this list is comprised of previous backups completed with this plugin), double-click the applicable saveset to open it.

(52)

To restore the entire disk, click the box to the left of the applicable disk title

to select it. Figure 3-25: Selections tab on NVBU Restore window

To select specific items, double-click a disk to open it, and then select the

items that you want to restore.

The Dos Compatibility Region is the first 32k – 512 bytes from start

of the disk that immediately follows the Master Boot Record (MBR). VaultDR backs up this region to support GRUB Stage 1.5. However, this region will always be backed up and restored regardless of the existence of GRUB Stage 1.5. This option is not selectable.

(53)

7. Select the Restore Options tab, where you can select the Restore Type: Physical Machine or VMDK Images.

Figure 3-26:

Restore Options tab

8. To restore the backup of a client to a physical machine, select the Physical Machine (the default) as the Restore Type.

If Physical Machine is selected, the Physical Recovery Options frame containing the Restore Name field is shown. By default, the value in this field is NVBU’s name for the VaultDR Client from which this backup was originally performed (based on the backup saveset selected from the Selections tab of the Restore window). This name is associated with a specific IP address that was previously configured. If this value is left at its default setting, selected data will be restored to the machine that was originally backed up. This field can be used to relocate restored data to a Standby VaultDR Client, if necessary. For complete details on this procedure and its use of this option, see Recovery to a Standby VaultDR Clienton page 67.

9. Set the additional options on the remaining tabs (for example, Target Client, Schedule, and Advanced Options), as required.

These options are not unique to the VaultDR System Plugins. For more information, refer to the NetVault: Backup Administrator’s Guide. 10.In the Job Title field, enter a suitable name for the job.

(54)

Notes

If selecting individual partitions for a restore, it is also necessary to select the

Master Boot Record and System Partition item. Failure to do so will result in a failed restore.

When performing a restore of a VaultDR Server backup, options available in

the Target Client tab should be left at their default settings. If a target other than the intended is selected from this tab the restore will fail.

3.6.2 Restoring as a VMDK Image

This option allows you to recover backups of the client to a VMDK Image, which can then be attached to a virtual machine created from VMware. This option effectively converts the backup of a physical machine to a virtual machine.

3.6.2.a Prerequisite

VaultDR Server must be installed on the NVBU Server.

3.6.2.b Restore Procedure

The following procedure illustrates how to restore a backup to a virtual machine. 1. On the NVBU Server, use the NVBU Console to open the NVBU Restore

window (via either of the toolbar buttons or by clicking Operations > Restore).

2. On the Selections tab, locate and double-click the applicable Client in the list of VaultDR Server backups.

3. Locate the VaultDR Server (labeled “VaultDR APM”), and double-click it to open it.

4. In the list of backup savesets that appears (this list is comprised of previous backups completed with this plugin), double-click the applicable saveset to open it.

(55)

To restore the entire disk, click the box to the left of the applicable disk title

to select it. Figure 3-27: Selections tab on NVBU Restore window

To select specific items, double-click a disk to open it, and then select the

Master Boot Record & System Partition and individual partitions that you want to restore.

Important: If restoring to a VMDK image, you must select both Master Boot Record & System Partition and the individual partitions or the restore job will fail.

7. Select the Restore Options tab.

The Restore Options tab allows you to select the Restore Type: Physical Machine or VMDK Images.

To restore the backup of a client to a virtual machine, select VMDK Images as the Restore Type.

(56)

Restoring the VMDK Image to a local directory of the NVBU Server: In the Local Target Directory box of the Vmdk Recovery Options

frame, enter a valid path to the location where the recovered images will be stored. If this field is left blank, the default value is the NetVault “temp” directory (“…/netvault/tmp”).

Figure 3-28:

Vmdk Recovery Options

Restoring the VMDK Image to a remote ESX Server:

1. Select the Restore to Remote ESX Server check box in the Vmdk Recovery Options frame.

(57)

Figure 3-29:

ESX Server Options

These options are required to restore VMDK Images directly to an ESX Server. This is useful when there is no local storage space on the NVBU Server machine or when using ESX Server.

ESX Host – Enter the host name or IP address of the ESX Server. Port – Enter the remote console port on the ESX Server.

Username – Enter the user name to log into the ESX Server. Password – Enter the password for the specified user name.

Path – Enter the directory on the ESX Server where the VMDK files

will be created. This path should always start with a datastore within square brackets — [datastore] dir. If the path specified does not exist, the plugin will not be able to connect to the ESX Server.

8. Set the additional options on the remaining tabs (for example, Target Client, Schedule, and Advanced Options), as required.

These options are not unique to the VaultDR System Plugins. For more information, refer to the NetVault: Backup Administrator’s Guide. 9. In the Job Title field, enter a suitable name for the job.

(58)

After the restore job has completed, you can create a virtual machine from the restored VMDK file using the VMware Server console. To do so, perform the following procedure.

1. Log into the VMware Server console.

2. Confirm that the VMDK file is located in the datastore path that was specified under ESX Server Options on the Restore Options tab.

Figure 3-30:

Datastore path on ESX Server

3. On the ESX Server, browse the datastore and navigate to the specified path. The path should contain a file with the extension “.vmdk”.

Figure 3-31:

(59)

4. In the upper-left corner of the VMware Server console, click the Create Virtual Machines icon.

Figure 3-32:

VMware console

5. When the Configuration dialog appears, select Custom, and click Next.

Figure 3-33:

(60)

6. In the Name field on the Name and Location dialog, enter a descriptive name for your virtual machine, and click Next.

Figure 3-34:

Name and Location dialog

7. When the Datastore dialog appears, select a datastore in which to store the virtual machine, and click Next.

Figure 3-35:

(61)

8. When the Virtual Machine Version dialog appears, select the version, and click Next. Figure 3-36: Virtual Machine Version dialog

9. When the Guest Operating System dialog appears, select the guest OS, and click Next.

Figure 3-37: