t, 2000 13:57
To: [EMAIL PROTECTED]
Subject: Re: Backup stgpool bug
>08/10/2000 00:52:45 ANR1257W Storage pool backup skipping damaged file on
>volume 0630A5: Node OD6-VERITAS, Type Backup, File space /data0002, File
>name /ora/klapa/dbdata/klapasxb1_1.dbf.
...
>State of SUCCESS??
In article <[EMAIL PROTECTED]>, "Loon,
E.J. van - SPLXM" <[EMAIL PROTECTED]> says:
>
>Hi *SM-ers!
>I discovered a real big problem with TSM (3.7.3 on AIX).
>Yesterday I ran a backup stgpool and I came across the following message in
>the activity log:
>
>08/10/2000 00:52:45 ANR1257W Storage pool b
Suppose a file has been backup stgpool once from primary pool TAPEP to
copypool TAPEC successfully.
My question is: if the file is detected damage while reading primary pool
TAPEP during TAPEC reclaimation, will ADSM keep TAPEC for that file image?
Thanks in advance.
Regards,
Eric Tang
>08/10/2000 00:52:45 ANR1257W Storage pool backup skipping damaged file on
>volume 0630A5: Node OD6-VERITAS, Type Backup, File space /data0002, File
>name /ora/klapa/dbdata/klapasxb1_1.dbf.
...
>State of SUCCESS? 0 Unreadable Bytes? This in NOT correct!
Eric - This may be one of those interpr
Well, technically they are in sync 'cause the file doesn't exist in either
pool !
Granted the damaged file is a problem...
Being a .dbf I'm guessing that was an archived file... if it were a "backed
up file" TSM, now that the file has been identified as damaged, would back
it up during the next
