RESTORE VOLUME did not fix anything here. We are back at those ANR9999D ssrecons.c(2342): Actual: Magic=1C9F3202, SrvId=-61862846, SegGroupId=3512872581838733325, SeqNum=805461472, converted=T.
Messages. It seems that the data already were damaged when the BACKUP STORAGEPOOL command run. I am wondering now in two ways : 1. How did this happen ? Ist there anything we can do to prevent these problems in the future ? 2. What should we do next ? Do we have other possibilites than to do a DELETE VOLUME xxx DISCARDDATA=YES ? regards Guenther "Prather, Wanda" <[EMAIL PROTECTED]> am 09.11.2001 16:03:56 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Kopie: (Blindkopie: Guenther Bergmann/PSZ/PrintCom/DE) Thema: Re: Antwort: Re: ANR9999D with a strange message In my case sometimes the RESTORE VOLUME fixes it, sometimes not. I am interested to know if it works for you. -----Original Message----- From: Guenther Bergmann [mailto:[EMAIL PROTECTED]] Sent: Friday, November 09, 2001 3:55 AM To: [EMAIL PROTECTED] Subject: Antwort: Re: ANR9999D with a strange message Hi, we have done an AUDIT VOLUME on this tape. Now we get messages like : "ANR1167E space reclamation for offsite volume(s) cannot copy damaged file .." Seem like all questionable files are set to a "damaged" state. The next step we will try is to do a RESTORE VOLUME of this tape. I hope that TSM then will take those "damaged" files from the copy pool. regards Guenther -- Guenther Bergmann UNIX Systemadministration PrintCom Service Zentrum Frankfurt +49 (0)69 / 272 86-439 Deutsche Post AG * Printcom Service Zentrum * Gutleutstr. 340-344* 60327 Frankfurt/M "Prather, Wanda" <[EMAIL PROTECTED]> am 08.11.2001 18:19:19 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Kopie: (Blindkopie: Guenther Bergmann/PSZ/PrintCom/DE) Thema: Re: ANR9999D with a strange message If you find out anything, please let me know! We did a DB restore about 9 months ago. Afterwards we started getting those errors sometimes on reclamation, even though we have run AUDIT FIX on every tape in the robot. But it doesn't cause offsite reclamation to stop; it just fails to reclaim those particular files, and just continues on to the next file/tape. TSM 4.1.3 on AIX 4.3.3. ************************************************************************ Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert ************************************************************************ -----Original Message----- From: Guenther Bergmann [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 07, 2001 3:52 AM To: [EMAIL PROTECTED] Subject: ANR9999D with a strange message Hi TSMers, i have inherited a bunch if TSM Servers, most of them running smoothly. During the last days we have set up offsite reclamation for a backup storage pool. Offsite reclamation terminates with: ANR9999D ssrecons.c(2356): Expected: Magic=53454652, SrvId=0, SegGroupId=1217892. SeqNum=1 I get about 50 or 100 of these messages, witch different values for Magic, SrvId, SegGroup ans SeqNum. This said, offsite reclamation fails. Server is TSM 4.1.4, running on AIX 4.3.3 Has someone already com over this ? Best regards Guenther -- Guenther Bergmann UNIX Systemadministration PrintCom Service Zentrum Frankfurt +49 (0)69 / 272 86-439 Deutsche Post AG * Printcom Service Zentrum * Gutleutstr. 340-344* 60327 Frankfurt/M
