Hp StoreAll Storage User Manual Page 156

  • Download
  • Add to my manuals
  • Print
  • Page
    / 254
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 155
KICKOFF_TIME=Wed Jul 18 05:18:12 2012
STOP_TIME=Mon Jul 23 14:36:59 2012
NUM_JOB_ERRORS=0
NUM_FILES_VALIDATED=1000000
NUM_FILES_SKIPPED=0
NUM_CONTENT_INCONSISTENCIES=0
NUM_METADATA_INCONSISTENCIES=0
#
Viewing and comparing hash sums for a file
If a validation scan summary file reports inconsistent hash sums for a file and you want to investigate
further, use the showsha (SHA test utility) and showvms (Validation Express Query lookup utility)
commands to compare the current hash sums with the hash sums that were originally calculated
for the file.
The showsha command calculates and displays the hash sums for a file. For example:
# /usr/local/ibrix/sbin/showsha rhnplugin.py
Path hash: f4b82f4da9026ba4aa030288185344db46ffda7b
Meta hash: 80f68a53bb4a49d0ca19af1dec18e2ff0cf965da
Data hash: d64492d19786dddf50b5a7c3bebd3fc8930fc493
The showvms command displays the hash sums stored for the file. For example:
# /usr/local/ibrix/sbin/showvms rhnplugin.py
VMSQuery returned 0
Path hash: f4b82f4da9026ba4aa030288185344db46ffda7b
Meta hash: 80f68a53bb4a49d0ca19af1dec18e2ff0cf965da
Data hash: d64492d19786dddf50b5a7c3bebd3fc8930fc493
last attempt: Wed Dec 31 17:00:00 1969
last success: Wed Dec 31 17:00:00 1969
changed: 0
In this example, the hash sums match and there are no inconsistencies. The 1969 dates appearing
in the showvms output mean than the file has not yet been validated.
Handling validation scan errors
When a validation scan detects files having hash values inconsistent with their original values, it
displays an alert in the events section of the GUI. However, the alert lists only the first inconsistent
file detected. It is important to check the validation summary report to identify all inconsistent files
that were flagged during the scan.
When there are inconsistencies, it is necessary to determine whether the cause is file corruption
or checksum corruption. Compare the file checksum with the backup file:
/usr/local/ibrix/sbin/showsha <fileFromBackup>
Checksum corruption:
If the checksums of the <filesystem/file> and <fileFromBackup> are identical, the
.archiving directory may have been corrupted (a checksum corruption). If this is the case, you
must restore the checksums:
If only a few files are inconsistent and you want to postpone restoring the checksums, you can
back up the files with a checksum inconsistency, delete those files from the file system, and
restore the backed up files to the file system.
If many checksums are corrupted, there may be a hardware failure. To restore the checksums,
complete the following procedure:
IMPORTANT: This procedure should be performed only under the guidance of HP Support.
1. Create a backup of the existing .archiving directory for future reference.
2. Replace the faulty hardware.
156 Managing data retention
Page view 155
1 2 ... 151 152 153 154 155 156 157 158 159 160 161 ... 253 254

Comments to this Manuals

No comments