Re: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2
That may be why we did not see it on all of our clients. It may turn out that 4.2.1.30 does not have the problem. However, this problem did not crop up until we put on 4.2.1.15 TSM server. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Paul Zarnowski [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 6:12 PM To: [EMAIL PROTECTED] Subject: Re: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2 Paul (or anyone), I'm not aware of the problem you ran into. Do you know if it was fixed in the 4.2.1.30 Windows client? Is there an APAR for this problem that I could look at? Thanks. At 04:31 PM 5/17/2002 -0400, you wrote: >Jim, >I would like to thank you for publishing this information. > >We got bit by the windows client at 4.2.1.20 and 4.2.1.26 failing half >way through a backup because of a locked file and the backup looking >successful. The result was we lost many backups for about 10 days >without realizing it. The problem was fixed by the 4.2.2 Windows >client. I recommend everyone go to that level if they are running >4.2.1.15 server (anything higher than 4.2.1.11). We think the problem >was introduced by us going to that level of the server. > >It would be really nice if the action you took here for this problem >had been taken for this backup integrity problem as well. It is >really unacceptable to lose backups or have backups with integrity >problems because of not having the information on a known problem. > >This forum is documented everywhere and used by many customers. It is >a great way to get this kind of information out. > >Paul D. Seay, Jr. >Technical Specialist >Naptheon, INC >757-688-8180 > > >-Original Message- >From: Jim Smith [mailto:[EMAIL PROTECTED]] >Sent: Friday, May 17, 2002 3:57 PM >To: [EMAIL PROTECTED] >Subject: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2 >Importance: High > > >Problem Description: > >The TSM 4.2.2 UNIX backup-archive clients may produce error >messages similar >to the following when performing incremental backup of files with hard >links: > > ANS1228E Sending of object '' failed > ANS4018E Error processing '': file name too long > >where is the name of the file that failed to back up. It is >important to note that file names experiencing this problem are NOT too >long. > >Message ANE4018E (same text as ANS4018E above) may also be logged >to the TSM >server. > >This problem affects files that have hard links. For affected files, the >problem occurs only during incremental backup. SELECTIVE backup of these >files works correctly. > >For files that have hard links, both the link and the original file >may be >affected by this problem: If the original file does not have a >backup version >on the TSM server, then the original file will experience the >problem. If the >hard link does not have a backup version on the TSM server, then the hard >link will experience the problem. > >Files with hard links where the file already has a backup version >(regardless >of whether the link has a backup version) are unaffected. > >Hard links where the link already has a backup version (regardless >of whether >the original file has a backup version) are unaffected. > >Files that have no hard links are unaffected. > >Client APAR IC33645 has been opened to address this problem. > >The version 4.2.2 UNIX clients have been removed from the FTP >download site. >They will soon be replaced with newer client code that fixes this >problem. > > >Circumvention: > >Use SELECTIVE backup to back up those files that are affected by this >problem. They can be identified by reviewing the ANS1228E and ANS4018E >messages in the dsmerror.log file. > >The backup-archive GUI may also be used to back up these files. From the >GUI, be sure to select the "Always backup" option (located in the >drop-down >list to the left of the "Help" button). > >Alternatively, customers who were running an earlier 4.2.x version of the >client can remove 4.2.2 and reinstall the earlier version. Customers who >upgraded from version 4.1.x or below can not back off, and must use the >circumvention described above. We plan on having a fix available soon, so >this circumvention is viewed as being very short-term. > > >Users Affected: > >All TSM 4.2.2 UNIX backup-archive clients. > > >Recommendation: > >Apply fixing code when available. We anticipate that the fix will be >delivered on or before the end of May 2002. > > >This statement was prepared by TSM Backup-Archive client development >and system test
Re: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2
Paul (or anyone), I'm not aware of the problem you ran into. Do you know if it was fixed in the 4.2.1.30 Windows client? Is there an APAR for this problem that I could look at? Thanks. At 04:31 PM 5/17/2002 -0400, you wrote: >Jim, >I would like to thank you for publishing this information. > >We got bit by the windows client at 4.2.1.20 and 4.2.1.26 failing half way >through a backup because of a locked file and the backup looking successful. >The result was we lost many backups for about 10 days without realizing it. >The problem was fixed by the 4.2.2 Windows client. I recommend everyone go >to that level if they are running 4.2.1.15 server (anything higher than >4.2.1.11). We think the problem was introduced by us going to that level of >the server. > >It would be really nice if the action you took here for this problem had >been taken for this backup integrity problem as well. It is really >unacceptable to lose backups or have backups with integrity problems because >of not having the information on a known problem. > >This forum is documented everywhere and used by many customers. It is a >great way to get this kind of information out. > >Paul D. Seay, Jr. >Technical Specialist >Naptheon, INC >757-688-8180 > > >-Original Message- >From: Jim Smith [mailto:[EMAIL PROTECTED]] >Sent: Friday, May 17, 2002 3:57 PM >To: [EMAIL PROTECTED] >Subject: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2 >Importance: High > > >Problem Description: > >The TSM 4.2.2 UNIX backup-archive clients may produce error messages >similar >to the following when performing incremental backup of files with hard >links: > > ANS1228E Sending of object '' failed > ANS4018E Error processing '': file name too long > >where is the name of the file that failed to back up. It is >important to note that file names experiencing this problem are NOT too >long. > >Message ANE4018E (same text as ANS4018E above) may also be logged to the >TSM >server. > >This problem affects files that have hard links. For affected files, the >problem occurs only during incremental backup. SELECTIVE backup of these >files works correctly. > >For files that have hard links, both the link and the original file may >be >affected by this problem: If the original file does not have a backup >version >on the TSM server, then the original file will experience the problem. If >the >hard link does not have a backup version on the TSM server, then the hard >link will experience the problem. > >Files with hard links where the file already has a backup version >(regardless >of whether the link has a backup version) are unaffected. > >Hard links where the link already has a backup version (regardless of >whether >the original file has a backup version) are unaffected. > >Files that have no hard links are unaffected. > >Client APAR IC33645 has been opened to address this problem. > >The version 4.2.2 UNIX clients have been removed from the FTP download >site. >They will soon be replaced with newer client code that fixes this >problem. > > >Circumvention: > >Use SELECTIVE backup to back up those files that are affected by this >problem. They can be identified by reviewing the ANS1228E and ANS4018E >messages in the dsmerror.log file. > >The backup-archive GUI may also be used to back up these files. From the >GUI, be sure to select the "Always backup" option (located in the >drop-down >list to the left of the "Help" button). > >Alternatively, customers who were running an earlier 4.2.x version of the >client can remove 4.2.2 and reinstall the earlier version. Customers who >upgraded from version 4.1.x or below can not back off, and must use the >circumvention described above. We plan on having a fix available soon, so >this circumvention is viewed as being very short-term. > > >Users Affected: > >All TSM 4.2.2 UNIX backup-archive clients. > > >Recommendation: > >Apply fixing code when available. We anticipate that the fix will be >delivered on or before the end of May 2002. > > >This statement was prepared by TSM Backup-Archive client development and >system test
Re: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2
Jim, I would like to thank you for publishing this information. We got bit by the windows client at 4.2.1.20 and 4.2.1.26 failing half way through a backup because of a locked file and the backup looking successful. The result was we lost many backups for about 10 days without realizing it. The problem was fixed by the 4.2.2 Windows client. I recommend everyone go to that level if they are running 4.2.1.15 server (anything higher than 4.2.1.11). We think the problem was introduced by us going to that level of the server. It would be really nice if the action you took here for this problem had been taken for this backup integrity problem as well. It is really unacceptable to lose backups or have backups with integrity problems because of not having the information on a known problem. This forum is documented everywhere and used by many customers. It is a great way to get this kind of information out. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Jim Smith [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 3:57 PM To: [EMAIL PROTECTED] Subject: TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2 Importance: High Problem Description: The TSM 4.2.2 UNIX backup-archive clients may produce error messages similar to the following when performing incremental backup of files with hard links: ANS1228E Sending of object '' failed ANS4018E Error processing '': file name too long where is the name of the file that failed to back up. It is important to note that file names experiencing this problem are NOT too long. Message ANE4018E (same text as ANS4018E above) may also be logged to the TSM server. This problem affects files that have hard links. For affected files, the problem occurs only during incremental backup. SELECTIVE backup of these files works correctly. For files that have hard links, both the link and the original file may be affected by this problem: If the original file does not have a backup version on the TSM server, then the original file will experience the problem. If the hard link does not have a backup version on the TSM server, then the hard link will experience the problem. Files with hard links where the file already has a backup version (regardless of whether the link has a backup version) are unaffected. Hard links where the link already has a backup version (regardless of whether the original file has a backup version) are unaffected. Files that have no hard links are unaffected. Client APAR IC33645 has been opened to address this problem. The version 4.2.2 UNIX clients have been removed from the FTP download site. They will soon be replaced with newer client code that fixes this problem. Circumvention: Use SELECTIVE backup to back up those files that are affected by this problem. They can be identified by reviewing the ANS1228E and ANS4018E messages in the dsmerror.log file. The backup-archive GUI may also be used to back up these files. From the GUI, be sure to select the "Always backup" option (located in the drop-down list to the left of the "Help" button). Alternatively, customers who were running an earlier 4.2.x version of the client can remove 4.2.2 and reinstall the earlier version. Customers who upgraded from version 4.1.x or below can not back off, and must use the circumvention described above. We plan on having a fix available soon, so this circumvention is viewed as being very short-term. Users Affected: All TSM 4.2.2 UNIX backup-archive clients. Recommendation: Apply fixing code when available. We anticipate that the fix will be delivered on or before the end of May 2002. This statement was prepared by TSM Backup-Archive client development and system test
TSM FLASH: UNIX BACKUP-ARCHIVE CLIENT V4.2.2
Problem Description: The TSM 4.2.2 UNIX backup-archive clients may produce error messages similar to the following when performing incremental backup of files with hard links: ANS1228E Sending of object '' failed ANS4018E Error processing '': file name too long where is the name of the file that failed to back up. It is important to note that file names experiencing this problem are NOT too long. Message ANE4018E (same text as ANS4018E above) may also be logged to the TSM server. This problem affects files that have hard links. For affected files, the problem occurs only during incremental backup. SELECTIVE backup of these files works correctly. For files that have hard links, both the link and the original file may be affected by this problem: If the original file does not have a backup version on the TSM server, then the original file will experience the problem. If the hard link does not have a backup version on the TSM server, then the hard link will experience the problem. Files with hard links where the file already has a backup version (regardless of whether the link has a backup version) are unaffected. Hard links where the link already has a backup version (regardless of whether the original file has a backup version) are unaffected. Files that have no hard links are unaffected. Client APAR IC33645 has been opened to address this problem. The version 4.2.2 UNIX clients have been removed from the FTP download site. They will soon be replaced with newer client code that fixes this problem. Circumvention: Use SELECTIVE backup to back up those files that are affected by this problem. They can be identified by reviewing the ANS1228E and ANS4018E messages in the dsmerror.log file. The backup-archive GUI may also be used to back up these files. From the GUI, be sure to select the "Always backup" option (located in the drop-down list to the left of the "Help" button). Alternatively, customers who were running an earlier 4.2.x version of the client can remove 4.2.2 and reinstall the earlier version. Customers who upgraded from version 4.1.x or below can not back off, and must use the circumvention described above. We plan on having a fix available soon, so this circumvention is viewed as being very short-term. Users Affected: All TSM 4.2.2 UNIX backup-archive clients. Recommendation: Apply fixing code when available. We anticipate that the fix will be delivered on or before the end of May 2002. This statement was prepared by TSM Backup-Archive client development and system test
