Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Backup\s+stgpool\s+bug\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Backup\s+stgpool\s+bug\s*$/: 7 ]

Total 7 documents matching your query.

1. Backup stgpool bug (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Thu, 10 Aug 2000 10:41:51 +0200; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00418.html (12,532 bytes)
2. Re: Backup stgpool bug (score: 1): Author: "Cook, Dwight E" <cookde AT BP DOT COM>; Date: Thu, 10 Aug 2000 06:53:00 -0500; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00423.html (14,109 bytes)
3. Re: Backup stgpool bug (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Thu, 10 Aug 2000 07:57:09 -0400; ... Eric - This may be one of those interpretation and semantics issues. The ANR1257W message description says that the file involved is one which was *previously* marked Damaged. Your most recent s; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00424.html (11,559 bytes)
4. Re: Backup stgpool bug (score: 1): Author: Eric Tang <tangeric AT HK1.IBM DOT COM>; Date: Thu, 10 Aug 2000 21:00:00 +0800; 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 reclai; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00437.html (10,703 bytes)
5. Re: Backup stgpool bug (score: 1): Author: Len Boyle <SNOLEN AT VM.SAS DOT COM>; Date: Thu, 10 Aug 2000 10:28:50 EDT; Good Morning At this time the file is marked damaged. If the damage was marked as damage due to an i/o error that was the problem on a drive and not the media, you may be able to clear the damage wit; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00452.html (11,429 bytes)
6. Re: Backup stgpool bug (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Thu, 10 Aug 2000 17:13:03 +0200; Hi Richard! This file was part of a filespace migration for one of my clients (migration to Veritas filesystem on a Sun client). My biggest concern is that the client did report 0 errors during the i; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00457.html (11,298 bytes)
7. Re: Backup stgpool bug (score: 1): Author: Richard Sims [mailto:rbs AT BU DOT EDU]; Date: Sun, 04 Oct 2015 17:28:41 -0500; ... Eric - This may be one of those interpretation and semantics issues. The ANR1257W message description says that the file involved is one which was *previously* marked Damaged. Your most recent s; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2000-08/msg00458.html (12,575 bytes)

Current List: 1 - 7
Page: [1]