Thank�s for your reply Sims. Peforming a audit db command: worked fine without any integrity error fix. Performing a audit volume command: Solved some problems with some tapes. In some cases, we lost the entire volume. Best Regards, _____________________________________________________ Roberto Zimmer de Godoy - <mailto:[EMAIL PROTECTED]> Systems Support Analyst Service IT Solutions IBM Premier Business Partner Microsoft Certified Solution Provider Partner <http://www.service.com.br/> +55(51) 212-3666 Rua Washington Luis, 820/902 CEP 90010-460 - Porto Alegre - RS - Reinhold Messner - -----Mensagem original----- De: Richard Sims [mailto:[EMAIL PROTECTED]] Enviada em: Wednesday, December 27, 2000 11:27 AM Para: [EMAIL PROTECTED] Assunto: Re: Big Trouble!!!! >ANR0548W Retrieve or restore failed for session 120 for node SERVER01 >(WinNT) processing filespace \\server01\i$ for file >\RAIZ\COM_COMISSIONAMENTO\BASE DE DADOS\BASE CABS\CABSSETEMBRO\ >COMISSIONAMENTO SETEMBRO.MDB stored as Backup - data integrity error >detected. > >This actually happens randomly with many files located on many tapes. > >Running the audit volume command (fix=3Dyes) on the tape with supposed >problem, it doesn=B4t show up any data integrity error and the process >complete successful. =20 Roberto - You would seem to be having integrity problems with your TSM database, rather than the integrity of the data on the tape. >I don=B4t have any DLT copy storage pool. Bad news. Given the reliability problems reported with DLT, you really should have a copy storage pool. The recommended action with regard to the above message, per the Messages manual and APAR IY09212, is to retry the restoral such that the server will attempt it from the copy storage pool, ostensibly using different TSM database information, which hopefully avoids the area where the integrity problems exist. You may have to perform a db audit, which as you know is time-consuming. You really should contact Tivoli Support and see if they can provide any expedient solutions, based upon the specific circumstances of your database. Richard Sims, BU
