Hipath 8000 V3.0 Maintenance Manual: Volume 2, Backup and Recovery

HiPath 8000
V3.0
Maintenance Manual
Volume 2, Backup and Recovery

*1PA31003-H8030-S113-2-7620*
1P A31003-H8030-S113-2-7620
The information provided in this document contains merely general descriptions or

characteristics of performance which in case of actual use do not always apply as
described or which may change as a result of further development of the products.
An obligation to provide the respective characteristics shall only exist if expressly
agreed in the terms of contract. The trademarks used are owned by
Siemens Enterprise Communications GmbH & Co. KG or their respective owners.
The customer is responsible for ensuring that the system is installed/maintained in
accordance with all the existing local country regulations and laws.
© Siemens Enterprise Communications GmbH & Co. KG 2007,

Hofmannstraße 51, D-81359 München, Germany
Reference No.: A31003-H8030-S113-2-7620
Subject to availability. Right of modification reserved.
bkhis.fm
History of Changes
History of Changes 0
Revision Date Summary

Number
1 May 2007 Initial publication.
2 June 2007 Second publication of document. Incorporated
additional information and corrections to Section 1.2,
Section 2.2, Section 2.2.4, Section 2.9.1, Section 2.9.3,
Section 2.10.1, and Section 2.10.3.
A31003-H8030-S113-2-7620, June 2007

HiPath 8000 V3.0, Maintenance Manual: Volume 2, Backup and Recovery 0-1
bkhis.fm
History of Changes
A31003-H8030-S113-2-7620, June 2007

0-2 HiPath 8000 V3.0, Maintenance Manual: Volume 2, Backup and Recovery
bkTOC.fm
Content
Content 0
History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-1

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-5
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-7
1 Backup and Restore Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 Back-up Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.4 Back-up Server Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.5 Back-up Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.6 Typical Time Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.6.1 Back-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.6.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2 Backup and Recovery Procedures Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1 Partitioning an External USB HDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2 Backup File System for a Single-Node or Redundant System . . . . . . . . . . . . . . . . . . 2-7
2.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2.2 Time Requirement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2.3 Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2.4 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.2.5 Errors and Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.3 Backup the Database Using an External USB HDD . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
2.3.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
2.4 Backup the Database Manually Using the Backup Script . . . . . . . . . . . . . . . . . . . . . 2-19
2.4.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.5 Restore the Database Using an External USB HDD . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.5.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
2.6 Retrieve the File System Backup from an External USB HDD . . . . . . . . . . . . . . . . . 2-22
2.6.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.7 Restore the Database Manually Using the Restore Script. . . . . . . . . . . . . . . . . . . . . 2-23
2.7.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
2.8 Restore Individual Files/Directories for a Single Node. . . . . . . . . . . . . . . . . . . . . . . . 2-24
2.8.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.9 Restore File System for a Single Node in a Redundant System . . . . . . . . . . . . . . . . 2-27
2.9.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
2.9.2 Information Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
2.9.3 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
2.10 Restore File System for a Single-Node or Redundant System . . . . . . . . . . . . . . . . 2-39
2.10.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
A31003-H8030-S113-2-7620, June 2007

bkTOC.fm
Content
2.10.2 Information Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40

2.10.3 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
3 Backup and Recovery Procedures Using the Common Management Portal. . . . . . 3-1
3.1 Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.1 Displaying Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.2 Adding an Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.3 Editing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.1.4 Deleting an Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.1.5 Testing an Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.6 Displaying/Clearing an Archive’s Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2 Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.2.1 Displaying Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.3 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.3.1 Displaying Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.3.2 Adding Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.3.3 Editing Schedules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.3.4 Clearing Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.4 Latest Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.5 Manual Backup of a Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.6 Restoring a Backup Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
4 Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Logging into the Computing Element (Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Starting the RTP CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-H8030-S113-2-7620, June 2007

bkLOF.fm
List of Figures
List of Figures 0
Figure 4-1 RTP CLI Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Figure 4-2 RTP CLI Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
A31003-H8030-S113-2-7620, June 2007

bkLOF.fm
List of Figures
A31003-H8030-S113-2-7620, June 2007

bkLOT.fm
List of Tables
List of Tables 0
Table 1-1 Restore Times Using a Back-up Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Table 1-2 Restore Times Using an External USB HDD . . . . . . . . . . . . . . . . . . . . . . 1-4
Table 2-1 Backup and Restore Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Table 2-2 Errors and Recovery Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table 2-3 System Restore Errors and Corrective Actions. . . . . . . . . . . . . . . . . . . . 2-38
Table 2-4 System Restore Errors and Corrective Actions. . . . . . . . . . . . . . . . . . . . 2-50
A31003-H8030-S113-2-7620, June 2007

bkLOT.fm
List of Tables
A31003-H8030-S113-2-7620, June 2007

Guidelines.fm
Backup and Restore Guidelines
Purpose
1 Backup and Restore Guidelines
1.1 Purpose
This section provides guidelines to facilitate the establishment of a HiPath 8000 back-up policy
such that recovery is possible in the event of a failure of the HiPath 8000 file system. The
section includes requirements for a customer supplied back-up server.
1.2 Overview
The HiPath 8000 employs mirrored disks to minimize the possibility of a catastrophic file system
failure. Because of the mirrored disks, complete failure of the file system is rare. However, the
file system must be backed-up periodically as a precautionary measure. A complete failure of
one or both nodes without a back-up will cause a prolonged HiPath 8000 outage with
associated loss of service.
This guide includes the procedures to back-up and restore the HiPath 8000 file system after
the following types of failures:
● Single node (CE01 or CE02)
● Both nodes (CE01 and CE02)
To recover the system from one of the above failures, the following must be available:
● SLES9-system-restore-boot-cd
● The Siemens provided Restore CD (it is recommended that the latest Restore CD be
obtained and used to recover the system)
● A Linux file system back-up of each node.
Without these items recovery is only possible via a complete installation of the
7 HiPath 8000, application of all required patches, and setting up all site/customer
specific configuration data. This is a long and error prone process.
The Linux file system back-ups can be kept on an external universal serial bus hard disk drive
(USB HDD) or a back-up server. If a back-up server is used it must meet the following
requirements:
● Supports FTP or sFTP for transfer of back-ups.
● Has adequate disk space for the back-ups.
● Stores at least two copies of each back-up on separate physical devices.
● Has a connection to the HiPath 8000 of adequate bandwidth to allow a fast recovery.
A31003-H8030-S113-2-7620, June 2007

Guidelines.fm
Back-up Server
1.3 Back-up Server

The back-up server may be dedicated to the HiPath 8000 or used for multiple devices
depending on the back-up strategy. The back-up server must meet the following requirements:
● The server shall be capable of receiving and sending HiPath 8000 back-ups generated
using the procedures described in Section 2.2, “Backup File System for a Single-Node or
Redundant System”, on page 2-7. Transfers will be via FTP or Secure FTP (OpenSS).
● Redundancy is required, for example by using duplicated disk drives.
– The server should have two disk partitions on different disk drives–primary back-up
and secondary back-up.
– All transfers to and from the HiPath 8000 will normally be to the primary back-up
partition.
– Manual operation or scripts can copy the back-ups from primary to secondary
partitions.
● File management, manual or scripted, is required to:
– Keep secondary back-up synchronized with primary back-up partition.
– Maintain two back-ups per HiPath 8000. When a new back-up is received the oldest
will be deleted.
– Mark a back-up as persistent such that it will not be automatically deleted.
– Delete old back-ups if the disk becomes full and transfer of back-ups from the HiPath
8000 to server is not possible.
● In place of duplicated disks the server may use:
– An optional optical or tape back-up system.
– Commercial disk shadowing mechanism.
1.4 Back-up Server Location

Both the customer and Siemens site personnel will need to decide the best location for the
back-up server. The following need to be considered:
● Use an existing back-up server, used for other equipment, to store the HiPath 8000 back-
ups.
● Bandwidth of the connection between the HiPath 8000 and the server. The back-ups are
large, hence low bandwidth will impact recovery time and prolong the outage.
● Should the server be local to the HiPath 8000. If local, off-site copies of the back-ups must
be maintained:
A31003-H8030-S113-2-7620, June 2007

Guidelines.fm
Back-up Procedures
– By transfer (FTP) to a remote server.

– Using back-up tape system. Tapes can then be held on and off-site.
1.5 Back-up Procedures

● A HiPath 8000 file system back-up must be made at the following times:
– After initial installation.
– After application of patches.
– After a software upgrade.
– After configuration changes.
● At least two copies of each back-up must be maintained.
● An off site copy of the back-up must be maintained.
● The recovery CDs must be kept on-site and off-site.
1.6 Typical Time Requirements
1.6.1 Back-up
Typically, the back-up takes approximately 1 hour and 45 minutes per node (CE) with an idle
system.
1.6.2 Restore
Typical restore times for a file system backup of 4.2 GB per node using a back-up server are
given in Table 1-1. Actual restore times will depend upon the backup size.
Step Per Node

Setup disks and file systems 10 min.
Retrieve backup image 10 min.
Restore file system(s) 45 min.
Total 1 hr. 5 min.
Table 1-1 Restore Times Using a Back-up Server
Typical recovery times for a database backup of 1.6 GB per node using an external USB HDD
are given in Table 1-2. Actual recovery times will depend upon the backup size.
A31003-H8030-S113-2-7620, June 2007

Guidelines.fm
Typical Time Requirements
Step Per Node

Setup disks and file systems 3 min.
Retrieve backup image 3 min.
Restore file system(s) 10 min.
Perform manual steps for DB 5 min.
Total 21 min.
Table 1-2 Restore Times Using an External USB HDD
A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup and Recovery Procedures Using the CLI
2 Backup and Recovery Procedures Using the CLI
Recovery procedures should only be performed by HiPath 8000 trained and

7 experienced personnel following verbal instructions from the next higher fault
resolution organization.
What do you want to do Procedure

Partition the external USB HDD and Section 2.1, “Partitioning an External USB HDD”, on
create an EXT3 file system page 2-2.
Backup file system for a single-node or Section 2.2, “Backup File System for a Single-Node
redundant system or Redundant System”, on page 2-7.
Backup configuration data If using an external USB HDD, refer to Section 2.3,
“Backup the Database Using an External USB HDD”,
on page 2-17.
If using the backup.sh script manually, refer to
Section 2.4, “Backup the Database Manually Using
the Backup Script”, on page 2-19.
If using the Common Management Portal (CMP),
refer to Section 3.5, “Manual Backup of a Backup
Set”, on page 3-10.
Restore configuration data If using an external USB HDD, refer to Section 2.5,
“Restore the Database Using an External USB HDD”,
on page 2-19.
If using the restore.sh script manually, refer to Section
2.7, “Restore the Database Manually Using the
Restore Script”, on page 2-23.
If using the CMP, refer to Section 3.6, “Restoring a
Backup Set”, on page 3-12.
Retrieving a file system backup from an Section 2.6, “Retrieve the File System Backup from
external USB HDD an External USB HDD”, on page 2-22.
Restore individual file/directory for Section 2.8, “Restore Individual Files/Directories for a
single node Single Node”, on page 2-24.
Restore file system for a single node in Section 2.9, “Restore File System for a Single Node
a redundant system in a Redundant System”, on page 2-27.
Table 2-1 Backup and Restore Procedures (Sheet 1 of 2)
A31003-H8030-S113-2-7620, June 2007

proc.fm
Partitioning an External USB HDD
What do you want to do Procedure

Restore file system for a single-node or Section 2.10, “Restore File System for a Single-Node
redundant system or Redundant System”, on page 2-39.
Table 2-1 Backup and Restore Procedures (Sheet 2 of 2)
2.1 Partitioning an External USB HDD

Typically, USB HDD drives contain a FAT32 file system; they have a file size limit of 4GB, which
is insufficient to backup some HiPath 8000 systems.
Partition a USB HDD and create an EXT3 file system as follows:
A system with a SUSE Linux operating system is required for this procedure. If you
> use a HiPath 8000 node, do it at a time of low traffic to help ensure that service is
not impacted.
1. Log on to the system as user root.

2. Connect and power on the USB HDD.
The system will take about 15 seconds to identify the device.
3. Identify the available disks with the command:
fdisk -1
The system will display disk information similar to the following example:
Disk /dev/sda: 73.4 GB, 73406611456 bytes
128 heads, 32 sectors/track, 35003 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System

/dev/sda1 1 1024 2097136 82 Linux swap
/dev/sda3 2049 3584 3145728 83 Linux
/dev/sda4 3585 35003 64346112 5 Extended
/dev/sda5 3585 5632 4194288 83 Linux
/dev/sda6 5633 5882 511984 83 Linux
/dev/sda7 5883 7930 4194288 83 Linux
/dev/sda8 7931 8954 2097136 83 Linux
/dev/sda9 8955 14074 10485744 83 Linux
/dev/sda10 14075 16634 5242864 83 Linux
/dev/sda11 16635 18170 3145712 83 Linux
/dev/sda12 18171 23290 10485744 83 Linux
/dev/sda13 23291 25338 4194288 83 Linux
A31003-H8030-S113-2-7620, June 2007

proc.fm
/dev/sda14 25339 26362 2097136 83 Linux

/dev/sda15 26363 35003 17696752 83 Linux
Disk /dev/sdb: 160.0 GB, 160041885696 bytes


/dev/sdb1 1 19457 156288321 7 FAT32
In this example, the first disk (/dev/sda) is the system disk and the second disk (/dev/sdb)
is the 160GB external USB HDD. Your drive might be identified differently (for example,
/dev/sdc, /dev/sdd, and so on). Use that value in the following steps that require the disk
identifier.
4. Display USB HDD information with the command:
fdisk /dev/sdb
The number of cylinders for this disk is set to 19457.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
5. Display the partition table with the command:

Command (m for help) : p
The system will display information similar to the following example:

/dev/sdb1 1 19457 156288321 7 FAT32
There may be 1 or 2 partitions. In this example there is 1 partition.

6. Delete all the partitions on the drive:
A31003-H8030-S113-2-7620, June 2007

proc.fm
Command (m for help) : d

Selected partition 1
7. Verify that the partition, or partitions, have been deleted with the command:
The system should show that there are no partitions as in the following example:
8. Create a primary partition with the command:

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-19457, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-19457, default 19457):
Using default value 19457
In this example, a primary partition number 1 is created and the default values for the first
and last cylinder are used.
9. Verify that the Linux partition was created with the command:
The system should show that the partition was created as in the following example:

/dev/sdb1 1 19457 156288321 83 Linux
10. Write out the partition table with the command:
A31003-H8030-S113-2-7620, June 2007

proc.fm
Command (m for help): w

The partition table has been altered!
Calling ioctl() to re-read partition table.

Syncing disks.
11. Display the new Linux partition with the command:
fdisk -1
Disk /dev/sda: 73.4 GB, 73406611456 bytes

/dev/sda3 2049 3584 3145728 83 Linux
/dev/sda4 3585 35003 64346112 5 Extended
/dev/sda5 3585 5632 4194288 83 Linux
/dev/sda6 5633 5882 511984 83 Linux
/dev/sda7 5883 7930 4194288 83 Linux
/dev/sda8 7931 8954 2097136 83 Linux
/dev/sda9 8955 14074 10485744 83 Linux
/dev/sda10 14075 16634 5242864 83 Linux
/dev/sda11 16635 18170 3145712 83 Linux
/dev/sda12 18171 23290 10485744 83 Linux
/dev/sda13 23291 25338 4194288 83 Linux
/dev/sda14 25339 26362 2097136 83 Linux
/dev/sda15 26363 35003 17696752 83 Linux


/dev/sdb1 1 19457 156288321 83 Linux
12. Format the first partition (in this example, sdb1 is the first partition) on the USB HDD with
the command:
mkfs.ext3 /dev/sdb1
A31003-H8030-S113-2-7620, June 2007

proc.fm
mke2fs 1.36 (05-Feb-2005)

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19546112 inodes, 39072080 blocks
1953604 blocks (5.00%) reserved for the super user
First data block=0
1193 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208, 4096000, 7962624, 11239424, 20480000, 23887872
Writing inode tables: 0/1193 …

Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.
13. Check the new file system with the following commands:
mkdir -m 777 /usb
mount /dev/sdb1 /usb
df -k /dev/sdb1
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 153834852 32828 145987608 1% /usb
14. Unmount the USB HDD with the command:

umount /usb
A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup File System for a Single-Node or Redundant System
2.2 Backup File System for a Single-Node or Redundant System
Read Chapter 1, “Backup and Restore Guidelines” before performing this

> procedure.
The backup script only backs up the following required partitions: /, /unisphere, /
home, /opt, /enterprise, and /var. Partitions with data that is not required are not
backed up.
2.2.1 Prerequisites
Prior to beginning the backup procedure, the following prerequisites must be fulfilled:
● The node (single-node system) or nodes (redundant system) are in a stable state–no
rolling upgrades, patching activities or system configuration changes are in progress.
● System is not operating at more than 50% of capacity. Sufficient capacity should be
available for the backup job.
● There is sufficient disk space on the local disks to accommodate the backup (this is verified
by the backup script itself).
You must be logged in as root to execute the commands and scripts in this
> procedure.
2.2.2 Time Requirement

The time required depends upon the backup size. A backup of 4.2 GB takes approximately 1
hour and 40 minutes when performed on an idle HiPath 8000.
2.2.3 Disk Space Requirements

Two backup images are maintained on the local disks. These images can be used to perform
selective restores of critical files, without a complete restore. In addition, space must be
available for creation of a third “current” backup.
2.2.4 Procedure
Use the following procedure to backup the file system for the node in a single-node system and
for both nodes in redundant systems.
A31003-H8030-S113-2-7620, June 2007

proc.fm
If you wish to use the FAT32 format on the external USB HDD, you must FTP the
> backup file to the HiPath 8000 Assistant and then write it to the external USB HDD.
Note that the FAT32 format only allows for a backup file size of up to 4GB minus 1
byte in length.
1. Log into Computing Element 1 (CE01)

See “Logging into the Computing Element (Node)” on page Go to Step 2
4-1.
2. Execute the backup script file
With no options, the script uses a default output directory (/ Go to Step 3
var/backup) and a default working storage directory (also /
var/backup). These directories must have sufficient space
to create the backup (this is verified by the script).
The backup script only backs up the following required
partitions: /, /unisphere, /home, /opt, /enterprise, and /var.
Partitions with data that is not required are not backed up.
cd /var/backup
./hiq_backup.sh
3. Do you want to over-ride the default directories? YES Go to Step 4

NO Go to Step 5
4. Specify output and working storage directories
Over-ride the default directories by passing the -d and -w Go to Step 5
options to the script as follows:
./hiq_backup.sh -d /tmp/backup -w /software/backup
Help can be obtained using the –? option as follows:
./hiq_backup.sh -?
5. Script scans for old backup files

Once the script has been started, it will scan for any old
backup files in the output directory as shown below
********************************
*** HiQ System Backup Script ***
********************************
Setting OS specific parameters...
Checking for old backups...
A31003-H8030-S113-2-7620, June 2007

proc.fm
If any backups are found, they will be listed in reverse order,

as shown below, with the newest backup first, along with the
action that will be taken for each backup - save, replace, or
delete.
Note that the output shown below occurs only if there are
existing backups.
*** OLD Backups found ***
# Modified Size (MB) Action File Name

------------------------------------------------
1 Apr 10 22:05 6532 Save /var/backup/
srx73_Bkup_Apr_10_2004_h22m05s11.tar
2 Apr 07 10:11 6330 Replace /var/backup/
3 Mar 31 14:19 6612 Delete /var/backup/
srx73_Bkup_Mar_31_2004_h14m19s13.tar
Choose handling of above backups:

1) Proceed with above actions
2) Keep all backups (don't delete any)
3) Select handling on per-file basis
4) Exit backup
Enter Option:
Were any backups listed? YES Go to Step 6

NO Go to Step 9
6. Choose handling of backups
Decide what to do with the existing backups:
● Proceed with the default actions (choice 1)
● Keep all old backups (choice 2)
● Select handling on a per-file basis (choice 3)
● Exit backup (choice 4)
By default, the most recent backup is saved, then next most
recent backup is replaced following successful backup, and
all other backups are marked for deletion.
Did you choose 3? YES Go to Step 7
NO Go to Step 8
A31003-H8030-S113-2-7620, June 2007

proc.fm
7. System prompts for backup handling action

The system displays the backup file(s) and prompts for the
desired action as shown below.
Select backups to save, delete or replace:
# Modified Size (MB) File Name

----------------------------------------
1 Apr 10 22:05 6532 /var/backup/
Enter 's' to save, 'd' to delete or 'r' to replace:
Select the desired action for each backup. Go to Step 8

● s = save
● d = delete
● r = replace
● q = quit
Only one backup can be selected for replacement.
8. Confirm selected backup choices
The system displays backup file handling and prompts for
required action as shown below.
All backups have been handled
New backup handling will be:
# Modified Size (MB) Action File Name

-------------------------------------------------
3 Mar 31 14:19 6612 Save /var/backup/
srx73_Bkup_Mar_31_2004_h14m19s13.tar
Enter 'y' to proceed, 'n' to repeat selection:
Enter ‘y’ to proceed or ‘n’ to redo the choice from step 7. Go to Step 9
9. Script checks for available disk space
After checking for old backups, the script performs an
available disk space check on the output and working
storage directories, and outputs the success message
shown below if enough space is available.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Checking available space... Go to Step 10

Available space check passed on backup destination
directory : /var/backup
10. Monitor for not enough space error message

The error message shown below is output if the space
check fails, along with the amount of space required on the
partition containing the output or working directory (in this
case /log).
Checking available space...
/log (containing /log/backup) does not have enough

space.
- Only 3768646 KB are available.
- The backup needs 6483635 KB
Was this error message displayed? YES Go to Step 11

NO Go to Step 12
11. Correct not enough space error
From the /unisphere/srx3000/srx/bin directory, run the Go to Step 2
./clear_backup script on both nodes to remove old patch set
backups as follows:
a. Issue ./clear_backup -list to display the patchsets
installed on the system.
b. Issue ./clear_backup -pset -<nn> to remove
patch set 1 through the patch set you specify with the
-<nn> option.
Caution: Do not use the -base option. This option
removes base package information that is required by
some other software to operate.
c. Run the backup script again and delete old backups.
If the space error reoccurs, delete other files from the
output/working directory partition or specify alternate
output/working directories (override the default directories
in step 3 on page 2-8) and run the backup script again.
A31003-H8030-S113-2-7620, June 2007

proc.fm
12. Script starts backup job

After all checks have passed, the script issues a
background job to create the backup image. The message
shown below is output, and indicates the Process-ID of the
backup job, the log file being used and the name of the final
output image.
Starting backup job... Go to Step 13
Backup job (12937) has started in the background.

Completion could take from 30 min. to 3 hours,
depending on whether the switch is busy.
- Monitor the lock file /lock/.backup_ended to
determine when backup completes.
- Check the log file /log/hiq_backup.sh_12826.log for
backup results.
- If successful, backup output file
will be placed in /var/backup.
13. Do you want to check the backup progress? YES Go to Step 14

NO Go to Step 15
14. Check the backup status
Execute the backup script file as follows:
./hiq_backup.sh -s
If the backup job is still in progress, the output shown below

will be displayed.
Checking backup status...
2 %: Current Size= 77886 MB Estimated Size=
3526456 MB
If the backup job has completed, the output shown below

will be displayed.
Checking backup status... Go to Step 16
Last successful backup completed on Apr 12 12:20
15. Monitor for backup job completion

As instructed in the output message, monitor the /lock
directory for the .backup_ended file which is created to
indicate the backup job has completed. See below for an
example of the completion message in the log file.
*** Backup Completed Successfully *** Go to Step 16
Transfer file /backup/srx72_Bkup_Mar_21_2004_h15m06s06.tar
to a remote storage server
A31003-H8030-S113-2-7620, June 2007

proc.fm
16. Check for errors

If you get the following status:
No current backup jobs running...
Check the log file for more information about
possible failure.
Check the log file for errors.
When the backup job has ended, check the log file for any
errors.
Were any errors detected? YES Go to Step 17
NO Go to Step 20
17. Take corrective action
Refer to Section 2.2.5, “Errors and Error Recovery”, on Go to Step 18
page 2-15 for the appropriate corrective action.
18. Was the error condition corrected? YES Go to Step 20
NO Go to Step 19
19. Escalate error handling
Contact next highest authority for assistance. END
20. Secure image
On successful completion, transfer the created backup
image from the node
to an external USB HDD Go to Step 21
OR
to a secure, remote storage location via FTP or Secure-FTP. Go to Step 26
21. Connect the external USB HDD to the current node
Connect the external USB HDD to one of the node’s USB Go to Step 22
ports and, if appropriate, power the USB HDD on.
22. Execute the script for copying the FS backup file to the
USB HDD
Execute the FS script and specify the -fs option to indicate
that you are copying a FS backup image as follows:
./hiq_backup_exthdd.sh -fs Go to Step 23
A31003-H8030-S113-2-7620, June 2007

proc.fm
23. Select the partition to which the backup file should be

copied
The script lists all the SCSI partitions that it found, apart
from the /dev/sda ones (which are the partitions where the
HiPath application is installed).
The following ext2/ext3 Linux partitions were found
1) /dev/sdb2 (avail space: 15G) Linux
2) /dev/sdb5 (avail space: 7.0M) Linux
3) /dev/sdb6 (avail space: 6.2M) Linux
4) /dev/sdb7 (avail space: 18G) Linux
Please choose the partition to copy the backup file

to (press q to quit): 1
Select the partition to which you want to store the copy of Go to Step 24
the backup file.
24. Select the file system backup file to be copied to the
external USB HDD
The script lists all the FS backup files that it found in the /var/
backup directory of the HiPath node.
The following backup files are available on the
system
1) grd15a_Bkup_Jul_11_2005_h09m03s12.tar (1.6G)
Please choose backup file to be transferred to

external USB HDD (press q to quit): 3
Select the FS backup file to be copied to the USB HDD.

The script checks for available space on the external USB
HDD and copies the selected backup file to the
/backup/cluster_name/node_name directory of the selected
partition of the USB HDD. The backup file is not removed
from the /var/backup directory of the node.
Checking for available space on '/dev/sdb2'...OK Go to Step 25
Making directory 'backup/GRD15S/grd15a' on '/mnt/
exthdd12667'...OK
Transferring backup file to external USB HDD...OK
Unmounting '/mnt/exthdd12667'...OK
Removing directory '/mnt/exthdd12667'...OK
Transfer of backup file to external USB HDD finished
successfully
25. Disconnect the USB HDD from the node Go to Step 26
A31003-H8030-S113-2-7620, June 2007

proc.fm
26. Is this a single-node system? YES END

NO Go to Step 27
27. Have you backed up CE02? YES END
NO Go to Step 28
28. Log into Computing Element 2 (CE02)
See Section 4.1, “Logging into the Computing Element Go to Step 2
(Node)”, on page 4-1 for instructions.
END End of procedure
2.2.5 Errors and Error Recovery

Table 2-2 shows the possible errors and recovery steps when an error occurs during the backup
process. The backup log file is located in /log and is named “hiq_backup_<pid>.log.”
Backup Step Error Type Description & Recovery Action

Initial setup Invalid inputs Check parameters supplied to the
backup script. Execute the script with
the -? option for usage information.
Initial setup Not running as “root” Log in with the super-user account.
Initial setup Failed to create output or working Check specified parameters.
directory
Space Check Unable to calculate free space or Internal script error. Collect log file.
total space
Space Check <file system> could not be found. Unable to find file system to be
backed up. Collect log file.
Space Check Insufficient space on output or Re-execute script and delete old
working directory backups.
Remove other files on output or
working partition.
Specify alternate values for output or
working directory.
Background Failure to dump a file system or create Internal script error. Collect log file.
backup job the tar archive.
execution
Table 2-2 Errors and Recovery Actions
A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup Step Error Type Description & Recovery Action

Background Failure to backup the Solid database Internal script error. Collect log file.
backup job
execution
Table 2-2 Errors and Recovery Actions
A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup the Database Using an External USB HDD
2.3 Backup the Database Using an External USB HDD

Use the following procedure to backup the database of a node and save the backup to an
external USB HDD. If you are not using an external USB HDD to store the backup, refer to
HiPath 8000 Assistant documentation to backup the database.
2.3.1 Procedure
The backup scripts only recognize EXT2/EXT3 partitions on the external USB HDD.
> Partitions with other formats (for example, FAT32 or NTFS) are not recognized and
you will not be able to backup files to those partitions.
1. Log into the desired node as root Go to Step 2

2. Connect the external USB HDD to the node
Connect the external USB HDD to one of the node’s USB ports Go to Step 3
and, if appropriate, power the USB HDD on.
3. Change to the /var/backup directory
Change to the /var/backup directory as follows:
#> cd /var/backup Go to Step 4
4. Execute the script for creating the database backup file and
copying it to the USB HDD
Execute the script and specify the -db option to indicate that you
are creating a database backup as follows:
./hiq_backup_exthdd.sh -db Go to Step 5
A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup the Database Using an External USB HDD
5. Select the partition to which the backup file should be

copied
The script lists all the SCSI partitions that it found, apart from the
/dev/sda ones (which are the partitions where the HiPath
application is installed).
1) /dev/sdb2 (size: 13G) Linux
2) /dev/sdb5 (size: 7.0M) Linux
Please choose the partition to copy the backup file

(press q to quit): 1
Select the partition to which you want to store the copy of the
backup file.
The database backup file is created and copied to the USB HDD.
The script creates the DB backup file (by calling an existing script
responsible for the task), checks for available space on the
external USB HDD and copies the created DB backup file to the
partition of the USB HDD. The original backup file is moved to
the /opt/unisphere/srx3000/mmgr/backup directory of the node.
Partition '/dev/sdb2' was chosen Go to Step 6
Creating mount point '/mnt/exthdd21510'...OK
Mounting partition '/dev/sdb2' on '/mnt/
exthdd21510'...OK
Creating database backup, please wait...OK
Checking for available space on '/dev/sdb2'...OK
Making directory 'backup/GRD15S/grd15a' on '/mnt/
exthdd21510'...OK
Copying database backup file to USB HDD...OK
Backup file was copied to '/mnt/exthdd21510/backup/
GRD15S/grd15a' as 'backup_all_Jul_14_2005_15h30m11s.tar'
Moving initial backup file 'backup_all.tar' to '/opt/
unisphere/srx3000/mmgr/backup'...OK
Database backup file created and transferred to external
USB HDD successfully
6. Disconnect the USB HDD from the node END

A31003-H8030-S113-2-7620, June 2007

proc.fm
Backup the Database Manually Using the Backup Script
2.4 Backup the Database Manually Using the Backup Script

Use the following procedure to backup the database manually using the backup.sh script and
store it to a different machine.
2.4.1 Procedure
Create a database backup and store it to a different machine as follows:
1. On either node, identify which node is active and on which node the database is running
with the command:
# su - srx -c “RtpSolid -l”
2. If necessary, switch nodes with the command:
# su - srx -c “RtpSolid -X”
3. From the active node where the database is running, start the database backup with the
following commands:
# cd /opt/unisphere/srx3000/mmgr/job/bin/backup_restore
# ./backup.sh
4. After the backup is complete (it takes several minutes), locate the database backup file
(backup_all.tar) with the command:
# cd /opt/unisphere/srx3000/mmgr/backup
5. Copy and paste the backup_all.tar file to a different machine (for example, a Windows PC).
2.5 Restore the Database Using an External USB HDD

Use the following procedure to restore the database from a DB backup file that is stored on an
external USB HDD.
2.5.1 Procedure
The restore scripts only recognize EXT2/EXT3 partitions on the external USB HDD.
you will not be able to use backup files from those partitions.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore the Database Using an External USB HDD

Change to the /var/backup directory as follows:
4. Execute the script for restoring the database from a USB
HDD
Execute the script and specify the -db option to indicate that you
are restoring a database as follows:
./hiq_restore_exthdd.sh -db Go to Step 5
5. Select the partition from which the backup file should be
retrieved

Please choose the partition that contains the backup file

Select the partition from which you want to retrieve the database Go to Step 6
backup file.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore the Database Using an External USB HDD
6. Select the database backup file to be retrieved from the

external USB HDD
The script lists all the DB backup files that it found in the
/backup/cluster_name/node_name directory of the external USB
HDD.
Directory '/backup/GRD15S/grd15a' on '/dev/sdb2' contains
the following backup files
1) backup_all_Jul_14_2005_15h30m11s.tar (13M)
2) backup_all_Jul_13_2005_18h01m46s.tar (13M)
Please choose backup file to be used (press q to quit): 1
Select the backup file to be retrieved from the USB HDD.

The script checks for available space on the /opt/unisphere/
srx3000/mmgr/job/bin/backup_restore directory of the node and
retrieves the selected backup file from the /backup/cluster_name/
node_name directory of the selected partition of the USB HDD.
Finally, it calls an existing script to perform the actual DB restore
from the backup file. The backup file is copied to the appropriate
directory of the node and is not removed from the external USB
HDD.
Checking for available space on '/opt/unisphere/srx3000/ Go to Step 7
mmgr/job/bin/backup_restore'...OK
Retrieving database backup file from USB HDD...OK
Restoring database from backup file, please wait...
<<Output without interest cut from here>>
Database restore finished successfully
7. Disconnect the USB HDD from the node END

A31003-H8030-S113-2-7620, June 2007

proc.fm
Retrieve the File System Backup from an External USB HDD
2.6 Retrieve the File System Backup from an External USB HDD
Use the following procedure to retrieve a file system backup file from an external USB HDD.
This procedure is typically executed just before a restore of individual files/directories (refer to
Section 2.8 on page 2-24).
2.6.1 Procedure
The restore scripts only recognize EXT2/EXT3 partitions on the external USB HDD.
you will not be able to use backup files from those partitions.

Change to the /var/backup directory as follows.
4. Execute the script for retrieving the FS backup file from the
USB HDD
Execute the FS script and specify the -fs option to indicate that
you are retrieving a FS backup image as follows:
./hiq_restore_exthdd.sh -fs Go to Step 5
retrieved
application is stored).

Please choose the partition that contains the backup file

A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore the Database Manually Using the Restore Script
Select the partition that contains the backup file. Go to Step 6

6. Select the file system backup file to be retrieved from the
external USB HDD
The script lists all the FS backup files that it found in the
/backup/cluster_name/node_name directory of the external USB
HDD.
Directory 'backup/GRD15S/grd15a' on '/dev/sdb2' contains
the following backup files
3) grd15a_Bkup_Mar_18_1993_h19m05s55.tar (1.6G)
Please choose backup file to be retrieved (press q to

quit): 1
Select the backup file to be retrieved from the USB HDD.

The script checks for available space on the /var/backup directory
of the node and retrieves the selected backup file from the /
backup/cluster_name/node_name directory of the selected
partition of the USB HDD. The backup file is copied to the /var/
backup directory of the node and is not removed from the external
USB HDD.
Checking for available space on '/var/backup'...OK Go to Step 7
Retrieving backup file from USB HDD...OK
Retrieval of backup file from external USB HDD finished
successfully
7. Disconnect the USB HDD from the node

Refer to Section 2.8 on page 2-24 to restore individual END
files/directories.
2.7 Restore the Database Manually Using the Restore Script

Use the following procedure to restore the database manually using the restore.sh script.
2.7.1 Procedure
Restore a database backup as follows:
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore Individual Files/Directories for a Single Node
The restore database procedure must be run from the primary node and it must be
> at state 4.
1. From either node, identify the primary node with the command:
# su - srx -c “RtpSolid -l”
2. If necessary, switch nodes with the command:
# su - srx -c “RtpSolid -X”
3. Ensure that the primary node is at state 4 with the command:
# /unisphere/srx3000/srx/startup/./srxqry
4. Copy the backup_all.tar file from the machine where you stored it and paste it back into the
/opt/unisphere/srx3000/mmgr/backup directory.
The name of the database backup file must be backup_all.tar or the restore.sh
> script will not run.
5. From the primary node, start the restore.sh script with the following commands:
# cd /opt/unisphere/srx3000/mmgr/job/bin/backup_restore
# ./restore.sh
After several minutes the database should be successfully restored.
2.8 Restore Individual Files/Directories for a Single Node

Individual file/directory restore is accomplished using the restore command. Restore can be
done on either the target machine or on any other Linux machine where the backup archive file
is stored.
You must be logged in as root to execute the commands and scripts in the following
> procedure. In order to perform this procedure, the node must be running from the
node’s hard disks. If the node is not able to boot from the hard disks, refer to Section
2.9 on page 2-27 or Section 2.10 on page 2-39 as appropriate.
A31003-H8030-S113-2-7620, June 2007

proc.fm
2.8.1 Procedure
1. Login to appropriate node as superuser Go to Step 2

2. Change directories
Change from the current directory to the directory where the Go to Step 3
backup archive file is stored as follows.
#> cd /var/backup
If the backup archive is not in /var/backup, replace /var/
backup with the correct directory location.
3. List backup tar archive contents
The archive contains multiple backup images, one for each
backed-up disk partition as shown below.
#> tar -tvf srxl22_Bkup_Jun_15_2004_h13m04s16.tar
-rw------- solid/dba 50921472 2004-06-15 solid.db
-rw-r--r-- root/root 369677181 2004-06-15 root.bk
-rw-r--r-- root/root 7735675 2004-06-15 home.bk
-rw-r--r-- root/root 176115988 2004-06-15 opt.bk
-rw-r--r-- root/root 369382572 2004-06-15 unisphere.bk
-rw-r--r-- root/root 3388611490 2004-06-15 var.bk
Where srxl22_Bkup_Jun_15_2004_h13m04s16.tar is the Go to Step 4

name of the backup archive file.
4. Extract appropriate backup image
Extract the backup image corresponding to the disk partition Go to Step 5
on which the files/directories to be restored are located:
#> nice -19 tar -xvf <backup archive file> unisphere.bk
unisphere.bk
5. Open backup image

Open the backup image in the interactive mode using the
restore command shown below:
#> restore -aif unisphere.bk Go to Step 6
Dump tape is compressed.
restore >
A31003-H8030-S113-2-7620, June 2007

proc.fm
6. List backup image contents

Use the ‘ls’ command to list the contents of the backup
image as shown below.
restore > ls Go to Step 7
.:
lost+found/ srx3000/
The above lists the directories from the root of the backup
image, in this case from /unisphere.
7. Change directories
Use the ‘cd’ command to change-directory within the
archive to the location of the file/directory to be restored,
then list the directory contents as shown below:
restore > cd srx3000/callp/bin
restore > ls
./srx3000/callp/bin:
Following is the contents of the bin directory

CDRHandler h323shm pdm
Cdm.exe h323sm prmgr
DNMP keys/ rsstest
EMHandler megacoccm# rtm
HiPathSubAgtPriLinux mgcpcm.exe samm
HiQSubAgtPriocntl mlhg sdmmain
OmapDispatcher mlhgprint sipsm
OpOvlTest= omapsm smdi
SrxMgcpShm omm smm
SrxMgcpSm ommprint spm
SrxUscConvert opovl_display_log srxVip.exe
Xdm.exe oprtt_ctl syncRTM
acarscan oprtt_dload trcmgr
admmain oprtt_driver ttud
caleadf oprtt_install ttudDaemon
cassm= oprtt_priocntl ucemain
cstasm= oprtt_read xlaMemDisplay
dbmanager oprtt_start xlaverify
digitMapCli oprtt_stop
genCmnTrcFile.pl= ovlMgr
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore File System for a Single Node in a Redundant System
Ignore any warnings that are displayed as a result of Go to Step 8

executing the ‘ls’ command.
8. Create list of files/directories to restore
Create a list of files/directories to be restored using the ‘add’
command as shown below:
restore > add oprtt_start
restore > add keys
restore > add ttud
In this example, oprtt_start, keys, and ttud have been added Go to Step 9
to the list of files/directories to restore.
9. Extract files
Extract the files using the ‘extract’ command. Wait for the
files/directories to be extracted. Answer ‘n’ to set the owner/
mode of the extracted file/directory as shown below.
restore > extract Go to Step 10
set owner/mode for '.'? [y/n] n
10. Quit restore

Quit restore using the ‘quit’ command as shown below:
restore > quit Go to Step 11
11. Verify files
The extracted files/directories should now be present in the Go to Step 12
current directory.
Use the ‘ls’ command to verify that the files/directories have
been extracted correctly.
12. Move files to desired location
Move the extracted files/directories from the current END
directory to the desired target location using the ‘mv’
command.
2.9 Restore File System for a Single Node in a Redundant System

The following sections provide the information necessary to restore a single node back into a
redundant system, where the partner node is operating normally. To restore a file system for
the node in a single-node system, refer to Section 2.10 on page 2-39.
A31003-H8030-S113-2-7620, June 2007

proc.fm
The procedure restores the operating system as well as the file system to a point
> where the node is restored to a running and bootable state.
2.9.1 Prerequisites
Prior to beginning the restore procedure, the following prerequisites must be fulfilled:
● The hardware of the node to be restored is fully functional.
● New hardware, other than the HDDs, must be identical to the original node hardware. The
HDDs can be the same size or larger.
If you replace a hard disk drive in a node, ensure that the SCSI RAID controller
> on that node is reconfigured as described in Section 3 of the HiPath 8000
Installation and Upgrade Guide. If this is not done, SLES9 might not recognize
the new hard drive and you will not be able to restore the system from the
backup.
● Access to the external USB HDD or to the backup server on which the backup images are
located.
● The Restore CD (it is recommended that the latest release of the Restore CD is used) is
available.
● The SLES9-system-restore-boot-cd is available.
2.9.2 Information Requirements

The following information needs to be available in preparation for the restore:
● The name(s) of the physical Ethernet interface(s) that will be used to connect from the
restored node(s) to the IP network (Example: eth0, hme0, bge0 etc.).
● The IP address(es) for the Ethernet interfaces identified above.
● If necessary, the IP address of the router used to access the storage server.
● The name of the backup file to be used to restore the node. The name should include the
complete path name required to access the file on the server.
● The user-id and password required for retrieving files from the storage server.
● If applicable, the name of the partition of the external USB HDD that contains the backup
image (for example, /dev/sdb2).
A31003-H8030-S113-2-7620, June 2007

proc.fm
● The cluster name and node name of the Hipath 8000 node that needs to be restored (the
FS restore script asks the user for the path [in the form /backup/cluster_name/node_name]
of the directory that contains the backup file).
You must be logged in as root to execute the commands and scripts in this
> procedure.
2.9.3 Procedure
The restore scripts recognize EXT2/EXT3, NTFS, and FAT32 partitions (the FAT32
> format only allows for a backup file size of up to 4GB minus 1 byte in length) on the
external USB HDD. This procedure assumes that EXT2/EXT3 partitions are used.
Caution: Performing this procedure will erase all data on the target node. Do not
7 perform this procedure unless a verified backup of the node is available.
1. Setup
To perform this procedure, you must have a monitor and Go to Step 2
keyboard connected to the node that is to be restored.
The actions that follow must be performed on the node that
is to be restored.
2. Boot system
Power the system off, then on.
Insert SLES9-system-restore-boot-cd into the DVD drive. Go to Step 3
3. Wait for system to initialize and boot from DVD
(If a dialog box appears stating: “You are about to install 32-
bit software on a 64-bit machine,” click OK.)
Select option Rescue Mode and specify pci=noacpi
Select keyboard type English
Wait for the Rescue login: prompt
Enter userid root (no password required) Go to Step 4
A31003-H8030-S113-2-7620, June 2007

proc.fm
4. Insert the Restore CD

Remove the SLES9-system-restore-boot-cd from the DVD Go to Step 5
drive. Insert the Restore CD into the DVD drive.
Note: It is recommended that the latest release of the
Restore CD is used.
5. Mount the CD
Mount the CD as follows (the mount point for Version 3.0 is Go to Step 6
/media/cdrom):
mkdir /media/cdrom
mount /dev/hda /media/cdrom
cd /media/cdrom
6. Execute the master restore script

Execute the master restore script to begin the restore
procedure. Two modes are possible–interactive or
automatic.
● Automatic mode runs all restore steps in sequence and
should be the normal choice.
● Interactive mode allows you to select the restore steps
one at a time, and is helpful for troubleshooting.
Choose the execution mode:
Automatic mode:
./hiq_restore.sh
Interactive mode (see note below):
./hiq_restore.sh -i
Note: Selecting interactive mode is discouraged. If you Go to Step 7

select interactive node, you will be presented with a Restore
Menu and prompted to select an option. Should you decide
to select the interactive mode, select the options in order,
i.e., 1, 2, 3.
A31003-H8030-S113-2-7620, June 2007

proc.fm
7. Initialize disk
When prompted, select the disk partition preference:
Note: Depending on the release level of the Restore CD, the
disk partition preference options shown may be different.
Please indicate the disk partition preference.
1. Release R8 and R9.
2. Release R10.x (V2.x) with old partitions.
/software/trace is 3 Gb.”
3. Release R10.x (V2.x) with Symphonia with old partitions.
4. Release R10.x (V2.x) IBM3650T with old partitions
/software/trace is 6 Gb.
5. Release R1x.x (V3.x) 73Gb Disk
/software is 8 Gb.
6. Generic with Symphonia and 73Gb Disk.
7. Release R1x.x (V3.x) 146Gb Disks
/software is 50Gb.
Note: If a HDD replacement results in a system with HDDs
of different capacities, use the option for the smaller
capacity HDD.
Options 1, 2, 3, and 4: Not applicable for V3.0 system.
Option 5: Use for a IBM x346-based system, 73 GB HDD,
and 8 GB /software partition.
Options 6: Use for IBM x346-based system and 73 GB
HDD.
Option 7: Use for a system with 146 GB HDDs and 50 GB
/software partition.
The restore script will now attempt to initialize the local disks
as shown below. This includes setting up the partition table
and creating file-systems on each partition.
Initiating Step: Disk Setup...
*** WARNING ***
This will erase ALL PARTITIONS AND DATA on /dev/sda!
Proceed with create disk label? [y/n] Total disk
space: 70006 MB
Creating partitions
Please wait...
Disk Setup Completed Successfully
A31003-H8030-S113-2-7620, June 2007

proc.fm
No interaction is required here. Go to Step 8

If an error occurs, refer to Table 2-3 on page 2-38 for
possible corrective actions.
A final warning is printed before proceeding to indicate the
disks on which data will be lost.
Enter ‘y’ to proceed with the initialization, or ‘n’ to exit the
script.
8. If applicable, connect the external USB HDD to the node
If you are retrieving the file system backup file from an Go to Step 9
external USB HDD, connect it to one of the node’s USB
ports and, if appropriate, power the USB HDD on.
9. Select backup file transfer mode
Following successful disk setup, select the transfer mode
that will be used to retrieve the backup file as shown below.
Either FTP, Secure FTP, or an external USB HDD can be
used (the external USB HDD must have been connected in
the previous step for option 3 to be displayed).
Initiating Step: Backup File Retrieval...
Enter backup source:

1...FTP Server (ftp)
2...Secure FTP Server (sftp)
3...External USB hard disk drive
Select either
1...FTP Server (ftp) or 2...Secure FTP Server (sftp) Go to Step 10
OR
3...External USB hard disk drive Go to Step 14
10. Enter the backup file name
Enter the backup file name, including the path required to
access the file on the FTP/sFTP server as shown below.
Enter Backup File Name []: Go to Step 11
/export/home/sis/jumpsrx/sctests/
A31003-H8030-S113-2-7620, June 2007

proc.fm
11. Respond to prompts for network parameters

Enter the parameters required for network setup, when
prompted by the script as shown below. Use eth0 for the
device parameter.
Enter Device to be used [eth0]: Go to Step 13
Enter Node's IP Address []: 10.77.82.10
Enter Node's NetMask []: 255.255.255.0
Enter Node's Default Gateway []: 10.77.82.1
The local IP interface, default router, server IP address, user

name, and password must be entered.
12. Respond to the prompt for the network parameters for
the backup server
Enter the IP address, netmask, and gateway for the backup
server.
13. Restore script retrieves backup file
The restore script now attempts to connect to the storage
server and retrieve the backup file as shown below.
Connecting......
Transfering file. May take up to 30 minutes. Please wait...
Progress.................................................
.........................................................
.........................................................
.........................................................
................................................
Transfer finished!
If an error occurs, the script prompts for a retry, and then Go to Step 17
requests re-entry of all network related parameters
(parameters entered the last time are retained as defaults),
before attempting to retrieve the backup file again.
14. Select the partition from which the backup file should
be retrieved
The script lists all the SCSI partitions that it found, apart
from the /dev/sda ones (which are the partitions where the
HiPath application is installed).
A31003-H8030-S113-2-7620, June 2007

proc.fm

Please choose partition containing the backup file


15. Specify the path of the directory that contains the
backup file(s)
Because the node has been booted from the SLES9 DVD,
the restore script has no means of finding out the cluster
name and node name of the node that is currently being
restored.
Please give path of directory containing the backup
file(s) on '/dev/sdb2' (i.e. /backup/cluster_name/
node_name)
/backup/GRD15S/grd15a
Specify the path of the directory that contains the backup Go to Step 16
file(s) in the form, “/backup/cluster_name/node_name.”
16. Select the backup file to be retrieved from the external
USB HDD
user-specified directory (/backup/cluster_name/
node_name) of the external USB HDD.
Directory '/backup/GRD15S/grd15a' on '/dev/sdb2'
contains the following backup files

quit): 1
Select the backup file to be retrieved from this directory.

The script retrieves the selected backup file from the
partition of the USB HDD to a temporary storage space on
the node. The backup file is copied to the node and is not
removed from the external USB HDD.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Retrieving backup file Go to Step 17

'grd15a_Bkup_Jul_11_2005_h12m34s29.tar' from '/mnt/
exthdd1719//backup/GRD15S/grd15a', please wait...OK
17. Restore script extracts backup images

After successful retrieval of the backup file, the script
extracts individual backup images from the complete tar file
as shown below.
Extracting individual backup files...
This step takes approximately 5 minutes. No interaction is Go to Step 18

required.
18. If applicable, disconnect the external USB HDD from
the node
When the script starts extracting the individual backup files, Go to Step 19
disconnect the USB HDD from the USB port of the node.
19. Restore script restores file systems
Once the backup images have been extracted, the script
restores the individual file systems onto corresponding
partitions on the disk as shown below.
Restoring file systems...
This may take a long time. Please wait...
Restoring File System "/mnt/home"...
File System "/mnt/home" restored...
Restoring File System "/mnt/opt"...
File System "/mnt/opt" restored...
Restoring File System "/mnt/root"...
File System "/mnt/root" restored...
Restoring File System "/mnt/unisphere"...
File System "/mnt/unisphere" restored...
Restoring File System "/mnt/var"...
File System "/mnt/var" restored...
Disk type and fstab file matched OK...
Restore Completed

required.
A31003-H8030-S113-2-7620, June 2007

proc.fm
20. Restore script makes disk bootable

Finally, the script installs the LILO boot loader to make the
disk bootable as shown below.
Initiating Step: Make Disk Bootable...
Make Disk Bootable Completed Successfully
Exiting...
This step takes approximately 30 seconds. No interaction is Go to Step 21

required.
21. Unmount the CD and remove the Restore CD from the
DVD drive.
Unmount the CD as follows:
cd
umount /media/cdrom
Remove the CD from the DVD drive. Go to Step 22

22. Reboot the node
After the restore script has ended, reboot the node using the Go to Step 23
“reboot” command.
23. Wait for node to reboot and go to State 3 Go to Step 24
24. Log into the node as superuser Go to Step 25
25. Replace the srxBootParams file
Replace the srxBootParams file as follows Go to Step 26
cd /unisphere/srx3000/srx/startup
rm srxBootParams
mv srxBootParams.orig srxBootParams
26. Restore database

Perform the following database restore steps after the Go to Step 30
reboot has completed. These steps should be executed on
the opposite node (the node that remained running in state
4 while the current node was restored):
● Connect to the database as follows:
/opt/solid/bin/solsql “tcpip 16760” dba dba
● Check the state of the node as follows:
ADMIN COMMAND ‘hsb state’;
A31003-H8030-S113-2-7620, June 2007

proc.fm
27. Is the state PRIMARY ACTIVE? YES Go to Step 28

NO Go to Step 29
28. Exit the database
Exit the database as follows: END
exit;
29. State is PRIMARY ALONE

Do the following” Go to Step 30
● Start a “netcopy” operation of the database to the
standby node as follows:
ADMIN COMMAND ‘hsb netcopy’;
● After the netcopy operation has completed, connect to
the standby and exit as follows:
ADMIN COMMAND ‘hsb connect’;
exit;
30. Start the RTP

From the /unisphere/srx3000/srx/startup directory, execute END
the following script:
./srxctrl 4 0
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore Step Error Type Description & Recovery Action

Disk Setup Failure to locate local or external Execute the parted command
disks. manually and check the list of printed
disks to ensure that the system boot
disk is listed. The boot disk should be
/dev/hd”x” or /dev/sd”x” on one of the
controllers.
If the system disk is not listed, the
restore cannot proceed – hardware
installation troubleshooting is
required. Restart the complete
restore process once the problem has
been corrected.
If the system disk is listed in the
format output, escalate error
resolution to next highest fault
clearance authority.
Error: Failed to compute system disk This is a script error; collect log file
size and escalate error resolution to next
highest fault clearance authority.
Error: Create Partitions Failed One or more partitions were not
created on the local disks using the
“mkpart” command.
Escalate error resolution to next
Error: Modify to ext3 Failed One or more partitions were not
modified on the local disks using the
“mkfs.ext3” command.
File Transfer Error: File transfer not started or 1. Network problem. Check network
aborted status.
2. IP inputs and/or file name given in
step 10 are incorrect
Table 2-3 System Restore Errors and Corrective Actions (Sheet 1 of 2)
A31003-H8030-S113-2-7620, June 2007

proc.fm
Restore File System for a Single-Node or Redundant System

File Unpacking Error: File unpacking Failed Backup file is corrupted or file is not
the perceived correct file.
Check the size of the file on the
server; it should be just under 1GB.
If file appears to be correct, collect log
file and escalate error resolution to
next highest fault clearance authority.
File System Error: Restore File System Failed This is a script error; collect the log file
Restore and escalate error resolution to next
Boot partition Error: Boot partition configuration This is a script error; collect log file
configuration Failed and escalate error resolution to next
2.10 Restore File System for a Single-Node or Redundant System
The procedure in this section restores the operating system as well as the file
> system to a point where the node in a single-node system or both nodes in a
redundant system are restored to a running and bootable state.
2.10.1 Prerequisites
Prior to beginning the restore procedure, the following prerequisites must be fulfilled:
● The hardware of the node or nodes to be restored is fully functional.
● New hardware, other than the HDDs, must be identical to the original node hardware. The
HDDs can be the same size or larger.
If you replace a hard disk drive in a node, ensure that the SCSI RAID controller
> on that node is reconfigured as described in Section 3 of the HiPath 8000
Installation and Upgrade Guide. If this is not done, SLES9 might not recognize
the new hard drive and you will not be able to restore the system from the
backup.
● Access to the external USB HDD or to the backup server on which the backup images are
located.
A31003-H8030-S113-2-7620, June 2007

proc.fm
● One or two (required to restore both nodes in a duplex system simultaneously) Restore
CDs (it is recommended that the latest release of the Restore CD is used).
● One or two (required to restore both nodes in a duplex system simultaneously) SLES9-
system-restore-boot-cd CDs.
Two monitors and keyboards are required to restore a redundant system (one
> for each node) if the HiPath 8000 does not include a KVM switch and you want
to restore both nodes simultaneously. You must be logged in as root to execute
the commands and scripts in the procedure.
2.10.2 Information Requirements

The following information needs to be available in preparation for the restore:
This information will not necessarily be used; however, it should be on hand in the
> event problems are encountered.
● The name(s) of the physical Ethernet interface(s) that will be used to connect from the
restored node(s) to the IP network (Example: eth0, hme0, bge0 etc.).
● The IP address(es) for the Ethernet interfaces identified in above.
● If necessary, the IP address of the router used to access the storage server.
● The names of the backup files to be used to restore the nodes. The name should include
the complete path name required to access the files on the server.
● The user-id and password required for retrieving files from the storage server.
● If applicable, the name of the partition of the external USB HDD that contains the backup
image (for example, /dev/sdb2).
● The cluster name and node name of the Hipath 8000 node that needs to be restored (the
FS restore script asks the user for the path [in the form /backup/cluster_name/node_name]
of the directory that contains the backup file).
2.10.3 Procedure
The restore scripts recognize EXT2/EXT3, NTFS, and FAT32 partitions (the FAT32
> format only allows for a backup file size of up to 4GB minus 1 byte in length) on the
external USB HDD. This procedure assumes that EXT2/EXT3 partitions are used.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Caution: Executing this procedure will erase all data on both nodes. Do not execute
7 this procedure unless a verified backup of the node is available.
1. Setup
To perform this procedure simultaneously on both nodes in a Go to Step 2
redundant system, you must have a monitor and keyboard
connected to each node or a monitor and keyboard
connected to the HiPath 8000 KVM switch.
The actions that follow must be performed on both nodes in
a redundant system; however, they do not have to be
performed simultaneously.
If you have two sets of CD/DVDs and the appropriate
equipment to restore the nodes simultaneously, perform this
procedure on CE 01 and CE 02 at the same time.
If you only have one set of CD/DVDs, perform this procedure
on CE 01 first, then CE02.
If you are restoring a single-node system, perform this
procedure on CE 01.
2. Boot system
Power the system off, then on.
Insert SLES9-system-restore-boot-cd into the DVD drive. Go to Step 3
A31003-H8030-S113-2-7620, June 2007

proc.fm
3. Wait for system to initialize and boot from DVD

(If a dialog box appears stating: “You are about to install 32-
bit software on a 64-bit machine,” click OK.)
Select option Rescue Mode and specify pci=noacpi
Select keyboard type English
Wait for the Rescue login: prompt
Enter userid root (no password required) Go to Step 4
4. Insert the Restore CD
Remove the SLES9-system-restore-boot-cd from the DVD Go to Step 5
drive.
Insert the Restore CD into the DVD drive.
Note: It is recommended that the latest release of the
Restore CD is used.
5. Mount the CD
Mount the CD as follows (the mount point for Version 3.0 is Go to Step 6
/media/cdrom):
mkdir /media/cdrom
mount /dev/hda /media/cdrom
cd /media/cdrom
6. Execute the master restore script
Execute the master restore script to begin the restore
procedure. Two modes are possible – interactive or
automatic.
● Automatic mode runs all restore steps in sequence and
should be the normal choice.
● Interactive mode allows you to select the restore steps
one at a time, and is helpful for troubleshooting.
Choose the execution mode:
● Automatic Go to Step 7
./hiq_restore.sh
● Interactive (see note below)
./hiq_restore.sh -i
Note: Selecting interactive mode is discouraged. If you select
interactive node, you will be presented with a Restore Menu
and prompted to select an option. Should you decide to
select the interactive mode, select the options in order, i.e., 1,
2, 3.
A31003-H8030-S113-2-7620, June 2007

proc.fm
7. Initialize disk
When prompted, select the disk partition preference:
Note: Depending on the release level of the Restore CD, the
disk partition preference options shown may be different.
Please indicate the disk partition preference.
1. Release R8 and R9.
2. Release R10.x (V2.x) with old partitions.
/software/trace is 3 Gb.”
3. Release R10.x (V2.x) with Symphonia with old partitions.
4. Release R10.x (V2.x) IBM3650T with old partitions
/software/trace is 6 Gb.
5. Release R1x.x (V3.x) 73Gb Disk
/software is 8 Gb.
6. Generic with Symphonia and 73Gb Disk.
7. Release R1x.x (V3.x) 146Gb Disks
/software is 50Gb.
Note: If a HDD replacement results in a system with HDDs of
different capacities, use the option for the smaller capacity
HDD.
Options 1, 2, 3, and 4: Not applicable for V3.0 system.
Option 5: Use for a IBM x346-based system, 73 GB HDD,
and 8 GB /software partition.
Options 6: Use for IBM x346-based system and 73 GB HDD.
Option 7: Use for a system with 146 GB HDDs and 50 GB
/software partition.
The restore script will now attempt to initialize the local disks
as shown below. This includes setting up the partition table
and creating file-systems on each partition.
Initiating Step: Disk Setup...
*** WARNING ***
This will erase ALL PARTITIONS AND DATA on /dev/sda!
Proceed with create disk label? [y/n] Total disk space:
70006 MB
Creating partitions
Please wait...
Disk Setup Completed Successfully
A31003-H8030-S113-2-7620, June 2007

proc.fm
No interaction is required here. Go to Step 8

If an error occurs, refer to Table 2-3 on page 2-38 for possible
corrective actions.
A final warning is printed before proceeding to indicate the
disks on which data will be lost.
Enter ‘y’ to proceed with the initialization, or ‘n’ to exit the
script.
8. If applicable, connect the external USB HDD to the node
If you are retrieving the file system backup file from a USB Go to Step 9
HDD, connect the external USB HDD to one of the node’s
USB ports and, if appropriate, power the USB HDD on.
9. Select backup file transfer mode
Following successful disk setup, select the transfer mode that
will be used to retrieve the backup file as shown below. Either
FTP, Secure FTP, or an external USB HDD can be used (the
external USB HDD must have been connected in the
previous step for option 3 to be displayed).
Initiating Step: Backup File Retrieval...
Enter backup source:

1...FTP Server (ftp)
2...Secure FTP Server (sftp)
3...External USB hard disk drive
Select either
1...FTP Server (ftp) or 2...Secure FTP Server (sftp) Go to Step 10
OR
3...External USB hard disk drive Go to Step 14
10. Enter the backup file name
Enter the backup file name, as shown below.
Enter Backup File Name []:
/export/home/sis/jumpsrx/sctests/
Enter the backup file name, including the path required to Go to Step 11
access the file on the FTP/sFTP server.
11. Respond to prompts for network parameters
Enter the parameters required for network setup, when
prompted by the script as shown below. Use eth0 for the
device parameter.
A31003-H8030-S113-2-7620, June 2007

proc.fm
Enter Device to be used [eth0]:

Enter Node's IP Address []: 10.77.82.10
Enter Node's NetMask []: 255.255.255.0
Enter Node's Default Gateway []: 10.77.82.1
The local IP interface, default router, server IP address, user Go to Step 13
name, and password must be entered.
For a duplex system, you will be prompted again to enter the
network parameters for the other node.
12. Respond to the prompt for the network parameters for
the backup server
Enter the IP address, netmask, and gateway for the backup
server.
13. Restore script retrieves backup file
The restore script now attempts to connect to the storage
server and retrieve the backup file as shown below.
Connecting......
Transfering file. May take up to 30 minutes. Please wait...
Progress..................................................
..........................................................
..........................................................
..........................................................
............................................
Transfer finished!
If an error occurs, the script prompts for a retry, and then Go to Step 17
requests re-entry of all network related parameters
(parameters entered the last time are retained as defaults),
before attempting to retrieve the backup file again.
A31003-H8030-S113-2-7620, June 2007

proc.fm
retrieved
The script lists all the SCSI partitions that it found, apart from
the /dev/sda ones (which are the partitions where the HiPath

Please choose partition containing the backup file

15. Specify the path of the directory that contains the
backup file(s)
Because the node has been booted from the SLES9 DVD,
the restore script has no means of finding out the cluster
name and node name of the node that is currently being
restored.
Please give path of directory containing the backup
file(s) on '/dev/sdb2' (i.e. /backup/cluster_name/
node_name)
/backup/GRD15S/grd15a
Specify the path of the directory that contains the backup Go to Step 16
file(s) in the form, “/backup/cluster_name/node_name.”
16. Select the backup file to be retrieved from the external
USB HDD
specified directory (/backup/cluster_name/node_name) of
the external USB HDD.
Directory '/backup/GRD15S/grd15a' on '/dev/sdb2'
contains the following backup files

quit): 1
Select the backup file to be retrieved from this directory.
A31003-H8030-S113-2-7620, June 2007

proc.fm
The script retrieves the selected backup file from the

partition of the USB HDD to a temporary storage space on
the node. The backup file is copied to the node and is not
removed from the external USB HDD.
Retrieving backup file Go to Step 17
'grd15a_Bkup_Jul_11_2005_h12m34s29.tar' from '/mnt/
exthdd1719//backup/GRD15S/grd15a', please wait...OK
17. Restore script extracts backup images
After successful retrieval of the backup file, the script extracts
individual backup images from the complete tar file as shown
below.
Extracting individual backup files...

required.
corrective actions.
18. If applicable, disconnect the external USB HDD from the
node
When the script starts extracting the individual backup files, Go to Step 19
disconnect the USB HDD from the USB port of the node.
A31003-H8030-S113-2-7620, June 2007

proc.fm
19. Restore script restores file systems

Once the backup images have been extracted, the script
restores the individual file systems onto corresponding
partitions on the disk as shown below.
Restoring file systems...
This may take a long time. Please wait...
Restoring File System "/mnt/home"...
File System "/mnt/home" restored...
Restoring File System "/mnt/opt"...
File System "/mnt/opt" restored...
Restoring File System "/mnt/root"...
File System "/mnt/root" restored...
Restoring File System "/mnt/unisphere"...
File System "/mnt/unisphere" restored...
Restoring File System "/mnt/var"...
File System "/mnt/var" restored...
Disk type and fstab file matched OK...
Restore Completed
required.
corrective actions.
20. Restore script makes disk bootable
Finally, the script installs the LILO boot loader to make the
disk bootable as shown below.
Initiating Step: Make Disk Bootable...
Make Disk Bootable Completed Successfully
Exiting...
This step takes approximately 30 seconds. No interaction is Go to Step 21
required.
corrective actions.
21. Unmount the CD and remove the Restore CD from the
DVD drive.
Unmount the CD as follows:
cd
umount /media/cdrom
Remove the CD from the DVD drive. Go to Step 22
22. Reboot CE01
After the restore script has ended, reboot CE01 using the Go to Step 23
“reboot” command.
23. Is this a single-node system? YES Go to Step 25
NO Go to Step 24
A31003-H8030-S113-2-7620, June 2007

proc.fm
24. Wait 30 seconds then reboot CE02 Go to Step 25

25. Wait for node to reboot and go to State 3 Go to Step 26
26. Login to both nodes (one node in single-node systems) Go to Step 27
as superuser
27. Replace the srxBootParams file on both nodes (one
node in single-node systems)
Replace the srxBootParams file as follows Go to Step 28
cd /unisphere/srx3000/srx/startup
rm srxBootParams
mv srxBootParams.orig srxBootParams
28. Restore the database
If the database has been backed up since the last file system Go to Step 29
backup, refer to Section 2.5 on page 2-19 or to HiPath 8000
Assistant documentation for instructions. Otherwise, the
database saved during the last file system backup has been
restored and you can omit this step if there is not a more
current database backup.
29. Start the RTP
Start the RTP from one node only. END
Go to /unisphere/srx3000/srx/startup and execute the
appropriate command for your type of system:
Redundant system: ./srxctrl 4 4
Single-node system: ./srxctrl 4 0
A31003-H8030-S113-2-7620, June 2007

proc.fm

Disk Setup Failure to locate local or external Execute the parted command
disks. manually and check the list of printed
disks to ensure that the system boot
disk is listed. The boot disk should be
/dev/hd”x” or /dev/sd”x” on one of the
controllers.
If the system disk is not listed, the
restore cannot proceed – hardware
installation troubleshooting is
required. Restart the complete
restore process once the problem has
been corrected.
If the system disk is listed in the
format output, escalate error
resolution to next highest fault
clearance authority.
Error: Failed to compute system disk This is a script error; collect log file
size and escalate error resolution to next
Error: Create Partitions Failed One or more partitions were not
created on the local disks using the
“mkpart” command.
Error: Modify to ext3 Failed One or more partitions were not
modified on the local disks using the
“mkfs.ext3” command.
File Transfer Error: File transfer not started or 1. Network problem. Check network
aborted status.
2. IP inputs and/or file name given in
Section 2.10.3, “Procedure”, on
page 2-40, Step 9 are incorrect
A31003-H8030-S113-2-7620, June 2007

proc.fm

File Unpacking Error: File unpacking Failed Backup file is corrupted or file is not
the perceived correct file.
Check the size of the file on the
server; it should be just under 1GB.
If file appears to be correct, collect log
file and escalate error resolution to
next highest fault clearance authority.
File System Error: Restore File System Failed This is a script error; collect the log file
Restore and escalate error resolution to next
Boot partition Error: Boot partition configuration This is a script error; collect log file
configuration Failed and escalate error resolution to next
A31003-H8030-S113-2-7620, June 2007

proc.fm
A31003-H8030-S113-2-7620, June 2007

Assistant_procedures.fm
Backup and Recovery Procedures Using the Common Management Portal
Archives
3 Backup and Recovery Procedures Using the

Common Management Portal
This chapter tells you how to backup and restore system configurations, system data and
applications.
Backing up and recovering the HiPath 8000 file system can only be performed using
> the CLI at this time. Refer to Chapter 2, “Backup and Recovery Procedures Using
the CLI” for instructions.
It provides information about

● Archives
● Backup Sets
● Schedules
● Latest Job Status
● Manual Backup of a Backup Set
● Restoring a Backup Set
3.1 Archives
The backups of the data and configurations of the system and its applications are stored in ar-
chives. Each archive can contain one or more backup sets. The data and configurations are
backed up in these backup sets either automatically or manually. The archives can be created
locally on the server computer, on another computer in the network or on a computer which has
remote access to your system.
The following sections describe the following tasks:
● Displaying Archives
● Adding an Archive
● Editing Archives
● Deleting an Archive
● Testing an Archive
● Displaying/Clearing an Archive’s Backup Sets
A31003-H8030-S113-2-7620, June 2007

Archives
3.1.1 Displaying Archives

To display all archives in the system, perform the following steps:
1. Log on to the Common Management Portal (CMP) with a valid user name and password.
2. Select the domain you want from the domain selection list Domain.
3. In the General application bar, click Backup.
4. In the navigation tree, click Archive. A list of the available archives appears.
Archive name
Name of the archive.
Protocol
Protocol via which access to the archive is possible.
Acting Node
Name of the node via which the archive is accessible.
Path
Path of the archive.
Server address (for FTP or SFTP only)
Server address of the computer on which the archive is stored via FTP or SFTP.
Login name (for FTP or SFTP only)
User name used to access the server computer.
3.1.2 Adding an Archive

To create a new archive, perform the following steps:
1. Log on to the CMP with a valid user name and password.
5. Click the Add button. The Add new archive window opens.
6. Enter a name for the archive in the Archive name field.
7. From the Acting Node drop-down list, select the node to which the backup is to be sent.
8. From the Protocol drop-down list, select the protocol via which the archive is to be saved.
The options available are as follows:
A31003-H8030-S113-2-7620, June 2007

Archives
HD
The archive is saved to the hard disk of the HiPath 8000 server. HD is not is not offered as
an option on a redundant HiPath 8000 system.
FTP
The archive is saved via FTP on a computer in the network.
SFTP
The archive is saved via Secure FTP on a computer in the network.
9. If you have selected the HD protocol, enter in the field Path to file system an absolute path
(e.g. /save/archive01) in which the archive is to be saved.
10. If you have selected the FTP or SFTP protocol, enter in the Path to server field a relative
path (e.g. save/archive01) in which the archive is to be saved. In addition, under Server
address, enter the server address of the computer on which the archive is to be saved.
Under Login name and Password, enter the user name and the password to be used for
access to the server computer.
11. If required, change the Largest number of backup sets in the Data field and the default
values in the System field. These fields allow you to define the maximum number of back-
up sets of type “Data” or of type “System” respectively that can be stored in this archive.
12. If you do not wish to save your entries, click Cancel.
13. If you wish to save your entries, click Save.
3.1.3 Editing Archives

To display or edit an existing archive, perform the following steps:
5. Select an archive by checking the box for the desired archive.
6. Click the Edit button. The Edit archive window opens.
7. From the Protocol drop-down list, select the protocol via which the archive is to be saved.
The options available are as follows:
HD
The archive is saved to the hard disk of the HiPath 8000 server. HD is not is not offered as
an option on a redundant HiPath 8000 system.
A31003-H8030-S113-2-7620, June 2007

Archives
FTP
The archive is saved via FTP on a network drive.
SFTP
The archive is saved via secure FTP on a network drive.
8. If you have selected the HD protocol, enter in the field Path to file system an absolute path
(e.g. /save/archive01) in which the archive is to be saved.
9. If you have selected the FTP or SFTP protocol, enter in the Path to server field a relative
path (e.g. save/archive01) in which the archive is to be saved. In addition, under Server
address, enter the server address of the computer on which the archive is to be saved.
Under Login name and Password, enter the user name and the password to be used for
access to the server computer.
10. If required, change the Largest number of backup sets in the Data field and the default
values in the System field. These fields allow you to define the maximum number of back-
up sets of type “Data” or of type “System” respectively that can be stored in this archive.
When the maximum number has been reached, the system will automatically delete the
oldest archive before creating a new one. Also, when the maximum number is changed,
the new setting is applied right away, which means that the system will delete archives im-
mediately if necessary.
11. If you do not wish to save your changes, click Cancel.
12. If you wish to save your changes, click Save.
3.1.4 Deleting an Archive

To delete an existing archive, perform the following steps:
5. Select one or more archives that you wish to delete by clicking the archive’s check box to
activate it.
6. Click the Delete button. The archive is deleted and removed from the list of archives.
A31003-H8030-S113-2-7620, June 2007

Archives
3.1.5 Testing an Archive

Here you can test whether you are able to access an archive. A check is made as to whether
the computer can be accessed and whether files can be created and deleted in the desired di-
rectory.
To test an existing archive, perform the following steps:
5. Select an archive by checking the box for the desired archive.
6. Click the Test archive button. You will be informed about the test results in a separate win-
dow.
3.1.6 Displaying/Clearing an Archive’s Backup Sets

Each archive can contain one or more backup sets. You can have all the backup sets for an
archive displayed. Alternatively however you can also have all the backup sets in the system
displayed (see Section 3.2.1, “Displaying Backup Sets”).
To have all backup sets for an archive displayed to you, perform the following steps:
5. Select an archive for which you wish to have the backup sets displayed by activating the
check box of the archive.
6. Click the Backup Set Content button. The Backup sets in archive window opens. A list
with the backup sets belonging to this archive is displayed.
Creation date
Date on which the backup set was created.
Comment
Comment, entered when the backup-set was created (optional).
Type
Type of backup set (“Data” or “System”).
A31003-H8030-S113-2-7620, June 2007

Backup Sets
7. Clicking the Display contents button allows you to display the contents of the backup set.
To do this you must mark the desired backup set beforehand.
8. You can use the Delete button to delete one of more backup sets from the archive. To do
this you must mark the desired backup sets beforehand.
9. Click the Close button to close the window.
3.2 Backup Sets

System configurations, system data (e.g. database contents) and applications can be backed
up in a backup set. Each archive can contain one or more backup sets. If the number of backup
sets saved exceeds the value set for the archive, the oldest backup sets are cleared. You can
display all the backup sets present in the system. Alternatively, you can have all the backup sets
for an archive displayed (see Section 3.1.6, “Displaying/Clearing an Archive’s Backup Sets”).
Backing up the HiPath 8000 file system can only be performed using the CLI at this
> time. Refer to Chapter 2, “Backup and Recovery Procedures Using the CLI” for
instructions.
3.2.1 Displaying Backup Sets

To display all backup sets present in the system, perform the following steps:
4. In the navigation tree, click Backup Sets. A list of the available backup sets appears.
Archive name
Name of the archive in which the backup set is saved.
Creation date
Date on which the backup set was created.
Comment
Comment, entered when the backup-set was created (optional).
Type
Type of backup set (“Data” or “System”).
5. Clicking the Display contents button allows you to display the contents of the backup set.
To do this you must mark the desired backup set beforehand.
A31003-H8030-S113-2-7620, June 2007

Schedules
6. You can use the Delete button to delete one of more backup sets from the archive. To do
this you must mark the desired backup sets beforehand.
3.3 Schedules
Schedules determine the times at which the automatic backup jobs will be started. The follow-
ing sections describe the following tasks:
● Displaying Schedules
● Adding Schedules
● Editing Schedules
● Clearing Schedules
3.3.1 Displaying Schedules

To have the schedules displayed, perform the following steps:
4. In the navigation tree, click Schedules. A list of the available schedules appears.
Name
Schedule name for the backup set.
Archive name
Name of the archive in which the backup set is saved.
Reoccurs
Setting showing when and how often the schedule is to be repeated
Day of week (for weekly backup only)
Day of backup.
Time
Time of backup.
3.3.2 Adding Schedules

To add a new schedule, perform the following steps:
A31003-H8030-S113-2-7620, June 2007

Schedules

(You can also initiate the addition of a schedule via the menu bar Tools > Scheduled
Backup. In this case go directly to step 6.)
5. Click the Add button. The Create schedule for a backup window is displayed.
6. A backup set can only be stored in one archive. To do this, either select ... to select an
existing archive, or click the Add button to create a new archive.
7. If required, enter a comment for your backup set.
8. Click the Continue button.
9. Select one of the following options from the Select backup type drop-down list:
Data
Here you are provided with a list of all backup units for a backup.
System
All backup units for a system backup are provided here.
Backing up the file system can only be performed using the CLI. Refer to
> Chapter 2, “Backup and Recovery Procedures Using the CLI” for instructions.
10. Select the backup units to be saved.

12. Enter the name of the schedule in the Name field.
13. In the Reoccurs drop-down list, enter the frequency with which the backup is to be repeat-
ed.
14. Enter the start time for the backup in the Backup at field.
15. Click the Add button. The new schedule is entered into the list of schedules.
3.3.3 Editing Schedules

To edit schedules, perform the following steps:
A31003-H8030-S113-2-7620, June 2007

Latest Job Status
5. Select a schedule entry and click the Edit button. The Edit backup schedule window is
displayed.
6. If necessary use the Reoccurs field to modify the setting for when and how often the
schedule is repeated.
7. If necessary use the Backup at field to modify the backup start time.
8. If you do not wish to save your changes, click Cancel.
9. If you wish to save your changes, click Save.
3.3.4 Clearing Schedules

To clear a schedule, perform the following steps:
5. Select one or more schedules by marking the desired schedules with check marks and
click the Delete button. The schedules are removed from the list.
3.4 Latest Job Status

This entry shows you information about the last job performed. Such jobs can involve backup,
restore or an import or export of data.
To display the last job status, perform the following steps:
4. In the navigation tree, click Job status. Information about the last job performed appears.
Backup unit
Name of the backup units.
Start
Start time of the job for the backup unit.
End
End time of the job for the backup unit.
A31003-H8030-S113-2-7620, June 2007

Manual Backup of a Backup Set
Estimated duration
Estimated duration of the job.
Status
Status of the job (OK, ERROR, RUNNING, STOPPED, WAITING)
Comment
Display warnings and error messages.
5. If you want to display further details for the last job performed, click the Details button. This
button is not available until the job has been processed.
3.5 Manual Backup of a Backup Set

If, in addition to performing planned backups, you wish to save the file system or a database
manually, proceed as follows:
A31003-H8030-S113-2-7620, June 2007

Manual Backup of a Backup Set
Backing up the HiPath 8000 file system can only be performed using the CLI at this
instructions.
For redundant systems with an internal HiPath 8000 Assistant, the database backup
must be run from the node where the oam_ip_alias is configured and where the
database is primary.
Determine on which node the oam_ip_alias is configured and on which node the
database is primary before you start the database backup as follows:
1. Find where oam_ip_alias is configured with the command:
ifconfig | grep oam_ip_alias
If there is no result (for example: inet addr:10.1.122.30 Bcast:
10.1.122.255 Mask:255.255.255.0) indicates that the oam_ip_alias is
not configured on this node.
2. Find which node has the primary database with the command:
su - srx -c “RtpSolid -l
An example of the output is as follows:
Server |C-S Conn. |HSB State |ClmonState |Interface
adsa12n1 |CONNECTED |PRIMARY ACTIVE |---- |127.0.0.1
adsa12n2 |CONNECTED |SECONDARY ACTIVE |UP |adsa12n2_cip0
Alternatively, you can use the CLI to backup the database, refer to Section 2.3,
“Backup the Database Using an External USB HDD”, on page 2-17 or Section 2.4,
“Backup the Database Manually Using the Backup Script”, on page 2-19.
2. Select Backup from the menu bar of the Tools menu. The Create backup set window
opens.
3. A backup set can only be stored in one archive. To do this, either select ... to select an
existing archive, or click the Add button to create a new archive.
4. If required, enter a comment for your backup set.
6. Select one of the following options from the Select backup type drop-down list:
Data
Here you are provided with a list of all backup units for a database backup.
A31003-H8030-S113-2-7620, June 2007

Restoring a Backup Set
System
All backup units for a system backup are provided here.
7. Select the backup units to be saved.
8. If you wish to make further changes to the archive, click the Back button.
9. If you wish to cancel the backup, click the Cancel button.
10. Click the Start backup button. A backup set with the items that you have selected is stored
in the archive that you have specified. The progress of the backup operation is displayed.
3.6 Restoring a Backup Set

If you wish to restore a file system or database from a saved backup set, proceed as follows:
Restoring the HiPath 8000 file system can only be performed using the CLI at this
instructions.
For redundant systems with an internal HiPath 8000 Assistant, the database restore
must be run from the node where the oam_ip_alias is configured and where the
database is primary.
Determine on which node the oam_ip_alias is configured and on which node the
database is primary before you start the database restore as follows:
1. Find where oam_ip_alias is configured with the command:
ifconfig | grep oam_ip_alias
If there is no result (for example: inet addr:10.1.122.30 Bcast:
10.1.122.255 Mask:255.255.255.0) indicates that the oam_ip_alias is
not configured on this node.
2. Find which node has the primary database with the command:
su - srx -c “RtpSolid -l
An example of the output is as follows:
Server |C-S Conn. |HSB State |ClmonState |Interface
adsa12n1 |CONNECTED |PRIMARY ACTIVE |---- |127.0.0.1
adsa12n2 |CONNECTED |SECONDARY ACTIVE |UP |adsa12n2_cip0
Alternatively, you can use the CLI to restore the database, refer to Section 2.5,
“Restore the Database Using an External USB HDD”, on page 2-19 or Section 2.7,
“Restore the Database Manually Using the Restore Script”, on page 2-23.
A31003-H8030-S113-2-7620, June 2007


2. Select the Restore menu item from the menu bar in the Tools menu. The Restore window
opens.
3. A backup set can only be stored in one archive. To perform the operation, either click the
... button to select an existing archive or click the Add button to restore the name of an
archive.
4. Once the archive is specified, click the Continue button.
5. Select a backup set from the list and click Continue.
6. If you wish to make further changes to the archive, click the Back button.
7. The backup units of the backup set are displayed. Select the backup units that you wish to
restore.
8. If you wish to cancel the restore, click the Cancel button.
9. Click Start Restore. The progress of the restoration is displayed.
A31003-H8030-S113-2-7620, June 2007

A31003-H8030-S113-2-7620, June 2007

Login.fm
Logging In
Logging into the Computing Element (Node)
4 Logging In
4.1 Logging into the Computing Element (Node)

Do the following to log into the computing element:
1. Establish an SSH connection to the node.
Depending on the system configuration, it can take more than 5 minutes before
> you can log in on the server.
2. The login prompt appears.
You might have to press return once or twice to get the login prompt to appear.
>
3. When the login prompt appears, log in using the appropriate User ID and password.
4.2 Starting the RTP CLI

Do the following to start the RTP CLI.
1. Login to the appropriate Computer Element.
See Section 4.1, “Logging into the Computing Element (Node)”, on page 4-1.
2. After you have successfully logged in to the Computer Element, enter the following
command to use Menu Mode (default):
RtpAdmCli
If you want to use Expert Mode, enter the following command:
RtpAdmCli -x
At this point the following dialog displays:
A31003-H8030-S113-2-7620, June 2007

Login.fm
Logging In
Starting the RTP CLI
RTP Command Line Interface
Copyright (C) Fujitsu Siemens Computers GmbH 1999 - 2007

All Rights Reserved
Copyright (C) 2000-2007 Siemens Network Convergence LLC.

All Rights Reserved.
NOTE: You may use this software only in accordance with the terms of your
license agreement, located on any of the installation CDs for this product.
(This process is running as "RtpAdmCli01")
Login:
Figure 4-1 RTP CLI Login
3. At the Login prompt, enter your User ID and press Enter. At the Password prompt, enter
your password and press Enter.
The main menu is displayed.
Main Menu:
Configuration Management........................1
Fault Management................................2
Performance Management..........................3
Security Management.............................4
System Management...............................5
Application-level Management....................6
Show Callback Output.....................94
Wait for Callbacks.......................95
Change Password..........................96
New Login................................97
Expert Mode..............................98
Exit.....................................99
Selection:
Figure 4-2 RTP CLI Main Menu
A31003-H8030-S113-2-7620, June 2007

bkIX.fm
Index
Index Z
A D
archives database
description 3-1 backing up 2-17, 3-10
displaying backup sets 3-5 restoring 2-19, 3-12
disk setup 2-38
B
backing up E
database errors and error recovery 2-15
procedure 2-17, 3-12
using an external USB HDD 2-17 F
backup file management 1-2
archives 3-1 file system
database 3-10 backing up 3-10
disk space requirements 2-7 backup
displaying archives 3-5 disk space requirements 2-7
file system 2-7, 3-1, 3-10 prerequisites 2-7
guidelines 1-1 procedure 2-7
job status 3-9 recommendations 1-3
manual 3-10 time required 2-7
procedures 2-1 prerequisites 2-28
redundant system 2-7 restoring 3-12
schedules 3-7 for a single-node or redundant system
server 2-39
location 1-2 procedure 3-12
redundancy 1-2 single node in a cluster 2-27
requirements 1-1 retrieving file system backup 2-22
single-node system 2-7 file transfer 2-38
time required 1-3, 2-7 file unpacking 2-39
type 3-11
bandwidth impact 1-2 J
bin directory 2-26 job status, backup 3-9
boot partition configuration 2-39
L
C Linux file system backups 1-1
computing element (CE) log in 4-1 logging
configuration data in as root 2-7
backing up into the computing element 4-1
to an external USB HDD 2-17
M
restoring from an external USB HDD 2-19
maintaining backups 1-2
manual backup 3-10
A31003-H8030-S113-2-7620, June 2007
HiPath 8000 V3.0, Maintenance Manual: Volume 2, Backup and Recovery Z-1
bkIX.fm
Index
manual file management 1-2
P
prerequisite backup procedure 2-7
prerequisite restore procedure 2-28
R
recovery requirements 1-1
redundancy 1-2
requirements
disk space 2-7
information for restore 2-28
restore 2-40
restore 3-12
guidelines 1-1
procedures 2-1, 3-12
time required 1-3
restoring
database procedure 2-19, 3-12
file system
for a single-node or redundant system
2-39
information requirements 2-28, 2-40
prerequisites 2-28
procedure 2-29, 2-40, 3-12
single node in a cluster 2-27
individual files or directories 2-24
RTP CLI 4-1
S
schedules, backup 3-7
scripted file management 1-2
secure FTP (OpenSS) 1-2
starting RTP CLI 4-1
system restoration 3-12
A31003-H8030-S113-2-7620, June 2007

Z-2 HiPath 8000 V3.0, Maintenance Manual: Volume 2, Backup and Recovery
www.siemens.com/hipath
The information provided in this document contains merely general

descriptions or characteristics of performance which in case of actual use
do not always apply as described or which may change as a result of
further development of the products.
An obligation to provide the respective characteristics shall only exist if
expressly agreed in the terms of contract.
The trademarks used are owned by
Siemens Enterprise Communications GmbH & Co. KG or their respective
owners.
© Siemens Enterprise Communications GmbH & Co. KG 2007 •

Hofmannstraße 51 • D-81359 München, Germany
Reference No.: A31003-H8030-S113-2-7620
Subject to availability. Right of modification reserved.
*1PA31003-H8030-S113-2-7620*

Hipath 8000 V3.0 Maintenance Manual: Volume 2, Backup and Recovery

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hipath 8000 V3.0 Maintenance Manual: Volume 2, Backup and Recovery

Uploaded by

Copyright:

Available Formats

HiPath 8000

Volume 2, Backup and Recovery

The information provided in this document contains merely general descriptions or

© Siemens Enterprise Communications GmbH & Co. KG 2007,

Revision Date Summary

A31003-H8030-S113-2-7620, June 2007

A31003-H8030-S113-2-7620, June 2007

History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-1

A31003-H8030-S113-2-7620, June 2007

2.10.2 Information Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40

A31003-H8030-S113-2-7620, June 2007

Figure 4-1 RTP CLI Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

A31003-H8030-S113-2-7620, June 2007

A31003-H8030-S113-2-7620, June 2007

Table 1-1 Restore Times Using a Back-up Server . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

A31003-H8030-S113-2-7620, June 2007

A31003-H8030-S113-2-7620, June 2007

1 Backup and Restore Guidelines

A31003-H8030-S113-2-7620, June 2007

1.3 Back-up Server

1.4 Back-up Server Location

A31003-H8030-S113-2-7620, June 2007

– By transfer (FTP) to a remote server.

1.5 Back-up Procedures

1.6 Typical Time Requirements

Step Per Node

A31003-H8030-S113-2-7620, June 2007

Step Per Node

A31003-H8030-S113-2-7620, June 2007

2 Backup and Recovery Procedures Using the CLI

Recovery procedures should only be performed by HiPath 8000 trained and

What do you want to do Procedure

A31003-H8030-S113-2-7620, June 2007

What do you want to do Procedure

2.1 Partitioning an External USB HDD

1. Log on to the system as user root.

Device Boot Start End Blocks Id System

A31003-H8030-S113-2-7620, June 2007

/dev/sda14 25339 26362 2097136 83 Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes

Device Boot Start End Blocks Id System

5. Display the partition table with the command:

Device Boot Start End Blocks Id System

There may be 1 or 2 partitions. In this example there is 1 partition.

A31003-H8030-S113-2-7620, June 2007

Command (m for help) : d

Device Boot Start End Blocks Id System

8. Create a primary partition with the command:

Device Boot Start End Blocks Id System

10. Write out the partition table with the command:

A31003-H8030-S113-2-7620, June 2007

Command (m for help): w

Calling ioctl() to re-read partition table.

Device Boot Start End Blocks Id System

Disk /dev/sdb: 160.0 GB, 160041885696 bytes

Device Boot Start End Blocks Id System

A31003-H8030-S113-2-7620, June 2007

mke2fs 1.36 (05-Feb-2005)

Writing inode tables: 0/1193 …

This filesystem will be automatically checked every 23 mounts or

14. Unmount the USB HDD with the command:

A31003-H8030-S113-2-7620, June 2007

2.2 Backup File System for a Single-Node or Redundant System