> The TDP and the TSM version are unsupported at this time.
>
> TSM 4.1.1
> TDP for Exchange 1.1.0.1
>
> This is more of a db problem that anything else.
>
> 01/06/03 07:56:55 ANR0548W Retrieve or restore failed for session 16501
> for node WAEXCH2_EXCH (TDP MSExchg NT) processing filespace QUAD
> ENTERPRISES.QGWI.WAEXCH2.IS for file \PRI\ 20020630202651.FULL stored as
> Backup - data integrity error detected.
> The error explanation says to try the restore again, which I did and was
> still unsuccessful, it then mentions a TSM DB integrity problem. Which I
> would have to call IBM for support. We plan on upgrading to 4.2.3 then to
> 5.1.2 in the next couple of months. But that doesn't help us now.
> Here are the steps I took to correct the problem
>
select * from backups where node_name='WAEXCH2_EXCH' and
ll_name='20020630202651.FULL' and hl_name='\PRI\'. To find the object_id

         NODE_NAME: WAEXCH2_EXCH
FILESPACE_NAME: QUAD ENTERPRISES.QGWI.WAEXCH2.IS
                   STATE: ACTIVE_VERSION
                     TYPE: FILE
              HL_NAME: \PRI\
               LL_NAME: 20020630202651.FULL
            OBJECT_ID: 36051700
     BACKUP_DATE: 2002-06-30 20:31:14.000000
DEACTIVATE_DATE:
                  OWNER:
        CLASS_NAME: EXCHANGE_CLASS

sho bfo 0 36051700                      Find what volume the file is on.

Bitfile Object: 0.36051700
**Archival Bitfile Entry
Bitfile Type: PRIMARY Storage Format: 9
Bitfile Size: 5.1643463206 Number of Segments: 2
Storage Pool ID: 8 Volume ID: 38068 Volume Name: 000206

audit volume 000206 fix=no      Checking for media errors. If a file error
is found there is the chance that it would be deleted from the database if
fix=yes is used.

01/08/03 15:47:52 ANR4133I Audit volume process ended for volume 000206;
66014 files inspected, 0 damaged files found and marked as damaged, 0
objects need updating.

Move data 000206 stgpool=sxtsmbupool1

All data was moved off to disk pool and in turn corrected the indexes in
TSM. All I can figure is the indexes were not sync'd or something. The
restore would not even attempt to mount tape 000206. I was kind of under a
crunch when this happened so I didn't have time to try a different restore
from the same tape.

Restore is now running. It took about 9 hours from beginning to end.