How To Recover A Computer From Disaster

134  Download (0)

Full text

(1)

LiveVault® Disaster

Recovery Guide

Version 7.60

Document Revision 0

25 June 2012

(2)

Notice

This documentation is a proprietary product of Autonomy and is protected by copyright laws and international treaty. Information in this documentation is subject to change without notice and does not represent a commitment on the part of Autonomy. While reasonable efforts have been made to ensure the accuracy of the information contained herein, Autonomy assumes no liability for errors or omissions. No liability is assumed for direct, incidental, or consequential damages resulting from the use of the information contained in this documentation.

The copyrighted software that accompanies this documentation is licensed to the End User for use only in strict accordance with the End User License Agreement, which the Licensee should read carefully before commencing use of the software. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyright owner. This documentation may use fictitious names for purposes of demonstration; references to actual persons, companies, or organizations are strictly coincidental.

Trademarks and Copyrights

Copyright 2012 Autonomy Corporation plc and all its affiliates. All rights reserved. Audit Center, Autonomy Consolidated Archive, Autonomy Express Search, Autonomy iManage ConflictsManager, Autonomy iManage RecordsManager, Autonomy Interaction Control Element (ICE), Autonomy Message Manager, Autonomy Notification Server, Autonomy Records Manager, Autonomy Windows Extension, Connected Backup, DeskSite, Digital Safe, Digital Supervisor, EAS On-Demand, EAS, Enterprise Archive Solution, FileShare, FileSite, iManage WorkSite MP, iManage WorkSite, iManage, Introspect, LiveVault, Meridio, OffSite, Scrittura, WorkDocs, WorkPortal, WorkRoute, WorkSite MP, WorkSite, WorkTeam, Zantaz, and all related titles and logos are trademarks of Autonomy Corporation plc and its affiliates.

Microsoft is a registered trademark, and MS-DOS, Windows, Windows 95, Windows NT, SharePoint, and other Microsoft products referenced herein are trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group. AvantGo is a trademark of AvantGo, Inc.

Epicentric Foundation Server is a trademark of Epicentric, Inc.

Documentum and eRoom are trademarks of Documentum, a division of EMC Corp. FileNet is a trademark of FileNet Corporation.

Lotus Notes is a trademark of Lotus Development Corporation. mySAP Enterprise Portal is a trademark of SAP AG.

Oracle is a trademark of Oracle Corporation.

Adobe is a trademark of Adobe Systems Incorporated. Novell is a trademark of Novell, Inc.

Stellent is a trademark of Stellent, Inc.

All other trademarks are the property of their respective owners.

Notice to Government End Users

If this product is acquired under the terms of a DoD contract: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of 252.227-7013. Civilian agency contract: Use, reproduction or disclosure is subject to 52.227-19 (a) through (d) and restrictions set forth in the accompanying end user agreement. Unpublished-rights reserved under the copyright laws of the United States. Autonomy, Inc., One Market Plaza, Spear Tower, Suite 1900, San Francisco, CA. 94105, US.

Acknowledgements

RSA Data Security, Inc. MD5 Message-Digest Algorithm; zlib general purpose compression library, Jean-loup Gailly and Mark Adler; Info-ZIP, more information at ftp://ftp.info-zip.org/pub/infozip/license.html; HTML-to-RTF Pro DLL 1.8 © 2002-2007 SautinSoft.

31 May 2012 Copyright Notice

(3)

Contents

About This Document

... 7

Documentation Updates... 7

Related Documentation... 8

Conventions ... 9

Notational Conventions ... 9

Command-line Syntax Conventions ...10

Notices ...11

Autonomy Product References ...12

Autonomy Customer Support ...12

Contact Autonomy...13

Chapter 1

Prepare for Disaster Recovery

... 15

Assumptions ...16

Before You Begin ...16

Terminology ...17

What to Expect...17

Gather As-Built Configuration Information ...18

Windows 2000 Server/Professional, or Windows Server 2003/2008 ...19

Microsoft Cluster Server (MSCS) Cluster Node ...20

Disaster Recovery with EFS (Encrypting File System) ...20

Recover a VMware Computer ...20

Select the Correct Disaster Recovery Procedure ...20

Chapter 2

Recover a Windows Server with DSRM

... 23

Summary of steps ...24

(4)

Contents

Chapter 3

Recover an Exchange Server on Windows 2003 Computers

... 37

Assumptions ... 37

Summary of steps... 38

Detailed steps... 39

Complete the Recovery on Exchange 2007 CCR Configurations ... 49

Chapter 4

Recover an Exchange Server on Windows 2008 computers

... 53

Assumptions ... 53

Summary of steps... 54

Detailed steps... 55

Complete the Recovery on Standalone Exchange Configurations... 64

Complete the Recovery on Exchange 2010 DAG Configurations ... 64

Complete the Recovery on Exchange 2007 CCR Configurations ... 66

Chapter 5

Recover a SQL Server with a SQL-aware policy

... 69

Assumptions ... 69

Summary of steps... 70

Detailed steps... 71

Post-restore considerations ... 80

Chapter 6

Recover a Windows 2003 Small Business Server

... 83

Assumptions ... 83 Summary of steps... 84 Detailed steps... 85

Chapter 7

Recover a DPM server

... 103 Summary of Steps ... 104

Recovering your DPM server... 104

(5)

Contents

Appendix A

In-place Upgrade of Windows 2000

...113

Appendix B

Restore a domain controller

...119

Appendix C

(6)
(7)

About This Document

This guide is for users who need to recover an entire computer that has failed.

Documentation Updates

Related Documentation

Conventions

Autonomy Product References

Autonomy Customer Support

Contact Autonomy

Documentation Updates

The information in this document is current as of LiveVault version 7.60. The

content was last modified 25 June 2012.

You can retrieve the most current product documentation from Autonomy’s

Knowledge Base on the Customer Support Site.

A document in the Knowledge Base displays a version number in its name, such

as IDOL Server 7.5 Administration Guide. The version number applies to the

product that the document describes. The document may also have a revision

number in its name, such as IDOL Server 7.5 Administration Guide Revision 6.

The revision number applies to the document and indicates that there were

revisions to the document since its original release.

It is recommended that you periodically check the Knowledge Base for revisions

to documents for the products your enterprise is using.

To access Autonomy documentation

1. Go to the Autonomy Customer Support site at

(8)

About This Document

2. Click Login.

3. Enter the login credentials that were given to you, and then click Submit.

The Knowledge Base Search page opens.

4. In the Search box, type a search term or phrase. To browse the Knowledge

Base using a navigation tree only, leave the Search box empty.

5. Ensure the Documentation check box is selected.

6. Click Search.

Documents that match the query display in a results list.

7. To refine the results list, select one or more of the categories in the Filter By

pane. You can restrict results by

Product Group. Filters the list by product suite or division. For example,

you could retrieve documents related to the iManage, IDOL, Virage or

KeyView product suites.

Product. Filters the list by product. For example, you could retrieve

documents related to IDOL Server, Virage Videologger, or KeyView Filter.

Component. Filters the list by a product’s components. For example, you

could retrieve documents related to the Content or Category component in

IDOL.

Version. Filters the list by product or component version number.

Type. Filters the list by document format. For example, you could retrieve

documents in PDF or HTML format. Guides are typically provided in both

PDF and HTML format.

8. To open a document, click its title in the results list.

To download a PDF version of a guide, open the PDF version, click the Save

icon

in the PDF reader, and save the PDF to another location.

Related Documentation

The following documents provide more details about LiveVault:

LiveVault Release Notes

LiveVault Quick Start Guide

LiveVault Environment Configuration Guide

LiveVault Agent Distribution Guide

(9)

Conventions

LiveVault Appliance Build Guide

LiveVault Appliance Setup and User Guide

LiveVault Data Shuttle User’s Guide

LiveVault Media Restore Server Build Guide

LiveVault MRS Request Guide for Partners

LiveVault Web Services Programming Reference

LiveVault Vault Build Guide: Multiple Volume Vaults

LiveVault Vault Build Guide: Single Volume Vaults

Conventions

The following conventions are used in this document.

Notational Conventions

This guide uses the following conventions.

Convention

Usage

Bold User-interface elements such as a menu item or button. For example:

Click Cancel to halt the operation.

Italics Document titles and new terms. For example:

For more information, see the IDOL Server

Administration Guide.

An action command is a request, such as a query or indexing instruction, sent to IDOL Server.

(10)

About This Document

Command-line Syntax Conventions

This guide uses the following command-line syntax conventions.

monospace font File names, paths, and code. For example:

The FileSystemConnector.cfg file is installed in C:\Autonomy\FileSystemConnector\.

monospace bold Data typed by the user. For example:

Type run at the command prompt.

In the User Name field, type Admin.

monospace italics Replaceable strings in file paths and code. For example:

user UserName

Convention

Usage

Convention

Usage

[ optional ] Brackets describe optional syntax. For example: [ -create ]

| Bars indicate “either | or” choices. For example: [ option1 ] | [ option2 ]

In this example, you must choose between option1 and option2.

{ required } Braces describe required syntax in which you have a choice and that at least one choice is required. For example:

{ [ option1 ] [ option2 ] }

In this example, you must choose option1, option2, or both options.

(11)

Conventions

The use of punctuation—such as single and double quotes, commas, periods—

indicates actual syntax; it is not part of the syntax definition.

Notices

This guide uses the following notices:

required Absence of braces or brackets indicates required syntax in which there is no choice; you must type the required syntax element.

variable

<variable>

Italics specify items to be replaced by actual values. For example:

-merge filename1

(In some documents, angle brackets are used to denote these items.)

... Ellipses indicate repetition of the same pattern. For example:

-merge filename1, filename2 [, filename3 ... ]

where the ellipses specify, filename4, and so on.

Convention

Usage

CAUTION A caution indicates an action can result in the loss of data.

IMPORTANT An important note provides information that is essential to completing a task.

NOTE A note provides information that emphasizes or supplements important points of the main text. A note supplies information that may apply only in special cases—for example, memory limitations, equipment configurations, or details that apply to specific versions of the software.

(12)

About This Document

Autonomy Product References

This document references the following Autonomy products:

LiveVault Software and Service

Autonomy Customer Support

Autonomy Customer Support provides prompt and accurate support to help you

quickly and effectively resolve any issue you may encounter while using

Autonomy products. Support services include access to the Customer Support

Site (CSS) for online answers, expertise-based service by Autonomy support

engineers, and software maintenance to ensure you have the most up-to-date

technology.

To access the Customer Support Site, go to

https://customers.autonomy.com

The Customer Support Site includes:

Knowledge Base

: The CSS contains an extensive library of end user

documentation, FAQs, and technical articles that is easy to navigate and

search.

Case Center

: The Case Center is a central location to create, monitor, and

manage all your cases that are open with technical support.

Download Center

: Products and product updates can be downloaded and

requested from the Download Center.

Resource Center

: Other helpful resources appropriate for your product.

To contact Autonomy Customer Support by e-mail or phone, go to

http://www.autonomy.com/content/Services/Support/index.en.html

TIP A tip provides additional information that makes a task easier or more productive.

(13)

Contact Autonomy

Contact Autonomy

For general information about Autonomy, contact one of the following locations:

Europe and Worldwide

North and South America

E-mail: autonomy@autonomy.com Telephone: +44 (0) 1223 448 000 Fax: +44 (0) 1223 448 001 Autonomy Corporation plc Cambridge Business Park  Cowley Rd Cambridge CB4 0WZ United Kingdom E-mail: autonomy@autonomy.com Telephone: 1 415 243 9955 Fax: 1 415 243 9984 Autonomy, Inc. One Market Plaza Spear Tower, Suite 1900 San Francisco CA 94105 USA

(14)
(15)

C

HAPTER

1

Prepare for Disaster

Recovery

To ensure that you can recover your computer, you must back up the computer's

system state and all data on the computer, including the operating system and

program files, with the exception of the specific files and directories that are

excluded.

For more information about excluded files, refer to the help topic Automatic and

Recommended Backup Exclusions in the Web Management Portal Webhelp. This

is the only way to ensure that your backup is configured to fully protect your

computers and data.

Several disaster recovery (DR) procedures differ in the details, but this chapter

contains important information for all of the different Disaster Recovery scenarios.

Identify the DR procedure in this guide that best matches your situation, and then

print that chapter to use as a checklist.

Assumptions

Before You Begin

Terminology

What to Expect

Windows 2000 Server/Professional, or Windows Server 2003/2008

(16)

Chapter 1 Prepare for Disaster Recovery

Disaster Recovery with EFS (Encrypting File System)

Recover a VMware Computer

Recover a VMware Computer

Select the Correct Disaster Recovery Procedure

Assumptions

The following assumptions are made in these procedures:

You configured your backup to protect the full computer (including its general

files and directories, its databases and applications, and its system state) and

that the initial synchronization completed for the computer. The LiveVault

service can restore only files, directories, system state, and metadata that you

have backed up with the LiveVault Service.

All Windows functions worked before the disaster occurred.

All databases and applications functions worked before the disaster occurred.

Before You Begin

Before beginning the disaster recovery process, verify the following information:

Correct operating system version. Have the appropriate operating system

installation. This must be the same operating system version that was on the

computer before the disaster occurred, preferably from the original media that

came with the hardware itself.

As-built hardware configuration. If you are using new hardware, ensure you

have the original computer's hardware and operating system “as-built”

configuration information.

VMWare. If you are recovering a VMware

®

operating system, it must be a

guest computer, and not the host. If your VMware host fails, you must recover

that separately before recovering the guests.

Restore method. Determine whether data and system state will be delivered

on a restore device or over the Internet.

This depends on the amount of data you restore and your Internet connection

bandwidth. In some instances, if the amount of data is small and your

(17)

Terminology

amount of data is large, it can take many days to restore over the Internet, and

having a media device shipped to you is better for your needs. A media device

can usually be shipped in one or two days.

Current or historic backup version. Determine whether you want to restore

the most current version of the data or a historic version.

If a hardware crash led to this disaster, most likely the hardware was

experiencing problems for days or weeks before the actual crash. You might

want to select a version that occurred before any hardware problems became

apparent.

If possible, start the original computer in safe mode and check the logs, for

example the System Application log. Verify if input/output (I/O), permissions,

or disk errors are evident in the days preceding the disaster. If possible, select

a version that you backed up before these errors started to occur.

Terminology

The following terms are used in this procedure to distinguish between computers:

Original computer. This is the computer that experienced a failure or has

been lost due to a disaster.

Recovering computer/recovered computer. This is the computer you are

building as part of the disaster recovery procedures. When you complete this

procedure, this will be your computer running the LiveVault agent software.

Depending on the failure circumstances, these can be the same or different

physical computers.

What to Expect

There are many factors to achieving a successful disaster recovery, and some

difficulties can arise.

When performing the recovery to the recovering computer hardware, the following

mismatches are the most common causes of system recovery failure:

Hardware Abstraction Layer (HAL)

To find the HAL, go to Computer Management>Device Manager >

Computer.

(18)

Chapter 1 Prepare for Disaster Recovery

RAID device

Keyboard type (PS/2 or USB)

Mouse type (PS/2 or USB)

As-built information required for recovery

Operating system version

Drive letters

The following conditions commonly cause a disaster recovery to fail:

Insufficient disk space on the recovering computer

Failure to start in DSRM mode

Entering the wrong path to the LiveVault agent software during installation

Gather As-Built Configuration Information

In preparing for a disaster recovery, you need to gather the following information

for each original computer into an as-built profile:

Operating system version. For example, Windows 2008 Enterprise Server.

Windows installation directory. For example, C:\Windows.

Windows Service Pack version. For example Windows 2008 Enterprise

Server with SP 1.

Additional Windows Hotfixes. Required if Windows 2000 Professional.

It is good practice to keep complete as-built information for your computers. The

subsets of the as-built information provided below are required for performing

disaster recovery. They are not comprehensive lists of the as-built information that

you should keep for your records.

(19)

Windows 2000 Server/Professional, or Windows Server 2003/2008

Windows 2000 Server/Professional, or Windows

Server 2003/2008

In preparing for a disaster recovery, you need to gather the following information

for each original computer:

Disk subsystem

Drive letters and partitions (for example, D: and E:)

Partition size for each

Partition file system format (for example, NTFS or FAT)

Whether or not the computer is a Primary or Backup Domain Controller

Whether or not Active Directory is installed

Active Directory structure, including portion/subtree names

Hardware configuration

Whether or not dual NICs are configured

Computer Name

Video Card and Video Bus

Applications

All installed applications

Verification that all database and application functions work

Whether or not Internet Information Services (IIS) components installed

Local Administrator’s password

Domain Administrator’s password

Original Installation media information.

For example, if a computer was installed with HP disks, a disaster recovery to

a Dell computer can fail.

Location of systemroot when the system state backup was taken. By default

this is C:\Windows.

NOTE You cannot recover a computer with a AGP card to a computer with a PCI-based card, and vice-versa.

(20)

Chapter 1 Prepare for Disaster Recovery

This location can sometimes be different than the default, for example, when a

user upgrades a computer from Windows 2000 to Windows 2003.

Refer to the following article to recover a computer with a nonstandard

location for systemroot:

Recovering from failed system drive with nondefault %SystemRoot% folder

.

Microsoft Cluster Server (MSCS) Cluster Node

Disaster recovery for cluster nodes is not supported.

For a cluster node, rebuild the computer, and then submit a restore request for the

computer's data.

Disaster Recovery with EFS (Encrypting File System)

If you use EFS on your Windows 2003 servers, refer to the following article for

best practices to ensure successful data recovery:

Encrypting File System in Windows XP and Windows Server 2003

.

Recover a VMware Computer

If your VMware host fails, recover your VMware host before you recover the guest

operating systems.

Select the Correct Disaster Recovery Procedure

Although the general preparation above applies to almost any disaster recovery

scenarios, specific disaster recovery procedures can differ, depending on the

following conditions:

The operating system on the original computer.

The backup policy you used to back up the original computer.

The applications you are recovering.

(21)

Select the Correct Disaster Recovery Procedure

Chapters 2-5 each provide a different type of disaster recovery procedure,

depending on which operating system you are using and what type of server you

are recovering.

To recover a specific server, print out only the chapter you need, and use it as a

checklist.

(22)
(23)

C

HAPTER

2

Recover a Windows Server

with DSRM

This chapter explains how to perform a disaster recovery for a Windows 2000

Server, Windows 2000 Advanced Server, Windows Server 2003 server, or

Windows 2008 server.

Use this chapter to recover file and print servers, as well as database servers

such as an Exchange 2000 Server or SQL server.

You can recover both Active Directory domain controllers and member servers

with this procedure.

Perform a disaster recovery in the event of a computer failure or disaster such as:

Hard disk failure or corruption, requiring the system drive (usually c:) to be

rebuilt

Windows cannot start or has been corrupted

(24)

Chapter 2 Recover a Windows Server with DSRM

Summary of steps

To recover your computer from a disaster, complete the following procedures:

1.

Submit a media restore device request

2.

Suspend backups on the recovering computer

3.

Disable NIC on the recovering computer

4.

Verify the keyboard and mouse type

5.

Install the operating system on the recovering computer

6.

Install the same service packs as on the original computer

7.

Verify the computer name of the recovering computer

8.

Restart the computer

9.

Configure the local drives

10.

Remove IIS Components from recovering computer

11.

On Windows 2000/2003 computers, copy the boot.ini file

12.

Disable the screen saver

13.

Install the agent software on the recovering computer

14.

Restart Recovering Computer in DSRM

15.

Log on to recovering computer with local administrator rights

16.

Define and run a restore policy

17.

On Windows 2000/2003, compare boot.ini files

18.

Restart the recovering computer in normal mode

19.

Resolve short name issues

20.

Determine whether this is a domain controller

21.

Enable the NIC

22.

Test the recovered computer

23.

Update or repair the agent software

24.

Resume backups on the recovered computer

Detailed steps

Autonomy recommends that you print out this chapter, and use it as a checklist for your disaster

recovery process.

(25)

Detailed steps

Complete the following procedures to recover your computer.

1

Submit a media restore device request

If you request a restore device, it takes at least 24 hours to ship the device. However, you can proceed with these instructions while you wait for your restore device to arrive.

If you are restoring over the Internet, skip this step.

2

Suspend backups on the recovering computer

To suspend backups, complete the following steps:

1. In the left pane of the Web Management Portal, select the server. The Computer Summary page opens.

2. In the right-pane, click Properties. The Computer Properties page opens. 3. Click Edit properties.

The Edit Properties page opens. 4. Select the Suspend backup check box. 5. Click Save.

3

Disable NIC on the recovering computer

If the recovering computer contains two Network Interface Cards (NICs), disable one of them:

If the NIC is a separate card that you can remove, remove it.

 If it is an onboard NIC, disable the NIC using the BIOS interface. For more information, see the hardware vendor’s documentation.

Otherwise, disable the NIC through the Windows Device Manager after you install the Windows operating system (in step 6). You do not need to restart the computer after you disable the NIC.

4

Verify the keyboard and mouse type

If possible, use the same type of keyboard and mouse on the target computer as those on the original computer, that is, USB or PS/2.

(26)

Chapter 2 Recover a Windows Server with DSRM

5

Install the operating system on the recovering computer

Install the Windows operating system on the recovering computer, according to the following requirements. If possible, use the same media used to install the operating system on the failed computer.

Install the same operating system version of Windows that existed on the original

computer.

Name the computer to the same name as the original computer. The Windows setup

program provides a suggested computer name by default; for example “w2008xr1fan”. If the original computer was named “corporate.megacompany.com”, then you must assign the computer name “corporate” to the recovering computer.

Install Windows to the same directory on the recovering computer as on the original

computer.

For example, if the original computer's installation directory was c:\Windows, then install Windows to c:\Windows on the recovering computer.

Install only Accessories and Utilities when prompted to specify the Windows components

to install. Clear the check boxes for all components except Accessories and Utilities.

NOTE Do not install the other Windows components (for example, Active Directory, Certificate Services, or Internet Information Services). The disaster recovery will restore all other

components. If you install them, the restore and the disaster recovery can fail.

If you install the IIS components now, the IIS components that the LiveVault service restores will not work. However, if you must install the IIS components now (for example, because you use a system imaging solution that includes these components), you will remove them later in the process.

6

Install the same service packs as on the original computer

Install the same service packs that you had on the original computer.

7

Verify the computer name of the recovering computer

Ensure that recovering computer has the same computer name as that of the original computer. For example, if the original computer was named “corporate.megacompany.com”, then you must assign the computer name “corporate” to the recovering computer.

IMPORTANT Assign the correct computer name to the recovering computer in order to run the system state restore. Otherwise, the recovering computer will not start correctly and the disaster recovery procedure will fail.

8

Restart the computer

Restart the recovering computer.

(27)

Detailed steps

9

Configure the local drives

Configure the disk drive letters and partitions on the recovering computer to match those that existed on the original computer:

Use the same partitions. If the original computer had partitions D: and E:, create the

recovering computer partitions on D: and E:. Otherwise, data restores will fail.

Use adequately sized partitions. Ensure that the new partitions have adequate size to

handle the restored data.

For example, the recovering computer's C: drive must be at least as large as the original computer's C: drive.

Format the recovering computer's partitions to be the same file system format as the

original computer's partitions (NTFS, FAT, etc.).

10

Remove IIS Components from recovering computer

Determine whether any Internet Information Services (IIS) components were installed during the Windows installation. To remove any that were installed, complete the following steps: 1. Open Control Panel.

2. Select Add/Remove Programs. The Add/Remove Program page opens. 3. Click Add/Remove Windows Components.

The Windows Components Wizard opens.

4. In the Windows Components Wizard, locate the Internet Information Services item. If the IIS check box is selected, IIS components are installed.

5. If the IIS check box is selected, clear the check box and then follow the instructions in the wizard to remove the IIS services components. You do not need to restart the system.

NOTE If IIS components are installed and you do not perform this step, the IIS components that the LiveVault service restores may not work.

(28)

Chapter 2 Recover a Windows Server with DSRM

11

On Windows 2000/2003 computers, copy the boot.ini file

To copy the boot.ini file, complete the following steps:

1. Copy the boot.ini file.

The boot.ini is located in the recovering computer’s root directory.

2. Name the copy something similar to BootFromCD_101504.ini (where 101504 represents the current date) to ensure no confusion exists between the copy and the restored boot.ini file, and to differentiate this copy from any other copies.

3. Take note of the name of the boot.ini copy. The copy will be referenced later during the disaster recovery process.

12

Disable the screen saver

Complete the following steps:

1. Disable the screen saver. You cannot disable the screen saver after entering DSRM. 2. In the Power Options, disable the password protect. The password might change due to

(29)

Detailed steps

13

Install the agent software on the recovering computer

To install the agent software, complete the following steps:

1. Log into the LiveVault Web Management Portal. 2. Select New Computer from the navigation pane.

3. Select the appropriate Agent for your operating system, and click Download. 4. Do not select Run on Download.

5. Save the file to a location on the recovering computer, and then run it with Administrator rights.

6. To run the install wizard, select Run.

7. To install the software in the appropriate destination folders, follow the instructions in the installation wizard.

8. Install the agent software to the same location on the recovering computer as it was on the original computer. Also, install the LiveVaultData directory to the same location as the original computer. After you click Finish and then Configure, the computer lets you configure your software.

The configuration wizard opens.

9. To validate your account, provide your user name and password combination in the configuration wizard.

10.Click Next.

11.Select Recovering a complete system.

12.Select the name of the original computer you are recovering from the list of computer names.

13.Click Next.

14.Provide the encryption key password.

This is the encryption key password that you entered when you first installed the software on the original computer.

(30)

Chapter 2 Recover a Windows Server with DSRM

14

Restart Recovering Computer in DSRM

Restart Windows 2008 in safe mode

To use the BCDEDIT utility on Microsoft Windows 2008 recovering computers, complete the following steps:

1. In Windows, click Start, and then click Run. The Run window opens.

2. Type cmd and press Enter.

The Command Prompt window opens. 3. Enter the following command:

BCDEDIT /set safeboot dsrepair

4. Restart the computer.

The computer restarts in safe mode.

Restart Windows 2000/2003 in DSRM mode

On Windows 2000 and 2003 computers, use Directory Services Restore Mode (DSRM) even if the computer is not a domain controller. For more information about Directory Services Restore Mode, see your Windows documentation.

To restart the computer in DSRM mode, complete the following steps: 1. Restart the computer.

2. During the normal start-up process, look for the Windows start-up options message at the bottom of the window, for example:

For troubleshooting and advanced startup options for Windows 2003, press F8

3. When you see this message, press F8. You will only see this message for a few seconds. Press F8 while you can see it.

4. From the Windows Advanced Options Menu, select Directory Services Restore Mode and press Enter.

To restart in Directory Services Restore Mode if you did not press F8, complete the following steps:

1. Open the boot.ini file in the recovering computer's root directory.

2. Go to the [operating systems] section and add the following switch to the end of the line that specifies the start path:

/safeboot:dsrepair /sos

For example:

[operating systems] multi(0)disk(0)rdisk(0)partition(1)\

WINNT=;Microsoft Windows 2000 Server; /fastdetect /safeboot:dsrepair / sos

(31)

Detailed steps

15

Log on to recovering computer with local administrator rights

After the computer restarts, log on to Windows with local Administrator rights.

IMPORTANT After you log on, do not log off or lock the computer for the remainder of this procedure.

16

Define and run a restore policy

Define and run a restore job that restores all of your files, directories, and the system state.

IMPORTANT You must restore the system state when you restore your files and directories. To create the restore job, complete the following steps:

1. In the Web Management Portal, select the recovering computer. The Summary tab opens.

2. Select the Restore tab. 3. Click New Restore.

The Restore wizard opens.

4. If you requested a restore device earlier, you must wait for your restore device to arrive. After it arrives, attach the device, and select Restore from device on network.

If you are restoring over the Internet, select Restore data over the internet. The Selection tab opens.

5. Name the Restore policy.

6. Select the version and time of the backup to restore.

7. To select all files and directories that you want to restore, use the Selection tab. 8. Select the System State check box.

9. Select the Options tab. The Options tab opens.

10.Select the check box Overwrite open files when the computer is restarted. 11.To perform the restore, click Next.

The Restore job is submitted, and you return to the Restore summary tab. 12.Ensure that this restore has completed correctly before you go to the next step. 13.Do not restart the recovering computer before you go to the next step.

IMPORTANT You can perform a System State restore only once without a restart. If you cancel the restore, or it restarts, you must restart the recovering computer before you try again.

(32)

Chapter 2 Recover a Windows Server with DSRM

17

On Windows 2000/2003, compare boot.ini files

To compare the restored boot.ini file and the copy of the boot.ini file, complete the following steps:

1. Go to the computer's root directory, and open both the restored boot.ini file (for example, boot.ini) and the copy of the boot.ini file (for example,

BootFromCD_101504.ini) that you made earlier in this procedure.

2. Compare the boot drive value (that is, the number of the partition from which the computer will start, for example: partition(1)).

3. If the boot drive values in these files match, then skip to Restart the computer. If the boot drive values in these files do not match, continue with this procedure. The restored boot.ini file's (for example, boot.ini) read-only attribute is set.

4. To clear the read-only attribute, complete the following steps: a. In Windows Explorer, go to and select the file.

b. Right-click the file and select Properties on the short-cut menu.

c. In the Properties dialog box, on the General tab, in the Attributes group, clear the Read-only check box. Then click OK.

5. Change the value in the restored boot.ini file (for example, boot.ini) to match the value specified in the copy of the boot.ini file (for example,

BootFromCD_101504.ini).

Your boot.ini configuration might require you to update the boot drive value for multiple lines in the restored boot.ini file.

CAUTION

(33)

Detailed steps

18

Restart the recovering computer in normal mode

Resume normal startup: Windows 2008 only

To resume normal startup, complete the following steps: 1. In Windows, click Start, and then Run.

The Run window opens. 2. Type cmd and press Enter.

The Command Prompt window opens. 3. Enter the following command:

BCDEDIT /deletevalue safeboot

Restart Windows 2000 and 2003 computers in normal mode

Restart the recovering computer in normal mode.

If you receive a Windows message that indicates that you must restart the computer because the computer has found new devices, restart the computer again as specified.

For example, if you are running Windows 2000 Service Pack 4 or followed the procedure in Microsoft Knowledge Base article 810161, at restart, Windows finds all devices as new hardware. Some services might not restart. You receive a prompt to restart the computer again (possibly multiple times) as the computer finds new devices. In this case, do not restart the computer each time you receive a prompt.

(34)

Chapter 2 Recover a Windows Server with DSRM

19

Resolve short name issues

If the SQL service fails to restart following a restore, there might be a short-name discrepancy. To determine if a short-name discrepancy is the cause of the problem, complete the following steps:

1. In Windows, click Start, and then Settings>Control Panel>Administrative

Tools>Services.

2. In the list of services on the right of the panel, right-click mssqlserver and choose properties.

3. Note the path and folder that Windows is looking in for the program.

4. In Windows or at a command prompt, navigate to the folder above, and note whether the program exists in that folder.

If the program is there, the failure of SQL to launch is not due to a short-name discrepancy. For more information, consult your SQL documentation.

If the program is not there, you have a short-name discrepancy. Continue with this procedure.

5. Complete the steps below to open a command prompt. a. In Windows, click Start, and then Run.

The Run window opens. b. Type cmd and press Enter.

The Command Prompt window opens.

c. Enter the following command to change directory to Program Files:

cd \Program Files

d. Enter the following command:

dir/x micro*

e. Press Enter.

6. Browse to each folder until you locate the SQL program. Temporarily rename the folder that contains the SQL program.

For example, if the folder containing the SQL program is Micros~1, rename Micros~1 to Temp_Micros~1. This forces Windows to reassign a new short name to that folder.

(35)

Detailed steps

7. Temporarily rename the folder that Windows associates with the SQL program. For example, if the service is looking in Micros~4 to launch the program, rename

Micros~4 to Temp_Micros~4. This forces Windows to reassign a new short name to that folder, which reestablishes the proper sequence of short names, so that SQL can find the correct folder and execute. You might have to temporarily rename other short-name folders as well, until the correct folder shuffles to the correct place in the numbering sequence. For example, when you rename Micros~1, the old Micros~2 becomes Micros~1 and the old Micros~3 becomes Micros~2. Keep track of the folders to avoid creating other discrepancies.

8. Rename the folder that contains the program to its original name. Windows dynamically reassigns the proper short name to this folder. Rename the other folder to its original name. Windows dynamically reassigns another short name to this folder.

20

Determine whether this is a domain controller

If this computer is not a domain controller, go to Enable the NIC. If the computer is a domain controller, complete the following steps: 1. Click the Start menu.

2. Select Administrative Tools>Active Directory Users and Computers. A list of domain controllers opens.

If only one Domain Controller is listed, skip to the step Enable the NIC. If other domain controllers are present and running, go to Enable the NIC.

If the recovering computer is the first domain controller of a multi-domain environment, see Restore a domain controller.

21

Enable the NIC

If you had to disable a NIC for the disaster recovery, complete the following steps to enable that NIC:

If the NIC is a separate card that was removed, insert the card.

 If it is an onboard NIC, use the BIOS interface to enable the NIC. For more information, see the hardware vendor’s documentation.

 If you disabled the NIC through the Windows Device Manager, it might be enabled for you. Verify the NIC's status in Device Manager and enable it if necessary.

After you enable the NIC, you might need to restart the recovered computer, and then configure the NIC.

(36)

Chapter 2 Recover a Windows Server with DSRM

22

Test the recovered computer

If the recovered computer fails to appear on the network, verify the following indicators:

Analyze the ipconfig output for errors.

Analyze Device Manager for errors.

Analyze the system logs for errors.

If necessary, refer to your Windows documentation to perform these tasks.

23

Update or repair the agent software

It is possible that the restore might have caused older files to be installed on the recovering system, which can cause an Agent software conflict.

To ensure that you have no conflict, complete the following steps: 1. Upgrade your computer to the most recent version of Agent software. 2. If you receive an option to Repair, choose the option.

3. When you are prompted to restart, restart the computer.

24

Resume backups on the recovered computer

To resume backups, complete the following steps:

1. In the Web Management Portal, select the recovering computer. 2. In the right-pane, click Properties.

The Properties page opens.

1. Click Edit properties.

The Edit Properties page opens. 3. Select the Resume backup check box.

The Backup Configuration Confirmation page opens. 4. Click Save.

(37)

C

HAPTER

3

Recover an Exchange Server

on Windows 2003 Computers

This procedure explains how to perform a disaster recovery for a Microsoft

Exchange 2003/2007 Server on Windows 2003 computers.

Backup and recovery of Exchange 2003 is only supported on Windows 2003, SP1

or higher.

Backup and recovery of Exchange 2007 is supported on all operating systems on

which Exchange 2007 runs.

To recover Exchange 2007 on Windows 2008 computers, see the chapter

Recover an Exchange Server on Windows 2008 computers

.

Perform a disaster recovery in the event of a computer failure or disaster such as:

Hard disk failure or corruption, requiring you to rebuild the system drive

Windows cannot start or has been corrupted

Physical computer loss

Assumptions

The following assumptions are made in these procedures:

You configured your backup to protect the full computer (including its general

files and directories, its databases and applications, and its system state) and

(38)

Chapter 3 Recover an Exchange Server on Windows 2003 Computers

that the initial synchronization completed for the computer. The LiveVault

service can restore only files, directories, system state, and metadata that you

have backed up with the LiveVault Service.

You configured an Exchange backup policy to protect your Exchange data in a

transactionally-safe manner.

For more information on backing up Exchange with an Exchange backup

policy, refer to the LiveVault Web Management Help system.

All Windows functions worked before the disaster occurred.

All databases and applications functions worked before the disaster occurred.

Summary of steps

To recover your computer from a disaster, complete the following procedures:

1.

Submit a media restore device request

2.

Suspend backups on the original computer

3.

Disable NIC on the recovering computer

4.

Verify the keyboard and mouse type

5.

Install the operating system on the recovering computer

6.

Install the same service packs as on the original computer

7.

Verify the computer name of the recovering computer

8.

Restart the computer

9.

Configure the local drives

10.

Remove IIS Components from recovering computer

11.

Copy the boot.ini file

12.

Disable the screen saver

13.

Install the agent software on the recovering computer

14.

Restart Recovering Computer in DSRM

15.

Log on to recovering computer with local administrator rights

16.

Define and run a file restore policy

17.

Define and run an Exchange restore policy

18.

Compare boot.ini files

(39)

Detailed steps

20.

Enable the NIC

21.

Test the recovered computer

22.

Update or repair the agent software

23.

Resume backups on the recovered computer

24.

Complete the Recovery on Exchange 2007 CCR Configurations

Detailed steps

Complete the following procedures to recover your computer Autonomy

recommends that you print out this chapter, and use it as a checklist for your

disaster recovery process.

Complete the following procedures to recover your computer.

1

Submit a media restore device request

If you request a restore device, it takes at least 24 hours to ship the device. However, you can proceed with these instructions while you wait for your restore device to arrive.

If you are restoring over the Internet, skip this step.

2

Suspend backups on the original computer

To suspend backups, complete the following steps:

1. In the LiveVault Web Management Portal, select the server. The Computer Summary page opens.

2. In the right-pane, click Properties. The Computer Properties page opens. 3. Click Edit properties.

The Edit Properties page opens. 4. Select Suspend backup. 5. Click Save.

(40)

Chapter 3 Recover an Exchange Server on Windows 2003 Computers

3

Disable NIC on the recovering computer

If the recovering computer contains two Network Interface Cards (NICs), disable one of them:

If the NIC is a separate card that you can remove, remove it.

 If it is an onboard NIC, disable the NIC using the BIOS interface. For more information, see the hardware vendor’s documentation.

Otherwise, disable the NIC through the Windows Device Manager after you install the Windows operating system (in step 6). You do not need to restart the computer after you disable the NIC.

4

Verify the keyboard and mouse type

If possible, use the same type of keyboard and mouse on the target computer as those on the original computer, that is, USB or PS/2.

5

Install the operating system on the recovering computer

Install the Windows operating system on the recovering computer, according to the following requirements. If possible, use the same media used to install the operating system on the failed computer.

Install the same operating system version of Windows that existed on the original

computer.

Name the computer to the same name as the original computer. The Windows setup

program provides a suggested computer name by default; for example “w2008xr1fan”. If the original computer was named “corporate.megacompany.com”, then you must assign the computer name “corporate” to the recovering computer.

Install Windows to the same directory on the recovering computer as on the original

computer. For example, if the original computer's installation directory was c:\Windows, then install Windows to c:\Windows on the recovering computer.

Install only Accessories and Utilities when prompted to specify the Windows

components to install. Clear the check boxes for all components except Accessories and Utilities.

Do not install the other Windows components (for example, Active Directory, Certificate Services, or Internet Information Services). The disaster recovery will restore all other components. If you install them, the restore and the disaster recovery can fail.

If you install the IIS components now, the IIS components that the LiveVault service restores will not work. However, if you must install the IIS components now (for example, because you use a system imaging solution that includes these components), you will remove them later in the process.

(41)

Detailed steps

6

Install the same service packs as on the original computer

Install the same service packs that you had on the original computer.

7

Verify the computer name of the recovering computer

Ensure that recovering computer has the same computer name as that of the original computer.

For example, if the original computer was named “corporate.megacompany.com”, then you must assign the computer name “corporate” to the recovering computer.

IMPORTANT Assign the correct computer name to the recovering computer in order to run the system state restore. Otherwise, the recovering computer might not start correctly and the disaster recovery procedure will fail.

8

Restart the computer

Restart the recovering computer.

9

Configure the local drives

Configure the disk drive letters and partitions on the recovering computer to match those that existed on the original computer:

Use the same partitions. If the original computer had partitions D: and E:, configure the

recovering computer partitions on D: and E:. Otherwise, data restores may fail.

Use adequately sized partitions. Ensure that the new partitions have adequate size to

handle the restored data. For example, the recovering computer's C: drive must be at least as large as the original computer's C: drive.

Format the recovering computer's partitions to be the same file system format as the

(42)

Chapter 3 Recover an Exchange Server on Windows 2003 Computers

10

Remove IIS Components from recovering computer

Determine whether any Internet Information Services (IIS) components were installed during the Windows installation. To remove any that were installed, complete the following steps: 1. Open Control Panel.

2. Select Add/Remove Programs. The Add/Remove Program page opens. 3. Click Add/Remove Windows Components.

The Windows Components Wizard opens.

4. In the Windows Components Wizard, locate the Internet Information Services item. If the IIS check box is selected, IIS components are installed.

5. If the IIS check box is selected, clear the check box and then follow the instructions in the wizard to remove the IIS services components. You do not need to restart the system.

NOTE If IIS components are installed and you do not perform this step, the IIS components that the LiveVault service restores may not work.

11

Copy the boot.ini file

To copy the boot.ini file, complete the following steps:

1. Copy the boot.ini file (in the recovering computer's root directory).

2. Name the copy something similar to BootFromCD_101504.ini (where 101504 represents the current date) to ensure no confusion exists between the copy and the restored boot.ini file, and to differentiate this copy from any other copies.

This copy will be referenced later during the disaster recovery, so note the name of the file.

12

Disable the screen saver

Complete the following steps:

1. Disable the screen saver. You cannot disable the screen saver in DSRM.

2. In the Power Options, disable the password protect. The password might change due to the restore.

(43)

Detailed steps

13

Install the agent software on the recovering computer

To install the agent, complete the following steps:

1. From the Web Management Portal, select New Computer from the navigation pane. 2. Select the appropriate Agent for your operating system, and click Download. 3. Do not select Run on Download.

4. Save the file to a location on the recovering computer, and then run it with Administrator rights.

5. To run the install wizard, select Run.

6. To install the software in the appropriate destination folders, follow the instructions in the installation wizard.

7. Install the agent software to the same location on the recovering computer as it was on the original computer. Also, install the LiveVaultData directory to the same location as the original computer. After you click Finish and then Configure, the computer lets you configure your software.

The configuration wizard opens.

8. To validate your account, provide your user name and password combination in the configuration wizard.

9. Click Next.

10.Select Recovering a complete system.

11.Select the name of the original computer you are recovering from the list of computer names. 12.Click Next.

13.Provide the encryption key password.

This is the encryption key password that you entered when you first installed the software on the original computer.

(44)

Chapter 3 Recover an Exchange Server on Windows 2003 Computers

14

Restart Recovering Computer in DSRM

To restart the computer in Directory Services Restore Mode (DSRM), complete the following steps:

1. Restart the computer.

2. During the normal start-up process, look for the Windows start-up options message at the bottom of the window, for example:

For troubleshooting and advanced startup options for Windows 2003, press F8

3. When you see this message, press F8. You will only see this message for a few seconds. Press F8 while you can see it.

4. From the Windows Advanced Options Menu, select Directory Services Restore Mode and press Enter.

To restart in Directory Services Restore Mode if you did not press F8, complete the following steps:

1. Open the boot.ini file in the recovering computer's root directory.

2. Go to the [operating systems] section and add the following switch to the end of the line that specifies the start path:

/safeboot:dsrepair /sos

For example:

[operating systems] multi(0)disk(0)rdisk(0)partition(1)\

WINNT=;Microsoft Windows 2000 Server; /fastdetect /safeboot:dsrepair / sos

3. Restart the recovering computer.

IMPORTANT Stay in DSRM mode until you are instructed to restart into normal mode.

15

Log on to recovering computer with local administrator rights

After the computer restarts, log on to Windows with local Administrator rights.

IMPORTANT After you log on, do not log off or lock the computer for the remainder of this procedure.

(45)

Detailed steps

16

Define and run a file restore policy

Define and run a restore job that restores all of your files, directories, and the system state.

IMPORTANT You must restore the system state when you restore your files and directories. To create the restore job, complete the following steps:

1. In the Web Management Portal, select the recovering computer. The Summary tab opens.

2. Select the Restore tab. 3. Click New Restore.

The Restore wizard opens.

If you requested a restore device earlier, you must wait for your restore device to arrive. After it arrives, attach the device, and select Restore from device on network.

If you are restoring over the Internet, select Restore data over the internet. The Selection tab opens.

4. Name the Restore policy.

5. Select the version and time of the backup version to restore.

6. To select all files and directories that you want to restore, use the Selection tab. 7. Select the System State check box.

8. Select the Options tab. The Options tab opens.

9. Select the check box Overwrite open files when the computer is restarted. 10.To perform the restore, click Next.

The Restore job is submitted, and you return to the Restore summary tab. 11.Ensure that this restore has completed correctly before you go to the next step. 12.Do not restart the recovering computer before you go to the next step.

IMPORTANT You can perform a System State restore only once without a restart. If you cancel the restore, or it restarts, you must restart the recovering computer before you try again.

(46)

Chapter 3 Recover an Exchange Server on Windows 2003 Computers

17

Define and run an Exchange restore policy

To restore an Exchange policy, complete the following steps:

1. In the LiveVault Web Management Portal, select the recovering computer. The Summary tab opens.

2. Select the Restore tab. 3. Click New Restore.

The Restore wizard page opens.

If you requested a restore device earlier, you must wait for your restore device to arrive. After it arrives, attach the device, and select Restore from device on network.

If you are restoring over the Internet, select Restore data over the internet. The What would you like to restore page opens.

4. Select Exchange Server, and then click Next.

5. In the Name to use for this restore request box, enter a name for the restore job. 6. Select Policy filter, and then select Exchange.

7. From the Version menu, select the backup version from which you want to restore the Mailbox and Public Folder stores. The most recent version is the default.

8. Select the top-level object in the object view of your Exchange Server's backed-up file structure. This ensures that you will restore all the files on the server.

9. In the Restore Request form, select the Options tab. 10.Select File Restore.

11.Select Overwrite existing files even if restored file is older. 12.Select Overwrite open files when the computer is rebooted.

13.Select Restore the Original Backup Security Attributes, and then click Next. The Restore Summary page opens.

14.Review your selections.

15.Perform one of the following actions:

To make changes to the restore request, click Previous.

To accept the restore request and start the restore process, click Done.

After you click Done, the LiveVault service starts to process of the restore request.

16.Review the restore job log on the Exchange Server computer to which you restored the files. Verify that the Mailbox and/or Public Folder Store was restored as expected.

(47)

Detailed steps

18

Compare boot.ini files

To compare the restored boot.ini file and the copy of the boot.ini file, complete the following steps:

1. Go to the computer's root directory, and open both the restored boot.ini file (for example, boot.ini) and the copy of the boot.ini file (for example, BootFromCD_101504.ini) that you made earlier in this procedure.

2. Compare the boot drive value (that is, the number of the partition from which the computer will start, for example: partition(1)).

3. If the boot drive values in these files match, then skip to Restart the computer. If the boot drive values in these files do not match, continue with this procedure. The restored boot.ini file's (for example, boot.ini) read-only attribute is set.

4. To clear the read-only attribute, complete the following steps: a. In Windows Explorer, go to and select the file.

b. Right-click the file and select Properties on the short-cut menu.

c. In the Properties dialog box, on the General tab, in the Attributes group, clear the Read-only check box. Then click OK.

5. Change the value in the restored boot.ini file (for example, boot.ini) to match the value specified in the copy of the boot.ini file (for example, BootFromCD_101504.ini). Your boot.ini configuration might require you to update the boot drive value for multiple lines in the restored boot.ini file.

CAUTION

If you fail to update the restored

boot.ini

file, you cannot restart the computer.

19

Restart the recovered computer in normal mode

Restart Windows 2003 computers in normal mode

Restart the recovering computer in normal mode.

If you receive a Windows message that indicates that you must restart the computer because the computer has found new devices, restart the computer again as specified.

Figure

Updating...

References