HP Integrity NonStop H-Series - Manual (Page 242)

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 17
Discrepancy Troubleshooting
Discrepancy Troubleshooting
Problem Recovery (page 1 of 2)
TSV Discrepancies
The first part of the
discrepancy report lists
TSVs under the heading
DUPLICATE TSV INFO. DSM/SCM assumes that if it finds at least one file in a TSV
that is also in the configuration, that TSV is a candidate for
management by DSM/SCM. However, if DSM/SCM also finds
the TSV on more than one volume, it cannot determine the
correct volume to use.
DSM/SCM therefore lists the volumes in the snapshot it sends
to the host but does not mark any of them for management by
DSM/SCM. If a TSV is listed only once, it is on more than one
volume. But in one of the volumes, no files in the TSV match
any of those in the configuration.
When you accept these duplicate TSVs, they appear in the
TSV list as new TSVs flagged by an asterisk (*). You must
decide which TSV is correct. Try matching files that have the
same expected and actual fingerprints. If the fingerprints
match, the discrepancy is not a problem. However, you should
decide if the target volume is correct because it is not the one
indicated in the configuration.
You need to perform a new Build/Apply to address duplicate
TSVs.
File Discrepancies
File discrepancies appear
in a discrepancy report. An SPR might be missing, or an old version of the file might be
in the configuration. Try placing the correct version of the file
into the configuration.
SRLs appear as
discrepancies in a
discrepancy report. NSKCOM produces SRLs during a DSM/SCM Build.
Therefore, they always turn up as discrepancies. These
discrepancies are not a problem, so you can accept them.
An SPR is in the
configuration that is not on
the target. DSM/SCM does not replace the files:
1. Delete or rename the files with discrepancies from the
target system (only if they are not needed for operation).
2. From the ZPHITI, run the Verify Database and
Independent Snapshot requests.
3. Receive the snapshot into the host (automatic if you
specify that the host has a network connection to the
target when you run ZPHIHMI).
4. Run the discrepancy report again. Missing files show a
discrepancy of Not Found, and the versions in the new
revision are sent on the next Apply.