Space reclamation is ended for volume
Hi Emmanuel, thanks for reply I success to move data from this tape i do that update volume S:\TSM_FILE_DEVCLASS\16AA.BFS access=offsite and move data S:\TSM_FILE_DEVCLASS\16AA.BFS stg=ACTIVEPOOL-FILE reconst=yes And success ANR1141I Move data process ended for volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0986I Process 1563 for MOVE DATA running in the BACKGROUND processed 15451 items for a total of 2,161,549,402 bytes with a completion state of SUCCESS at 10:40:00. And after ANR2017I Administrator ADMIN issued command: UPDATE VOLUME S:\TSM_FILE_DEVCLASS\16AA.BFS access=readwri ANR2208I Volume S:\TSM_FILE_DEVCLASS\16AA.BFS deleted from storage pool ACTIVEPOOL-FILE. ANR1341I Scratch volume S:\TSM_FILE_DEVCLASS\16AA.BFS has been deleted from storage pool ACTIVEPOOL-FILE. The volume was deleted, i'am see if i have another problem of space reclamation. Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Space reclamation is ended for volume
Hi everybody, My problem __ ANRD_1627081930 (ssrecons.c:784) Thread52: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 (PROCESS: 327) ANRD Thread52 issued message from: (PROCESS: 327) ANR1092E Space reclamation is ended for volume S:\TSM_FILE_DEVCLASS\16AA.BFS. An internal server error was detected. (PROCESS: 327) ANRD Thread52 issued message 1092 from: (PROCESS: 327) __ I try to update volume S:\TSM_FILE_DEVCLASS\16AA.BFS access=readonly and perform a move data but i have this ANR0984I Process 54 for MOVE DATA started in the BACKGROUND at 09:32:18. ANR1140I Move data process started for volume S:\TSM_FILE_DEVCLASS\16AA.BFS (process ID 54). ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\4508.BFS mounted. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\16AA.BFS mounted. ANR0513I Process 54 opened output volume S:\TSM_FILE_DEVCLASS\4508.BFS. ANR0512I Process 54 opened input volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANRD_1627081930 (ssrecons.c:784) Thread59: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 ANRD Thread59 issued message from: ANR1156W Move data process terminated for volume S:\TSM_FILE_DEVCLASS\16AA.BFS - internal server error detected. ANRD Thread59 issued message 1156 from: ANR0985I Process 54 for MOVE DATA running in the BACKGROUND completed with completion state FAILURE at 09:32:18. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\4508.BFS. Anyone have a idea to correct this error? Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Space reclamation is ended for volume
Try to use audit volume with fix=yes... Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of mik Sent: 12 12 2013 11:54 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Space reclamation is ended for volume Hi everybody, My problem __ ANRD_1627081930 (ssrecons.c:784) Thread52: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 (PROCESS: 327) ANRD Thread52 issued message from: (PROCESS: 327) ANR1092E Space reclamation is ended for volume S:\TSM_FILE_DEVCLASS\16AA.BFS. An internal server error was detected. (PROCESS: 327) ANRD Thread52 issued message 1092 from: (PROCESS: 327) __ I try to update volume S:\TSM_FILE_DEVCLASS\16AA.BFS access=readonly and perform a move data but i have this ANR0984I Process 54 for MOVE DATA started in the BACKGROUND at 09:32:18. ANR1140I Move data process started for volume S:\TSM_FILE_DEVCLASS\16AA.BFS (process ID 54). ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\4508.BFS mounted. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\16AA.BFS mounted. ANR0513I Process 54 opened output volume S:\TSM_FILE_DEVCLASS\4508.BFS. ANR0512I Process 54 opened input volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANRD_1627081930 (ssrecons.c:784) Thread59: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 ANRD Thread59 issued message from: ANR1156W Move data process terminated for volume S:\TSM_FILE_DEVCLASS\16AA.BFS - internal server error detected. ANRD Thread59 issued message 1156 from: ANR0985I Process 54 for MOVE DATA running in the BACKGROUND completed with completion state FAILURE at 09:32:18. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\4508.BFS. Anyone have a idea to correct this error? Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Space reclamation is ended for volume
Thanks for reply Grigori, I do audit volume S:\TSM_FILE_DEVCLASS\16AA.BFS It's success I do audit volume S:\TSM_FILE_DEVCLASS\16AA.BFS fix=yes Success too with no error. But move data S:\TSM_FILE_DEVCLASS\16AA.BFS stg=ACTIVEPOOL-FILE reconst=yes ANR1157I Removable volume S:\TSM_FILE_DEVCLASS\16AA.BFS is required for move process. ANR0984I Process 1500 for MOVE DATA started in the BACKGROUND at 10:53:42. ANR1140I Move data process started for volume S:\TSM_FILE_DEVCLASS\16AA.BFS (process ID 1500). ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\16AA.BFS mounted. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\3649.BFS mounted. ANR0512I Process 1500 opened input volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0513I Process 1500 opened output volume S:\TSM_FILE_DEVCLASS\3649.BFS. ANRD_1627081930 (ssrecons.c:784) Thread27: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 ANRD Thread27 issued message from: ANR1156W Move data process terminated for volume S:\TSM_FILE_DEVCLASS\16AA.BFS - internal server error detected. ANRD Thread27 issued message 1156 from: ANR0985I Process 1500 for MOVE DATA running in the BACKGROUND completed with completion state FAILURE at 10:53:42. ANR0514I Session 1172 closed volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0514I Session 1172 closed volume S:\TSM_FILE_DEVCLASS\3649.BFS. In the console i see that ANR1040I Space reclamation started for volume S:\TSM_FILE_DEVCLASS\16AA.BFS, storage pool ACTIVEPOOL-FILE (process number 1497). ANR1044I Removable volume S:\TSM_FILE_DEVCLASS\16AA.BFS is required for space reclamation. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\16AA.BFS mounted. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\3649.BFS mounted. ANR0512I Process 1497 opened input volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0513I Process 1497 opened output volume S:\TSM_FILE_DEVCLASS\3649.BFS. ANRD_1627081930 (ssrecons.c:784) Thread27: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 ANRD Thread27 issued message from: ANR1092E Space reclamation is ended for volume S:\TSM_FILE_DEVCLASS\16AA.BFS. An internal server error was detected. ANRD Thread27 issued message 1092 from: ANR0985I Process 1497 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 10:52:31. Thanks for the help. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Space reclamation is ended for volume
Hi Mickael! Audit the volume like this: Audit vol S:\TSM_FILE_DEVCLASS\16AA.BFS This will show you the files which are corrupted on the volume. It could be that the volume was corrupted after a successful backup stgpool, so first try a restore: Restore volume S:\TSM_FILE_DEVCLASS\16AA.BFS If the restore is successful the volume should be empty afterwards, if not you will have to perform an audit again but with the fix=yes: Upd vol S:\TSM_FILE_DEVCLASS\16AA.BFS access=readonly Audit vol S:\TSM_FILE_DEVCLASS\16AA.BFS fix=yes Bear in mind that the corrupted files will be deleted from TSM. If these files are Backup/archive client files it's not a very big issue: they will be backed up again during the next backup cycle. Are the files part of a TDP backup then things are different, in that case your whole backup series is corrupted and you will have to schedule a new full backup for that TDP client a.s.a.p. Kind regards, Eric van Loon AF/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of mik Sent: donderdag 12 december 2013 9:54 To: ADSM-L@VM.MARIST.EDU Subject: Space reclamation is ended for volume Hi everybody, My problem __ ANRD_1627081930 (ssrecons.c:784) Thread52: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 (PROCESS: 327) ANRD Thread52 issued message from: (PROCESS: 327) ANR1092E Space reclamation is ended for volume S:\TSM_FILE_DEVCLASS\16AA.BFS. An internal server error was detected. (PROCESS: 327) ANRD Thread52 issued message 1092 from: (PROCESS: 327) __ I try to update volume S:\TSM_FILE_DEVCLASS\16AA.BFS access=readonly and perform a move data but i have this ANR0984I Process 54 for MOVE DATA started in the BACKGROUND at 09:32:18. ANR1140I Move data process started for volume S:\TSM_FILE_DEVCLASS\16AA.BFS (process ID 54). ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\4508.BFS mounted. ANR8340I FILE volume S:\TSM_FILE_DEVCLASS\16AA.BFS mounted. ANR0513I Process 54 opened output volume S:\TSM_FILE_DEVCLASS\4508.BFS. ANR0512I Process 54 opened input volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANRD_1627081930 (ssrecons.c:784) Thread59: Byte count mismatch for object 0.206273217 source: 0.62939, target: 0.920075 ANRD Thread59 issued message from: ANR1156W Move data process terminated for volume S:\TSM_FILE_DEVCLASS\16AA.BFS - internal server error detected. ANRD Thread59 issued message 1156 from: ANR0985I Process 54 for MOVE DATA running in the BACKGROUND completed with completion state FAILURE at 09:32:18. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\16AA.BFS. ANR0514I Session 995 closed volume S:\TSM_FILE_DEVCLASS\4508.BFS. Anyone have a idea to correct this error? Regards, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
Space reclamation is ended for volume
Hi Eric van Loon and thanks for the reply, I have already try the audit volume and audit volume fix=yes and no error on th file, i dont understand. Regars, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Space reclamation is ended for volume
Hi Mik, In order to preserve the existing backuped data on the volume, I can suggest you this : 1) Put the tape in readOnly mode: upd vol Volume_Name access=reado 2) Protect current valid datas : Move data Volume_name -- It move all good datas, even the ones that have not been copied yet. -- It flags bad files as damaged 3) audit the tape and fix it : audit vol volume_name fix=yes 4) restore the destroyed datas (when a copy of them exist) : restore vol Volume_Name Hope it helps, Emmanuel -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de mik Envoyé : jeudi 12 décembre 2013 11:10 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Space reclamation is ended for volume Hi Eric van Loon and thanks for the reply, I have already try the audit volume and audit volume fix=yes and no error on th file, i dont understand. Regars, Mickael. +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
ANR1162W Space reclamation skipping damaged file on volume
Seeing these errors on replicated TSM server during reclaim process, both servers have been upgraded recently to 6.3.3 ANR1162W Space reclamation skipping damaged file on volume D:\WIN2K_PRIM2\0001A370.BFS: Node NEREUS, Type Backup, File space \\nereus\d$file:///\\nereus\d$, File name \STELLENT\IDCM1\WEBLAYOUT\GROUPS\RECORDSGROUP\DOCUMEN- TS\RM_INTERNALINFO\AKK.CXPC2PZPK5ANS08KDXD 821.HTM. Then if I audit the volume this is the result, I know I can delete the volume and re-replicate it It is a de-deduplicated storage pool. Prior to 6.3.3 we saw this but never the ANRD messages audit vol D:\WIN2K_PRIM2\0001A370.BFS fix=yes ANR2312I Audit Volume (Repair) process started for volume D:\WIN2K_PRIM2\0001A370.BFS (process ID 175). ANR8340I FILE volume D:\WIN2K_PRIM2\0001A370.BFS mounted. ANR0512I Process 175 opened input volume D:\WIN2K_PRIM2\0001A370.BFS. ANRD_2164256325 BfGetBitfileExtents(bfaggrut.c:4572) Thread38: BFBE Entry not found for object 702767727 ANRD Thread38 issued message from: ANRD Thread38 07FEE92F9839 OutDiagToCons()+159 ANRD Thread38 07FEE92F33BC outDiagfExt()+fc ANRD Thread38 07FEE8CAD44B BfGetBitfileExtents()+e0b ANRD Thread38 07FEE8CBFBA8 bfRtrvExt()+1328 ANRD Thread38 07FEE8D00ED4 AfAuditBitfile()+d4 ANRD Thread38 07FEE8CC3716 bfAuditBitfile()+cc6 ANRD Thread38 07FEE8BD4508 AdmVolDelThread()+1708 ANRD Thread38 07FEE8BD6875 AdmAuditVolThread()+7b5 ANRD Thread38 07FEE8AE6384 startThread()+124 ANRD Thread38 74431D9F endthreadex()+43 ANRD Thread38 74431E3B endthreadex()+df ANRD Thread38 7704652D BaseThreadInitThunk()+d ANRD Thread38 7727C521 RtlUserThreadStart()+21 ANRD_2547000324 bfRtrvExt(bfrtrv.c:1444) Thread38: Error 9979 obtaining deduplication information for object 702767726 in super bitfile 702767540 in pool 16 ANRD Thread38 issued message from: ANRD Thread38 07FEE92F9839 OutDiagToCons()+159 ANRD Thread38 07FEE92F33BC outDiagfExt()+fc ANRD Thread38 07FEE8CBFBFB bfRtrvExt()+137b ANRD Thread38 07FEE8D00ED4 AfAuditBitfile()+d4 ANRD Thread38 07FEE8CC3716 bfAuditBitfile()+cc6 ANRD Thread38 07FEE8BD4508 AdmVolDelThread()+1708 ANRD Thread38 07FEE8BD6875 AdmAuditVolThread()+7b5 ANRD Thread38 07FEE8AE6384 startThread()+124 ANRD Thread38 74431D9F endthreadex()+43 ANRD Thread38 74431E3B endthreadex()+df ANRD Thread38 7704652D BaseThreadInitThunk()+d ANRD Thread38 7727C521 RtlUserThreadStart()+21 ANR2327W Audit volume process terminated for volume D:\WIN2K_PRIM2\0001A370.BFS - internal server error detected. ANR0515I Process 175 closed volume D:\WIN2K_PRIM2\0001A370.BFS. ANR0985I Process 175 for AUDIT VOLUME (REPAIR) running in the BACKGROUND completed with completion state FAILURE at 08:01:10. ANR1893E Process 175 for AUDIT VOLUME (REPAIR) completed with a completion Thanks, Tim Brown Supervisor Computer Operations Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601
Re: ANR1162W Space reclamation skipping damaged file on volume
Check a recent APAR https://www-304.ibm.com/support/entdocview.wss?uid=swg1IC95938myns=aparmynp=DOCTYPEcomponentmync=E for a similar problem. I was running node replication and had some damaged files. The files had been de-duped by the node. Volume audits with fix=yes resolved the trouble. The above APAR was created shortly after my PMR was closed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim Brown Sent: Tuesday, September 24, 2013 7:08 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1162W Space reclamation skipping damaged file on volume Seeing these errors on replicated TSM server during reclaim process, both servers have been upgraded recently to 6.3.3 ANR1162W Space reclamation skipping damaged file on volume D:\WIN2K_PRIM2\0001A370.BFS: Node NEREUS, Type Backup, File space \\nereus\d$file:///\\nereus\d$, File name \STELLENT\IDCM1\WEBLAYOUT\GROUPS\RECORDSGROUP\DOCUMEN- TS\RM_INTERNALINFO\AKK.CXPC2PZPK5ANS08KDXD 821.HTM. Then if I audit the volume this is the result, I know I can delete the volume and re-replicate it It is a de-deduplicated storage pool. Prior to 6.3.3 we saw this but never the ANRD messages audit vol D:\WIN2K_PRIM2\0001A370.BFS fix=yes ANR2312I Audit Volume (Repair) process started for volume D:\WIN2K_PRIM2\0001A370.BFS (process ID 175). ANR8340I FILE volume D:\WIN2K_PRIM2\0001A370.BFS mounted. ANR0512I Process 175 opened input volume D:\WIN2K_PRIM2\0001A370.BFS. ANRD_2164256325 BfGetBitfileExtents(bfaggrut.c:4572) Thread38: BFBE Entry not found for object 702767727 ANRD Thread38 issued message from: ANRD Thread38 07FEE92F9839 OutDiagToCons()+159 ANRD Thread38 07FEE92F33BC outDiagfExt()+fc ANRD Thread38 07FEE8CAD44B BfGetBitfileExtents()+e0b ANRD Thread38 07FEE8CBFBA8 bfRtrvExt()+1328 ANRD Thread38 07FEE8D00ED4 AfAuditBitfile()+d4 ANRD Thread38 07FEE8CC3716 bfAuditBitfile()+cc6 ANRD Thread38 07FEE8BD4508 AdmVolDelThread()+1708 ANRD Thread38 07FEE8BD6875 AdmAuditVolThread()+7b5 ANRD Thread38 07FEE8AE6384 startThread()+124 ANRD Thread38 74431D9F endthreadex()+43 ANRD Thread38 74431E3B endthreadex()+df ANRD Thread38 7704652D BaseThreadInitThunk()+d ANRD Thread38 7727C521 RtlUserThreadStart()+21 ANRD_2547000324 bfRtrvExt(bfrtrv.c:1444) Thread38: Error 9979 obtaining deduplication information for object 702767726 in super bitfile 702767540 in pool 16 ANRD Thread38 issued message from: ANRD Thread38 07FEE92F9839 OutDiagToCons()+159 ANRD Thread38 07FEE92F33BC outDiagfExt()+fc ANRD Thread38 07FEE8CBFBFB bfRtrvExt()+137b ANRD Thread38 07FEE8D00ED4 AfAuditBitfile()+d4 ANRD Thread38 07FEE8CC3716 bfAuditBitfile()+cc6 ANRD Thread38 07FEE8BD4508 AdmVolDelThread()+1708 ANRD Thread38 07FEE8BD6875 AdmAuditVolThread()+7b5 ANRD Thread38 07FEE8AE6384 startThread()+124 ANRD Thread38 74431D9F endthreadex()+43 ANRD Thread38 74431E3B endthreadex()+df ANRD Thread38 7704652D BaseThreadInitThunk()+d ANRD Thread38 7727C521 RtlUserThreadStart()+21 ANR2327W Audit volume process terminated for volume D:\WIN2K_PRIM2\0001A370.BFS - internal server error detected. ANR0515I Process 175 closed volume D:\WIN2K_PRIM2\0001A370.BFS. ANR0985I Process 175 for AUDIT VOLUME (REPAIR) running in the BACKGROUND completed with completion state FAILURE at 08:01:10. ANR1893E Process 175 for AUDIT VOLUME (REPAIR) completed with a completion Thanks, Tim Brown Supervisor Computer Operations Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 [Confidentiality notice:] *** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***
Re: ANR1162W Space reclamation skipping damaged file
If you don't need the data want to delete the volume: delete volume discarddata=yes -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Tuesday, October 14, 2008 2:17 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANR1162W Space reclamation skipping damaged file What if I decide I don't need the data on that tape anymore? Regards, Orin Orin Rehorst * e-mail: [EMAIL PROTECTED] ( Phone: (713)670-2443 7Fax: (713)670-2457 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Tuesday, October 14, 2008 6:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ANR1162W Space reclamation skipping damaged file I had this issue come up a couple of times and when the Audit xx fix=yes didn't help I did what Richard suggested Restore Volume. I also did the preview first. Regards Tim Mark Stapleton wrote: What if any error messages did you get during the AUDIT VOLUME? -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Monday, October 13, 2008 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1162W Space reclamation skipping damaged file Get this problem. I ran audit volume VT0090 fix=yes, and that didn't help. 10/12/2008 06:54:13 ANR1162W Space reclamation skipping damaged file on volume VT0090: Node EXCHANGE1, Type Backup, File space EXCHANGE1\First Storage Group, File name \data\\Public Folder Store (EXCHANGE1)\ full. (PROCESS: 310) Please advise. Regards, Orin This message and any included attachments are from Siemens Medical Solutions and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you
Re: ANR1162W Space reclamation skipping damaged file
I had this issue come up a couple of times and when the Audit xx fix=yes didn't help I did what Richard suggested Restore Volume. I also did the preview first. Regards Tim Mark Stapleton wrote: What if any error messages did you get during the AUDIT VOLUME? -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Monday, October 13, 2008 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1162W Space reclamation skipping damaged file Get this problem. I ran audit volume VT0090 fix=yes, and that didn't help. 10/12/2008 06:54:13 ANR1162W Space reclamation skipping damaged file on volume VT0090: Node EXCHANGE1, Type Backup, File space EXCHANGE1\First Storage Group, File name \data\\Public Folder Store (EXCHANGE1)\ full. (PROCESS: 310) Please advise. Regards, Orin
Re: ANR1162W Space reclamation skipping damaged file
What if I decide I don't need the data on that tape anymore? Regards, Orin Orin Rehorst * e-mail: [EMAIL PROTECTED] ( Phone: (713)670-2443 7Fax: (713)670-2457 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Tuesday, October 14, 2008 6:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ANR1162W Space reclamation skipping damaged file I had this issue come up a couple of times and when the Audit xx fix=yes didn't help I did what Richard suggested Restore Volume. I also did the preview first. Regards Tim Mark Stapleton wrote: What if any error messages did you get during the AUDIT VOLUME? -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Monday, October 13, 2008 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1162W Space reclamation skipping damaged file Get this problem. I ran audit volume VT0090 fix=yes, and that didn't help. 10/12/2008 06:54:13 ANR1162W Space reclamation skipping damaged file on volume VT0090: Node EXCHANGE1, Type Backup, File space EXCHANGE1\First Storage Group, File name \data\\Public Folder Store (EXCHANGE1)\ full. (PROCESS: 310) Please advise. Regards, Orin
ANR1162W Space reclamation skipping damaged file
Get this problem. I ran audit volume VT0090 fix=yes, and that didn't help. 10/12/2008 06:54:13 ANR1162W Space reclamation skipping damaged file on volume VT0090: Node EXCHANGE1, Type Backup, File space EXCHANGE1\First Storage Group, File name \data\\Public Folder Store (EXCHANGE1)\ full. (PROCESS: 310) Please advise. Regards, Orin
Re: ANR1162W Space reclamation skipping damaged file
What if any error messages did you get during the AUDIT VOLUME? -- Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orin Rehorst Sent: Monday, October 13, 2008 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1162W Space reclamation skipping damaged file Get this problem. I ran audit volume VT0090 fix=yes, and that didn't help. 10/12/2008 06:54:13 ANR1162W Space reclamation skipping damaged file on volume VT0090: Node EXCHANGE1, Type Backup, File space EXCHANGE1\First Storage Group, File name \data\\Public Folder Store (EXCHANGE1)\ full. (PROCESS: 310) Please advise. Regards, Orin
Re: ANR1162W Space reclamation skipping damaged file
If Audit Volume fails, and it's a primary storage pool volume, consider doing Restore Volume, first with a preview. Richard Sims
DRPOOL Space Reclamation Problems
We're having some problems over the past week with a tape volume that is in our library. Reclamation of DRPOOL for a particular volume keeps failing and shows multiple failure events over the course of the job. Here are the messages from one of the failures. Any ideas on how to clear this up? The tape in question, A5 is an archtape and is loaded in the tape library. Just for some background too, this is a TSM Server on a Windows 2003 box running v532. Any help would be appreciated as I have just about exhausted Google and IBM's site figuring this one out. Barrett Keziah Systems Administrator Ravenscroft School 7409 Falls of Neuse Rd. Raleigh, NC 27615 Process Reclaim StgPool DRPOOL (33) status TSM Process Number: 33 Started: 23-May-2007 18:09 Finished: 23-May-2007 18:09 Status: TSMSTATE_FAILURE Messages Logged: ANR0984I Process 33 for SPACE RECLAMATION started in the BACKGROUND at 18:09:50. ANR4931I Reclamation process 33 started for copy storage pool DRPOOL automatically, threshold=60, offsiteRclmLimit=No Limit, duration=None. ANR1040I Space reclamation started for volume M01155, storage pool DRPOOL (process number 33). ANR1040I Space reclamation started for volume M01151, storage pool DRPOOL (process number 33). ANR1040I Space reclamation started for volume A2, storage pool DRPOOL (process number 33). ANR1040I Space reclamation started for volume M01153, storage pool DRPOOL (process number 33). ANR1040I Space reclamation started for volume A00013, storage pool DRPOOL (process number 33). ANR1044I Removable volume A5 is required for space reclamation. ANR0985I Process 33 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 18:09:53. ## This email and any attachments are confidential and intended solely for use by the individual or entity to whom they are addressed and should not be disseminated without permission. No confidentiality or privilege is waived by any mistransmission. If you have received this email in error, please delete it and all copies of it from your system immediately. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Ravenscroft. Note: This e-mail message has been scanned for Viruses by NetIQ MailMarshal. Ravenscroft accepts no liability for any damage caused by viruses transmitted by this email. In addition, Ravenscroft reserves the right to monitor all e-mail communications through its networks. ##
Re: DRPOOL Space Reclamation Problems
It is an Exabyte 7 slot single tape drive if that helps out. Barrett -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Thursday, May 24, 2007 9:01 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DRPOOL Space Reclamation Problems On May 24, 2007, at 8:39 AM, Barrett Keziah wrote: ... The tape in question, A5 is an archtape and is loaded in the tape library. ... ANR1044I Removable volume A5 is required for space reclamation. ... A tape may be physically present in a library, but not in a way which allows it to be mountable. In a 3494, for example, a tape may be misplaced because the 3494 Library Manager lost track of it, typically because it's stuck in a drive (dismount failure, which is often apparent through the drive or path being offline in TSM). More simply, the tape may not be checked in to TSM. Not knowing your library type, we can't specifically advise, but you know how to perform the needed library and/or TSM queries to track this down. The TSM SHow LIBRary command may help, if it's a drive issue. If a SCSI library, an Elements review may help, or an Audit Library may be needed. But start with the library itself. A physical inspection of the library may be a good move, to assure that the tape wasn't dropped inside it, for example. Richard Sims ## This email and any attachments are confidential and intended solely for use by the individual or entity to whom they are addressed and should not be disseminated without permission. No confidentiality or privilege is waived by any mistransmission. If you have received this email in error, please delete it and all copies of it from your system immediately. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Ravenscroft. Note: This e-mail message has been scanned for Viruses by NetIQ MailMarshal. Ravenscroft accepts no liability for any damage caused by viruses transmitted by this email. In addition, Ravenscroft reserves the right to monitor all e-mail communications through its networks. ##
Re: DRPOOL Space Reclamation Problems
On May 24, 2007, at 8:39 AM, Barrett Keziah wrote: ... The tape in question, A5 is an archtape and is loaded in the tape library. ... ANR1044I Removable volume A5 is required for space reclamation. ... A tape may be physically present in a library, but not in a way which allows it to be mountable. In a 3494, for example, a tape may be misplaced because the 3494 Library Manager lost track of it, typically because it's stuck in a drive (dismount failure, which is often apparent through the drive or path being offline in TSM). More simply, the tape may not be checked in to TSM. Not knowing your library type, we can't specifically advise, but you know how to perform the needed library and/or TSM queries to track this down. The TSM SHow LIBRary command may help, if it's a drive issue. If a SCSI library, an Elements review may help, or an Audit Library may be needed. But start with the library itself. A physical inspection of the library may be a good move, to assure that the tape wasn't dropped inside it, for example. Richard Sims
Offiste Space Reclamation Issues
Lately I have been having problems with TSM running offiste space reclamation. I have it scheduled to run reclamation on the offsite storage pools in the evening, and it seems that every evening, I start getting read errors as well as tape drive issues. This only occurs after the schedule kicks off. I have copy stgpool processes that run during the day that have no problems, and all the drives function fine during that time, so it does not appear to be a drive issue. Also, it does not appear to be a tape issue either, as I have repeatedly marked the questionable tapes as unavailable, only to have new tapes with problems the next night. Anyone else experiencing this? W2K3 TSM 5.3.2.0 Mel Dennis
Re: Offiste Space Reclamation Issues
Mel, We were having some trouble in the same area. Let me explain our situation. We where moving our diskpool the tape, every morning, and in the afternoon, we performed our offsite reclamation for all our offsite tapes. What happened is we started to have errors, and the offsite reclamation would fail. In the server error log there was reported an invalid attempt to free memory. So I did some reading on the error, and I learned that if the offsite reclamation is looking for a file that it needs to reclaim the offsite tapes it must be on a tape. If it finds it on disk it will start to have problems. So once I made sure that the migration was completed successfully our offsite reclamation started to work fine. However, our migration eventually failed completely due to a faulty controller card. We replaced the controller card and everything works nicely. Here is some links that might help. http://www-1.ibm.com/support/docview.wss?uid=swg1IC45931 I know you are running 5.3.2, and it has said it should be fixed. You never know, IBM releases things too early! http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmreadme.doc/rdme5354.htm Hope this helps! Aaron [EMAIL PROTECTED] 2/7/2006 6:31:42 AM Lately I have been having problems with TSM running offiste space reclamation. I have it scheduled to run reclamation on the offsite storage pools in the evening, and it seems that every evening, I start getting read errors as well as tape drive issues. This only occurs after the schedule kicks off. I have copy stgpool processes that run during the day that have no problems, and all the drives function fine during that time, so it does not appear to be a drive issue. Also, it does not appear to be a tape issue either, as I have repeatedly marked the questionable tapes as unavailable, only to have new tapes with problems the next night. Anyone else experiencing this? W2K3 TSM 5.3.2.0 Mel Dennis
Space Reclamation Eating Tapes
I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Things have changed in 5.3. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:35 To: ADSM-L@VM.MARIST.EDU Subject: Re: Space Reclamation Eating Tapes Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
Such as? :) Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Things have changed in 5.3. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:35 To: ADSM-L@VM.MARIST.EDU Subject: Re: Space Reclamation Eating Tapes Don't think that is it, I only have 2 storage pools out of like 12 that have collocation turned on (these storage pools are for large file servers). So collocation shouldn't be affecting most of them. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Monday, November 28, 2005 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Space Reclamation Eating Tapes Sounds like a collocation problem. Q stg / q node / q collocgroup. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: maandag 28 november 2005 15:22 To: ADSM-L@VM.MARIST.EDU Subject: Space Reclamation Eating Tapes I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
It has been my experience that, if primary tape pool maxscratch value is set greater than tapes used when reclamation kicks off, it mounts a brand new scratch tapes. I suspect that there is some logical reason how tapes are reclaimed ... such as why not taking already used tape. However I have had success by lowering the maxscratch count less than tapes used will allow TSM not to use new scratch tapes but use already used tapes. Now, if one is using collocation, I tried to think of a reason why one would starting reclamation. My experience shows that since any gain of tapes by performing reclamation of collocation pool is short lived because TSM will shortly attempt to use new scratch tapes. Sung Y. Lee ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 11/28/2005 09:21:45 AM: I recently migrated our Windows 2K3 TSM server from 5.2.1.3 to 5.3.2.0 and since then, it seems that whenever I kick off space reclamation for my primary tape storage pools, it eats up scratch tapes, instead of freeing them up. Is there a reason for this? I understand that occasionally TSM will need a scratch tape to combine other tapes, but it should then free those other tapes up and return them to the scratch pool. I've checked the reuse delay on the storage pools, and they are set to 0, so I know that isn't the problem. Mel Dennis
Re: Space Reclamation Eating Tapes
On Nov 28, 2005, at 11:42 AM, Sung Y Lee wrote: It has been my experience that, if primary tape pool maxscratch value is set greater than tapes used when reclamation kicks off, it mounts a brand new scratch tapes. ... I've never seen that behavior - that would result in a large number of tapes in Filling state, and that does not happen. TSM requests a fresh tape when the would-be candidate filling tape is in an unusable state (as from previous tape errors) or that volume is in use (current output volume or being dismounted). If a TSM instance was always calling for new volumes, that would constitute a violation of its design, and should be reported as a defect. In any case, this thread is largely proceeding without substantive information. We need to see the results of analyses which examined tape states, Activity Log, and volume contents. Richard Sims
Errors when running Space Reclamation
I have been recieving Space Reclamation Failures on my TSM server lately and I am not sure why. When I go back to the time of the events, I get the following ANRD log report: (sorry for the length of the report, but I figured it would be best to include it all) 11/20/2005 15:59:12 ANR8337I LTO volume A00541 mounted in drive LTODRV13 (mt4.3.1.3). (SESSION: 25342) 11/20/2005 15:59:12 ANR0510I Session 25342 opened input volume A00541. (SESSION: 25342) 11/20/2005 16:00:28 ANRD afmove.c(5788): ThreadId43 Unexpected result code (45) from ssCopy. (SESSION: 25342) 11/20/2005 16:00:28 ANRD ThreadId43 issued message from: (SESSION: 25342) 11/20/2005 16:00:28 (43) Context report (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSinkThread (45) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating SM Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no sessions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating AS Vol Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No mounted (or mount in progress) volumes. (SESSION: 25342) 11/20/2005 16:00:29 (45) Failed attempt #1 to get SSV-mutex (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssSession Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service sessions active. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssOpenSeg Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service segments found. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating BF Copy Control Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No global copy control blocks. (SESSION: 25342) 11/20/2005 16:00:29 (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSrcThread (46) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (46) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (46) Tsn=0:160675859 -- Valid=1, inRollback=0, endNTA=0, State=2, Index=3, LatchCount=0, SavePoint=0, TotLogRecs=0, TotLogBytes=0, UndoLogRecs=0, UndoLogBytes=0, LogReserve=0, PageReserve=0, Elapsed=99 (secs), MinLsn=0.0.0, MaxLsn=0.0.0, LastLsn=0.0.0, UndoNextLsn=0.0.0, logWriter=False, backupTxn=False (SESSION: 25342) 11/20/2005 16:00:29 (46) Open objects: (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Damaged- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -BF.Aggregate.Attributes- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Vol.Segments- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -Restore.Sessions- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -Collocation.Group.Member- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Vol.Clusters- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AS.Volume.Status- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Segments- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Bitfiles- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Vol.Partial.Bitfiles- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -SS.Volume.Names- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -SS.Volume.Ids- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating SM Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (46) *** no sessions found *** (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating AS Vol Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (46) Mounted (or mount in progress) volumes: (SESSION: 25342) 11/20/2005 16:00:29 (46) Volume A00541
Re: Errors when running Space Reclamation
When posting PLEASE INCLUDE YOUR SERVER platform version. If you have recently upgraded to TSM 5.3.x, it may be IC47584. I have a PMR open and am hoping to get a test fix shortly. While annoying, it appears to be harmless. Try cleaning up that volume by doing a MOVE DATA instead of a reclamation. If that doesn't work, see if it is continually trying to mount the same output tape. If so, mark that tape as READONLY until you get past this problem. In every case, by simply changing the combination of input/output tapes, I've been able to get past it. (But then it just pops up in another place a few days later.) I am TSM 5.2.3.0 on Windows. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: Monday, November 21, 2005 9:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Errors when running Space Reclamation I have been recieving Space Reclamation Failures on my TSM server lately and I am not sure why. When I go back to the time of the events, I get the following ANRD log report: (sorry for the length of the report, but I figured it would be best to include it all) 11/20/2005 15:59:12 ANR8337I LTO volume A00541 mounted in drive LTODRV13 (mt4.3.1.3). (SESSION: 25342) 11/20/2005 15:59:12 ANR0510I Session 25342 opened input volume A00541. (SESSION: 25342) 11/20/2005 16:00:28 ANRD afmove.c(5788): ThreadId43 Unexpected result code (45) from ssCopy. (SESSION: 25342) 11/20/2005 16:00:28 ANRD ThreadId43 issued message from: (SESSION: 25342) 11/20/2005 16:00:28 (43) Context report (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSinkThread (45) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating SM Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no sessions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating AS Vol Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No mounted (or mount in progress) volumes. (SESSION: 25342) 11/20/2005 16:00:29 (45) Failed attempt #1 to get SSV-mutex (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssSession Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service sessions active. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssOpenSeg Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service segments found. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating BF Copy Control Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No global copy control blocks. (SESSION: 25342) 11/20/2005 16:00:29 (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSrcThread (46) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (46) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (46) Tsn=0:160675859 -- Valid=1, inRollback=0, endNTA=0, State=2, Index=3, LatchCount=0, SavePoint=0, TotLogRecs=0, TotLogBytes=0, UndoLogRecs=0, UndoLogBytes=0, LogReserve=0, PageReserve=0, Elapsed=99 (secs), MinLsn=0.0.0, MaxLsn=0.0.0, LastLsn=0.0.0, UndoNextLsn=0.0.0, logWriter=False, backupTxn=False (SESSION: 25342) 11/20/2005 16:00:29 (46) Open objects: (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Damaged- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -BF.Aggregate.Attributes- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Vol.Segments- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -Restore.Sessions- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -Collocation.Group.Member- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name -AF.Vol.Clusters- (sp=0) (SESSION: 25342) 11/20/2005 16:00:29 (46)name
Re: Errors when running Space Reclamation
Your right, I am on a Windows 2K3 server and I recently migrated from version 5.2.1.3 to 5.3.2.0. I'll try out those suggestions. Mel Dennis Systems Engineer - IT743 Siemens Power Generation 4400 Alafaya Trail Orlando, FL 32826 MC Q1-110 Tel: (407) 736-2360 Win: 439-2360 Fax: (407) 736-5069 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Monday, November 21, 2005 11:13 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Errors when running Space Reclamation When posting PLEASE INCLUDE YOUR SERVER platform version. If you have recently upgraded to TSM 5.3.x, it may be IC47584. I have a PMR open and am hoping to get a test fix shortly. While annoying, it appears to be harmless. Try cleaning up that volume by doing a MOVE DATA instead of a reclamation. If that doesn't work, see if it is continually trying to mount the same output tape. If so, mark that tape as READONLY until you get past this problem. In every case, by simply changing the combination of input/output tapes, I've been able to get past it. (But then it just pops up in another place a few days later.) I am TSM 5.2.3.0 on Windows. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: Monday, November 21, 2005 9:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Errors when running Space Reclamation I have been recieving Space Reclamation Failures on my TSM server lately and I am not sure why. When I go back to the time of the events, I get the following ANRD log report: (sorry for the length of the report, but I figured it would be best to include it all) 11/20/2005 15:59:12 ANR8337I LTO volume A00541 mounted in drive LTODRV13 (mt4.3.1.3). (SESSION: 25342) 11/20/2005 15:59:12 ANR0510I Session 25342 opened input volume A00541. (SESSION: 25342) 11/20/2005 16:00:28 ANRD afmove.c(5788): ThreadId43 Unexpected result code (45) from ssCopy. (SESSION: 25342) 11/20/2005 16:00:28 ANRD ThreadId43 issued message from: (SESSION: 25342) 11/20/2005 16:00:28 (43) Context report (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSinkThread (45) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating SM Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) *** no sessions found *** (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating AS Vol Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No mounted (or mount in progress) volumes. (SESSION: 25342) 11/20/2005 16:00:29 (45) Failed attempt #1 to get SSV-mutex (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssSession Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service sessions active. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating ssOpenSeg Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No storage service segments found. (SESSION: 25342) 11/20/2005 16:00:29 (45) Generating BF Copy Control Context Report: (SESSION: 25342) 11/20/2005 16:00:29 (45) No global copy control blocks. (SESSION: 25342) 11/20/2005 16:00:29 (SESSION: 25342) 11/20/2005 16:00:29 (43) Thread SsAuxSrcThread (46) is a child thread related to: 43 (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating TM Context Report: (struct=tmTxnDesc) (slots=256) (SESSION: 25342) 11/20/2005 16:00:29 (46) *** no transactions found *** (SESSION: 25342) 11/20/2005 16:00:29 (46) Generating Database Transaction Table Context: (SESSION: 25342) 11/20/2005 16:00:29 (46) Tsn=0:160675859 -- Valid=1, inRollback=0, endNTA=0, State=2, Index=3, LatchCount=0, SavePoint=0, TotLogRecs=0, TotLogBytes=0, UndoLogRecs=0, UndoLogBytes=0, LogReserve=0, PageReserve=0, Elapsed=99 (secs), MinLsn=0.0.0, MaxLsn=0.0.0, LastLsn=0.0.0, UndoNextLsn=0.0.0, logWriter=False, backupTxn=False (SESSION: 25342) 11/20/2005 16:00:29 (46) Open objects: (SESSION: 25342) 11/20/2005 16:00:29
Space reclamation error for volumes dedicated to directory structure storage ....
Hi all, Since upgrade to TSM 5.3.1, I'm facing a strange problem affecting reclamation on specific copypool dedicated to directories structure. What happens is as follows : 09/15/05 09:34:28 ANR0984I Process 375 for SPACE RECLAMATION started in the BACKGROUND at 09:34:28. (PROCESS: 375) 09/15/05 09:34:28 ANR4931I Reclamation process 375 started for copy storage pool COPYLTO2_DIR automatically, threshold=70, offsiteRclmLimit=No Limit, duration=None. (PROCESS: 375) 09/15/05 09:34:28 ANR1040I Space reclamation started for volume 000559, storage pool COPYLTO2_DIR (process number 375). (PROCESS: 375) 09/15/05 09:35:19 ANR8337I LTO volume 000507 mounted in drive LTO2DR7 (/dev/rmt23). (PROCESS: 375) 09/15/05 09:35:30 ANR1340I Scratch volume 000507 is now defined in storage pool COPYLTO2_DIR. (PROCESS: 375) 09/15/05 09:35:30 ANR0513I Process 375 opened output volume 000507. (PROCESS: 375) 09/15/05 09:55:04 ANR1173E Space reclamation for offsite volume(s) cannot copy file in storage pool DISKPOOL_DIR: Node X, Type Backup, File space \\X\i$, fsId 5, File name \SMSPKGI$\PAC00055\BW\PLANNING\ MAP. (PROCESS: 375) 09/15/05 09:55:04 ANR0102E asalloc.c(8720): Error 1 inserting row in table AS.Segments. (PROCESS: 375) Snipped, lots of ANR1173/ANR0102 errors .. I already spoke with IBM, and they told me to issue REPAIR stgvol command against the volume being reclamed : 09/15/05 12:22:50 ANR2017I Administrator X issued command: REPAIR STGVOLS voln=000559 (SESSION: 54405) 09/15/05 12:22:50 ANR0984I Process 387 for REPAIR STGVOL started in the BACKGROUND at 12:22:50. (SESSION: 54405, PROCESS: 387) 09/15/05 12:22:50 ANR4752I REPAIR STGVOL process 387 started for 1 volumes. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR4757I REPAIR STGVOL finished evaluating volume 000559, no repair was needed. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR4754I REPAIR STGVOL process 387 ended, processed 1 of 1 total volumes with 0 repaired. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR0987I Process 387 for REPAIR STGVOL running in the BACKGROUND processed 1 items with a completion state of SUCCESS at 12:23:24. (SESSION: 54405, PROCESS: 387) So, it looks like the volume is OK. It's now the second time within 2 weeks that this happens (on different volumes, but always for that storage pool), and I can't figure out what the problem is. Someone having an idea ? Just for info : if I kill the reclamation process and let it automatically start again (even without performing repair stgvol), I don't get any error anymore ... Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] **
Re: Space reclamation error for volumes dedicated to directory structure storage ....
I upgraded one server to 5.3.1.3 a couple of weeks ago. Had one occurance of something similar; only my reclaim just said internal server error and died. Restarting reclaim didn't fix it. But my reclaim was appending data to a filling tape that was almost full. I directed it to a different tape with MOVE DATA instead of reclaim, and it finished OK. Have seen nothing else strange. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of PAC Brion Arnaud Sent: Thursday, September 15, 2005 9:10 AM To: ADSM-L@VM.MARIST.EDU Subject: Space reclamation error for volumes dedicated to directory structure storage Hi all, Since upgrade to TSM 5.3.1, I'm facing a strange problem affecting reclamation on specific copypool dedicated to directories structure. What happens is as follows : 09/15/05 09:34:28 ANR0984I Process 375 for SPACE RECLAMATION started in the BACKGROUND at 09:34:28. (PROCESS: 375) 09/15/05 09:34:28 ANR4931I Reclamation process 375 started for copy storage pool COPYLTO2_DIR automatically, threshold=70, offsiteRclmLimit=No Limit, duration=None. (PROCESS: 375) 09/15/05 09:34:28 ANR1040I Space reclamation started for volume 000559, storage pool COPYLTO2_DIR (process number 375). (PROCESS: 375) 09/15/05 09:35:19 ANR8337I LTO volume 000507 mounted in drive LTO2DR7 (/dev/rmt23). (PROCESS: 375) 09/15/05 09:35:30 ANR1340I Scratch volume 000507 is now defined in storage pool COPYLTO2_DIR. (PROCESS: 375) 09/15/05 09:35:30 ANR0513I Process 375 opened output volume 000507. (PROCESS: 375) 09/15/05 09:55:04 ANR1173E Space reclamation for offsite volume(s) cannot copy file in storage pool DISKPOOL_DIR: Node X, Type Backup, File space \\X\i$, fsId 5, File name \SMSPKGI$\PAC00055\BW\PLANNING\ MAP. (PROCESS: 375) 09/15/05 09:55:04 ANR0102E asalloc.c(8720): Error 1 inserting row in table AS.Segments. (PROCESS: 375) Snipped, lots of ANR1173/ANR0102 errors .. I already spoke with IBM, and they told me to issue REPAIR stgvol command against the volume being reclamed : 09/15/05 12:22:50 ANR2017I Administrator X issued command: REPAIR STGVOLS voln=000559 (SESSION: 54405) 09/15/05 12:22:50 ANR0984I Process 387 for REPAIR STGVOL started in the BACKGROUND at 12:22:50. (SESSION: 54405, PROCESS: 387) 09/15/05 12:22:50 ANR4752I REPAIR STGVOL process 387 started for 1 volumes. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR4757I REPAIR STGVOL finished evaluating volume 000559, no repair was needed. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR4754I REPAIR STGVOL process 387 ended, processed 1 of 1 total volumes with 0 repaired. (SESSION: 54405, PROCESS: 387) 09/15/05 12:23:24 ANR0987I Process 387 for REPAIR STGVOL running in the BACKGROUND processed 1 items with a completion state of SUCCESS at 12:23:24. (SESSION: 54405, PROCESS: 387) So, it looks like the volume is OK. It's now the second time within 2 weeks that this happens (on different volumes, but always for that storage pool), and I can't figure out what the problem is. Someone having an idea ? Just for info : if I kill the reclamation process and let it automatically start again (even without performing repair stgvol), I don't get any error anymore ... Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] **
Re: Question about Space Reclamation..
Hoi Roark,
If you cannot affort to upgrade to 5.3.x, you can also use more tapepools.
So you can make a tapepool for very small nodes, with collocation off, so it
still uses less tapes and a tapepool for the big nodes with collocation on.
If neccesary, you can make more tapepools, but remember, if you want to use
a diskpool (and most sites do) you need a diskpool for each tapepool.
But best thing is to upgrade to 5.3.x and learn the command line commands
:-), so you can use collocation groups.
Collocation on copypools is most of the times nonsens... Even if you want it
in case of a big disaster, the costs are enormous and fast restores per
machine is not the biggest issue at that moment if you can use a library
with enoufh drives to restore multiple machines simmultanious.
You cannot change a filling tape to full, but you can use move data
{volname} stg={diskpool} to move the data of the tape quickly to disk. If
you set the access of the tapes you want to clean to readonly first, the
data will be migrated to the filling tapes you don't want to clean.
Regards,
Maurice van 't Loo
- Original Message -
From: Roark Ludwig [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, August 26, 2005 1:56 AM
Subject: Re: [ADSM-L] Question about Space Reclamation..
I have been handed a TSM system in the past week that has been running for
a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this
system
is running TSM 5.2.2.
We have run out of tapes as the setting for collocation (yes) is trying to
use a tape for each node (as I understand it, ,,please correct me if I am
wrong)..
We have decided that since we have about 80 volumes with less then 1%
utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for
the TAPEPOOL and COPYPOOLS.
We are expecting to add another set of nodes and don't wish to consume
more
of our volumes (with small percent utilization) as we add the nodes.
Question ..
Will this setting COLLOCATION=NO stop the addition of volumes? (I expect
the answer is YES,, please correct me if I am wrong.)
Now to the second question.
I see no easy way to have Space Reclamation condense the volumes included
in the two pools as it will only process FULL volumes. (Again Please
jump
in here).
QUESTION: is it acceptable to set the status from FILLING to FULL for
the volumes with low percentage utilized to force Space Reclamation ?
OR
is there an easier way to accomplish the GOAL of reducing the number of
volumes needed for the pools?(given that we have set COLLOCATION=NO)
or should we simply wait out the natural filling of the volumes and allow
normal Space Reclamation as time proceeds?
Has anyone done this in the past?
How have others dealt with this??
Thanks for any input.
Re: Question about Space Reclamation..
Hi,
Just one thing to add. If the command line isn't your friend, tools like
tsmmanager can help you a lot. Just checkout the website (and look at
the pricing) and download the demo.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Maurice van 't Loo
Sent: dinsdag 30 augustus 2005 11:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Question about Space Reclamation..
Hoi Roark,
If you cannot affort to upgrade to 5.3.x, you can also use more
tapepools.
So you can make a tapepool for very small nodes, with collocation off,
so it still uses less tapes and a tapepool for the big nodes with
collocation on.
If neccesary, you can make more tapepools, but remember, if you want to
use a diskpool (and most sites do) you need a diskpool for each
tapepool.
But best thing is to upgrade to 5.3.x and learn the command line
commands :-), so you can use collocation groups.
Collocation on copypools is most of the times nonsens... Even if you
want it in case of a big disaster, the costs are enormous and fast
restores per machine is not the biggest issue at that moment if you can
use a library with enoufh drives to restore multiple machines
simmultanious.
You cannot change a filling tape to full, but you can use move data
{volname} stg={diskpool} to move the data of the tape quickly to disk.
If you set the access of the tapes you want to clean to readonly first,
the data will be migrated to the filling tapes you don't want to clean.
Regards,
Maurice van 't Loo
- Original Message -
From: Roark Ludwig [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, August 26, 2005 1:56 AM
Subject: Re: [ADSM-L] Question about Space Reclamation..
I have been handed a TSM system in the past week that has been running
for
a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this
system
is running TSM 5.2.2.
We have run out of tapes as the setting for collocation (yes) is
trying to use a tape for each node (as I understand it, ,,please
correct me if I am wrong)..
We have decided that since we have about 80 volumes with less then 1%
utilized and 20 or so with large utilization %'s to set COLLOCATION=NO
for the TAPEPOOL and COPYPOOLS.
We are expecting to add another set of nodes and don't wish to consume
more
of our volumes (with small percent utilization) as we add the nodes.
Question ..
Will this setting COLLOCATION=NO stop the addition of volumes? (I
expect the answer is YES,, please correct me if I am wrong.)
Now to the second question.
I see no easy way to have Space Reclamation condense the volumes
included in the two pools as it will only process FULL volumes.
(Again Please
jump
in here).
QUESTION: is it acceptable to set the status from FILLING to FULL
for the volumes with low percentage utilized to force Space
Reclamation ?
OR
is there an easier way to accomplish the GOAL of reducing the number
of
volumes needed for the pools?(given that we have set
COLLOCATION=NO)
or should we simply wait out the natural filling of the volumes and
allow normal Space Reclamation as time proceeds?
Has anyone done this in the past?
How have others dealt with this??
Thanks for any input.
Re: Question about Space Reclamation..
True ;-)
I use Operational Reporting and Access with a bunch of advanced selects (on
imported tables) to monitor and the command admin client to enter the
commands... that's cheaper... more Dutch ;-)
Regards,
Maurice
- Original Message -
From: Bos, Karel [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Tuesday, August 30, 2005 12:20 PM
Subject: Re: [ADSM-L] Question about Space Reclamation..
Hi,
Just one thing to add. If the command line isn't your friend, tools like
tsmmanager can help you a lot. Just checkout the website (and look at
the pricing) and download the demo.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Maurice van 't Loo
Sent: dinsdag 30 augustus 2005 11:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Question about Space Reclamation..
Hoi Roark,
If you cannot affort to upgrade to 5.3.x, you can also use more
tapepools.
So you can make a tapepool for very small nodes, with collocation off,
so it still uses less tapes and a tapepool for the big nodes with
collocation on.
If neccesary, you can make more tapepools, but remember, if you want to
use a diskpool (and most sites do) you need a diskpool for each
tapepool.
But best thing is to upgrade to 5.3.x and learn the command line
commands :-), so you can use collocation groups.
Collocation on copypools is most of the times nonsens... Even if you
want it in case of a big disaster, the costs are enormous and fast
restores per machine is not the biggest issue at that moment if you can
use a library with enoufh drives to restore multiple machines
simmultanious.
You cannot change a filling tape to full, but you can use move data
{volname} stg={diskpool} to move the data of the tape quickly to disk.
If you set the access of the tapes you want to clean to readonly first,
the data will be migrated to the filling tapes you don't want to clean.
Regards,
Maurice van 't Loo
- Original Message -
From: Roark Ludwig [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, August 26, 2005 1:56 AM
Subject: Re: [ADSM-L] Question about Space Reclamation..
I have been handed a TSM system in the past week that has been running
for
a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this
system
is running TSM 5.2.2.
We have run out of tapes as the setting for collocation (yes) is
trying to use a tape for each node (as I understand it, ,,please
correct me if I am wrong)..
We have decided that since we have about 80 volumes with less then 1%
utilized and 20 or so with large utilization %'s to set COLLOCATION=NO
for the TAPEPOOL and COPYPOOLS.
We are expecting to add another set of nodes and don't wish to consume
more
of our volumes (with small percent utilization) as we add the nodes.
Question ..
Will this setting COLLOCATION=NO stop the addition of volumes? (I
expect the answer is YES,, please correct me if I am wrong.)
Now to the second question.
I see no easy way to have Space Reclamation condense the volumes
included in the two pools as it will only process FULL volumes.
(Again Please
jump
in here).
QUESTION: is it acceptable to set the status from FILLING to FULL
for the volumes with low percentage utilized to force Space
Reclamation ?
OR
is there an easier way to accomplish the GOAL of reducing the number
of
volumes needed for the pools?(given that we have set
COLLOCATION=NO)
or should we simply wait out the natural filling of the volumes and
allow normal Space Reclamation as time proceeds?
Has anyone done this in the past?
How have others dealt with this??
Thanks for any input.
Re: Question about Space Reclamation..
Thanks to all of you..
With a weekend of reading and some experimentation, I believe that the
problems have been overcome. I might still have lots of questions, but you
all have been very helpful.
Roark
Maurice van 't
Loo
[EMAIL PROTECTED] To
TERS.NL ADSM-L@VM.MARIST.EDU
Sent by: ADSM:cc
Dist Stor
Manager Subject
[EMAIL PROTECTED] Re: [ADSM-L] Question about Space
.EDU Reclamation..
08/30/2005 04:10
AM
Please respond to
ADSM: Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
True ;-)
I use Operational Reporting and Access with a bunch of advanced selects (on
imported tables) to monitor and the command admin client to enter the
commands... that's cheaper... more Dutch ;-)
Regards,
Maurice
- Original Message -
From: Bos, Karel [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Tuesday, August 30, 2005 12:20 PM
Subject: Re: [ADSM-L] Question about Space Reclamation..
Hi,
Just one thing to add. If the command line isn't your friend, tools like
tsmmanager can help you a lot. Just checkout the website (and look at
the pricing) and download the demo.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Maurice van 't Loo
Sent: dinsdag 30 augustus 2005 11:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Question about Space Reclamation..
Hoi Roark,
If you cannot affort to upgrade to 5.3.x, you can also use more
tapepools.
So you can make a tapepool for very small nodes, with collocation off,
so it still uses less tapes and a tapepool for the big nodes with
collocation on.
If neccesary, you can make more tapepools, but remember, if you want to
use a diskpool (and most sites do) you need a diskpool for each
tapepool.
But best thing is to upgrade to 5.3.x and learn the command line
commands :-), so you can use collocation groups.
Collocation on copypools is most of the times nonsens... Even if you
want it in case of a big disaster, the costs are enormous and fast
restores per machine is not the biggest issue at that moment if you can
use a library with enoufh drives to restore multiple machines
simmultanious.
You cannot change a filling tape to full, but you can use move data
{volname} stg={diskpool} to move the data of the tape quickly to disk.
If you set the access of the tapes you want to clean to readonly first,
the data will be migrated to the filling tapes you don't want to clean.
Regards,
Maurice van 't Loo
- Original Message -
From: Roark Ludwig [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Friday, August 26, 2005 1:56 AM
Subject: Re: [ADSM-L] Question about Space Reclamation..
I have been handed a TSM system in the past week that has been running
for
a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this
system
is running TSM 5.2.2.
We have run out of tapes as the setting for collocation (yes) is
trying to use a tape for each node (as I understand it, ,,please
correct me if I am wrong)..
We have decided that since we have about 80 volumes with less then 1%
utilized and 20 or so with large utilization %'s to set COLLOCATION=NO
for the TAPEPOOL and COPYPOOLS.
We are expecting to add another set of nodes and don't wish to consume
more
of our volumes (with small percent utilization) as we add the nodes.
Question ..
Will this setting COLLOCATION=NO stop the addition of volumes? (I
expect the answer is YES,, please correct me if I am wrong.)
Now to the second question.
I see no easy way to have Space Reclamation condense the volumes
included in the two pools as it will only process FULL volumes.
(Again Please
jump
in here).
QUESTION: is it acceptable to set the status from FILLING to FULL
for the volumes with low percentage utilized to force Space
Reclamation ?
OR
is there an easier way to accomplish the GOAL of reducing the number
of
volumes needed for the pools?(given that we have set
COLLOCATION=NO)
or should we simply wait out the natural filling of the volumes and
allow normal Space Reclamation as time proceeds?
Has anyone done this in the past?
How have others dealt with this??
Thanks for any input.
Re: Question about Space Reclamation..
Hi, I can think of 2 ways around this - 1. install 5.3 (at level 5.3.1.13 to avoid a bad bug). I have done this And collocation groups work great, the feature is a great solution to this problem. 2. When migration occurs, TSM selects the volume currently used by the node. Do a process like this to put all the small nodes onto 1 volume. A. list all the low use volumes. B. make move data commands for all but one. C. update all the volumes to readonly except the one omitted in B. D. run the move data commands one at a time. E. make all the volumes readwrite again. Hope this helps, Bill Colwell -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Friday, August 26, 2005 1:38 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Question about Space Reclamation.. There is a middle ground here. If you set COLLOCATION=NO, it will drastically affect your RESTORE performance. Over time, you could in theory have to mount EVERY TAPE to do a full restore of a client. That is why collocation is a good thing. But collocation will, by default, put each client on its own tape, thereby using a LOT of tapes. The alternative is to control collocation by setting the MAXSCRATCH value for your TAPEPOOL. Assume you are starting out with a new TSM server; if you have 80 clients and set MAXSCRATCH to 40, TSM will stack 2 clients per tape. This is a good thing, too. You get 90% of the benefits of collocation, with only half the tapes. This is a very common thing to do; there are plenty of sites that have more clients than slots in their library! The drawback is that you have to check on the value of MAXSCRATCH often. As you get more tapes in FULL status (assuming you are like the rest of us and your site is CONSTANTLY growing its storage farm), you have to keep increasing the value of MAXSCRATCH. That's easy: update stgpool TAPEPOOL maxscratch=xxx. Or do it from the admin GUI. What I do is: 1) Decide whether you want to stack 2, 3, etc. clients per tape. For example, pick TWO. 2) Then the number of TAPEPOOL tapes you wand to be in FILLING status is #clients/TWO. 3) Count the number of tapes in TAPEPOOL that are already FULL. 3) Set TAPEPOOL MAXSCRATCH to: DESIRED FILLING + ALREADY FULL. Check it one a week (or more often if you fill up a lot of tapes daily) and add more to MAXSCRATCH as tapes get full. Regarding COPYPOOL, I don't see any reason to collocate that at all. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roark Ludwig Sent: Thursday, August 25, 2005 7:56 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Question about Space Reclamation.. I have been handed a TSM system in the past week that has been running for a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system is running TSM 5.2.2. We have run out of tapes as the setting for collocation (yes) is trying to use a tape for each node (as I understand it, ,,please correct me if I am wrong).. We have decided that since we have about 80 volumes with less then 1% utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for the TAPEPOOL and COPYPOOLS. We are expecting to add another set of nodes and don't wish to consume more of our volumes (with small percent utilization) as we add the nodes. Question .. Will this setting COLLOCATION=NO stop the addition of volumes? (I expect the answer is YES,, please correct me if I am wrong.) Now to the second question. I see no easy way to have Space Reclamation condense the volumes included in the two pools as it will only process FULL volumes. (Again Please jump in here). QUESTION: is it acceptable to set the status from FILLING to FULL for the volumes with low percentage utilized to force Space Reclamation ? OR is there an easier way to accomplish the GOAL of reducing the number of volumes needed for the pools?(given that we have set COLLOCATION=NO) or should we simply wait out the natural filling of the volumes and allow normal Space Reclamation as time proceeds? Has anyone done this in the past? How have others dealt with this?? Thanks for any input.
Re: Question about Space Reclamation..
== On Fri, 26 Aug 2005 21:33:58 -0400, David E Ehresman [EMAIL PROTECTED] said: Uhh, how about for restore performance when it matters most, during a disaster! I come down on the other side of this, myself. Biggest reason is, you just can't afford to collocate the offsites. Imagine sending one tape per node offsite, every day. If you've got some sort of long-haul fiber solution, and can expose the physical volume granularity at the remote site to your local server, then it would be very useful to collocate. So in your site-wide disaster, you are going to have a mishmash anyway. On the other hand, the media-failure case is much more common. In those cases, I find the noncollocated copy pool to be a reasonable price to pay for the savings in slots and tapes. All these calculations might be different with collocation groups; hopefully in a week or two I'll be considering that as a concrete problem. (chortle) - Allen S. Rout
Re: Question about Space Reclamation..
Hello, one reason why I updated to version 5.3 was that there is the possibility to create collocation groups. I have now packed all small servers (about 20 of them) in one group, about 10 medium servers in another group and I made groups for large servers with about 1-3 nodes each. So now no server is spread across more than 1-4 tapes (except for the really large ones) and the tapes have a good utilization. One problem still existing is that for each collocation group (we have 6 of them) there is one tape send to the offsite location each day (we have collocation=group turned on the copy pool). And as we do offsite reclamation only on the weekend we have 5*6=30 tapes that are very little utilized at the end of the week. But I think there is no way around this. I'm not sure if this might work, but couldn't you just use the move data STGPOOL_NAME-command to move the data from your 1% utilized volumes? regards, Volker Maibaum Tel: +49 711 939 0972 Fax: +49 711 939 160972 [EMAIL PROTECTED] Am Donnerstag, den 25.08.2005, 16:56 -0700 schrieb Roark Ludwig: I have been handed a TSM system in the past week that has been running for a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system is running TSM 5.2.2. We have run out of tapes as the setting for collocation (yes) is trying to use a tape for each node (as I understand it, ,,please correct me if I am wrong).. We have decided that since we have about 80 volumes with less then 1% utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for the TAPEPOOL and COPYPOOLS. We are expecting to add another set of nodes and don't wish to consume more of our volumes (with small percent utilization) as we add the nodes. Question .. Will this setting COLLOCATION=NO stop the addition of volumes? (I expect the answer is YES,, please correct me if I am wrong.) Now to the second question. I see no easy way to have Space Reclamation condense the volumes included in the two pools as it will only process FULL volumes. (Again Please jump in here). QUESTION: is it acceptable to set the status from FILLING to FULL for the volumes with low percentage utilized to force Space Reclamation ? OR is there an easier way to accomplish the GOAL of reducing the number of volumes needed for the pools?(given that we have set COLLOCATION=NO) or should we simply wait out the natural filling of the volumes and allow normal Space Reclamation as time proceeds? Has anyone done this in the past? How have others dealt with this?? Thanks for any input.
Re: Question about Space Reclamation..
Why colloocate the offsite tapes? Original message Date: Fri, 26 Aug 2005 08:26:44 +0200 From: Maibaum, Volker [EMAIL PROTECTED] Subject: Re: [ADSM-L] Question about Space Reclamation.. To: ADSM-L@VM.MARIST.EDU Hello, one reason why I updated to version 5.3 was that there is the possibility to create collocation groups. I have now packed all small servers (about 20 of them) in one group, about 10 medium servers in another group and I made groups for large servers with about 1-3 nodes each. So now no server is spread across more than 1-4 tapes (except for the really large ones) and the tapes have a good utilization. One problem still existing is that for each collocation group (we have 6 of them) there is one tape send to the offsite location each day (we have collocation=group turned on the copy pool). And as we do offsite reclamation only on the weekend we have 5*6=30 tapes that are very little utilized at the end of the week. But I think there is no way around this. I'm not sure if this might work, but couldn't you just use the move data STGPOOL_NAME-command to move the data from your 1% utilized volumes? regards, Volker Maibaum Tel: +49 711 939 0972 Fax: +49 711 939 160972 [EMAIL PROTECTED] Am Donnerstag, den 25.08.2005, 16:56 -0700 schrieb Roark Ludwig: I have been handed a TSM system in the past week that has been running for a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system is running TSM 5.2.2. We have run out of tapes as the setting for collocation (yes) is trying to use a tape for each node (as I understand it, ,,please correct me if I am wrong).. We have decided that since we have about 80 volumes with less then 1% utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for the TAPEPOOL and COPYPOOLS. We are expecting to add another set of nodes and don't wish to consume more of our volumes (with small percent utilization) as we add the nodes. Question .. Will this setting COLLOCATION=NO stop the addition of volumes? (I expect the answer is YES,, please correct me if I am wrong.) Now to the second question. I see no easy way to have Space Reclamation condense the volumes included in the two pools as it will only process FULL volumes. (Again Please jump in here). QUESTION: is it acceptable to set the status from FILLING to FULL for the volumes with low percentage utilized to force Space Reclamation ? OR is there an easier way to accomplish the GOAL of reducing the number of volumes needed for the pools?(given that we have set COLLOCATION=NO) or should we simply wait out the natural filling of the volumes and allow normal Space Reclamation as time proceeds? Has anyone done this in the past? How have others dealt with this?? Thanks for any input. Fred Johanson
Re: Question about Space Reclamation..
There is a middle ground here. If you set COLLOCATION=NO, it will drastically affect your RESTORE performance. Over time, you could in theory have to mount EVERY TAPE to do a full restore of a client. That is why collocation is a good thing. But collocation will, by default, put each client on its own tape, thereby using a LOT of tapes. The alternative is to control collocation by setting the MAXSCRATCH value for your TAPEPOOL. Assume you are starting out with a new TSM server; if you have 80 clients and set MAXSCRATCH to 40, TSM will stack 2 clients per tape. This is a good thing, too. You get 90% of the benefits of collocation, with only half the tapes. This is a very common thing to do; there are plenty of sites that have more clients than slots in their library! The drawback is that you have to check on the value of MAXSCRATCH often. As you get more tapes in FULL status (assuming you are like the rest of us and your site is CONSTANTLY growing its storage farm), you have to keep increasing the value of MAXSCRATCH. That's easy: update stgpool TAPEPOOL maxscratch=xxx. Or do it from the admin GUI. What I do is: 1) Decide whether you want to stack 2, 3, etc. clients per tape. For example, pick TWO. 2) Then the number of TAPEPOOL tapes you wand to be in FILLING status is #clients/TWO. 3) Count the number of tapes in TAPEPOOL that are already FULL. 3) Set TAPEPOOL MAXSCRATCH to: DESIRED FILLING + ALREADY FULL. Check it one a week (or more often if you fill up a lot of tapes daily) and add more to MAXSCRATCH as tapes get full. Regarding COPYPOOL, I don't see any reason to collocate that at all. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roark Ludwig Sent: Thursday, August 25, 2005 7:56 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Question about Space Reclamation.. I have been handed a TSM system in the past week that has been running for a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system is running TSM 5.2.2. We have run out of tapes as the setting for collocation (yes) is trying to use a tape for each node (as I understand it, ,,please correct me if I am wrong).. We have decided that since we have about 80 volumes with less then 1% utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for the TAPEPOOL and COPYPOOLS. We are expecting to add another set of nodes and don't wish to consume more of our volumes (with small percent utilization) as we add the nodes. Question .. Will this setting COLLOCATION=NO stop the addition of volumes? (I expect the answer is YES,, please correct me if I am wrong.) Now to the second question. I see no easy way to have Space Reclamation condense the volumes included in the two pools as it will only process FULL volumes. (Again Please jump in here). QUESTION: is it acceptable to set the status from FILLING to FULL for the volumes with low percentage utilized to force Space Reclamation ? OR is there an easier way to accomplish the GOAL of reducing the number of volumes needed for the pools?(given that we have set COLLOCATION=NO) or should we simply wait out the natural filling of the volumes and allow normal Space Reclamation as time proceeds? Has anyone done this in the past? How have others dealt with this?? Thanks for any input.
Re: Question about Space Reclamation..
Regarding COPYPOOL, I don't see any reason to collocate that at all. Uhh, how about for restore performance when it matters most, during a disaster! David
Re: Question about Space Reclamation..
I have been handed a TSM system in the past week that has been running for a year. IT has collocation = yes for TAPEPOOL and COPYPOOLS. this system is running TSM 5.2.2. We have run out of tapes as the setting for collocation (yes) is trying to use a tape for each node (as I understand it, ,,please correct me if I am wrong).. We have decided that since we have about 80 volumes with less then 1% utilized and 20 or so with large utilization %'s to set COLLOCATION=NO for the TAPEPOOL and COPYPOOLS. We are expecting to add another set of nodes and don't wish to consume more of our volumes (with small percent utilization) as we add the nodes. Question .. Will this setting COLLOCATION=NO stop the addition of volumes? (I expect the answer is YES,, please correct me if I am wrong.) Now to the second question. I see no easy way to have Space Reclamation condense the volumes included in the two pools as it will only process FULL volumes. (Again Please jump in here). QUESTION: is it acceptable to set the status from FILLING to FULL for the volumes with low percentage utilized to force Space Reclamation ? OR is there an easier way to accomplish the GOAL of reducing the number of volumes needed for the pools?(given that we have set COLLOCATION=NO) or should we simply wait out the natural filling of the volumes and allow normal Space Reclamation as time proceeds? Has anyone done this in the past? How have others dealt with this?? Thanks for any input.
Re: Space reclamation
Hi Moses I agree with Richard. (Input files damaged). If you want to reclaim the tapes for re-use, an easy way is to check them into your library, update the volume access to readw, then use the move data command to empty the tape/s Regards Steve Hartland Lechabile Storage Solutions 0824645461 -Original Message- From: Moses Show [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 5:49 PM To: [EMAIL PROTECTED] Subject:Re: Space reclamation Thank you Mike Bantz [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 15/06/2004 16:40 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Space reclamation Offsite volume SPL500L1 is the main clue here - some of your offsite tapes need reclamation, but for fairly obvious reasons that reclamation can't happen right now. Check in those tapes to your library and the reclamation will start up for 'em, even if they're not being marked for vaultretr status or are empty. If you have no plans on bringing them back just for reclamation, I wouldn't worry too much about it. HTH, Mike Bantz -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Moses Show Sent: Tuesday, June 15, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Space reclamation Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:31:19 AM. == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:45:23 AM.
Space reclamation
Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:31:19 AM.
Re: Space reclamation
Offsite volume SPL500L1 is the main clue here - some of your offsite tapes need reclamation, but for fairly obvious reasons that reclamation can't happen right now. Check in those tapes to your library and the reclamation will start up for 'em, even if they're not being marked for vaultretr status or are empty. If you have no plans on bringing them back just for reclamation, I wouldn't worry too much about it. HTH, Mike Bantz -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Moses Show Sent: Tuesday, June 15, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Space reclamation Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:31:19 AM.
Re: Space reclamation
Thank you Mike Bantz [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 15/06/2004 16:40 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Space reclamation Offsite volume SPL500L1 is the main clue here - some of your offsite tapes need reclamation, but for fairly obvious reasons that reclamation can't happen right now. Check in those tapes to your library and the reclamation will start up for 'em, even if they're not being marked for vaultretr status or are empty. If you have no plans on bringing them back just for reclamation, I wouldn't worry too much about it. HTH, Mike Bantz -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Moses Show Sent: Tuesday, June 15, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Space reclamation Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:31:19 AM. == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:45:23 AM.
Re: Space reclamation
Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? Well, the Messages manual pretty much explains why this can happen. In http://people.bu.edu/rbs/ADSM.QuickFacts I include some supplementary info. You probably have some onsite volumes (used as representatives of the contents of the offsite volume being reclaimed) which are unavailable or which contain damaged files. Check your Activity Log history for past tape problems, as well as do Query Volume for volumes which are Unavailable or Destroyed. Richard Sims
Re: Space reclamation
Well normally offsite reclamation will use the onsite tapes as input. So you normally don't checkin your offsite tapes for offsite reclamation - they stay offsite and the process reads your onsite tapes. I would check the activity log for other error messages. -Original Message- From: Mike Bantz [mailto:[EMAIL PROTECTED] Sent: June 15, 2004 10:40 AM To: [EMAIL PROTECTED] Subject: Re: Space reclamation Offsite volume SPL500L1 is the main clue here - some of your offsite tapes need reclamation, but for fairly obvious reasons that reclamation can't happen right now. Check in those tapes to your library and the reclamation will start up for 'em, even if they're not being marked for vaultretr status or are empty. If you have no plans on bringing them back just for reclamation, I wouldn't worry too much about it. HTH, Mike Bantz -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Moses Show Sent: Tuesday, June 15, 2004 9:35 AM To: [EMAIL PROTECTED] Subject: Space reclamation Earlier on this morning we commenced a Space reclamation job but we being given multiple messages referring to different volume numbers, of the following type ANR1163W Offsite volume SPL500L1 still contains files which could not be moved. However after struggling for a little while we rebooted the server and thses messages appeared to stop. Can anyody shed any light as to why this has happened ? == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 06/15/2004, 11:31:19 AM.
Re: Multiple space reclamation streams
unfortunately it si not possible to run multiple reclamation streams on a tape pool. [EMAIL PROTECTED] 3/29/04 7:45:06 AM Can I run multiple reclaimation streams on a single tape pool concurrently? Where can I RTFM or find the syntax? TIA ... JC
Space Reclamation Failure Question
I received the following error: ANR0986I Process 700 for SPACE RECLAMATION running in the BACKGROUND processed 160232 items for a total of 79,052,641,621 bytes with a completion state of FAILURE at 19:48:48. What happens to the tapes that had data transferred to them before the failure occurred? Since the reclamation failed, will those tapes go back to scratch??? Thanks, Marc - The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender.
Re: Space Reclamation Failure Question
Whatever was transferred has been transferred. It doesn't wipe out the reclamation that had been done before the failure. More examination of the actlog may reveal reason for failure. Could be as simple as tape error or a restore needed a tape that reclamation was using and preempted the reclamation process. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 02/12/04 09:29AM I received the following error: ANR0986I Process 700 for SPACE RECLAMATION running in the BACKGROUND processed 160232 items for a total of 79,052,641,621 bytes with a completion state of FAILURE at 19:48:48. What happens to the tapes that had data transferred to them before the failure occurred? Since the reclamation failed, will those tapes go back to scratch??? Thanks, Marc - The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: More mount points thru space reclamation
Can you spare few more minutes to report the misleading error message to IBM? It seems you've spent nearly a whole day beating your head over it. Save this time to the others. Zlatko Krastev IT Consultant Lars-Erik Öhman [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.01.2004 16:24 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: More mount points thru space reclamation I found the problem my self! I had to increase the Maximum Scratch Volumes Allowed from 100 that I had as a maximum of volumes, to more! Cryptic error message but now it´s solved!! /Larsa
Space reclamation running since 23Dec2003
Hi TSM'ers, here a sequence of what had happened with a TSM-SERVER 5.1.8.1 on an IBM H70 under AIX 4.3.3-11 and 6 months old 3584-LTO2 library with 4 drives 1. SPACE RECLAMATION started as follows: 23.12.2003 03:16:14 ANR1040I Space reclamation started for volume 373ABW, storage pool LTO_EC (process number 254). 23.12.2003 03:16:14 ANR1044I Removable volume 373ABW is required for space reclamation. 23.12.2003 03:16:16 ANR1142I Moving data for collocation cluster 1 of 23.12.2003 03:39:22 ANR8337I LTO volume 373ABW mounted in drive LTO_3 (/dev/rmt4). 23.12.2003 03:41:32 ANR1142I Moving data for collocation cluster 2 of 6412 on volume 373ABW. 2. Reading errors started rzds3# grep ANR8359 q.actl.20031223.redu 23.12.2003 19:51:55 ANR8359E Media fault detected on LTO volume 373ABW in drive LTO_3 (/dev/rmt4) of library 3584. 23.12.2003 21:32:05 ANR8359E Media fault detected on LTO volume 373ABW in drive LTO_3 (/dev/rmt4) of library 3584. ... and continued rzds3# grep ANR8359 q.actl.2003122*.redu | wc -l 28 rzds3# grep ANR8359 q.actl.2003123*.redu | wc -l 10 rzds3# grep ANR8359 q.actl.200401*.redu | wc -l 14 Until today I got 52 READING-errors, which show up as well in the AIX-based errpt. 3. The current state tsm: DS3q proc 254 ProcessProcess Description Status Number - 254Space Reclamation Volume 373ABW (storage pool LTO_EC), Moved Files: 907296, Moved Bytes: 30,652,121,214, Unreadable Files: 558, Unreadable Bytes: 22,733,876. Current Physical File (bytes): None Current input volume: 373ABW. Current output volume: 368ABW. tsm: DS3q vol 373ABW f=d Volume Name: 373ABW Storage Pool Name: LTO_EC Device Class Name: LTOCL Estimated Capacity (MB): 181,698.7 Pct Util: 12.9 Volume Status: Full Access: Read-Only Pct. Reclaimable Space: 90.2 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 497 Write Pass Number: 1 Approx. Date Last Written: 29.10.2003 10:31:42 Approx. Date Last Read: 05.01.2004 17:37:16 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 53 Volume Location: Last Update by (administrator): Last Update Date/Time: 08.07.2003 06:53:37 tsm: DS3q actlog begint=18:00 s=ANR1142I Date/TimeMessage -- 05.01.2004 18:00:58 ANR1142I Moving data for collocation cluster 2845 of 6412 on volume 373ABW. 05.01.2004 18:06:05 ANR1142I Moving data for collocation cluster 2846 of 6412 on volume 373ABW. 05.01.2004 18:09:36 ANR1142I Moving data for collocation cluster 2847 of 6412 on volume 373ABW. 4. What to do next ? 1. Wait until the tape is processed with its 6412 clusters and get the missing data from the copy-tapes ? 2. Can't wait so long because the impact on TSM's DB is very bad, i.e. I get only 50% of the normal throughput AND 2 tape-drives are kept for another 2 weeks, i.e. HALT RESTAT the server and hope for some positive effect ? 3. Any better idea ? With some hope for good response and a HAPPY, HEALTHY NEW YEAR -- MfG / Ciao - - - - - - - - - - - - - - - - - - - - - - - - - - - - Peter Dümpert Email: [EMAIL PROTECTED] Rechenzentrum der Technischen Universität Fax : ++49/531/391-5549 D 38092 BraunschweigTel : ++49/531/391-5535
Re: Space reclamation running since 23Dec2003
Looks like there is probably some data that is lost on that tape, unless you have a copy storage pool... To get around that you will want to take the recl up to 100 to pause reclamation, then if you have a copy storage pool, and this tape is in the primary pool mark the volume destroyed, rebuild the volume from the copy pool if you have a copy storage pool, and this tape is in the copy pool mark the volume destroyed, run another backup storage pool to recreate the data on the tape... if you do NOT have a copy storage pool, run an audit volume against the tape... fix=yes will delete the bad data run a move data to clear the tape resumre reclamation as normal... hope this helps... Dwight Peter Duempert [EMAIL PROTECTED]To: [EMAIL PROTECTED] .de cc: Sent by: ADSM: Subject: Space reclamation running since 23Dec2003 Dist Stor Manager [EMAIL PROTECTED] .EDU 01/05/2004 11:25 AM Please respond to Peter Duempert Hi TSM'ers, here a sequence of what had happened with a TSM-SERVER 5.1.8.1 on an IBM H70 under AIX 4.3.3-11 and 6 months old 3584-LTO2 library with 4 drives 1. SPACE RECLAMATION started as follows: 23.12.2003 03:16:14 ANR1040I Space reclamation started for volume 373ABW, storage pool LTO_EC (process number 254). 23.12.2003 03:16:14 ANR1044I Removable volume 373ABW is required for space reclamation. 23.12.2003 03:16:16 ANR1142I Moving data for collocation cluster 1 of 23.12.2003 03:39:22 ANR8337I LTO volume 373ABW mounted in drive LTO_3 (/dev/rmt4). 23.12.2003 03:41:32 ANR1142I Moving data for collocation cluster 2 of 6412 on volume 373ABW. 2. Reading errors started rzds3# grep ANR8359 q.actl.20031223.redu 23.12.2003 19:51:55 ANR8359E Media fault detected on LTO volume 373ABW in drive LTO_3 (/dev/rmt4) of library 3584. 23.12.2003 21:32:05 ANR8359E Media fault detected on LTO volume 373ABW in drive LTO_3 (/dev/rmt4) of library 3584. ... and continued rzds3# grep ANR8359 q.actl.2003122*.redu | wc -l 28 rzds3# grep ANR8359 q.actl.2003123*.redu | wc -l 10 rzds3# grep ANR8359 q.actl.200401*.redu | wc -l 14 Until today I got 52 READING-errors, which show up as well in the AIX-based errpt. 3. The current state tsm: DS3q proc 254 ProcessProcess Description Status Number - 254Space Reclamation Volume 373ABW (storage pool LTO_EC), Moved Files: 907296, Moved Bytes: 30,652,121,214, Unreadable Files: 558, Unreadable Bytes: 22,733,876. Current Physical File (bytes): None Current input volume: 373ABW. Current output volume: 368ABW. tsm: DS3q vol 373ABW f=d Volume Name: 373ABW Storage Pool Name: LTO_EC Device Class Name: LTOCL Estimated Capacity (MB): 181,698.7 Pct Util: 12.9 Volume Status: Full Access: Read-Only Pct. Reclaimable Space: 90.2 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 497 Write Pass Number: 1 Approx. Date Last Written: 29.10.2003 10:31:42 Approx. Date Last Read: 05.01.2004 17:37:16 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 53 Volume Location: Last Update by (administrator): Last Update Date/Time: 08.07.2003 06:53:37 tsm: DS3q actlog begint=18:00 s=ANR1142I Date/TimeMessage -- 05.01.2004 18:00:58 ANR1142I Moving data for collocation cluster 2845
More mount points thru space reclamation
I have set up copy pools between my backup sites a few weeks ago, and now during chistmas I have got this problem. 2004.01.02 08:25:53 ANR1163W Offsite volume CARNSWETSM2.BFS.071993625 still contains files which could not be moved. 2004.01.02 08:25:53 ANR1163W Offsite volume CARNSWETSM2.BFS.070013489 still contains files which could not be moved. 2004.01.02 08:25:53 ANR1082W Space reclamation terminated for volume CARNSWETSM2.BFS.071830391 - insufficient number of mount points available for removable media. I can´t find where I increase this value. Anyone out there that can give me a hint?? This problems only occurs only on one of my sites and there are not any more processes going on on at any site. Thanks in advance... /Larsa This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message.
Re: More mount points thru space reclamation
... ANR1082W Space reclamation terminated for volume CARNSWETSM2.BFS.071830391 - insufficient number of mount points available for removable media. ... Larsa - See entry Drives, not all in library being used in http://people.bu.edu/rbs/ADSM.QuickFacts for the most common causes. If necessary, re-post with Query Drive and Query Path information, etc., to show us more of the config. Richard Sims, BU
Re: More mount points thru space reclamation
Here is the config for the server: Q dr: Library Name Drive Name Device Type On-Line --- --- LB6 LB6DR0 LTO Yes LB6 LB6DR1 LTO Yes LB6 LB6DR2 LTO Yes Q path: Source Name Source Type Destination Destination On-Line NameType --- --- --- --- --- CARNSWETSM1 SERVER LB6 LIBRARY Yes CARNSWETSM1 SERVER LB6DR0 DRIVE Yes CARNSWETSM1 SERVER LB6DR1 DRIVE Yes CARNSWETSM1 SERVER LB6DR2 DRIVE Yes Q stg stdbktsm2c: Storage DeviceEstimated Pct Pct High Low Next Pool Name Class Name CapacityUtilMigrMig Mig Storage (MB)Pct Pct Pool --- -- -- - - --- --- STDBKTSM2CTSM2CLASS4,414,183.45.2 9 The copy storage pool config: Copy Storage Pools : STDBKTSM2C Storage Pool Name STDBKTSM2C Storage Pool Type COPY Device Class Name TSM2CLASS Estimated Capacity (MB) 4414183.8 Pct Util 45.2 Pct Migr - Pct Logical 99.3 High Mig Pct - Low Mig Pct - Migration Processes - Next Storage Pool - Maximum Size Threshold - Access READWRITE Description - Overflow Location - Cache Migrated Files? - Collocate? NO Reclamation Threshold 60 Maximum Scratch Volumes Allowed 100 Delay Period for Volume Reuse 0 Migration in Progress? - Amount Migrated (MB) - Elapsed Migration Time (seconds) - Reclamation in Progress? No Volume Being Migrated/Reclaimed - Last Update Date/Time 2003-07-11 12:58:48.00 Last Update by (administrator) LAROHM Reclaim Storage Pool - Migration Delay - Migration Continue - Storage Pool Data Format Native Copy Storage Pool(s) - Continue Copy on Error? - CRC Data NO The server device class: Server Device Classes : TSM2CLASS Device Class Name TSM2CLASS Device Access Strategy Sequential Storage Pool Count 1 Device Type SERVER Format - Est/Max Capacity 100G Mount Limit 2 Mount Wait (min) - Mount Retention (min) 2 Label Prefix ADSM Drive Letter - Library - Directory - Server Name CARNSWETSM2 Retry Period 10 Retry Interval 30 Twosided - Shared - Last Update by (administrator) LAROHM Last Update Date/Time 2004-01-02 10:49:54.00 All of this looks the same, but in the other direction :-), as far as I can se on the other site where it seems to work just fine!! Or is the problem on the destination server??? /Larsa -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: den 2 januari 2004 12:52 To: [EMAIL PROTECTED] Subject: Re: More mount points thru space reclamation ... ANR1082W Space reclamation terminated for volume CARNSWETSM2.BFS.071830391 - insufficient number of mount points available for removable media. ... Larsa - See entry Drives, not all in library being used in http://people.bu.edu/rbs/ADSM.QuickFacts for the most common causes. If necessary, re-post with Query Drive and Query Path information, etc., to show us more of the config. Richard Sims, BU This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message.
Re: More mount points thru space reclamation
Forgot the versions of the servers: TSM1: W2K SP4 and TSM version 5.1.7.0 TSM2: W2K SP4 and TSM version 5.1.5.0 The way it works is between TSM2 to TSM1 with space reclamation. /Larsa -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: den 2 januari 2004 12:52 To: [EMAIL PROTECTED] Subject: Re: More mount points thru space reclamation ... ANR1082W Space reclamation terminated for volume CARNSWETSM2.BFS.071830391 - insufficient number of mount points available for removable media. ... Larsa - See entry Drives, not all in library being used in http://people.bu.edu/rbs/ADSM.QuickFacts for the most common causes. If necessary, re-post with Query Drive and Query Path information, etc., to show us more of the config. Richard Sims, BU This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message. This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message.
Re: More mount points thru space reclamation
I found the problem my self! I had to increase the Maximum Scratch Volumes Allowed from 100 that I had as a maximum of volumes, to more! Cryptic error message but now it´s solved!! /Larsa -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: den 2 januari 2004 12:52 To: [EMAIL PROTECTED] Subject: Re: More mount points thru space reclamation ... ANR1082W Space reclamation terminated for volume CARNSWETSM2.BFS.071830391 - insufficient number of mount points available for removable media. ... Larsa - See entry Drives, not all in library being used in http://people.bu.edu/rbs/ADSM.QuickFacts for the most common causes. If necessary, re-post with Query Drive and Query Path information, etc., to show us more of the config. Richard Sims, BU This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message. This communication is from a Carnegie company within the Carnegie Group. The information contained in it, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorised use, review, retransmissions, dissemination, copying or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete or shred the material immediately. Thank you. Opinions, conclusions and other information expressed in this message are not given or endorsed by my firm or employer unless otherwise indicated by an authorised representative independent of this message.
Re: space reclamation on a server storage pool?
Because only the DB of TSM1 knows what is in that virtual volume. From TSM2's perspective this is single file and that's it. If that file was Oracle data file, would you expect TSM to know what is the content of it?! Zlatko Krastev IT Consultant John C Dury [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 08.10.2003 07:31 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:space reclamation on a server storage pool? We have 2 systems. TSM1 and TSM2. TSM2 is used solely as an offsite system to backup our primary tape storage pool on TSM1. When I run reclamation on the server storage pool on TSM1, the process requests a mount on TSM2 and a mount on TSM1. It appears to be copying data from the mount on TSM1 to TSM2. Why wouldn't reclamation mount 2 tapes on TSM2 and copy the data that way instead of through the network which is going to be much slower. Essentially it seems like it is going to copy the exact same data from TSM1 to TSM2 two times because it gets copied once during the BACKUP STG command, and then again during the space reclamation of the server storage pool. This seems like a great waste of time when the exact same data should already be on the TSM2 system and could be moved directly from 1 tape to another where it would be considerably faster. Does this make sense? Why would it be done this way? John
Re: space reclamation on a server storage pool?
John Zlatko is right. Since only TSM1 knows what is on the virtual volume, only TSM1 can perform reclamation of the virtual volume. The TSM designers then had a design choice about how this is acomplished. The obvious way is for reclamation of the virtual volume to be accomplished by mounting the virtual volume to be reclaimed on TSM1 as input, along with a scratch virtual volume for the output. This involves two physical tape mounts on TSM2, but crucially the data would have to pass over the network from TSM2 to TSM1 when it was read and then from TSM1 to TSM2 when it was written. The way it is actually implemented avoids this duplication. TSM uses the fact that the virtual volume is a copy storage pool volume and therefore all the data containted within it will also typically be located on a primary storage pool volume held locally on TSM1. By using this data instead of the data held on the virtual volume, only the writing of the data is performed over the network. So the process has actually been optimised to reduce network utilisation. However, it should be remembered that reclamation of the virtual volume alone is useless without also separately performing reclamtion of the physical volumes on TSM2 in the way that you describe. Going slightly off-topic, it is debatable whether using the primary storage pool volumes as source for the reclamation is optimal in most real-world scenarios. Since the primary storage pool (physical) volumes will typically be co-located and the copy storage pool (virtual) volumes typically won't be, the 50% reduction in network utilisation is more than negated by the increased number of physical tape mounts required. That is to say the mount of a virtual volume as source typically requires only one physical tape mount on the destination server, whereas to mount the physical volumes required from the primary storage pool requires as many tape mounts as there are nodes whose data is contained in the virtual volume (assuming co-location at the node level). Having said that, if there are a large number of virtual volumes to be reclaimed, TSM will optimise the tape mounts from the primary storage pool to ensure each physical volume is only mounted once. With all that said, I've spent five years struggling to get my head round TSM server-to-server comms and now we're just about to rip it out in favour of SAN-based off-siting of data with library-sharing based on Gresham EDT and ACSLS! Neil Schofield Yorkshire Water Services Ltd. Visit our web site to find out about our award winning Cool Schools community campaign at http://www.yorkshirewater.com/yorkshirewater/schools.html The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
space reclamation on a server storage pool?
We have 2 systems. TSM1 and TSM2. TSM2 is used solely as an offsite system to backup our primary tape storage pool on TSM1. When I run reclamation on the server storage pool on TSM1, the process requests a mount on TSM2 and a mount on TSM1. It appears to be copying data from the mount on TSM1 to TSM2. Why wouldn't reclamation mount 2 tapes on TSM2 and copy the data that way instead of through the network which is going to be much slower. Essentially it seems like it is going to copy the exact same data from TSM1 to TSM2 two times because it gets copied once during the BACKUP STG command, and then again during the space reclamation of the server storage pool. This seems like a great waste of time when the exact same data should already be on the TSM2 system and could be moved directly from 1 tape to another where it would be considerably faster. Does this make sense? Why would it be done this way? John
Re: Space reclamation
From: Chandrasekhar, C.R [mailto:[EMAIL PROTECTED] For auto reclamation you must have minimum two tape drives in your library. This is only partially correct. You can set up automated reclamation for one-drive libraries, but only for primary tape pools; see the relevant admin's guide for details on single-drive reclamation schemes. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Space reclamation
Questions: (j) Can I use reclaimation when I have got only i1 tape drive and the reclamation pool is to another sequential stgpool? We can do manual reclamation using file device class(sequential), ref Admin guide for instructions. (ii) what is the meaning of insufficient mount points in the message. For info, my client nodes are defined with a max no of 2 mount points. For auto reclamation you must have minimum two tape drives in your library. (iii) Why TSM is not loading the required volume when the tape is alaready in the library? Library does not have two drives to load source and target tapes for auto reclamation. CRC, C.R.Chandrasekhar. Systems Executive. Tivoli Certified Consultant (TSM). TIMKEN Engineering Research - INDIA (P) Ltd., Bangalore. Phone No: 91-80-5536113 Ext:3032. Email:[EMAIL PROTECTED] -Original Message- From: RAMNAWAZ NAVEEN [mailto:[EMAIL PROTECTED] Sent: Monday, July 21, 2003 6:12 PM To: [EMAIL PROTECTED] Subject: Space reclamation Hi, I am quite new to TSM and trying to configure some setups by myself currebntly facing some problems. My setup is as follows: I run a daily backup for around 200 GB on LTO tapes. I permanently have 3 tapes in a 3590 library defined to a stgpool (UATPOOL). I want to keep the last 3 copies. So I am using the expiry features and want to use reclamation to recover the recalimable space so that my automated backups goes continuosly on these 3 volumes. My problem is that I am geeting the following messages : ANR1040I Space reclamation started for volume UATHOT01, storage pool UAT_POOL (process number 39). ANR1044I Removable volume UATHOT01 is required for space reclamation. ANR0985I Process 39 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 16:13:35. ANR1082W Space reclamation terminated for volume UATHOT01 - insufficient number of mount points available for removable media. ANR1042I Space reclamation for storage pool UAT_POOL will be retried in 60 seconds. ANR1043I Space reclamation retry delay ended; checking volume reclamation status for storage pool UAT_POOL. Questions: (j) Can i use reclaimation when i have got only i1 tape drive and the reclamation pool is to another sequential stgpool? (ii) what is the meaning of insufficient mount points in the message. For info, my client nodes are defined with a max no of 2 mount points. (iii) Why TSM is not loading teh required volume when the tape is alaready in the library? All assistance will be much appreciated Thansk regards ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/
Space reclamation
Hi, I am quite new to TSM and trying to configure some setups by myself currebntly facing some problems. My setup is as follows: I run a daily backup for around 200 GB on LTO tapes. I permanently have 3 tapes in a 3590 library defined to a stgpool (UATPOOL). I want to keep the last 3 copies. So I am using the expiry features and want to use reclamation to recover the recalimable space so that my automated backups goes continuosly on these 3 volumes. My problem is that I am geeting the following messages : ANR1040I Space reclamation started for volume UATHOT01, storage pool UAT_POOL (process number 39). ANR1044I Removable volume UATHOT01 is required for space reclamation. ANR0985I Process 39 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 16:13:35. ANR1082W Space reclamation terminated for volume UATHOT01 - insufficient number of mount points available for removable media. ANR1042I Space reclamation for storage pool UAT_POOL will be retried in 60 seconds. ANR1043I Space reclamation retry delay ended; checking volume reclamation status for storage pool UAT_POOL. Questions: (j) Can i use reclaimation when i have got only i1 tape drive and the reclamation pool is to another sequential stgpool? (ii) what is the meaning of insufficient mount points in the message. For info, my client nodes are defined with a max no of 2 mount points. (iii) Why TSM is not loading teh required volume when the tape is alaready in the library? All assistance will be much appreciated Thansk regards ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/
Space Reclamation problem
Hello all, I have a problem with reclaiming two tapes. This is the message I get on the server console: ANR0984I Process 2134 for SPACE RECLAMATION started in the BACKGROUND at 11:28:00. ANR1040I Space reclamation started for volume 000975, storage pool NTWTAPE (process number 2134). ANR1044I Removable volume 000975 is required for space reclamation. ANR1171W Unable to move files associated with node WKS00102, filespace \\wks00102\c$ fsId 1 on volume 000975 due to restore in progress. ANR0985I Process 2134 for SPACE RECLAMATION running in the BACKGRUND completed with completion state FAILURE at 11:28:00. ANR1089W Space reclamation terminated for volume 000975 - lock conflict. I checked current sessions and there are no restores in progress. The server is at 5.1.6.4. Any help would be appreciated Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Re: Space Reclamation problem
Do a query restore and see if any restartable restores are there. If so and they aren't being used then use cancel restore x where x is the session number - note should shoule include the - in front of the session number. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/09/03 11:39AM Hello all, I have a problem with reclaiming two tapes. This is the message I get on the server console: ANR0984I Process 2134 for SPACE RECLAMATION started in the BACKGROUND at 11:28:00. ANR1040I Space reclamation started for volume 000975, storage pool NTWTAPE (process number 2134). ANR1044I Removable volume 000975 is required for space reclamation. ANR1171W Unable to move files associated with node WKS00102, filespace \\wks00102\c$ fsId 1 on volume 000975 due to restore in progress. ANR0985I Process 2134 for SPACE RECLAMATION running in the BACKGRUND completed with completion state FAILURE at 11:28:00. ANR1089W Space reclamation terminated for volume 000975 - lock conflict. I checked current sessions and there are no restores in progress. The server is at 5.1.6.4. Any help would be appreciated Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: Space Reclamation problem
Hi, I think there is a restartable restore session on your tsm server that has created a lock file for that particular tape. so use the command query restore to find any restartable restore session is available on your tsm server and cancel the session using cancel restore command. Hope this should solve your problem regards N.Suresh -Original Message- From: Remeta, Mark [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 5:40 PM To: [EMAIL PROTECTED] Subject: Space Reclamation problem Hello all, I have a problem with reclaiming two tapes. This is the message I get on the server console: ANR0984I Process 2134 for SPACE RECLAMATION started in the BACKGROUND at 11:28:00. ANR1040I Space reclamation started for volume 000975, storage pool NTWTAPE (process number 2134). ANR1044I Removable volume 000975 is required for space reclamation. ANR1171W Unable to move files associated with node WKS00102, filespace \\wks00102\c$ fsId 1 on volume 000975 due to restore in progress. ANR0985I Process 2134 for SPACE RECLAMATION running in the BACKGRUND completed with completion state FAILURE at 11:28:00. ANR1089W Space reclamation terminated for volume 000975 - lock conflict. I checked current sessions and there are no restores in progress. The server is at 5.1.6.4. Any help would be appreciated Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Re: Space Reclamation problem
Bingo! Thank you very much!!! Mark -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 11:44 AM To: [EMAIL PROTECTED] Subject: Re: Space Reclamation problem Do a query restore and see if any restartable restores are there. If so and they aren't being used then use cancel restore x where x is the session number - note should shoule include the - in front of the session number. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/09/03 11:39AM Hello all, I have a problem with reclaiming two tapes. This is the message I get on the server console: ANR0984I Process 2134 for SPACE RECLAMATION started in the BACKGROUND at 11:28:00. ANR1040I Space reclamation started for volume 000975, storage pool NTWTAPE (process number 2134). ANR1044I Removable volume 000975 is required for space reclamation. ANR1171W Unable to move files associated with node WKS00102, filespace \\wks00102\c$ fsId 1 on volume 000975 due to restore in progress. ANR0985I Process 2134 for SPACE RECLAMATION running in the BACKGRUND completed with completion state FAILURE at 11:28:00. ANR1089W Space reclamation terminated for volume 000975 - lock conflict. I checked current sessions and there are no restores in progress. The server is at 5.1.6.4. Any help would be appreciated Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ## Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Space Reclamation problem
It sounds like a client has a halted restore. You'll have to check the client for restartable restores. Figuring out which client can be tricky if you have a lot of them. You may want look at the contents of the problem tapes to find out which machines have files on them: Q CONT ## where ## is the tape number. To see if a machine has a restartable restore, from the client command line on a machine do: Q REST - Forwarded by Bradley Wallace/TheGuardian on 07/09/2003 12:00 PM - Remeta, Mark [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Dist Stor Subject: Space Reclamation problem Manager [EMAIL PROTECTED] 07/09/2003 11:39 AM Please respond to ADSM: Dist Stor Manager Hello all, I have a problem with reclaiming two tapes. This is the message I get on the server console: ANR0984I Process 2134 for SPACE RECLAMATION started in the BACKGROUND at 11:28:00. ANR1040I Space reclamation started for volume 000975, storage pool NTWTAPE (process number 2134). ANR1044I Removable volume 000975 is required for space reclamation. ANR1171W Unable to move files associated with node WKS00102, filespace \\wks00102\c$ fsId 1 on volume 000975 due to restore in progress. ANR0985I Process 2134 for SPACE RECLAMATION running in the BACKGRUND completed with completion state FAILURE at 11:28:00. ANR1089W Space reclamation terminated for volume 000975 - lock conflict. I checked current sessions and there are no restores in progress. The server is at 5.1.6.4. Any help would be appreciated Mark Remeta Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately.
Re: Newbie question about Space Reclamation
You did not provided version and OS of the server. Can you provide also some information about your library - vendor, model, number of drives, types of drives (it is possible the library is brand new with LTO2 or upgraded with mixed LTO/DLT). Output of some commands may show the situation in detail: - q dri - q path - q v 476afxl1 f=d - q v 505afxl1 f=d - q stg backup_stg_pool f=d - q stg the pool 476afxl1 belongs to f=d - q dev ltoclass1 f=d Plus any obvious error messages in the actlog. Is there any reason for those 564 unreadable files? Zlatko Krastev IT Consultant Stephen Comiskey [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 19.02.2003 18:18 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Newbie question about Space Reclamation Hi, I'm only new to TSM and on a bit of a steep learning curve. We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... q proc Process Description Status - Space ReclamationOffsite Volume(s) (storage pool BACKUP_COPY_POOL), Moved Files: 0, Moved Bytes: 0, Unreadable Files: 564, Unreadable Bytes: 10,214,383. Current Physical File (bytes): 180,031,126 Waiting for mount of input volume 476AFXL1 (821 seconds). Current output volume: 505AFXL1. q mount ANR8379I Mount point in device class LTOCLASS1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8330I LTO volume 505AFXL1 is mounted R/W in drive LTO_DRIVE1 (\\. \TAPE0), status: IN USE. ANR8334I 2 matches found. I know I'm missing something real simple here, I've search a number of forums (including this lists archives) but I may be entering the wrong search parameters Any assistance you can provide is much appreciated. cheers Stephen
Newbie question about Space Reclamation
Hi, I'm only new to TSM and on a bit of a steep learning curve. We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... q proc Process Description Status - Space ReclamationOffsite Volume(s) (storage pool BACKUP_COPY_POOL), Moved Files: 0, Moved Bytes: 0, Unreadable Files: 564, Unreadable Bytes: 10,214,383. Current Physical File (bytes): 180,031,126 Waiting for mount of input volume 476AFXL1 (821 seconds). Current output volume: 505AFXL1. q mount ANR8379I Mount point in device class LTOCLASS1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8330I LTO volume 505AFXL1 is mounted R/W in drive LTO_DRIVE1 (\\. \TAPE0), status: IN USE. ANR8334I 2 matches found. I know I'm missing something real simple here, I've search a number of forums (including this lists archives) but I may be entering the wrong search parameters Any assistance you can provide is much appreciated. cheers Stephen
Re: Newbie question about Space Reclamation
With the infor you've included, I would sya you should do a q request. It is probably requesting a volume that is out of the library. I would sya a restore could be using that volume, but that would show up in q mount. Other possibility is there is a problem with that atpe and it won't mount. In that case do a q actlog and see if any errors about this tape. David Longo [EMAIL PROTECTED] 02/19/03 11:18AM Hi, I'm only new to TSM and on a bit of a steep learning curve. We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... q proc Process Description Status - Space ReclamationOffsite Volume(s) (storage pool BACKUP_COPY_POOL), Moved Files: 0, Moved Bytes: 0, Unreadable Files: 564, Unreadable Bytes: 10,214,383. Current Physical File (bytes): 180,031,126 Waiting for mount of input volume 476AFXL1 (821 seconds). Current output volume: 505AFXL1. q mount ANR8379I Mount point in device class LTOCLASS1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8330I LTO volume 505AFXL1 is mounted R/W in drive LTO_DRIVE1 (\\. \TAPE0), status: IN USE. ANR8334I 2 matches found. I know I'm missing something real simple here, I've search a number of forums (including this lists archives) but I may be entering the wrong search parameters Any assistance you can provide is much appreciated. cheers Stephen MMS health-first.org made the following annotations on 02/19/2003 11:46:32 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: Newbie question about Space Reclamation
Dwight, Thanks for the pointers... I did a q vol 476afxl1 f=d and access=Read/Write, the tape is in the library and there are no requests outstanding and Mount Limit = Drives :-( My head is starting to hurt !! Stephen |-+--- | | Cook, Dwight E| | | DWIGHT.E.COOK@s| | | aic.com| | | | | | 19/02/03 16:47 | | | | |-+--- ---| | | |To: Stephen Comiskey/Dublin/IE/RoyalSun@RoyalSunInt | |cc: | |Subject: RE: Newbie question about Space Reclamation | ---| THIS MESSAGE ORIGINATED ON THE INTERNET - Please read the detailed disclaimer below. --- check : availability of the tape 476AFXL1 (q vol 476AFXL1 f=d) make sure it is available ie. acc=readwrite availability of the tape within the atl (q libvol * 476AFXL1) make sure it is checked in... try a query request because if a tape needs to be checked into a library a request will be issued availability of your drives (q drive) make sure they are all on-line and OK... mount limit associated with the device class used by these tapes (q dev blah f=d) look for Mount Limit: DRIVES OK, drives states limit is equal to available drives could have a hard number... try those things first... Dwight -Original Message- From: Stephen Comiskey [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 10:19 AM To: [EMAIL PROTECTED] Subject: Newbie question about Space Reclamation Hi, I'm only new to TSM and on a bit of a steep learning curve. We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... q proc Process Description Status - Space ReclamationOffsite Volume(s) (storage pool BACKUP_COPY_POOL), Moved Files: 0, Moved Bytes: 0, Unreadable Files: 564, Unreadable Bytes: 10,214,383. Current Physical File (bytes): 180,031,126 Waiting for mount of input volume 476AFXL1 (821 seconds). Current output volume: 505AFXL1. q mount ANR8379I Mount point in device class LTOCLASS1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8330I LTO volume 505AFXL1 is mounted R/W in drive LTO_DRIVE1 (\\. \TAPE0), status: IN USE. ANR8334I 2 matches found. I know I'm missing something real simple here, I've search a number of forums (including this lists archives) but I may be entering the wrong search parameters Any assistance you can provide is much appreciated. cheers Stephen --- The following message has been automatically added by the mail gateway to comply with a Royal SunAlliance IT Security requirement. As this email arrived via the Internet you should be cautious about its origin and content. Replies which contain sensitive information or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please speak to your local desktop support team or IT security contact. ---
Re: Newbie question about Space Reclamation
In looking at the output of the q mount I see the ~waiting~ and remembered... often if a tape encounters errors upon being mounted, recovery work will be performed on the tape automatically (triggered by the drive) and it will show ~waiting on mount~ until the drive gets through with it (or at least with 3590's I've seen this) It might be that the tape is actually in a drive but hasn't ~officially~ been mounted yet. I don't know if LTO tapes have all the VCR information on them like a 3590 does but if so, you might be seeing this mount pause while the system attempts to fix problems that the drive has discovered... Dwight -Original Message- From: Stephen Comiskey [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 11:13 AM To: [EMAIL PROTECTED] Subject: Re: Newbie question about Space Reclamation Dwight, Thanks for the pointers... I did a q vol 476afxl1 f=d and access=Read/Write, the tape is in the library and there are no requests outstanding and Mount Limit = Drives :-( My head is starting to hurt !! Stephen |-+--- | | Cook, Dwight E| | | DWIGHT.E.COOK@s| | | aic.com| | | | | | 19/02/03 16:47 | | | | |-+--- --- | | | |To: Stephen Comiskey/Dublin/IE/RoyalSun@RoyalSunInt | |cc: | |Subject: RE: Newbie question about Space Reclamation | --- | THIS MESSAGE ORIGINATED ON THE INTERNET - Please read the detailed disclaimer below. --- check : availability of the tape 476AFXL1 (q vol 476AFXL1 f=d) make sure it is available ie. acc=readwrite availability of the tape within the atl (q libvol * 476AFXL1) make sure it is checked in... try a query request because if a tape needs to be checked into a library a request will be issued availability of your drives (q drive) make sure they are all on-line and OK... mount limit associated with the device class used by these tapes (q dev blah f=d) look for Mount Limit: DRIVES OK, drives states limit is equal to available drives could have a hard number... try those things first... Dwight -Original Message- From: Stephen Comiskey [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 10:19 AM To: [EMAIL PROTECTED] Subject: Newbie question about Space Reclamation Hi, I'm only new to TSM and on a bit of a steep learning curve. We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... q proc Process Description Status - Space ReclamationOffsite Volume(s) (storage pool BACKUP_COPY_POOL), Moved Files: 0, Moved Bytes: 0, Unreadable Files: 564, Unreadable Bytes: 10,214,383. Current Physical File (bytes): 180,031,126 Waiting for mount of input volume 476AFXL1 (821 seconds). Current output volume: 505AFXL1. q mount ANR8379I Mount point in device class LTOCLASS1 is waiting for the volume mount to complete, status: WAITING FOR VOLUME. ANR8330I LTO volume 505AFXL1 is mounted R/W in drive LTO_DRIVE1 (\\. \TAPE0), status: IN USE. ANR8334I 2 matches found. I know I'm missing something real simple here, I've search a number of forums (including this lists archives) but I may be entering the wrong search parameters Any assistance you can provide is much appreciated. cheers Stephen --- The following message has been automatically added by the mail gateway to comply with a Royal SunAlliance IT Security requirement. As this email arrived via the Internet you should be cautious about its origin and content. Replies which contain sensitive information or legal/contractual obligations are particularly vulnerable. In these cases you should not reply unless you are authorised to do so, and adequate encryption is employed. If you have any questions, please speak to your local desktop support team or IT security contact. ---
Re: Newbie question about Space Reclamation
I did a q vol 476afxl1 f=d and access=Read/Write, the tape is in the library and there are no requests outstanding and Mount Limit = Drives :-( I'm chuckling a bit to myself, thinking of the old joke of how you discern a software person: That person will indefinitely look at command display indications in pondering the condition of a device. There are times when you need to just go look at the darned drive and see what its panel says about its condition. Never overlook the obvious: I can't tell you how many times in my career I've seen quite intelligent people obsess over erudite factors because they could be more intriguing than reality. Time is a limited resource. Start by looking in the areas which will most likely yield the most immediate results, and dig into laborious detail only as it becomes necessary. Richard Sims, BU
Re: Newbie question about Space Reclamation
From: Stephen Comiskey [mailto:[EMAIL PROTECTED]] We have a scheduled job each Friday to reclaim our copy pool tapes (update stg backup_copy_pool reclaim=75), the process starts and the output volume is mounted OK however the server wait for the input (60K+ seconds). I've pasted some output from the console below... Please refer to the answer to question 04-17, posted in the TSM monthly FAQ, posted around the first of each month. Look for it in http://search.adsm.org. -- Mark Stapleton ([EMAIL PROTECTED])
space reclamation errors (fwd)
in case someone has the same problem: the problem i had was with maximun scratch volumes setting for my storage pool. it was set to a number smaller than the actual number of scratch tapes, for some odd reason. i bumped number up to the actual number of scratch tapes in the library, and bam!, migrations are cranking away. alex ------ Alex Lazarevich | Systems | Imaging Technology Group [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu ------ -- Forwarded message -- Date: Thu, 6 Feb 2003 09:35:40 -0600 (CST) From: Alexander Lazarevich [EMAIL PROTECTED] To: ADSM Mailing List [EMAIL PROTECTED] Subject: space reclamation errors I've got a big problem, I'm hoping someone can help me out. We are using ADSM server v 3.1, on an AIX 4.3.3 machine. We are planning to upgrade very soon, so please don;t comment about that. We also have an IBM 3575 L18 tape library (180 tapes, 2 drives), which we are also upgrading soon. Our current library is very full, and I changed a few policies a few days ago and now the server is stuck in a loop, unable to reclaim any space in the tape library. I'll try to outline what's happened: 1) We have a few different policies, and I changed them by first changing the standard policy set, and then activated that new standard policy set. The policy change was going to delete a lot of backup items, which it did during the next automatic expiration. 2) I also had improperly set the destination storage pool for the policies to ITG-DISK, which is our storage pool disks. Realizing my mistake this morning, I just changed the destination storage pool to ITG-TAPE, which is the correct setting. ITG-TAPE is our 3575 tape library. That is the correct destination. 3) But as of right now, I'm getting errors when I try to do the following: 3.1) Delete a filespace: ANR0984I Process 501 for DELETE FILESPACE started in the BACKGROUND at 09:32:42. ANR0800I DELETE FILESPACE: \\zworykin\c$ for node ZWORYKIN.ITG.UIUC.EDU started as process 501. ANR0802I Delete Filespace \\zworykin\c$ (backup/archive data) for node ZWORYKIN.ITG.UIUC.EDU started. ANR0859E Data storage object erasure failure, DELETE FILESPACE process aborted. ANR0985I Process 501 for DELETE FILESPACE running in the BACKGROUND completed with completion state FAILURE at 09:32:47. The Messages book doesn't say mcuh about what is wrong, other than to look at the logs, which I am, and it doesn;t say why I can't delete a filespace. 3.2) Migrate data from one tape (which happens to have 98% reclaimable space on it) back into the storage pool ITG-TAPE: ANR0984I Process 497 for SPACE RECLAMATION started in the BACKGROUND at 09:20:46. ANR1040I Space reclamation started for volume 2C738D, storage pool ITG-3575TAPE (process number 497). ANR1044I Removable volume 2C738D is required for space reclamation. ANR8324I 3570 volume 2C738D is expected to be mounted (R/O). ANR1142I Moving data for collocation cluster 1 of 1 on volume 2C738D. ANR8337I 3570 volume 26DE0C mounted in drive TAPEDRIVE2 (/dev/rmt0). ANR8468I 3570 volume 2C64BC dismounted from drive TAPEDRIVE1 (/dev/rmt1) in library ITG-3575. ANR2017I Administrator ALAZAREV issued command: QUERY PROCESS ANR8337I 3570 volume 2C738D mounted in drive TAPEDRIVE1 (/dev/rmt1). ANR2017I Administrator ALAZAREV issued command: QUERY PROCESS ANR8341I End-of-volume reached for 3570 volume 26DE0C. ANR0985I Process 497 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at 09:21:48. ANR1086W Space reclamation terminated for volume 2C738D - insufficient space in storage pool. ANR1042I Space reclamation for storage pool ITG-3575TAPE will be retried in 60 seconds. ANR8336I Verifying label of 3570 volume 26DE0C in drive TAPEDRIVE2 (/dev/rmt0). ANR8468I 3570 volume 26DE0C dismounted from drive TAPEDRIVE2 (/dev/rmt0) in library ITG-3575. ANR1043I Space reclamation retry delay ended; checking volume reclamation status for storage pool ITG-3575TAPE. Doesn anyone have any idea what's going on here? I'm kinda stuck. Any ideas would be appreciated. Thanks! Alex ------ Alex Lazarevich | Systems | Imaging Technology Group [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu ------
Re: Space reclamation of offsite copy pool takes forever
Are you running with colocation enabled anywhere? For best reclaim performance, I have found that having colocation enabled=yes on both onsite and offsite pools works the best. Why? Reduction of tape mounts. Cost? Need more tapes, especially in offsite pool. Per pool: Keep in mind that onsite reclamation is 1 process PER tape: find a tape needing reclaim-mount tape-relocate data-dismount. Offsite reclamation is 1 process for ALL tapes: find all tapes needing reclaim-select tape x(these appear to be done in age order)-figure out where all local copies of data are stored-until x is finished(mount onsite tape-relocate data-dismount onsite-next local tape)-next tape x (offiste tape) So it's concievable and likely that one onsite tape could be mounted several times because some of it's files are on multiple offsite tapes. Al Brazner, Bob [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 11/11/02 05:44 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Space reclamation of offsite copy pool takes forever Reclamation of our offsite copy pool is taking forever. Right now, we have 200+ volumes in that pool. Normally, threshold is set at 60% and I get maybe 8 or 9 volumes returned after processing for 7 hours (on beefy AIX, with TSM at 5.1.5). Lately I've tried setting the threshold at 99, then 98, then 97, etc., but I don't see much improvement in overall freeing up of tapes. It appears that most of the time is taken up with mounting input volumes. Even though we have a 3494, I'd say 80% of the time is spent waiting for tape mounts. Is there any way to get space reclamation to free up offsite tapes faster? Note, for my onsite tape pool, I do not see this problem (e.g., I can easily free up 30 tapes in 5 hours or less). Bob Brazner Johnson Controls, Inc. (414) 524-2570
Space reclamation of offsite copy pool takes forever
Reclamation of our offsite copy pool is taking forever. Right now, we have 200+ volumes in that pool. Normally, threshold is set at 60% and I get maybe 8 or 9 volumes returned after processing for 7 hours (on beefy AIX, with TSM at 5.1.5). Lately I've tried setting the threshold at 99, then 98, then 97, etc., but I don't see much improvement in overall freeing up of tapes. It appears that most of the time is taken up with mounting input volumes. Even though we have a 3494, I'd say 80% of the time is spent waiting for tape mounts. Is there any way to get space reclamation to free up offsite tapes faster? Note, for my onsite tape pool, I do not see this problem (e.g., I can easily free up 30 tapes in 5 hours or less). Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Space reclamation of offsite copy pool takes forever
Hello, Have you first tried to see what current reclaimable spaces are available for offsite volumes. Here's a select command which will list all the offsite volumes in the order of pct_reclaimable. Command: select volume_name, stgpool_name, access, pct_reclaim from volumes where stgpool_name='OFF3494' order by pct_reclaim desc Modify the stgpool name for your server It is possible that you don't have any offsite volumes reach are reclaimable at your reclaimable threshold and yes reclaimable process can take a very long time. Sometimes, I was lucky to get even 3 tapes back running thru the night. Also make sure expiration is running. Sung Y. Lee E-mail [EMAIL PROTECTED] Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation of offsite copy pool takes forever Dist Stor Manager [EMAIL PROTECTED] .EDU 11/11/2002 05:44 PM Please respond to ADSM: Dist Stor Manager Reclamation of our offsite copy pool is taking forever. Right now, we have 200+ volumes in that pool. Normally, threshold is set at 60% and I get maybe 8 or 9 volumes returned after processing for 7 hours (on beefy AIX, with TSM at 5.1.5). Lately I've tried setting the threshold at 99, then 98, then 97, etc., but I don't see much improvement in overall freeing up of tapes. It appears that most of the time is taken up with mounting input volumes. Even though we have a 3494, I'd say 80% of the time is spent waiting for tape mounts. Is there any way to get space reclamation to free up offsite tapes faster? Note, for my onsite tape pool, I do not see this problem (e.g., I can easily free up 30 tapes in 5 hours or less). Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Space reclamation of offsite copy pool takes forever
This is why I do not use the reclaimation process. I have written a process that does MOVE DATA vv reconstruct=yes commands for the volumes that have less than a reclamation number. I set the reclamation in the storage pool to 100 so they will not reclaim. Then I can run as many simultaneously as my drives can handle, usually 5 to 6. Yes, from the same storage pool. We actually do this because we use closed box and the tapes may return before they are empty, so 14 days before there return I move the data to new volumes going offsite. I also have a second threshold. If the tape has been offsite more than say 14 days and is less than say 10% utilized I reclaim them as well. There are many beauties to this process and only a couple negatives. You get your tapes refreshed at the offsite no matter what. You can use closed box. Keeps the tapes full at whatever level you want. Allows you to have a built in scratch pool for disaster recovery. Keeps collocated volumes down to a minimum (fewer mounts). On the negative side, it requires tape drives. The process is home grown using TSM selects and AIX KSH scripts. We use separate pools for database and exchange backups or similar type data. Those backups do not have to be recycled before return because there are always full copies of these offsite. Maybe ITSM development will take a look at doing something like this in the future. This is the case for smaller storage pools and more of them. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Brazner, Bob [mailto:Bob.Brazner;JCI.COM] Sent: Monday, November 11, 2002 6:44 PM To: [EMAIL PROTECTED] Subject: Space reclamation of offsite copy pool takes forever Reclamation of our offsite copy pool is taking forever. Right now, we have 200+ volumes in that pool. Normally, threshold is set at 60% and I get maybe 8 or 9 volumes returned after processing for 7 hours (on beefy AIX, with TSM at 5.1.5). Lately I've tried setting the threshold at 99, then 98, then 97, etc., but I don't see much improvement in overall freeing up of tapes. It appears that most of the time is taken up with mounting input volumes. Even though we have a 3494, I'd say 80% of the time is spent waiting for tape mounts. Is there any way to get space reclamation to free up offsite tapes faster? Note, for my onsite tape pool, I do not see this problem (e.g., I can easily free up 30 tapes in 5 hours or less). Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Space reclamation of offsite copy pool takes forever
Bob, IMHO, you are working too hard. 66% reclaim level will reclaim 3 tapes to get 2 scratches, so must write 1 full tape's worth of data. 80% will reclaim 5 tapes to get 4 scratches, so must write 1 full tape... 90% will reclaim 10 tapes to get 9 scratches, so must write 1 full tape ... So, number1 recommendation from me would be to buy some more tapes and increase your reclaim level. Now the reclaim process will process lots of individual tapes to build that 1 output tape,as you have noted. Thus run it as infrequently as possible to get the maximum value from each pass. I'd suggest kicking it off over the weekend and just letting it go till Monday morning - depending on your load of course. Cancel it then if it hasn't finished. After all, the easiest way to reclaim data is to just let it expire. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia. [EMAIL PROTECTED] 12/11/2002 9:44:27 Reclamation of our offsite copy pool is taking forever. Right now, we have 200+ volumes in that pool. Normally, threshold is set at 60% and I get maybe 8 or 9 volumes returned after processing for 7 hours (on beefy AIX, with TSM at 5.1.5). Lately I've tried setting the threshold at 99, then 98, then 97, etc., but I don't see much improvement in overall freeing up of tapes. It appears that most of the time is taken up with mounting input volumes. Even though we have a 3494, I'd say 80% of the time is spent waiting for tape mounts. Is there any way to get space reclamation to free up offsite tapes faster? Note, for my onsite tape pool, I do not see this problem (e.g., I can easily free up 30 tapes in 5 hours or less). Bob Brazner Johnson Controls, Inc. (414) 524-2570 ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Space Reclamation Failing
Hi All, Running TSM V5.1.0 on Windows 2000 server SP2. Started running Space Reclamation process on the Tape Volumes. The process runs for a while moves some data and then just stops. Tried to cancel process, it remains pending but doesn't stop. What could be possibly wrong ?? Any help is greatly appreciated. Thanks, Prasanna Ghanekar EDS Get 250 full-color business cards FREE right now! http://businesscards.lycos.com
How many tapes reclaimed by space reclamation?
Hello all, Does anyone have a script/SQL command to figure out how many tapes are below the reclamation threshold? I'm sure there has to be something easy, but every command I've tried hasn't worked. Thanks, Rob Hefty IS Operations Lab Safety Supply
Re: How many tapes reclaimed by space reclamation?
Hello Rob, Here are two scripts I use. If you use these scripts, be sure you do not put spaces in pct_reclaim=67. If you put a space by the character, it gets translated into a file re-direct statement if you run the script on a DOS/Windows box command line admin. Al Name Line Command Number -- -- RECLAIMCO- 10 select count(volume_name) as vaults from volumes where UNT pct_reclaim=67 and stgpool_name='COPYVAULT' 20 select count(volume_name) as carts from volumes where pct_reclaim=67 and stgpool_name='TAPEPOOL' 30 select count(volume_name) as copydirs from volumes where pct_reclaim=67 and stgpool_name='COPY_DIRECTORIES' Name Line Command Number -- -- SHOW_RECL- 10 select volume_name,stgpool_name,pct_reclaim from volumes AIM where pct_reclaim=67 order by stgpool_name,pct_reclaim desc Alan Davenport Senior Storage Administrator Selective Insurance [EMAIL PROTECTED] (973) 948-1306 -Original Message- From: Rob Hefty [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 09, 2002 8:04 AM To: [EMAIL PROTECTED] Subject: How many tapes reclaimed by space reclamation? Hello all, Does anyone have a script/SQL command to figure out how many tapes are below the reclamation threshold? I'm sure there has to be something easy, but every command I've tried hasn't worked. Thanks, Rob Hefty IS Operations Lab Safety Supply
Re: Expected throughput rate for space reclamation
As Paul says, this will depend as much on your data as on your hardware. Using 3590E tape drives, yesterday we got rates of 1.6MB/s to 55.4MB/s as reported by Servergraph/TSM on our 5 tape to tape storage pool copies; the median was 27.4MB/s. The rates on our 8 tape storage pool reclaims last night ranged from 2.1MB/s to 25.1MB/s with a median of 8.2MB/s. David Ehresman
AW: How many tapes reclaimed by space reclamation?
Hi Rob, I have seen that some people have sent scripts to you. So you don't need my ones. But there is one point I would like to tell you : if your client sends compressed data and the file-information shows the original size there can be a lot of data on a tape if the reclaimable space is 90 %. I saw this often with my Novell-Pool. Then the reclamation runs for these 10 % a long time ( in these cases I look at the PCT UTILIZED too (the sum of PCT UTILIZED and PCT RECLAIMABLE in these cases is always a lot more than 100 % (e.g.130%)). Best wishes Chris -Ursprüngliche Nachricht- Von: Rob Hefty [SMTP:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 9. Oktober 2002 14:04 An: [EMAIL PROTECTED] Betreff: How many tapes reclaimed by space reclamation? Hello all, Does anyone have a script/SQL command to figure out how many tapes are below the reclamation threshold? I'm sure there has to be something easy, but every command I've tried hasn't worked. Thanks, Rob Hefty IS Operations Lab Safety Supply
space reclamation when using server-to-server communication
Hello TSMers, I've got a problem with my space reclamation for virtual volumes. We use two TSM Servers Version 4.2.2.0 (OS Sun Solaris 2.7). They do server-to-server communication. When space reclamation starts for the first reclaimable virtual volume in a storage pool, everything looks fine. Then the second reclaimable virtual volume starts their reclamation process and I allways get an ANRD error. Here is what TSM reports: ANR8340I SERVER volume TBS.BFS.032957914 mounted. ANR8340I SERVER volume TBS.BFS.033992020 mounted. ANR1340I Scratch volume TBS.BFS.033992020 is now defined in storage pool REMOTE_UNIX. ANR0986I Process 360 for SPACE RECLAMATION running in the background processed 34 items for a total of 1.997.933 bytes with a completion state of SUCCESS at 14:05:16. ANR1041I Space reclamation ended for volume TBS.BFS.032957914. ANR0984I Process 361 for SPACE RECLAMATION started in the background at 14:05:16. ANR1040I Space reclamation started for volume TBS.BFS.033704013 storage pool REMOTE_UNIX (process number 361). ANR1044I Removable volume TBS.BFS.033704013 is required for space reclamation. ANR8340I SERVER volume TBS.BFS.033704013 mounted. ANR1341I Scratch volume TBS.BFS.032957914 has been deleted from storage pool REMOTE_UNIX. ANR8213E Session 93 aborted due to send error; error 32. ANRD pvrserv.c(918): ThreadId 43 ServWrite: Error writing SERVER volume TBS.BFS.033992020 rc=30. ANR1411W Access mode for volume TBS.BFS.033992020 now set to read-only due to write error. When I move data from TBS.BFS.033992020, no problems occured. Can anybody explain, what happened at the server? MfG/regards Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Re: space reclamation when using server-to-server communication
Sascha Maybe this helps: APAR= IX78238 ANRD PVRSERV.C(833): SERVWRITE: ERROR WRITING SERVER VOLUME X. RC=30 WHEN COMMTIMEOUT VALUE TIME REQUIRED TO MOUNT TAPE. APAR= IC22660 ANRD PVRSERV.C(833): SERVWRITE: ERROR WRITING SERVER VOLUME X. RC=30 WHEN COMMTIMEOUT VALUE TIME REQUIRED TO MOUNT TAPE. LOCAL FIX: Increase the commtimeout value on the source server. Jeroen -Original Message- From: Sascha Braeuning [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 08, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: space reclamation when using server-to-server communication Hello TSMers, I've got a problem with my space reclamation for virtual volumes. We use two TSM Servers Version 4.2.2.0 (OS Sun Solaris 2.7). They do server-to-server communication. When space reclamation starts for the first reclaimable virtual volume in a storage pool, everything looks fine. Then the second reclaimable virtual volume starts their reclamation process and I allways get an ANRD error. Here is what TSM reports: ANR8340I SERVER volume TBS.BFS.032957914 mounted. ANR8340I SERVER volume TBS.BFS.033992020 mounted. ANR1340I Scratch volume TBS.BFS.033992020 is now defined in storage pool REMOTE_UNIX. ANR0986I Process 360 for SPACE RECLAMATION running in the background processed 34 items for a total of 1.997.933 bytes with a completion state of SUCCESS at 14:05:16. ANR1041I Space reclamation ended for volume TBS.BFS.032957914. ANR0984I Process 361 for SPACE RECLAMATION started in the background at 14:05:16. ANR1040I Space reclamation started for volume TBS.BFS.033704013 storage pool REMOTE_UNIX (process number 361). ANR1044I Removable volume TBS.BFS.033704013 is required for space reclamation. ANR8340I SERVER volume TBS.BFS.033704013 mounted. ANR1341I Scratch volume TBS.BFS.032957914 has been deleted from storage pool REMOTE_UNIX. ANR8213E Session 93 aborted due to send error; error 32. ANRD pvrserv.c(918): ThreadId 43 ServWrite: Error writing SERVER volume TBS.BFS.033992020 rc=30. ANR1411W Access mode for volume TBS.BFS.033992020 now set to read-only due to write error. When I move data from TBS.BFS.033992020, no problems occured. Can anybody explain, what happened at the server? MfG/regards Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Re: space reclamation when using server-to-server communication
Where do your virtual volumes go ??? (straight to tape or first to a buffer diskpool ???) If they go straight to tape there is the possibility that your second virtual volume to be reclaimed ends up being on the physical volume to which your first reclamation process opened its output volume. (thus the output voume gets closed on the remote server because the tape is rewound to find the second input/reclamation volume) What is the mount retention of your device class for your virtual volumes ??? Generally virtual volumes are only used for a unit of work (or until their estimated capacity is reached), since your reclamation processes are actually TWO different processes I would expect TSM to close that output virtual volume at the end of the first process and thus terminate its use. I would not expect the second process to pick that back up and try to use it... and this might be what is going on in that the virtual volume is closed upon completion of the first reclamation and then the second process tries to use it but it is closed... Try this, if your mount retention for your device class for your virtual volumes isn't zero, try setting it to zero. This way upon completion of the first reclamation every one / all routines involved will agree to close out that virtual volume, then when your second reclamation initiates it will call for a new scratch. NOW for the flip side of my twisted thinking... if your mount retention IS currently zero, try setting it up to 1 or 2, IF currently zero it ~might~ be triggering an early close of the volume even though the one environment knows it has additional work to go to it. BUT generally I'd expect the normal flow of things to be: upon completion of the first reclamation task, the output virtual volume to be closed (since that is a completed unit of work) and upon the initiation of the second reclamation task, a new output virtual volume to be opened... Dwight -Original Message- From: Sascha Braeuning [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 08, 2002 2:35 AM To: [EMAIL PROTECTED] Subject: space reclamation when using server-to-server communication Hello TSMers, I've got a problem with my space reclamation for virtual volumes. We use two TSM Servers Version 4.2.2.0 (OS Sun Solaris 2.7). They do server-to-server communication. When space reclamation starts for the first reclaimable virtual volume in a storage pool, everything looks fine. Then the second reclaimable virtual volume starts their reclamation process and I allways get an ANRD error. Here is what TSM reports: ANR8340I SERVER volume TBS.BFS.032957914 mounted. ANR8340I SERVER volume TBS.BFS.033992020 mounted. ANR1340I Scratch volume TBS.BFS.033992020 is now defined in storage pool REMOTE_UNIX. ANR0986I Process 360 for SPACE RECLAMATION running in the background processed 34 items for a total of 1.997.933 bytes with a completion state of SUCCESS at 14:05:16. ANR1041I Space reclamation ended for volume TBS.BFS.032957914. ANR0984I Process 361 for SPACE RECLAMATION started in the background at 14:05:16. ANR1040I Space reclamation started for volume TBS.BFS.033704013 storage pool REMOTE_UNIX (process number 361). ANR1044I Removable volume TBS.BFS.033704013 is required for space reclamation. ANR8340I SERVER volume TBS.BFS.033704013 mounted. ANR1341I Scratch volume TBS.BFS.032957914 has been deleted from storage pool REMOTE_UNIX. ANR8213E Session 93 aborted due to send error; error 32. ANRD pvrserv.c(918): ThreadId 43 ServWrite: Error writing SERVER volume TBS.BFS.033992020 rc=30. ANR1411W Access mode for volume TBS.BFS.033992020 now set to read-only due to write error. When I move data from TBS.BFS.033992020, no problems occured. Can anybody explain, what happened at the server? MfG/regards Sascha Brduning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Expected throughput rate for space reclamation
We are achieving 30GB/hour doing our tape-to-tape storage pool backup and are happy with that rate. With this in mind, what do you feel would be an acceptable rate for tape-to-tape space reclamation? I realize that every hardware configuration is different and different shops have different constrained resources, but I'm hoping some of you have some rules-of-thumb as to how tape stgpool backup typically compares to tape stgpool reclamation. Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Expected throughput rate for space reclamation
It has more to do with the file sizes and numbers of objects in aggregates, etc. Then, hardware comes into play, so drastically, there is no answer to this question. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Brazner, Bob [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 08, 2002 6:34 PM To: [EMAIL PROTECTED] Subject: Expected throughput rate for space reclamation We are achieving 30GB/hour doing our tape-to-tape storage pool backup and are happy with that rate. With this in mind, what do you feel would be an acceptable rate for tape-to-tape space reclamation? I realize that every hardware configuration is different and different shops have different constrained resources, but I'm hoping some of you have some rules-of-thumb as to how tape stgpool backup typically compares to tape stgpool reclamation. Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Space reclamation runs, but tapes don't free up
You can find it documented in the back of the Admin. Reference. I did an audit before upgrading from 4.1.1.5 to 5.1.1.2 and I had to do it again on 5.1.1.6. So if you are going to do an audit, I would recommend waiting until you are on 5.1.1.6 On Wed, 2 Oct 2002, Johnn D. Tan wrote: Paul: What is the exact syntax for auditdb? I've seen you mention it twice now. I'm on 4.1.3 server (migrating to 5.1.1.6 tomorrow!) and don't see this mentioned anywhere. This is part of 4.2 and later? johnn My recommendations is for people to get to 4.2.2.12 or higher for those of us on 4.2 and get the backupgroups cleaned up before attempting a 5.1.1.6 migration. This probably includes running an auditdb before starting the ugprade as well. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Burton, Robert [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 9:30 AM To: [EMAIL PROTECTED] Subject: Re: Space reclamation runs, but tapes don't free up There is a known problem opened with IBM on this... We were told to upgrade to tsm 4.2.2.4 or higher...this seemed to clean up most but not all these problems... If you q content on the tape it is empty, yet if you try to do reclamation or delete it you are informed that there is still data on it We were told we would have to issue an auditdb to clean it up...this would knock our production server off the air for over 27 hrs...so we opted no to do this When we tried to upgrade from tsm 4.2.2.4 to tsm 5.1.0.0 we experienced the following problem: Item PQ64254 APAR Identifier .. PQ64254 Last Changed..02/09/12 ANRD IMINIT.C GROUP.MEMBERS ERROR 8 UPGRADEDB We were informed to upgrade to 5.1.1.4 or higher and run a cleanup backupgroups commandthis also fixed nothing I have an additiona PMR opened with IBM on this problem and am waiting to hear back... thanks Robert Burton Enterprise Storage Network Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 * 416-348-3849 * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 8:53 AM To: [EMAIL PROTECTED] Subject: Re: Space reclamation runs, but tapes don't free up Michael, Why has your tape got a status of filling ? That would be a reason why it would not return to scratch Are all your problem tapes like that? Michael Moore [EMAIL PROTECTED] on 10/02/2002 01:34:26 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Space reclamation runs, but tapes don't free up We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc
Re: Space reclamation runs, but tapes don't free up
We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation runs, but tapes don't free up Dist Stor Manager [EMAIL PROTECTED] .EDU 10/01/02 08:13 PM Please respond to ADSM: Dist Stor Manager System is TSM 4.1.2.0 on AIX 4.3.3. I run reclamation daily on my tape backup copy pool, but the backlog of unreclaimed tapes continues to grow (as determined by SQL select looking for volumes in the pool that meet my reclamation threshold - 60%). The space reclamation process mounts a number of tapes, and a good number of bytes get moved, but the count continues to grow. My onsite tape backup pool does not suffer from this problem. I'm not seeing the number of ANR1341I messages (Scratch volume volume name has been deleted from storage pool storage pool name) that I would expect. Nor, am I seeing the expected number of ANR1342I messages (Scratch volume volume name is now pending - volume will be deleted from storage pool storage pool name after the reuse delay period for this storage pool has elapsed). I should be seeing one or both messages for each offsite volume reclaimed, right? Because my offsite tapes are not getting reclaimed in a timely fashion, I'm faced with a lack of scratch tapes every day. Any ideas anyone? Bob Brazner Johnson Controls, Inc. (414) 524-2570
Re: Space reclamation runs, but tapes don't free up
Michael, Why has your tape got a status of filling ? That would be a reason why it would not return to scratch Are all your problem tapes like that? Michael Moore [EMAIL PROTECTED] on 10/02/2002 01:34:26 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Space reclamation runs, but tapes don't free up We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation runs, but tapes don't free up Dist Stor Manager [EMAIL PROTECTED] .EDU 10/01/02 08:13 PM Please respond to ADSM: Dist Stor Manager System is TSM 4.1.2.0 on AIX 4.3.3. I run reclamation daily on my tape backup copy pool, but the backlog of unreclaimed tapes continues to grow (as determined by SQL select looking for volumes in the pool that meet my reclamation threshold - 60%). The space reclamation process mounts a number of tapes, and a good number of bytes get moved, but the count continues to grow. My onsite tape backup pool does not suffer from this problem. I'm not seeing the number of ANR1341I messages (Scratch volume volume name has been deleted from storage pool storage pool name) that I would expect. Nor, am I seeing the expected number of ANR1342I messages (Scratch volume volume name is now pending - volume will be deleted from storage pool storage pool name after the reuse delay period for this storage pool has elapsed). I should be seeing one or both messages for each offsite volume reclaimed, right? Because my offsite tapes are not getting reclaimed in a timely fashion, I'm faced with a lack of scratch tapes every day. Any ideas anyone? Bob Brazner Johnson Controls, Inc. (414) 524-2570 ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Space reclamation runs, but tapes don't free up
Yes.. I now have approximately 200 tapes in this status, and so far the only fix is to audit each volume. IBM/Tivoli is looking into how they are getting in this state. I am waiting on some trace parms from them. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 John Naylor john.naylor@SCOTTISH-SOUTTo: [EMAIL PROTECTED] HERN.CO.UK cc: Sent by: ADSM: Dist Stor Subject: Re: Space reclamation runs, but tapes don't free up Manager [EMAIL PROTECTED] 10/02/02 08:53 AM Please respond to ADSM: Dist Stor Manager Michael, Why has your tape got a status of filling ? That would be a reason why it would not return to scratch Are all your problem tapes like that? Michael Moore [EMAIL PROTECTED] on 10/02/2002 01:34:26 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Space reclamation runs, but tapes don't free up We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation runs, but tapes don't free up Dist Stor Manager [EMAIL PROTECTED] .EDU 10/01/02 08:13 PM Please respond to ADSM: Dist Stor Manager System is TSM 4.1.2.0 on AIX 4.3.3. I run reclamation daily on my tape backup copy pool, but the backlog of unreclaimed tapes continues to grow (as determined by SQL select looking for volumes in the pool that meet my reclamation threshold - 60%). The space reclamation process mounts a number of tapes, and a good number of bytes get moved, but the count continues to grow. My onsite tape backup pool does not suffer from this problem. I'm not seeing the number of ANR1341I messages (Scratch volume volume name has been deleted from storage pool storage pool name) that I would expect. Nor, am I seeing the expected number of ANR1342I messages (Scratch volume volume name is now pending - volume will be deleted from storage pool storage pool name after the reuse delay period for this storage pool has elapsed). I should be seeing one or both messages for each offsite volume reclaimed, right? Because my offsite tapes are not getting reclaimed in a timely fashion, I'm
Re: Space reclamation runs, but tapes don't free up
There is a known problem opened with IBM on this... We were told to upgrade to tsm 4.2.2.4 or higher...this seemed to clean up most but not all these problems... If you q content on the tape it is empty, yet if you try to do reclamation or delete it you are informed that there is still data on it We were told we would have to issue an auditdb to clean it up...this would knock our production server off the air for over 27 hrs...so we opted no to do this When we tried to upgrade from tsm 4.2.2.4 to tsm 5.1.0.0 we experienced the following problem: Item PQ64254 APAR Identifier .. PQ64254 Last Changed..02/09/12 ANRD IMINIT.C GROUP.MEMBERS ERROR 8 UPGRADEDB We were informed to upgrade to 5.1.1.4 or higher and run a cleanup backupgroups commandthis also fixed nothing I have an additiona PMR opened with IBM on this problem and am waiting to hear back... thanks Robert Burton Enterprise Storage Network Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 * 416-348-3849 * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 8:53 AM To: [EMAIL PROTECTED] Subject: Re: Space reclamation runs, but tapes don't free up Michael, Why has your tape got a status of filling ? That would be a reason why it would not return to scratch Are all your problem tapes like that? Michael Moore [EMAIL PROTECTED] on 10/02/2002 01:34:26 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Space reclamation runs, but tapes don't free up We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation runs, but tapes don't free up Dist Stor Manager [EMAIL PROTECTED] .EDU 10/01/02 08:13 PM Please respond to ADSM: Dist Stor Manager System is TSM 4.1.2.0 on AIX 4.3.3. I run reclamation daily on my tape backup copy pool, but the backlog of unreclaimed tapes continues to grow (as determined by SQL select looking for volumes in the pool that meet my reclamation threshold - 60%). The space
Re: Space reclamation runs, but tapes don't free up
If a tape is EMPTY, but the access is OFFSITE, TSM won't delete the tape until the access if change to READWRITE, or the MOVE DRMEDIA to bring the tape back onsite. Until then, the tape will remain EMPTY and won't go scratch. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Moore Sent: Wednesday, October 02, 2002 9:11 AM To: [EMAIL PROTECTED] Subject: Re: Space reclamation runs, but tapes don't free up Yes.. I now have approximately 200 tapes in this status, and so far the only fix is to audit each volume. IBM/Tivoli is looking into how they are getting in this state. I am waiting on some trace parms from them. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 John Naylor john.naylor@SCOTTISH-SOUTTo: [EMAIL PROTECTED] HERN.CO.UK cc: Sent by: ADSM: Dist Stor Subject: Re: Space reclamation runs, but tapes don't free up Manager [EMAIL PROTECTED] 10/02/02 08:53 AM Please respond to ADSM: Dist Stor Manager Michael, Why has your tape got a status of filling ? That would be a reason why it would not return to scratch Are all your problem tapes like that? Michael Moore [EMAIL PROTECTED] on 10/02/2002 01:34:26 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Space reclamation runs, but tapes don't free up We are having a similar problem with our server (v4.2.2.12, on OS/390 v2.10). Here is my problem: The reclaim runs, and ends, but the tapes are not being updated as empty. If I run an audit of the tape volume, it will then go to empty, and be deleted during our next MOVEDRMEDIA command. Here is an expamle of one tape that we ran the audit on: Before Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 9,216.0 Pct Util: 0.0 Volume Status: Filling Access: Offsite Pct. Reclaimable Space: 100.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 ast Update by (administrator): MOOREH Last Update Date/Time: 08/01/2002 01:34:34 After Audit query: Volume Name: 321343 Storage Pool Name: DEV_TAPEOS Device Class Name: 3590_OFFSITE_COPY Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 2 Write Pass Number: 1 Approx. Date Last Written: 08/01/2002 01:20:28 Approx. Date Last Read: 08/01/2002 00:31:52 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: TSM390 Last Update by (administrator): MOOREH Last Update Date/Time: 09/27/2002 09:49:11 I do have an ETR open with IBM on this issue. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Brazner, Bob Bob.Brazner@JCI.To: [EMAIL PROTECTED] COM cc: Sent by: ADSM: Subject: Space reclamation runs, but tapes don't free up Dist Stor Manager [EMAIL PROTECTED] .EDU 10/01/02 08:13 PM Please respond to ADSM: Dist Stor Manager System is TSM 4.1.2.0 on AIX 4.3.3. I run reclamation daily on my tape backup copy pool, but the backlog of unreclaimed tapes continues to grow (as determined by SQL select looking for volumes in the pool that meet my reclamation threshold - 60%). The space reclamation process mounts a number of tapes, and a good number of bytes get moved, but the count continues to grow. My onsite tape backup pool does not suffer from this problem. I'm not seeing the number of ANR1341I messages (Scratch volume
