Table of Contents
Advertisement
storage level = 1 on VV = VOL00100
path ( Fileset24: /home/bill/file2)
========= Trying to recover bitfile =========
0786ab2c-156b-1047-8c81-02608c2f971f
00336b52 4631 10cf 00 00 00 02
storage level = 1 on VV = VOL00100
path ( Fileset24: /home/bill/file3)
========= Trying to recover bitfile =========
.
.
.
== Setting VV condition to DOWN for empty VV VOL00100 ==
0723ab2c-176b-1047-8c81-02608c2f971f
00226b52 4631 10cf 00 00 00 17
== Setting VV condition to DOWN for empty VV VOL00200 ==
0456ab2c-176b-1047-8c81-02608c2f971f
00226b52 4631 10cf 00 00 00 17
At the end of the recovery, any damaged volume that has been emptied by recover will have its VV
Condition set to DOWN. The system administrator may wish to delete resources and export the volume
from the HPSS System using the Storage System Manager (SSM) after recover completes.
15.3.1.1.2. Without Secondary Copies
When no secondary copy of the data exists, the system administrator cannot use the recover utility to
recover the data. In this case, the system administrator should make every attempt to repack the damaged
volumes. If recover is used against a damaged volume with no secondary copies, any damaged segments
will be reported but will not be purged from the volume. To do this, see Section 8.4.3: Repacking and
Reclaiming Volumes on page 259. For example:
recover VOL00100 VOL00200
In the case of no secondary copies and damaged segments, status messages are logged. The messages
should be similar to the following:
========= Can't recover bitfile =========
003fcadc-53fb-10cf-8c81-02608c2f971f
00336b52 4631 10cf 00 00 00 02
storage level = 1 on VV = VOL00100
path ( Fileset24: /home/bill/file1)
lost segments from this storage level
offset = 0
, length = 32768
offset = 32768, length = 32768
offset = 65536, length = 32768
.
.
========= Can't recover bitfile =========
163001bc-2274-10ef-8c81-02608c2f971f
00336b52 4631 10cf 00 00 00 02
HPSS Management Guide
November 2009
Release 7.3 (Revision 1.0)
363
Advertisement
Table of Contents
