Arkeia PI Disaster Recovery

ARKEIA
DISASTER RECOVERY
August 2005
Copyright
This manual, including all the figures and screenshots it contains, is
Copyright 2001-2005 by Arkeia SA, All Rights Reserved.
Arkeia Arkeia SA
1808 Aston Avenue 31, rue Delizy
Suite 220 93692 Pantin Cedex
Carlsbad, CA 92008 France
USA
Tel : +1 (760) 431 - 1319 Tel : +33 (0)1 48 10 89 89

Fax : +1 (760) 602 - 8599 Fax : +33 (0)1 48 10 89 90
US, Canada, Mexico, South America, Europe, Middle East Africa, and central
Australia, Pacific Rim, China Asia
Linux is a registered trademark owned worldwide by Linus Torvalds.
Document edition: 1.2 Dated: 19-Aug-2005 Status: Released
2 Arkeia Disaster Recovery

ARKEIA SOFTWARE LICENSE AGREEMENT
In order to preserve and protect its rights within the framework of currently applicable leg-
islation, Arkeia Corporation and Arkeia SA, hereinafter referred to as ARKEIA,
does not sell rights to this SOFTWARE, but grants the right to use this SOFT-
WARE, within the terms of this license agreement, hereinafter referred to as
LICENSE AGREEMENT, and expressly retains ownership rights to all ARKEIA
SOFTWARE. If you do not agree with all the terms and conditions of this
LICENSE AGREEMENT you can obtain a refund by returning the SOFTWARE,
all its manuals, its documentation and the original sealed license envelope, in sal-
able condition, to the place you obtained them.
1. GRANT OF LICENSE. In return for payment of LICENSE fees included in

the cost of the SOFTWARE and your commitment to comply with the terms
and conditions of this LICENSE AGREEMENT as well as the limited war-
ranty attached to, ARKEIA, the licenser, grants to you, the LICENSEE, the
non-exclusive and non-transferable right to use the SOFTWARE on a single
computer known as the backup server, here in after referred to as the
SERVER, and its associated client computers, here in after referred to as
CLIENTS, provided that the terms and conditions of the license are complied
with.
If the SERVER or CLIENT on which the SOFTWARE is operated consti-

tutes a system with several users, the LICENSE AGREEMENT shall apply
to all such users without incurring additional costs.
ARKEIA reserves all rights that are not expressly granted to the LICENSEE.
2. COPYRIGHT. The beneficiary of the LICENSE is the owner of the magnetic

media, or any other type of media on which the SOFTWARE is initially, or
subsequently, recorded or stored. However, this License is granted on the
express condition that ARKEIA retains copyrights to the SOFTWARE
recorded on the original media as well as copyrights to all copies made, irre-
spective of the format and the media of said original media and said copies
This LICENSE does not constitute a sale of the original SOFTWARE or of

any copy thereof.
3. REPRODUCTION RESTRICTIONS. This SOFTWARE and the accompa-

nying written materials are protected by copyright. Unauthorized reproduc-
tion of the SOFTWARE, including its modification, integration or inclusion
in another software, or of the accompanying written materials is strictly for-
bidden. The LICENSEE is liable to legal sanctions for any copyright
infringement caused or prompted by any breach, on the part of the LIC-
ENSEE, of the terms and conditions of this LICENSE AGREEMENT.
Subject to the above-mentioned restrictions, the LICENSEE is authorized to

make one (1) backup copy of the SOFTWARE if said SOFTWARE is not
copy-protected.
Arkeia Disaster Recovery 3

- Notice of copyright must appear on the backup copy.
4. RESTRICTIONS OF USE. The LICENSEE is authorized to physically

transfer the SOFTWARE from one SERVER to another SERVER on condi-
tion that said SOFTWARE is completely and totally removed from the origi-
nal SERVER. Electronic transfers of the SOFTWARE from one SERVER to
another within a distribution network for the purpose of copying the SOFT-
WARE or the accompanying written materials are strictly forbidden. The
LICENSEE shall not modify, adapt, translate, reverse engineer, decompile,
disassemble or create written materials based on the SOFTWARE, and shall
not modify, adapt, translate or write literature based on the written materials
without the prior express written consent from ARKEIA.
5. TRANSFER RESTRICTIONS. No person whomsoever shall be authorized

to operate this SOFTWARE without the prior express written consent from
ARKEIA. Any beneficiary of a transfer thus authorized shall be bound by the
terms and conditions of this LICENSE AGREEMENT and the limited war-
ranty attached there. Under no circumstances shall the LICENSEE be enti-
tled to transfer, convey, lease or sell the SOFTWARE, nor shall it be entitled
to dispose thereof, in any manner whether temporary or permanent, except
where otherwise expressly provided for herein.
6. CANCELLATION. This LICENSE AGREEMENT shall remain valid until

its cancellation and shall be canceled, as a right without prior notice by
ARKEIA should the LICENSEE fail to comply with the terms and condi-
tions of this LICENSE AGREEMENT. In the event of cancellation, the LIC-
ENSEE shall immediately destroy all written materials and all copies of the
SOFTWARE, including modified copies, where appropriate.
7. MISCELLANEOUS. This LICENSE AGREEMENT is governed by the

laws of the State of California (USA) if the LICENSEE acquired the SOFT-
WARE in the USA with respect to ARKEIA, their successors and assigns.
This LICENSE AGREEMENT is governed by the laws of the country of
France if the LICENSEE acquired the SOFTWARE in any country except
the USA, with respect to ARKEIA, their successors and assigns.
If you would like further information on this LICENSE AGREEMENT, please

write to:
Arkeia Corporation
1808 Aston Avenue
Suite 220
Carlsbad, CA 92008
USA

WARRANTY *
ARKEIA warrants its SOFTWARE for a period of ninety (90) days as of the date
of delivery thereof. This warranty also includes reconditioning or replacing SOFT-
WARE media.
ARKEIA does not warrant and does not enter into any commitments regarding the
content of the documentation and the software. ARKEIA further disclaims any
implicit warranties tied to the sale of the right to use license of this SOFTWARE
with respect to its quality, its results, its merchantability or its suitability for a par-
ticular purpose. Consequently, the license to use this SOFTWARE is granted as
is, without any promise being made.
In the event of a defect in the software or in the documentation, the LICENSEE,

and not ARKEIA, its dealers, distributors, agents, or employees shall bear all costs
needed for servicing, repair or correction.
Under no circumstances shall ARKEIA, or anyone else participating in the design,

production and delivery of this SOFTWARE, be liable for any damages, whether
direct, indirect, secondary or incidental, including, but not limited to, damages
caused by loss of profit, business interruption, loss of information or any other
loss, resulting from the use of this SOFTWARE, even if ARKEIA has been
informed of the possibility of such damages.
Information or advice given verbally or in writing by ARKEIA, its dealers, distrib-

utors, agents or employees shall not constitute a warranty, nor affect in any way
this warranty, and as such, the recipient shall not in any way depend on any such
information or advice.
Arkeia and ARKEIA SOFTWARE are registered trademarks (TM) of ARKEIA

Software, All Rights Reserved. All other trademarks mentioned in this documenta-
tion are the property of their respective owners.
(*) Warranty may vary according to local regulations.
Arkeia Disaster Recovery 5

TABLE OF CONTENTS
Copyright ..........................................................................................................2
ARKEIA SOFTWARE LICENSE AGREEMENT ...............................................3
WARRANTY * ...................................................................................................5
Client DR backup ............................................................................................10
Client DR restoration ......................................................................................11
Server DR backup ..........................................................................................11
Server DR restoration .....................................................................................11
Allow Disaster Recovery info ..........................................................................12
Create a Disaster Recovery toolbox ...............................................................12
Dedicated tapes and tape pools .............................................................12
Backup the client and server computer configuration.............................13
Backup the server database and index ..................................................14
Create a recovery diskette......................................................................15
Backup for Disaster Recovery ........................................................................16
Re-configure the network interface .................................................................19
Re-configure the network................................................................................21
Restore the file system ...................................................................................26
Format and partition the new disks.........................................................27
Label the file systems .............................................................................28
Activate the swap partition......................................................................28
Restore the data .............................................................................................29
List of data tapes needed .......................................................................29
Load the data tapes ................................................................................29
Monitor the restoration............................................................................29
Recover the bootloader ..................................................................................30
Boot the new server........................................................................................31
Restore the server database and index ..........................................................32
Complete the server restoration .....................................................................32
Update the index ....................................................................................32
Recover the server bootloader .......................................................................32
Supported SCSI cards ....................................................................................32
Disaster Recovery DR Manual 7

8 Disaster Recovery DR Manual
ARKEIA DISASTER RECOVERY
When a large portion, or all, of the data in a client or server is destroyed, you can
use Disaster Recovery to rebuild the computer and put it back on line, provided
you have properly configured Arkeia Disaster Recovery (DR), and have an effec-
tive backup regime in place.
This manual tells you how to use Arkeia and the Arkeia Disaster Recovery appli-
cation to:
1. prepare for a disaster recovery, and
2. restore a client, or server.
The Disaster Recovery Disaster Recovery application can be used under both the
Arkeia Network Backup and Arkeia Server backup applications.
!
Using Disaster Recovery Disaster Recovery for an Arkeia server
computer requires an additional license, which can be obtained
from Arkeia sales. Go to the Arkeia website www.arkeia.com to
puchase a license, or for a free demonstration license.
Please make sure that you have the correct license, by checking with Arkeia,
before attempting to start a Disaster Recovery on an Arkeia server or client.
It is important to test the Disaster Recovery procedure to make sure it supports the
hardware that will be restored, especially using the drivers that are present on the
Arkeia Disaster Recovery CD.
How Disaster Recovery works

Disaster Recovery provides system recovery and data restoration functions. It
allows you to quickly recover from critical storage failure or common hardware
problems. It also allows systems to be quickly put back online in the case of more
serious events, such as fire or floods, but only if the backup tapes are available.
You can only restore what you have backed up, and you can only restore the back-
ups you can find.
!
The Disaster Recovery procedure is entirely based on the avail-
ability of backup tapes (or other backup media). If the backup
media is damaged or missing, there is nothing that Disaster
Recovery (or any other backup software) can do. For this reason,
we highly recommend that you make copies of all backup media.
Disaster Recovery provides a simple utility to quickly duplicate
backup media, in its standard distribution. For more information
on this utility, refer to the Arkeia User Manual section titled Dupli-
cate a tape on page 221.

At present, Disaster Recovery is only available for Linux clients
and servers.
Disaster Recovery is a four-stage process:

1. System information. Important system information must be backed-up by
Arkeia for each server and client computer. This information will allow the
Disaster Recovery procedure rebuild the network and the disk configuration
of the damaged computers.
2. Total backup. A total backup is performed by Arkeia, to have a starting point
for the recovery procedure.
3. Intermediate backups. A continuing backup procedure must be established.
Depending on the importance of a given computer, the amount of its mis-
sion-critical data, and the rate at which this data changes, it may be advisable
to create a backup schedule, using the Periodic backup function of Disaster
Recovery. For more information on this function, refer to the Arkeia User
Manual chapter Chapter 8:Periodic backup on page 117.
4. System restoration. Restoration requires the computer operating system to
be rebuilt first, then the client or server files to be restored from backups.
Through these four stages, Disaster Recovery is able to:

return any Linux computer back to the state it was in before disaster struck,
or
completely restore the system and data to a new computer
using your backups and the Arkeia Disaster Recovery CD-ROM provided with the
Disaster Recovery plug-in.
Disaster recovery: client and server

The Disaster Recovery process is designed to restore a computer, whether it is an
Arkeia server or client, to the exact state it was in at its last avaiilable backup. To
do this, it has to take into account:
the parameters and configuration of the hard disk,
the network card and network parameters, and
the Arkeia database and index of files backed up (servers only)
The procedure for backup and recovery of a client is different to the procedure for
a server. Both procedures are described in detail in separate sections of this man-
ual. The procedures are summarized below.
Client DR backup
1. Backup the system information required to reconstruct the client computer:
a. Disk configuration - partitions, file systems, file system block size, file
system label.
b. Network configuration - network card, TCP/IP parameters.
2. Backup all the files present on the computer.

Client DR restoration
1. Boot the target computer from the Arkeia DR CD-ROM.
2. Enter the system parameters as they are requested by the Arkeia DR program
which runs from the Arkeia DR CD-ROM.
3. The DR program recovers the client system configuration from the Arkeia
backup server.
4. The client computer configuration is reconstructed by the DR program:
a. hard disks are partitioned,
b. the partitions are formatted, and
c. the partitions are mounted.
5. The client data is restored to the hard disks.
6. The original bootloader is restored.
7. The recovered client is restarted and brought online.
Server DR backup
1. Backup all the files present on the server computer.
2. Backup the system information required to reconstruct the server:
a. Disk configuration - partitions, file systems, file system block size, file
system label.
b. Network configuration - network card, TCP/IP parameters.
c. Server database (dbase/f3xxx) and index (dbase/03dbtree) of server
backups (where xxx indicates a directory).
Server DR restoration
1. Boot the target computer from the Arkeia DR CD-ROM.
2. Enter the name of the tape drive where the tapes containing the server data
will be loaded. If you have a tape library, it must be used in a single drive
manually-loaded mode during the DR restoration.
3. The DR program recovers the server system configuration from the nomi-
nated tape drive, including the Arkeia database and index.
4. The server computer configuration is reconstructed by the DR program:
a. hard disks are partitioned,
b. the partitions are formatted,
c. the partitions are mounted.
5. The server data files are restored to the hard disks.
6. The original bootloader is restored.
7. The recovered server is restarted and brought online.
How to prepare for Disaster Recovery

Successful Disaster Recovery requires thorough preparation. Following the steps
in this section will ensure that your system is backed up for Disaster Recovery, and
that the information necessary for a full restoration of systems and data is avail-
able.

Allow Disaster Recovery info
When creating Savepacks, adding trees to a Savepack or reconfiguring the trees in
a Savepack, click on to see the Advanced options screen which con-

tains the Disaster recovery info allowed checkbox:
Click to check this box to include the information Arkeia needs for Disaster
Recovery in the backup of the associated Savepack or tree. If a Savepack has this
checkbox filled, the trees added to it will inherit the property. The Allow disaster
recovery property for an individual tree can be changed
An individual tree can have the Allow disaster recovery property inherited from its
parent Savepack reversed through the Tree advanced options menu.
Create a Disaster Recovery toolbox

Disaster Recovery procedures are usually activated under emergency conditions,
so it is useful to prepare a set of Disaster Recovery tools which will contain every-
thing you need to restore a client or server, in less stressful circumstances. Your
Disaster Recovery toolbox will contain:
Tapes and tape pool dedicated solely to the Disaster Recovery backups of
your server and clients.
Backup of the system configuration information for the server and client
computers.
Backup of the server database and index.
A recovery diskette containing the system configuration information for each
server and client computer.
Dedicated tapes and tape pools

You are strongly advised to create tapes and tape pools dedicated to Disaster
Recovery and the data required to restore servers and clients from bare metal.
These tapes should be kept in a safe and secure place, either off-site, such as the
vault in a bank; or on-site, for instance, in a fireproof safe, away from the room
which contains the server.
For increased safety of your data, duplicate the Disaster Recovery tapes using the
tape duplication utility of Disaster Recovery. For more information on this utility,
refer to the Arkeia User Manual section Duplicate a tape on page 221.
!
During a Disaster Recovery, Disaster Recovery will ask the opera-
tor for the different tapes by name. Labeling the tapes clearly will
substantially reduce the time necessary for the restoration opera-
tion.
Proper handling and storage of the Disaster Recovery tapes is also important. For
more information on this subject, refer to Handling and replacing backup media on
page 51 in the Arkeia User Manual, and the documentation supplied by the maker
of the backup media.

For more information on the creation of tapes and tape pools, refer to the Arkeia
User Manual Chapter 6:Create objects and users on page 69.
Backup the client and server computer configuration

A backup of the system parameters is essential for the reconstruction of a server or
client from a bare metal computer. The system parameters are divided into three
different classes:
The network configuration information.
The hard disk drive parameters.
The Arkeia database and index (for servers only).
The Arkeia database and index is a special class which relates only to an Arkeia
server. Its backup is described in the next section, Backup the server database and
index on page 14.
A computer is recovered by Arkeia from its backup through:

an Arkeia server on the network, if it is a client; or
a tape drive located on the computer to be recovered, if it is a server.
The Arkeia daemon arkeiad needs to be running for Arkeia to function. The Arkeia
daemon in turn requires the network to be configured, therefore the first item to be
restored on a client or server is its network configuration.
To backup the network configuration of a given computer, Disaster Recovery has a

resident plug-in, named sysinfo especially for this task. If you are using sysinfo to
backup the system configuration and parameters of an Arkeia server, Arkeia rec-
ommends that you use dedicated tapes and Savepacks to optimize this operation. If
you are using sysinfo to backup the system configuration and parameters of an
Arkeia client, using dedicated tapes or Savepacks is not necessary.
From the Main menu, click on

Backup > Savepacks > Browse trees
to access the sysinfo plug-in.
Click on the icon to display the list of computers declared as clients to the current
Arkeia server. Click on the name of a computer to display the plug-ins available on
that client:
The resident plug-ins that are available in a standard Disaster Recovery installation
are file, to backup the file systems of an Arkeia client and sysinfo, which is the
plug-in used to backup the system information of the client. The / after their
respective names indicates that these elements contain sub-elements.
Double click on sysinfo to display the different classes of information that can be
backed-up:

In the example above, three standard classes are available:
1. config (network parameters);
2. system (hard disk parameters); and
3. dbase/ (Arkeia database and index, only present on an Arkeia server).
Click on checkboxes next to config and system to select them for backup to tape.
The system information items are displayed in the Savepack as a path using the
following syntax:
computer_name!sysinfo:/config
computer_name!sysinfo:/system
Therefore, for a computer named saturn.usa.acme.com, the sysinfo information is

displayed as:
saturn.usa.acme.com!sysinfo:/config
saturn.usa.acme.com!sysinfo:/system
The same syntax will appear in the Arkeia logs.
Once the network parameters (the sysinfo:/config shown above) have been
backed-up, they can be restored to a Disaster Recovery diskette. This diskette will
be useful to rapidly restore a system. See Create a recovery diskette on page 15 for
more details.
Backup the server database and index

The Disaster Recovery server stores detailed information in its database and its
index each time a backup operation is performed. The computer name and target
file, directory or path, are essential details for the proper completion of a Disaster
Recovery procedure, and they are contained in the Arkeia server database and
index.
Use the sysinfo plug-in to save this information as we did above for the config and
system data, but this time choose the dbase/ path instead of the config and system
files. Click on the dbase/ to display the two parts of the Arkeia database:
In the example shown above, the f3 file is the configuration database itself, and the
o3dbtree folder is the Arkeia index.
The Arkeia database (or f3) can be large, but the index (which is contained in the
directory o3dbtree/) is much larger, because it contains one part for each client
declared to the current server. For instance, if a given Arkeia server has ten clients,
named puter01 to puter10, the o3dbtree/ index will contain ten sub-directories, with
the same names as the computers: o3dbtree/puter01, o3dbtree/puter02, and so on to
o3dbtree/puter10.
Using the index, it is therefore easy to retrieve the server data, and only the server
data, by restoring only the sub-directory that corresponds to the desired server.

There are some important points to keep in mind when saving the database and
index information of an Arkeia server:
The database and the index should be saved at the same time. Restoration,
though, can be partial (client by client).
Since both the index and the database are updated every time Disaster
Recovery performs an operation on a client, you should backup both on a
regular basis. However, even if a Disaster Recovery procedure has to be
launched without the benefit of a complete database and index backup, the
arkrstdb utility can help complete the missing entries in the database and
index. For more information, refer to the Arkeia User Manual section named
Recover the Arkeia database: arkrstdb on page 215.
Whenever an Arkeia server which performs backup operations on itself is
reconstructed under Disaster Recovery, it is recommended that you backup
the index of the server separately from the index of its clients. For instance, if
the server is named plex, the index information that should be backed up is
contained in sysinfo:/dbase/o3dbtree/f3 and sysinfo:/dbase/o3dbtree/plex.
Client database and index backup

If necessary, the database and index can be backed up and restored, even if no
Disaster Recovery procedure is launched. This is possible only for the client index
entries, not for the server-related information contained in the index. This will be
useful if the database or the index become damaged.
Create a recovery diskette

The Disaster Recovery procedure of Disaster Recovery also allows a recovery dis-
kette to be created for each system. This diskette, once created, contains the con-
figuration information needed to quickly recover the hard disk and network
parameters for the given computer.
The recovery diskette contains information which you may find difficult to locate,
after the computer has failed. The question and answer section which starts the
Disaster Recovery procedure will be much shorter if you have a recovery diskette
because the default values will be changed to the correct values stored previously
on the diskette. To create a recovery diskette for a given computer, follow the steps
detailed below:
1. Use the instructions above (in the section titled Backup the client and server
computer configuration on page 13) to perform a complete backup of the
system configuration (with the sysinfo:/config plug-in).
2. Restore the system configuration, contained in sysinfo:/config, to disk, by
using the redirection function of Disaster Recovery. For more information on
the redirection of a restoration, refer to the Arkeia User Manual section
named Redirecting a restoration on page 142.
3. Copy the file created by this restoration to a diskette.
The Disaster Recovery procedure is now able to use this diskette to automatically
provide correct default values to the questions asked in the first step of the Disaster
Recovery procedure.

!
The diskette used in the Disaster Recovery procedure should be
formatted either with the MS-DOS fat or with the Linux ext2 file
systems. For more information on the formatting commands,
refer to the documentation and to the man pages of your system.
Since the Recovery file stored on the diskette is quite small, it is best to store sev-
eral of these files on a single diskette, by giving different names to each file. For
instance, if a Disaster Recovery diskette should be created for the three following
computers:
Computer 1: mars.usa.acme.com
Computer 2: jupiter.usa.acme.com
Computer 3: saturn.usa.acme.com
It is possible to create three separate files, named: mars.cfg, jupiter.cfg and sat-
urn.cfg that can then be stored on the same diskette. When the Disaster Recovery
procedure is launched, it will ask first for the Recovery diskette then, if several
files are found, it will ask which one should be used for the current target com-
puter.
Backup for Disaster Recovery

The Disaster Recovery procedure of Disaster Recovery will restore a damaged
computer, but it will only be effective if backups are performed on a regular basis
on all computers and all data that you require to be restored.
!
Even if the computer configuration information has been saved to
backup media, you still need to save the data contained on its
hard disks, and not just the basic computer configuration infor-
mation.
At sites protected by Disaster Recovery Disaster Recovery, the following backup

factors must be reviewed and carefully applied to all computers:
Saving each computer configuration information should be done immedi-
ately. If necessary, Disaster Recovery diskettes should be created and dupli-
cated immediately, with one copy kept on-site and another kept off-site.
Saving the complete original state of the hard disk drive of all computers
(client and server) should also be done as soon as possible. Duplicate the
backup tapes (or backup media), with one copy kept on-site and another kept
off-site.
A comprehensive backup policy must be established, using the differential
and incremental backup functions of Disaster Recovery. These functions
allow you to save only the files that have been modified since the last com-
plete backup and therefore reduce the time necessary to perform backups.
For more information on these functions, refer to the Arkeia User Manual
Chapter 7:Interactive backup on page 105 and Chapter 8:Periodic backup
on page 117.
A second backup policy should be established, in order to frequently save the
database and the index of the Arkeia server itself.

To ensure a reliable backup of the Arkeia server configuration, you should
make a separate backups of the configuration data, which is stored in
sysinfo/ tree on the server, after you have backed up your data. The order is
important.
In the Arkeia client above, disaster recovery backup savepacks could be

configured like this
Savepack 1
voyager.arkeia.com!file:/
voyager.arkeia.com!lotus:/
voyager.arkeia.com!lotus6:/
voyager.arkeia.com!mysql:/
Savepack 2
voyager.arkeia.com!sysinfo:/
and the backup is configured so that Savepack 1 is always backed up before

Savepack 2. It is not strictly necessary to have two savepacks, but the
/sysinfo tree must always be backed up after the other data.
The more critical the data backed up by the server, the more frequent should
be the backup.
!
You should be aware of the size of the database and the index
when setting the backup policy of these elements.
The remaining information in this chapter describes how to recover a client or

server to a "bare metal" computer.
Reboot for Disaster Recovery

The client recovery and server recovery procedures described in this chapter
assume that the client or server is being restored to a " bare metal" computer, that is
a computer without an operating system and without formatted disks.
!
If you recover a client or server to a computer which has an exist-
ing operating system or existing formatted hard disk, the operat-
ing system and disk format (which includes any data on the disk)
will be obliterated and replaced with the backed up operating sys-
tem and disk format.
Although it is not essential, the most reliable Disaster Recovery operation will
occur when the computer receiving the recovered data is identical to the computer
from which the data came. This includes:
Hard disk: the computer used for the Disaster Recovery procedure should
have a hard disk with a size at least as large as the original computer. If a
larger disk is used, the unused space will be assigned as an unused (or: free)

partition. It is also recommended that you use a disk with the same geometry
as the original.
Network card: The computer used for the Disaster Recovery procedure
should have a network card equivalent to the original computer, if a Disaster
Recovery diskette is used. However, the network card can be automatically
detected at the beginning of the procedure, and a different card can therefore
be installed in a crashed computer.
"
If a different network card is installed in the new computer, when the
recovered system is restored, the network parameters will be overwrit-
ten with the old parameters, so you will have to re-install the network
card with the new parameters.
SCSI card: If the original computer used a SCSI card to control its hard
disks, you should check that this card is on the list of supported SCSI cards
in the section Supported SCSI cards on page 32. A Disaster Recovery CD-
ROM is supplied by Arkeia with every copy of Disaster Recovery that has a
valid Disaster Recovery license. All the listed drivers are present on the
Disaster Recovery CD-ROM under /lib/modules/2.4.20-xfs/kernel/drivers.
Arkeia versions prior to 5.1.12 are not able to detect the SCSI card and load the
correct SCSI modules automatically. If you are running a version prior to 5.1.12
you will have to determine which card is installed in the computer, and which mod-
ule supports that card. To load a module, log in to a virtual terminal (Alt+F2 or
Alt+F3) and type this command:
insmod <module_path>
To start the Disaster Recovery procedure, power on the target computer, and make
sure its BIOS is set to boot from the CD-ROM drive.
!
The Disaster Recovery procedure does not support computers
that either do not have a CD-ROM drive or that cannot boot from
the CD-ROM drive. It is unlikely that recovery of computers which
cannot boot from a CD-ROM drive will succeed.
Insert the Arkeia Disaster Recovery CD-ROM, and re-boot the computer.

Re-configure the network interface
When computer has booted, the first screen of the Arkeia Disaster Recovery proce-
dure will be displayed.
After the initialization stage under Linux, the Disaster Recovery procedure will ask
for your keyboard type, and whether a recovery diskette is available. If a Disaster
Recovery diskette is available, enter y for Yes. If several Recovery files are present
on the floppy, the Disaster Recovery procedure will then ask which file should be
used for the computer being restored.

The Disaster Recovery procedure will ask a series of questions to initialize and
restore the network connection of the computer. These questions are always fol-
lowed by a default value, enclosed in square brackets. For instance, in the screen
above, the default value for the first question is [eth0] (equivalent to the Ethernet
card 0 device) which is the default Linux network interface.
"
Even if a Disaster Recovery diskette has been inserted for the system
being recovered, the Disaster Recovery procedure will ask the ques-
tions detailed below. The difference is that when you have a Disaster
Recovery diskette, the default values offered at the prompt will be the
values read from the recovery diskette, so they need not be typed in,
just press Enter to confirm.
The questions asked by the Disaster Recovery procedure are:

Question 1: What is your network interface?
Enter the correct interface, or press the Enter key to select the
default value, which is eth0.
Question 2: What is your network card?

Enter the correct model, or the closest model you can find in the
supported network card list, or press Enter to select the default
value.
!
The Disaster Recovery procedure will attempt to detect the cor-
rect model of the network card. The result of this detection will
then appear as the default value. If a Recovery diskette has been
prepared, the default value will always be the one that has been
saved on the diskette.
If the network card default value does not seem correct, entering the letter h for
Help, instead of a value, will display all the models that are supported by the Disas-
ter Recovery procedure. The value of the correct model should then be entered
after the question.

After the network interface has been entered, the Disaster Recovery procedure will
probe it in order to make sure it functions properly.
Re-configure the network

When it has completed the network card initialization, the Disaster Recovery pro-
cedure continues with a series of questions, designed to configure the network
parameters themselves, this is the second step of the Disaster Recovery procedure:
Question 3: Local computer name.

Enter the name of the computer to be restored in the FQDN
(Fully-Qualified Domain Name) format. For instance:
sygma.eu.acme.com is a syntactically correct name under this stan-
dard.
Question 4: Local IP address.

Enter the IP address of the computer to be restored. For instance,
192.168.7.52 is a syntactically correct IP address.

Question 5: Netmask.
Enter the IP netmask of the local network.
Question 6: Gateway/Gateway IP address.

The Disaster Recovery procedure asks if your network uses a
gateway. If this is the case, it will then ask for the IP address of
the gateway.
Question 7: DNS/IP address of DNS.

The Disaster Recovery procedure also asks if the local network
uses a dedicated DNS computer. If this is the case, the procedure
asks the operator to enter the TCP/IP address of the DNS server.
!
The Disaster Recovery procedure does not support DHCP. If the
network the crashed computer is connected to uses DHCP, con-
figure the DHCP server in such a way that both the crashed com-
puter and the Arkeia server used for its restoration always use the
same fixed TCP/IP address.
For more information on this configuration, refer to the documentation supplied

with your DHCP implementation.
Question 8: Is the local computer the Arkeia server?

If you are using another computer as the Arkeia server to restore
the crashed computer, answer n (for: No) in order to start the
server configuration process. If you are trying to restore an
Arkeia server, answer y (for: Yes). The default value is No. If the
answer to this question is Yes, the Disaster Recovery continues
with the process detailed in the next section: Restore an Arkeia
server on page 31.
Question 9: Name of the Arkeia server?

Enter the name of the Arkeia server in FQDN format. For
instance arkeia.nyc.stratus.com is a syntactically correct name.
Question 10: IP address of the Arkeia server?

Enter a valid IP address for the Arkeia server. For instance
192.168.7.141 is a syntactically correct IP address.
Question 11: TCP port used by the Arkeia server?

Enter the TCP port used by the Arkeia server to communicate
with its client. By default, the port used is 617. This port may be
changed by the system administrator, for instance if it conflicts
with another network application or if a firewall has been setup to
filter network traffic.
Question 12: TCP port used by local computer?

Enter the TCP/IP port used by the local computer to connect to
the Arkeia server. By default, this value is 617, but can be
changed by the system administrator (see Question 11 above).

Question 13: Arkeia login/password?
Enter the login used to connect to the Arkeia server to retrieve
data. By default, the login used is root and the password is empty.
The login/password combination is defined when creating users
on the Arkeia server. For more information on this subject, please
refer to the Arkeia User Manual Chapter 2:Installation proce-
dure on page 29, and to Chapter 6: Create objects and users on
page 69.
When these questions are answered, the Disaster Recovery procedure will display
the complete list of parameters and their values under the heading Configuration
data. The procedure then requests confirmation that all parameters have been
entered correctly.
If one of the parameters is incorrect, answer n for No. The procedure then restarts
from the beginning and asks again for the network card configuration, computer
name, TCP/IP address, and so on.

If the parameters are correct, the Disaster Recovery then attempts to initialize the
network card that was configured in the first step of the procedure. If needed, the
complete network configuration can then be displayed, as in the example above.
If necessary the route table of the system can also be displayed.

To finish this re-configuration and start the client restoration, press Enter.
Restore a client
If at the point in the re-configuration of the network where you are asked if the
computer is a server (Question 8 here on page 22), you answered n for no, you will
be directed to the client restoration procedure, after the network connection is re-
configured.
The Disaster Recovery procedure will now contact the Arkeia server defined on
the network, and retrieve the configuration information about the damaged com-
puter from the Arkeia backup server database.
!
If the amount of data to be restored is large, the Disaster Recov-
ery procedure may require you to insert several tapes into the
Arkeia server drives, therefore a Disaster Recovery operation
should not be left unattended.

In this example, the Disaster Recovery process indicates that it needs one tape
named LT01_tape, and asks for the drive number in which it can find that tape.
If during the restoration of the client computer configuration an additional tape is

necessary, the process will pause, display the name of the tape that it requires and
the list of drives available. You must then insert the requested tape into one of the
drives and indicate which drive contains the tape.
The restoration is done in two phases:

1. First Arkeia Disaster Recovery will rebuild the file system of the damaged
computer, including the partitions and the hard disk formatting.
2. Next, the partitions are mounted and the restoration of the data is launched.
Restore the file system

In this phase of restoration, the configuration of the clients disks is retrieved from
the backup tape, the new disk is formatted and the filesystem re-established. In the
example below, we see that the original computer had only one disk (/dev/hda)
with three partitions (/dev/hda1, /dev/hda2, and /dev/hda3).

Format and partition the new disks
You can re-partition the disk

manually, or let Disaster
Recovery do it for you.
You can let Disaster Recovery repartition the new disk in the same configuration as
the original, or you can format and repartition the new disk manually if:
the destination disk is smaller than the original disk, because Disaster Recov-
ery cannot partition the disk in this case, or
the destination disk is bigger than the original, because Disaster Recovery
would leave the extra space unused, or
you wish to re-size the partitions.
For each disk, Disaster Recovery will ask whether you want to format it or not. If
you answer no for a disk, that disk will not be formatted or partitioned. This is use-
ful if, for example, the original computer had two disks and you want to re-create
only one disk. The disks for which you answer yes, are formatted and partitioned.
In the example below, the:

/dev/hda1 partition is formatted with an ext3 file system, and
/dev/hda3 partition is formatted with an ReiserFS file system.
Label the file systems
The original file system labels are then displayed. You can allow Disaster Recov-
ery to restore them, or you can manually apply different labels.
!
It is important to restore the filesystem labels because some
Linux distros, for example Red Hat, configure the fstab file to
mount devices according to their labels.
In the example above, /dev/hda1 is labeled / and the /dev/hda3 filesystem has no
label.
Activate the swap partition
The restoration process typically requires a large amount of memory, so for a more
efficient restoration, it is recommended that you activate a swap partition, if you
have the space available.

Restore the data
Disaster Recovery begins the data restoration process by querying the Arkeia data-
base for the tapes needed. If the disks to be restored are very large, this will take a
long time.
List of data tapes needed
When the query is completed, Arkeia lists all the tapes needed for the restoration.
In the example above, only one tape is needed: LT01_tape1.
Load the data tapes
You are then asked to insert each tape from the list in turn into an available drive,
and indicate which drive contains the tape. This process is repeated for each tape in
the list, until all the data is restored.
Monitor the restoration

You can monitor the restoration process by connecting to the backup server
through Disaster Recovery, then selecting the restoration job. Log into the backup
server, and click on Main menu: > Running jobs

Select the restore job started above to see the Restore screen:
For more information about the Restore screen, see the Arkeia User Manual How
to launch the restoration on page 145.
The last step in the Disaster Recovery process, for both clients and servers, is the
installation of the bootloader.
Recover the bootloader

Usually, the bootloader used by Linux systems is the program lilo (the LInux
LOader).It is possible that some Linux systems use grub or another bootloader.
If the user has created a Disaster Recovery diskette, the bootloader configuration
may have been detected automatically. The two boot loaders that can be detected

automatically by the sysinfo plug-in are grub and lilo. If the bootloader has been
detected automatically, the default answer value will be the executable detected.
The Disaster Recovery procedure will ask which command should be used to
install the bootloader. As mentioned above, the default value is /sbin/lilo. If the
damaged computer used another bootloader, its complete path and name should be
entered when requested. For grub, this path is usually /usr/sbin/grub.
!
If grub is used as the bootloader of the computer, you may have to
enter the following command at the grub prompt:
root (hd0,0)
setup (hd0)
This command assumes that the computer boots from the first
partition of the first disk: (hd0,0). The first hard disk can be a
SCSI disk (/dev/sda1 under Linux) or an IDE disk (/dev/hda1 under
Linux).
After this last stage, the Disaster Recovery procedure is complete and the computer
completely restored.
Restore an Arkeia server

When a server is damaged a full recovery is possible, provided a backup is avail-
able. First the servers disks are configured, then the Arkeia server database and
index are restored. Next, the database and index are queried to locate the backup of
the servers files, then the files are restored from the backup media. The backup
data for each client is then restored. At this point, the server is restored to the status
of its last available backup. The server recovery process will run much more
smoothly if:
a Disaster Recovery diskette is available for the original, and
the tapes containing the server backup are labeled, and readily available.
Note that the server is restored from its own backup tapes.
These are the specific steps required:
1. Boot the new server computer from the Disaster Recovery DR CD-ROM,
and re-configure its disks and network connection (see Reboot for Disaster
Recovery on page 17).
2. Restore the Arkeia database and index information pertaining to the server.
3. Use the backup information contained in the database and index restored in
the last step to completely restore the servers hard disk.
Boot the new server

Before the server can be restored, it is necessary to configure the computer which
will host it. The highest restoration reliability will be achieved when the target
computer has the same hardware specifications as the original server computer.
The process of booting and configuring a new computer is described in Create a

recovery diskette on page 15. At the point in the re-configuration of the network
where you are asked if the computer is a server (Question 8 on page 22), answer y
for yes. You will be asked to insert the backup tape that contains the system infor-
mation.
When the correct hard disk parameters have been retrieved from the backup tape,
the Disaster Recovery process will apply them to the server hard disk and proceed
with the next step.
Restore the server database and index

At this stage of the Disaster Recovery process, the only things restored on the
Arkeia server are the network parameters and the disk parameters. The second step
of an Arkeia server Disaster Recovery is the restoration of the information con-
tained in the server database and index. The tape locations of all the files that were
on the original server are recorded in this database, and Disaster Recovery will use
this information to recover the servers original files from the backup tapes. You
will now be prompted to insert the tape which contains the server database, and its
recovery will start.
When the Arkeia server database has been restored, the Disaster Recovery process
will prompt you to insert the tapes that contain the index of the Arkeia server. For
instance, if the name of the server is apex, its index will be saved by the sysinfo
plug-in as: apex!sysinfo:/dbase/o3dbtree/apex.
Complete the server restoration

When the Arkeia database and the index that contain the relevant information for
the server have been restored, the Disaster Recovery process will prompt the oper-
ator to insert the tapes needed to retrieve the server data.
Update the index

Due to its size, the index is not backed up as frequently as the database so it is pos-
sible that the index you have just restored is not complete. The utility arkrstdb
enables you to bring the index up to date. You need to run arkrstdb only on the
backup tapes used after the last index backup, up to the point of the server failure.
For more information, refer to the Arkeia User Manual section named Recover the
Arkeia database: arkrstdb on page 215.
Recover the server bootloader

When the restoration has been completed, the Disaster Recovery is terminated and
the Arkeia server has been successfully brought back online.
The bootloader should now be installed on the server. For more information on this
step, refer to Recover the bootloader on page 30.
Supported SCSI cards

3ware Hardware ATA-RAID 3ware is the only hardware ATA-Raid product in Linux
to date. This card is 2,4, or 8 channel master mode support only.
3w-xxxx.o

53c7 and 8xx NCR family of SCSI controllers NCR53c810/820/720,
NCR53c700/710/700-66 Not to be confused with the NCR 5380 controllers.
53c7,8xx.o
AM53/79C974 SCSI host adapters

AM53C974.o
BusLogic MultiMaster and FlashPoint SCSI Host Adapters

BusLogic.o
Mylex DAC960/DAC1100 PCI RAID Controller support

DAC960.o
NCR53c406a SCSI host adapter

NCR53c406a.o
Initio INI-A100U2W SCSI host adapter

a100u2w.o
SCSI host adapters manufactured by AdvanSys

advansys.o
Adaptec AHA-1510, AHA-1520, AHA-1522, and AHA-2825 SCSI host adapters It

also works for the AVA-1505, but the IRQ etc. must be manually specified in this
case.
aha152x.o
Adaptec AHA-1542 SCSI host Adapter

aha1542.o
Adaptec AHA-11740 SCSI host Adapter

aha1740.o
Adaptecs PCI based SCSI controllers (not the hardware RAID controllers)
Adaptec AHA-274x, AHA-284x, AHA-29xx, AHA-394x, AHA-398x, AHA-274x,
AHA-274xT, AHA-2842, AHA-2910B, AHA-2920C, AHA-2930/U/U2, AHA-
2940/W/U/UW/AU/, U2W/U2/U2B/, U2BOEM, AHA-2944D/WD/UD/UWD, AHA-
2950U2/W/B, AHA-3940/U/W/UW/, AUW/U2W/U2B, AHA-3950U2D, AHA-
3985/U/W/UW, AIC-777x, AIC-785x, AIC-786x, AIC-787x, AIC-788x , AIC-789x,
AIC-3860
aic7xxx.o
ACARD 870U/W SCSI host adapter

atp870u.o
Compaq Smart Array 5xxx controllers SA 5300 SA 5i SA 532 SA 5312

cciss.o
Compaq Smart Array controllers SMART (EISA) SMART-2/E (EISA) SMART-2/P

SMART-2DH SMART-2SL SMART-221 SMART-3100ES SMART-3200 Integrated
Smart Array Controller SA 4200 SA 4250ES SA 431 RAID LC2 Controller
cpqarray.o
Compaq StorageWorks Fibre Channel 64-bit/66Mhz Host Bus Adapter

cpqfc.o
Domex DMX3191D SCSI Host Adapters

dmx3191d.o
Adaptecs I2O based RAID controllers as well as DPT SmartRaid V cards

dpt_i2o.o
Data Technology Corp DTC 3180/3280 SCSI Host Adapters

dtc.o

EATA/DMA-compliant SCSI host adapters DTP SCSI host adapters (EATA/DMA)
PM2011B/9X ISA, PM2021A/9X ISA, PM2012A, PM2012B, PM2022A/9X EISA,
PM2122A/9X, PM2322A/9X, SmartRAID PM3021, PM3222, PM3224
eata.o
EATA-PIO protocol compliant SCSI Host Adapters like the DPT PM2001 and the
PM2012A
eata_pio.o
Future Domains 16-bit SCSI host adapters (TMC-1660/1680, TMC-1650/1670,

TMC-3260, TMC-1610M/MER/MEX) and other adapters based on the Future
Domain chipsets (Quantum ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at
least one IBM board) NOTE: Newer Adaptec AHA-2920C boards use the Adaptec
AIC-7850 chip and should use the aic7xxx driver (Adaptec AIC7xxx chipset SCSI
controller support). This Future Domain driver works with the older Adaptec AHA-
2920A boards with a Future Domain chip on them.
fdomain.o
Generic NCR family of SCSI controllers NCR5380 and NCR53c400 cards Not to
be confused with the NCR 53c7 or 8xx controllers.
g_NCR5380.o
Intel/ICP (former GDT SCSI Disk Array) RAID Controller

gdth.o
IOMEGA MatchMaker parallel port SCSI adapter

imm.o
Always IN2000 SCSI host adapter

in2000.o
Initio 91XXU(W) SCSI host adapter

initio.o
IBM ServeRAID hardware RAID controllers

ips.o
AMI MegaRAID 418, 428, 438, 466, 762, 490 and 467 SCSI host adapters
megaraid.o
NCR53C8XX family of PCI-SCSI controllers 810/810A/815/

825/825A/860/875/876/895 chipsets
ncr53c8xx.o
Pro Audio Spectrum/Studio 16

pas16.o
PCI2000I EIDE interface card (acts as a SCSI host adapter)

pci2000.o
PCI2220I EIDE interface card (acts as a SCSI host adapter)

pci2220i.o
IOMEGA PPA3 parallel port SCSI host adapter

ppa.o
Perceptive Solutions PSI240i EIDE interface card (acts as a SCSI host adapter)
psi240i.o
QLogic ISP1x80/1x160 SCSI host adapter

qla1280.o
ISA, VLB, and PCMCIA versions of the Qlogic FastSCSI! cards as well as any
other card based on the FASXX chip (including the Control Concepts

SCSI/IDE/SIO/PIO/FDC cards) This driver does NOT support the PCI versions of
these cards. The PCI versions are supported by the Qlogic ISP driver below.
qlogicfas.o
QLogic ISP2100 SCSI-FCP host adapter

qlogicfc.o
QLogic ISP1020 Intelligent SCSI cards IQ-PCI, IQ-PCI-10, IQ-PCI-D This driver
works for all QLogic PCI SCSI host adapters (IQ-PCI, IQ-PCI-10, IQ_PCI-D)
except for the PCI-basic card
qlogicisp.o
Seagate ST01/ST02 and Future Domain TMC-8xx SCSI controllers

seagate.o
Symbios sym53c416 SCSI host adapter

sym53c416.o
NCR53C8XX/SYM53C8XX family of PCI-SCSI controllers This driver also sup-

ports the subset of LSI53C10XX Ultra-160 controllers that are based on the
SYM53C8XX SCRIPTS language. It does not support LSI53C10XX Ultra-320 PCI-
X SCSI controllers.
sym53c8xx.o
sym53c8xx_2.o
Trantor T128/T128F/T228 SCSI host adapter

t128.o
Tekram DC390(T) and Am53/79C974 SCSI host adapters

tmscsim.o
UltraStor 14F and 34F SCSI-2 host adapters

u14-34f.o
UltraStor 14F, 24F and 34F SCSI-2 host adapter family

ultrastor.o
Western Digital 7000 SCSI host adapter family

wd7000.o

INDEX
A
Arkeia daemon 13
arkeiad 13
B
bootloader 11
C
CD-ROM bootable 11
Configuration data 23
D
device 20
Disaster Recovery
license 9
disaster recovery CD-ROM 11
Disaster Recovery toolbox 12
disk configuration 10
DNS 22
F
file system label 28
firewall 22
FQDN 21, 22
fstab 28
G
grub 30, 31
H
hard disk parameter restoration 10
hard disk partition 11

I
IDE 31
index 14
interface 20, 21
IP address 21
L
license
Disaster Recovery 9
lilo 30, 31
M
man 16
model 20
N
netmask 22
network configuration 10
network parameter restoration 10
P
password 23
plug-in 13, 14, 15, 31, 32
R
recovery diskette 12, 15
repartition the new disk
partition the new disk 27
restoration
lost computer 10
route table 24
S
SCSI 31
SCSI cards supported by DR 18
server system configuration 11
swap partition 28
sysinfo 13, 14, 31, 32
/config 14, 15
/dbase 15, 32

/system 14
system parameter 13
system restoration 10
T
tape duplication 12
tape pool 12, 13
TCP/IP 22, 23


Arkeia PI Disaster Recovery

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Arkeia PI Disaster Recovery

Transféré par

Droits d'auteur :

Formats disponibles

ARKEIA

Tel : +1 (760) 431 - 1319 Tel : +33 (0)1 48 10 89 89

Linux is a registered trademark owned worldwide by Linus Torvalds.

Document edition: 1.2 Dated: 19-Aug-2005 Status: Released

2 Arkeia Disaster Recovery

1. GRANT OF LICENSE. In return for payment of LICENSE fees included in

If the SERVER or CLIENT on which the SOFTWARE is operated consti-

2. COPYRIGHT. The beneficiary of the LICENSE is the owner of the magnetic

This LICENSE does not constitute a sale of the original SOFTWARE or of

3. REPRODUCTION RESTRICTIONS. This SOFTWARE and the accompa-

Subject to the above-mentioned restrictions, the LICENSEE is authorized to

Arkeia Disaster Recovery 3

4. RESTRICTIONS OF USE. The LICENSEE is authorized to physically

5. TRANSFER RESTRICTIONS. No person whomsoever shall be authorized

6. CANCELLATION. This LICENSE AGREEMENT shall remain valid until

7. MISCELLANEOUS. This LICENSE AGREEMENT is governed by the

If you would like further information on this LICENSE AGREEMENT, please

4 Arkeia Disaster Recovery

In the event of a defect in the software or in the documentation, the LICENSEE,

Under no circumstances shall ARKEIA, or anyone else participating in the design,

Information or advice given verbally or in writing by ARKEIA, its dealers, distrib-

Arkeia and ARKEIA SOFTWARE are registered trademarks (TM) of ARKEIA

(*) Warranty may vary according to local regulations.

Arkeia Disaster Recovery 5

Disaster Recovery DR Manual 7

How Disaster Recovery works

Disaster Recovery DR Manual 9

Disaster Recovery is a four-stage process:

Through these four stages, Disaster Recovery is able to:

Disaster recovery: client and server

10 Disaster Recovery DR Manual

How to prepare for Disaster Recovery

Disaster Recovery DR Manual 11

a Savepack, click on to see the Advanced options screen which con-

Create a Disaster Recovery toolbox

Dedicated tapes and tape pools

12 Disaster Recovery DR Manual

Backup the client and server computer configuration

A computer is recovered by Arkeia from its backup through:

To backup the network configuration of a given computer, Disaster Recovery has a

From the Main menu, click on

Disaster Recovery DR Manual 13

Therefore, for a computer named saturn.usa.acme.com, the sysinfo information is

The same syntax will appear in the Arkeia logs.

Backup the server database and index

14 Disaster Recovery DR Manual

Client database and index backup

Create a recovery diskette

Disaster Recovery DR Manual 15

Backup for Disaster Recovery

At sites protected by Disaster Recovery Disaster Recovery, the following backup

16 Disaster Recovery DR Manual

In the Arkeia client above, disaster recovery backup savepacks could be

and the backup is configured so that Savepack 1 is always backed up before

The remaining information in this chapter describes how to recover a client or

Reboot for Disaster Recovery

Disaster Recovery DR Manual 17

18 Disaster Recovery DR Manual

Disaster Recovery DR Manual 19

The questions asked by the Disaster Recovery procedure are:

Question 2: What is your network card?

20 Disaster Recovery DR Manual

Re-configure the network

Question 3: Local computer name.