Backup Retention Period
Hi all, What happen if I change my backup retention period. I want to change my backup retention period from 90 days to 30 days. Does it expire all the backup done before. Thanks NORITA BINTI HASAN Senior Programmer Enterprise Systems Services Information Communications Tech. Div 6th Floor,Pos Malaysia HQ 50670 Kuala Lumpur * : 03 - 22756638 *: 016 - 6090530 Pos Malaysia Berhad is Malaysia's national postal company Visit us online at www.pos.com.my NOTICE This message may contain privileged and/or confidential information. If you are not the addressee or authorised to receive this email, you must not use, copy, disclose or take any action based on this email. If you have received this email in error, please advise the sender immediately by reply e-mail and delete this message. Pos Malaysia Berhad takes no responsibility for the contents of this email. Email scanned and protected by POS Malaysia Email scanned and protected by POS Malaysia
Re: Adding Tables to TSM Database
We us an enterprise scheduler to issue a define client action on the TSM server for each node to backup. We use the scheduler to limit the number of active jobs to about 80. The command we use is: define clientaction SERVERNAME action=i wait=yes Andy Huebner From: ADSM: Dist Stor Manager on behalf of Richard Sims Sent: Tue 9/26/2006 5:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Adding Tables to TSM Database There is no provision for adding tables to the (proprietary) TSM database. Where TSM scheduling is insufficient (even with the TSM 5.3 enhancements), you should instead use client-based scheduling mechanisms (cron, etc.) to fulfill specific needs. Richard Sims This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Help, Scratch tapes not mounting properly!!!!
Hi, Google ANR8806E. Seems to be unlabeled tapes. Label libv should solve it. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: dinsdag 26 september 2006 17:22 To: ADSM-L@VM.MARIST.EDU Subject: Help, Scratch tapes not mounting properly Hello everyone, I am receiving the following error messages when my NDMP backups run. The TSM server is AIX 5.2.7.1 and the library is an SL8500 with LTO2 drives. The library is defined as an ACSLS library on TSM and these were scratch tapes. Does anyone have any suggestions as to how to fix this issue or what might be wrong? Thanks! Date/Time Message -- 09/26/06 01:49:35 ANR8337I NAS volume N01172 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:35 ANR8806E Could not write volume label N01172 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8806E Could not write volume label N01169 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:50:57 ANR8806E Could not write volume label N01201 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8806E Could not write volume label N01200 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:52 ANR8806E Could not write volume label N01203 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 03:15:46 ANR8337I NAS volume N01221 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:15:46 ANR8806E Could not write volume label N01221 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:16:00 ANR8337I NAS volume N01230 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:16:00 ANR8806E Could not write volume label N01230 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:43 ANR8337I NAS volume N01231 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:43 ANR8806E Could not write volume label N01231 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:51 ANR8337I NAS volume N01232 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:51 ANR8806E Could not write volume label N01232 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8337I NAS volume N01234 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8806E Could not write volume label N01234 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:24 ANR8337I NAS volume N01233 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:19:24 ANR8806E Could not write volume label N01233 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:44:56 ANR8337I NAS volume N01238 mounted in drive LTO2-53 (c96t0l0). (SESSION: 22244, PROCESS: 447) 09/26/06 03:44:56 ANR8806E Could not write volume label N01238 on the tape in library NASLIB. (SESSION: 22244, PROCESS: 447) 09/26/06 03:45:29 ANR8337I NAS volume N01237 mounted in drive LTO2-21 (c64t0l0). (SESSION: 22244, PROCESS: 446) 09/26/06 03:45:29 ANR8806E Could not write volume label N01237 on the tape in library NASLIB. (SESSION: 22244, PROCESS: 446) Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r
Re: Adding Tables to TSM Database
Hi Adrian, you could create a master script which runs daily at 00:00 and checks for holidays, and then inactivates schedules. A sql statement like this can find any particular date - select 'HOLIDAY' from status where year(current_date) = 2006 and month(current_date) = 9 and day(current_date) = 26 Unnamed[1] -- HOLIDAY Hope this helps, Bill Colwell -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Compton Sent: Tuesday, September 26, 2006 4:38 AM To: ADSM-L@VM.MARIST.EDU Subject: Adding Tables to TSM Database Importance: High Hi all, I would like to use a calendar in TSM to determine when to schedule/not to schedule scripts/schedules based on a calendar. The use of TSM's dayofweek, Month etc does not go deep enough, and there are certain things I would like to schedule based on a calendar specific to my organisation i.e public holidays etc. Can one easily add tables to the TSM database or should this be avoided. Has anyone tried someting simliar. I am using 5.3 on AIX 5.3 (p500 LPAR) Thanks in advance Adrian Compton
Re: 5.3.3 Database Upgrade Timeframe
thanks - Original Message - From: "David Longo" <[EMAIL PROTECTED]> To: Sent: Tuesday, September 26, 2006 10:42 AM Subject: Re: 5.3.3 Database Upgrade Timeframe I just went from 5.2.6.0 to 5.3.2 with a 120GB DB. Took about 5 minutes for the DB upgrade part. Total downtime on AIX platform was about 45 minutes, counting UpgradingTSM filesets and a reboot. 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] Tim Brown <[EMAIL PROTECTED]> 09/26/06 10:32 AM >>> I have a 31 gb TSM database. Any ideas based on users previous experiences how long it will take to upgrade a 5.2.3 database to 5.3.3 Also is it true that all other server activity should be stopped during this process. Tim Brown Systems Specialist Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 ## 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. ##
5.3.3 Database Upgrade Timeframe
I have a 31 gb TSM database. Any ideas based on users previous experiences how long it will take to upgrade a 5.2.3 database to 5.3.3 Also is it true that all other server activity should be stopped during this process. Tim Brown Systems Specialist Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
TSM 5.3 - Archive
Dear List, I have defined the policy domain with backup retention 30 days and archive retention 365. I have some quires: 1. When the Archive will happen? Like daily or weekly .etc... 2. In backup settings, we have backup versions are their. Like How many different versions of the file should be kept? , etc.. in Archive Settings there is any options is their or not.? Can any one please help me out in this regard. Regards, Murugan DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
Help, Scratch tapes not mounting properly!!!!
Hello everyone, I am receiving the following error messages when my NDMP backups run. The TSM server is AIX 5.2.7.1 and the library is an SL8500 with LTO2 drives. The library is defined as an ACSLS library on TSM and these were scratch tapes. Does anyone have any suggestions as to how to fix this issue or what might be wrong? Thanks! Date/Time Message -- 09/26/06 01:49:35 ANR8337I NAS volume N01172 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:35 ANR8806E Could not write volume label N01172 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8806E Could not write volume label N01169 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:50:57 ANR8806E Could not write volume label N01201 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8806E Could not write volume label N01200 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:52 ANR8806E Could not write volume label N01203 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 03:15:46 ANR8337I NAS volume N01221 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:15:46 ANR8806E Could not write volume label N01221 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:16:00 ANR8337I NAS volume N01230 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:16:00 ANR8806E Could not write volume label N01230 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:43 ANR8337I NAS volume N01231 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:43 ANR8806E Could not write volume label N01231 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:51 ANR8337I NAS volume N01232 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:51 ANR8806E Could not write volume label N01232 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8337I NAS volume N01234 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8806E Could not write volume label N01234 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:24 ANR8337I NAS volume N01233 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:19:24 ANR8806E Could not write volume label N01233 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:44:56 ANR8337I NAS volume N01238 mounted in drive LTO2-53 (c96t0l0). (SESSION: 22244, PROCESS: 447) 09/26/06 03:44:56 ANR8806E Could not write volume label N01238 on the tape in library NASLIB. (SESSION: 22244, PROCESS: 447) 09/26/06 03:45:29 ANR8337I NAS volume N01237 mounted in drive LTO2-21 (c64t0l0). (SESSION: 22244, PROCESS: 446) 09/26/06 03:45:29 ANR8806E Could not write volume label N01237 on the tape in library NASLIB. (SESSION: 22244, PROCESS: 446) Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: 5.3.3 Database Upgrade Timeframe
I just went from 5.2.6.0 to 5.3.2 with a 120GB DB. Took about 5 minutes for the DB upgrade part. Total downtime on AIX platform was about 45 minutes, counting UpgradingTSM filesets and a reboot. 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] >>> Tim Brown <[EMAIL PROTECTED]> 09/26/06 10:32 AM >>> I have a 31 gb TSM database. Any ideas based on users previous experiences how long it will take to upgrade a 5.2.3 database to 5.3.3 Also is it true that all other server activity should be stopped during this process. Tim Brown Systems Specialist Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 ## 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. ##
AW: [ADSM-L] help with a select statement
select node_name, count(*) as "#of files", class_name from backups where node_name='x' group by node_name, class_name should give you a list like: NODE_NAME#of files CLASS_NAME -- --- -- x 31479 DEFAULT x 3009 DIRECTORIES x 2233 SYSTEM HTH Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Whitlock, Brett Gesendet: Dienstag, 26. September 2006 15:29 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] help with a select statement Has someone got a handy dandy select statement that will give me client names and the number of backup and archive files by management class? Thanks Brett
Re: FSCK problem on TSM
On Sep 26, 2006, at 8:46 AM, Adrian Compton wrote: ... It may also be worthwhile creating it as a RLV before restoring. Have you any ideas/experience/cautions in doing this. I dont want to be gung-ho in our approach here. Adrian - You'll find RLVs to be delightfully simple to implement, compared with TSM volumes in file systems. Collected nuances and details, based upon experience, can be found in topic Raw logical volume in http://people.bu.edu/rbs/ADSM.QuickFacts or the TSM Wiki. There are IBM Technotes, at least some of which are noted in the QuickFacts. The TSM Admin Guide and TSM Performance Tuning Guide should be the principal references, of course. The List archives also contain experiential information. Richard Sims
Re: FSCK problem on TSM
Hi My next storage pool for DISKPOOL is the OVERFLOW storage pool. It is backed up to Offsite daily as with DISKPOOL. I guess I am covered in the interim then. Thanks for your assistance. Regards, Adrian Compton "Bos, Karel" <[EMAIL PROTECTED] IGIN.COM> To Sent by: "ADSM: ADSM-L@vm.marist.edu Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .edu> Re: [ADSM-L] FSCK problem on TSM 26/09/06 14:02 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .edu> Hi, The next stg parm should be working. Overflow, I don't know. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Compton Sent: dinsdag 26 september 2006 13:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: FSCK problem on TSM The file system is an Enhanced JFS2 file system. It is 1.15TB. It is on a EMC SAN, and mounted as /backup on the TSM LPAR. It consists of a number of LUNS on the EMC SAN. It contains all of our DISKPOOLS. My logs are now fine as I allocated more log space using dsmfmt and the TSM Server could restart. My Logs andTSM DB's are on seperate filesystem i.e /usr After rebooting the LPAR, AIX wont mount the filesystem because of a superblock error. We have determined that an FSCK is running, and apparently this can take days on a large file system. I see now that we should have a large Raw Logical Volume to overcome these contraints. To keep Tivoli running we have had to exclude this FS (/backup/) from mounting, but are now running without the DISKPOOL. Hence my question about the OVERFLOW storage pool automatically becoming the recipient in place of the DISKPOOL without having to change any parameters. Apologies for my explanation, but I have only been working with TSM for 5 months now although I have training behind me. Thanks in advance. Adrian Compton Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: To Dist Stor ADSM-L@vm.marist.edu Manager" cc <[EMAIL PROTECTED] .edu> Subject Re: [ADSM-L] FSCK problem on TSM 26/09/06 13:07 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .edu> You're not giving us enough information to understand what the actual problem is there. Disk storage pool space and Recovery Log space are very different things and very much should be in very different places, having different service and recovery needs, including mirroring for the TSM database and recovery log. With AIX, you should ideally be using Raw Logical Volumes, as described in the Admin Guide and other TSM documentation, such as the Performance Tuning Guide. This will eliminate all the file system issues and greatly facilitate disaster recovery. Always thoroughly review vendor configuration recommendations before proceeding with an implementation. And always implement monitoring, to avoid needless disruptions like this. Again, I won't add further recommendations, absent the solid information needed to provide proper guidance. Richard Sims On Sep 26, 2006, at 6:29 AM, Adrian Compton wrote: > Hi > > Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out > of space. In hind sight, the Server was bounced and I now have fsck > running forever almost as if in a loop. At present it would take days > as the filesystem concerned is 1.150TB. > > Apparently we need to patch the OS as the FSCK gets into a loop, and > has to complete the checks of the superblocksbefore it can be mounted. > This filesystem contains my DISKPOOLS. > > My questions are/ > > 1. Will any clients that normally go to DISPOOL now automatically go > to overflow until the filesystem comes backup. > 2. what is the recommended max filesystem size to prevent this long > FSCK. > 3. Is there any other way to resolve this long wait for the check to > complete. > > Regards > > Adrian Compton (See attached file: disclaimer.txt)ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e
Re: FSCK problem on TSM
Hi, The next stg parm should be working. Overflow, I don't know. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Compton Sent: dinsdag 26 september 2006 13:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: FSCK problem on TSM The file system is an Enhanced JFS2 file system. It is 1.15TB. It is on a EMC SAN, and mounted as /backup on the TSM LPAR. It consists of a number of LUNS on the EMC SAN. It contains all of our DISKPOOLS. My logs are now fine as I allocated more log space using dsmfmt and the TSM Server could restart. My Logs andTSM DB's are on seperate filesystem i.e /usr After rebooting the LPAR, AIX wont mount the filesystem because of a superblock error. We have determined that an FSCK is running, and apparently this can take days on a large file system. I see now that we should have a large Raw Logical Volume to overcome these contraints. To keep Tivoli running we have had to exclude this FS (/backup/) from mounting, but are now running without the DISKPOOL. Hence my question about the OVERFLOW storage pool automatically becoming the recipient in place of the DISKPOOL without having to change any parameters. Apologies for my explanation, but I have only been working with TSM for 5 months now although I have training behind me. Thanks in advance. Adrian Compton Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: To Dist Stor ADSM-L@vm.marist.edu Manager" cc <[EMAIL PROTECTED] .edu> Subject Re: [ADSM-L] FSCK problem on TSM 26/09/06 13:07 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .edu> You're not giving us enough information to understand what the actual problem is there. Disk storage pool space and Recovery Log space are very different things and very much should be in very different places, having different service and recovery needs, including mirroring for the TSM database and recovery log. With AIX, you should ideally be using Raw Logical Volumes, as described in the Admin Guide and other TSM documentation, such as the Performance Tuning Guide. This will eliminate all the file system issues and greatly facilitate disaster recovery. Always thoroughly review vendor configuration recommendations before proceeding with an implementation. And always implement monitoring, to avoid needless disruptions like this. Again, I won't add further recommendations, absent the solid information needed to provide proper guidance. Richard Sims On Sep 26, 2006, at 6:29 AM, Adrian Compton wrote: > Hi > > Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out > of space. In hind sight, the Server was bounced and I now have fsck > running forever almost as if in a loop. At present it would take days > as the filesystem concerned is 1.150TB. > > Apparently we need to patch the OS as the FSCK gets into a loop, and > has to complete the checks of the superblocksbefore it can be mounted. > This filesystem contains my DISKPOOLS. > > My questions are/ > > 1. Will any clients that normally go to DISPOOL now automatically go > to overflow until the filesystem comes backup. > 2. what is the recommended max filesystem size to prevent this long > FSCK. > 3. Is there any other way to resolve this long wait for the check to > complete. > > Regards > > Adrian Compton ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n
Re: FSCK problem on TSM
The file system is an Enhanced JFS2 file system. It is 1.15TB. It is on a EMC SAN, and mounted as /backup on the TSM LPAR. It consists of a number of LUNS on the EMC SAN. It contains all of our DISKPOOLS. My logs are now fine as I allocated more log space using dsmfmt and the TSM Server could restart. My Logs andTSM DB's are on seperate filesystem i.e /usr After rebooting the LPAR, AIX wont mount the filesystem because of a superblock error. We have determined that an FSCK is running, and apparently this can take days on a large file system. I see now that we should have a large Raw Logical Volume to overcome these contraints. To keep Tivoli running we have had to exclude this FS (/backup/) from mounting, but are now running without the DISKPOOL. Hence my question about the OVERFLOW storage pool automatically becoming the recipient in place of the DISKPOOL without having to change any parameters. Apologies for my explanation, but I have only been working with TSM for 5 months now although I have training behind me. Thanks in advance. Adrian Compton Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM:To Dist Stor ADSM-L@vm.marist.edu Manager" cc <[EMAIL PROTECTED] .edu> Subject Re: [ADSM-L] FSCK problem on TSM 26/09/06 13:07 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .edu> You're not giving us enough information to understand what the actual problem is there. Disk storage pool space and Recovery Log space are very different things and very much should be in very different places, having different service and recovery needs, including mirroring for the TSM database and recovery log. With AIX, you should ideally be using Raw Logical Volumes, as described in the Admin Guide and other TSM documentation, such as the Performance Tuning Guide. This will eliminate all the file system issues and greatly facilitate disaster recovery. Always thoroughly review vendor configuration recommendations before proceeding with an implementation. And always implement monitoring, to avoid needless disruptions like this. Again, I won't add further recommendations, absent the solid information needed to provide proper guidance. Richard Sims On Sep 26, 2006, at 6:29 AM, Adrian Compton wrote: > Hi > > Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run > out of > space. In hind sight, the Server was bounced and I now have fsck > running > forever almost as if in a loop. At present it would take days as the > filesystem concerned is 1.150TB. > > Apparently we need to patch the OS as the FSCK gets into a loop, > and has to > complete the checks of the superblocksbefore it can be mounted. This > filesystem contains my DISKPOOLS. > > My questions are/ > > 1. Will any clients that normally go to DISPOOL now automatically > go to > overflow until the filesystem comes backup. > 2. what is the recommended max filesystem size to prevent this long > FSCK. > 3. Is there any other way to resolve this long wait for the check to > complete. > > Regards > > Adrian Compton
help with a select statement
Has someone got a handy dandy select statement that will give me client names and the number of backup and archive files by management class? Thanks Brett
Re: TSM 5.3 with Tape Library 3580 error
Hi Rajea, I could able to view the "Medium Changers" and all the "lto drives" from TSM Server. But I have installed same as on the TSM Storage Agent ( Client Machine) I could not able view the same in the server. Please advice how to resolve this problem. I awaiting for your favorable reply. Regards, Murugan -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rejean Larivee Sent: Monday, September 25, 2006 6:34 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3 with Tape Library 3580 error Hello, if you installed the ultrium device driver correctly, then you should be able to see the medium changer and the drives in device manager. Right-click on "My Computer" and select Manage and then select "Device Manager". Expand the "Medium Changers" section. There should be an "IBM 3584 Tape Library" entry. Right click on it and select "properties". Go the "driver" tab. The Driver Provider should be "IBM Corporation" and Driver Version should be 6.1.3.8. Expand the "Tape Drives" section. There should be eight (8) entries of "IBM ULT3580-TDx ..." entries. Right click on it and select "properties". Go the "driver" tab. The Driver Provider should be "IBM Corporation" and Driver Version should be 6.1.3.8. If you cannot see the medium changer or drives in Device Manager, or the driver tab is not showing the right information, then the ulirum driver is not installed correctly or the library/drives are not connected properly. You may want to refer to the following article on our support pages which I wrote recently, http://www-1.ibm.com/support/docview.wss?uid=swg21240603 The above document offers more details on diagnosing this kind of issue. Bye ! Rejean Larivee IBM Tivoli Storage Manager Level2 Support Murugan_Pachamall ayan ADSM-L@VM.MARIST.EDU Sent by: "ADSM: cc Dist Stor Manager" Subject <[EMAIL PROTECTED] Re: TSM 5.3 with Tape Library 3580 .EDU> error 09/25/2006 08:55 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hi Rajean, I have installed the driver IBMTape.x86_6138 and I am getting the same. Please advice how to proceed further. Regards, Murugan -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rejean Larivee Sent: Monday, September 25, 2006 5:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 5.3 with Tape Library 3580 error Hello, you need to install the ultrium device driver. From your post, it does not appear this was done. You can download the latest IBM ultrium device driver for Windows 2003 - 32 bit here : ftp://ftp.software.ibm.com/storage/devdrvr/Windows/Win2003/Latest/IBMTap e.x86_6138.zip Extract the zip file and run the install.exe to install the driver for the 3584 and 3580 drives. Following that, you should be able to see the Medium Changer and Tape Drives under "Device Manager". Bye ! Rejean Larivee IBM Tivoli Storage Manager Level2 Support Murugan_Pachamall ayan ADSM-L@VM.MARIST.EDU Sent by: "ADSM: cc Dist Stor Manager" Subject <[EMAIL PROTECTED] TSM 5.3 with Tape Library 3580 .EDU> error 09/25/2006 07:17 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> Hi, I have installed the following modules in Windows 2003 Server 1. Tivoli Storage Agent 5.3.2.0 2. Tivoli Storage Manager device driver 5.3.2.0 I attached 3584Library with 8 x 3580LTO Drives through SAN.. But I could not able to view the medium changer and tape drives. I can see only device name :mt6.0.0.2 , TSM device type : 4mm, Device Id : Seagate DAT 9SP40-00 How can I view all the drives and medium changer . Please can any one help me out in this regard. Regards, Murugan DISCLAIMER: This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMP
Re: FSCK problem on TSM
You are quite correct Richard. Thanks We are considreing the option of trashing the filesystem where the disk?.dsm files for the DISKPOOL reside, and restoring it from the daily offsite backup done of the diskpool. It may also be worthwhile creating it as a RLV before restoring. Have you any ideas/experience/cautions in doing this. I dont want to be gung-ho in our approach here. Thanks Adrian Compton Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM:To Dist Stor ADSM-L@vm.marist.edu Manager" cc <[EMAIL PROTECTED] .edu> Subject Re: [ADSM-L] FSCK problem on TSM 26/09/06 14:16 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .edu> On Sep 26, 2006, at 7:58 AM, Adrian Compton wrote: > To keep Tivoli running we have had to exclude this FS (/backup/) from > mounting, but are now running without the DISKPOOL. Hence my > question about > the OVERFLOW storage pool automatically becoming the recipient in > place of > the DISKPOOL without having to change any parameters. If your TSM server came up, it should see all the DISKPOOL volumes missing, and so all incoming data should then go to the next level of the storage pool hierarchy, assuming that's in writable condition and has space. You might formally perform an Update Stgpool to mark it Unavailable until such time as its original volumes are returned to service, or (RLV) substitutes might be put into place. The more awkward situation is outgoing data, which is to say that any data which arrived in the backup disk pool but which is not represented in the overflow area is unavailable for restorals - something which needs to be publicized to the affected client community before they attempt to restore data and find some or all of it missing. Richard Sims
Re: Adding Tables to TSM Database
There is no provision for adding tables to the (proprietary) TSM database. Where TSM scheduling is insufficient (even with the TSM 5.3 enhancements), you should instead use client-based scheduling mechanisms (cron, etc.) to fulfill specific needs. Richard Sims
Re: FSCK problem on TSM
hi adrian, if no space within of your storage-pools is available, the data will be send to the according "Next Storagepool". if this is a sequential tape-pool and their are not enough tape-drives available, you will see a lot of mount-requests by your clients during their backup/archive-operation. the OVFLOcation is only used if you checkout cartridges in case of to less slots in your library, and you need to checkin scratch-tapes. - snip - OVFLOcation Specifies the overflow location for the storage pool. The server assigns this location name to a volume that is ejected from the library by the command. This parameter is optional. The location name can be a maximum length of 255 characters. Enclose the location name in quotation marks if the location name contains any blank characters. Note: This parameter is not available for storage pools that use the following data formats: + NETAPPDUMP + CELERRADUMP + NDMPDUMP - snap - you can define an additional primary storage-pool based on disk-volumes defined on another filesystem and define this storage-pool as the next-storagepool of your defect-pool. regards uwe schreiber [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 26.09.2006 12:29 Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject FSCK problem on TSM Hi Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out of space. In hind sight, the Server was bounced and I now have fsck running forever almost as if in a loop. At present it would take days as the filesystem concerned is 1.150TB. Apparently we need to patch the OS as the FSCK gets into a loop, and has to complete the checks of the superblocksbefore it can be mounted. This filesystem contains my DISKPOOLS. My questions are/ 1. Will any clients that normally go to DISPOOL now automatically go to overflow until the filesystem comes backup. 2. what is the recommended max filesystem size to prevent this long FSCK. 3. Is there any other way to resolve this long wait for the check to complete. Regards Adrian Compton
Re: FSCK problem on TSM
On Sep 26, 2006, at 7:58 AM, Adrian Compton wrote: To keep Tivoli running we have had to exclude this FS (/backup/) from mounting, but are now running without the DISKPOOL. Hence my question about the OVERFLOW storage pool automatically becoming the recipient in place of the DISKPOOL without having to change any parameters. If your TSM server came up, it should see all the DISKPOOL volumes missing, and so all incoming data should then go to the next level of the storage pool hierarchy, assuming that's in writable condition and has space. You might formally perform an Update Stgpool to mark it Unavailable until such time as its original volumes are returned to service, or (RLV) substitutes might be put into place. The more awkward situation is outgoing data, which is to say that any data which arrived in the backup disk pool but which is not represented in the overflow area is unavailable for restorals - something which needs to be publicized to the affected client community before they attempt to restore data and find some or all of it missing. Richard Sims
FSCK problem on TSM
Hi Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out of space. In hind sight, the Server was bounced and I now have fsck running forever almost as if in a loop. At present it would take days as the filesystem concerned is 1.150TB. Apparently we need to patch the OS as the FSCK gets into a loop, and has to complete the checks of the superblocksbefore it can be mounted. This filesystem contains my DISKPOOLS. My questions are/ 1. Will any clients that normally go to DISPOOL now automatically go to overflow until the filesystem comes backup. 2. what is the recommended max filesystem size to prevent this long FSCK. 3. Is there any other way to resolve this long wait for the check to complete. Regards Adrian Compton
Re: FSCK problem on TSM
You're not giving us enough information to understand what the actual problem is there. Disk storage pool space and Recovery Log space are very different things and very much should be in very different places, having different service and recovery needs, including mirroring for the TSM database and recovery log. With AIX, you should ideally be using Raw Logical Volumes, as described in the Admin Guide and other TSM documentation, such as the Performance Tuning Guide. This will eliminate all the file system issues and greatly facilitate disaster recovery. Always thoroughly review vendor configuration recommendations before proceeding with an implementation. And always implement monitoring, to avoid needless disruptions like this. Again, I won't add further recommendations, absent the solid information needed to provide proper guidance. Richard Sims On Sep 26, 2006, at 6:29 AM, Adrian Compton wrote: Hi Yesterday my TSM server (p500 LPAR AIX 5.3) had the TSM Logs run out of space. In hind sight, the Server was bounced and I now have fsck running forever almost as if in a loop. At present it would take days as the filesystem concerned is 1.150TB. Apparently we need to patch the OS as the FSCK gets into a loop, and has to complete the checks of the superblocksbefore it can be mounted. This filesystem contains my DISKPOOLS. My questions are/ 1. Will any clients that normally go to DISPOOL now automatically go to overflow until the filesystem comes backup. 2. what is the recommended max filesystem size to prevent this long FSCK. 3. Is there any other way to resolve this long wait for the check to complete. Regards Adrian Compton
Re: TSM loses tape drives (again and again and again...)
have you setup persistent binding, may be this solve your problems. --- Rob Berendt <[EMAIL PROTECTED]> escribió: > I don't use TSM to back up the other lpar's. I > don't even think there is > an i5/os client for TSM. i5/os people tend to use > one of two things. What > comes with the OS, or IBM's BRMS. I've done a few > bare metal restores > with what comes with the OS and have not had a > hitch. > So, I don't have that issue. > > Good point about the separate location. Maybe we'll > practice a DR > scenario when we get our DR site up and running > shortly. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > Richard van Denzel <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" > > 09/21/2006 10:11 AM > Please respond to > "ADSM: Dist Stor Manager" > > > To > ADSM-L@VM.MARIST.EDU > cc > > Subject > Re: [ADSM-L] TSM loses tape drives (again and again > and again...) > > > > > > > Rob, > > Just my 2 cents. I tend not to run TSM on a > virtual/lparred environment > at all. > If you do that, you not only lose your production > environment, but also > your backup. > > I always try to put TSM on a separate machine > (preferrable on a separate > location). > > Met vriendelijke groet, with kind regards, > > Richard van Denzel > > -Oorspronkelijk bericht- > Van: ADSM: Dist Stor Manager > [mailto:[EMAIL PROTECTED] Namens Rob > Berendt > Verzonden: donderdag 21 september 2006 14:52 > Aan: ADSM-L@VM.MARIST.EDU > Onderwerp: Re: [ADSM-L] TSM loses tape drives (again > and again and > again...) > > Virtualizaton? Is there a possibility that if I ran > the lpar as, not a > guested linux lpar, but a dedication linux lpar I > wouldn't have this > issue? > > Well, we normally only reboot every 8 weeks to allow > maintenance. We do > boot occasionally but mostly to duplicate this > situation for IBM. I > have the rebuild steps pretty well documented. I > have a reboot > scheduled this weekend and the documentation printed > out. I plan on > being out of state so we'll see how well my > documentation is and how > well they follow it. > > I'd like to be able to script this, however I can't > figure out how to do > that either. And my previous inquiries to the list > as to how, didn't > really fly. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > Remco Post <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" > > 09/21/2006 08:43 AM > Please respond to > "ADSM: Dist Stor Manager" > > > To > ADSM-L@VM.MARIST.EDU > cc > > Subject > Re: [ADSM-L] TSM loses tape drives (again and again > and again...) > > > > > > > Rob Berendt wrote: > > I have this nailed down a little bit more. I ran > the following: > > IBMtapeutil -f /dev/IBMtape1 inquiry 80 and > IBMtapeutil -f > > /dev/IBMtape2 inquiry 80 Then I rebooted this > Linux on i5 lpar (hosted > > > underneath an i5/os lpar). > I > > ran the IBMtapeutil commands again and the serial > numbers flipflopped > > between the two. Of course, TSM doesn't like it > when path names > change. > I > > am thinking the possible solutions are either to > get Linux to stop > > flipflopping the serial numbers or to tell TSM not > to give a rip about > the > > serial numbers. Trouble is, I can't figure out > either way. > > > > Let me first say that yes this is annoying, and > should not happen. I > guess there is very little you can do in a > virtualised environment as 5i > lpar's are. > > Now just for the record, how often do you reboot? I > tend not to reboot > on a daily or even monthly basis, it's 24*7 > production environment > > Now for a 'work-arond' you could possibly quite > easily build a > server script to do a bunch of 'update drive. > serial=autodetect' > things and run that after every reboot My guess > being that you don't > daily change the number of drives either > > > Rob Berendt > > -- > > Group Dekko Services, LLC > > Dept 01.073 > > PO Box 2000 > > Dock 108 > > 6928N 400E > > Kendallville, IN 46755 > > http://www.dekko.com > > > -- > Met vriendelijke groeten, > > Remco Post > > SARA - Reken- en Netwerkdiensten > http://www.sara.nl > High Performance Computing Tel. +31 20 592 3000 > Fax. +31 20 668 3167 > PGP Key fingerprint: 6367 DFE9 5CBC 0737 7D16 B3F6 > 048A === message truncated === __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
Adding Tables to TSM Database
Hi all, I would like to use a calendar in TSM to determine when to schedule/not to schedule scripts/schedules based on a calendar. The use of TSM's dayofweek, Month etc does not go deep enough, and there are certain things I would like to schedule based on a calendar specific to my organisation i.e public holidays etc. Can one easily add tables to the TSM database or should this be avoided. Has anyone tried someting simliar. I am using 5.3 on AIX 5.3 (p500 LPAR) Thanks in advance Adrian Compton
Re: Help, Scratch tapes not mounting properly!!!!
Hi Karel, I did the following command to checkin a bulk amount of tapes: 09/25/06 10:23:20 ANR2017I Administrator LIDZR8V issued command: LABEL libvol naslib search=yes checkin=scratch volrange=n01230 ,n01339 overwrite=yes (SESSION: 11019) Some of the tapes in question are in this range, but I did have 2 tapes mount correctly and work: N01235 & N01236. That's why I'm confused and not understanding what is wrong? Any ideas? Thanks again! Joni Moyer Highmark Storage Systems, Senior Systems Programmer Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] "Bos, Karel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 09/26/2006 11:28 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Help, Scratch tapes not mounting properly Hi, Google ANR8806E. Seems to be unlabeled tapes. Label libv should solve it. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: dinsdag 26 september 2006 17:22 To: ADSM-L@VM.MARIST.EDU Subject: Help, Scratch tapes not mounting properly Hello everyone, I am receiving the following error messages when my NDMP backups run. The TSM server is AIX 5.2.7.1 and the library is an SL8500 with LTO2 drives. The library is defined as an ACSLS library on TSM and these were scratch tapes. Does anyone have any suggestions as to how to fix this issue or what might be wrong? Thanks! Date/Time Message -- 09/26/06 01:49:35 ANR8337I NAS volume N01172 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:35 ANR8806E Could not write volume label N01172 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8806E Could not write volume label N01169 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:49:57 ANR8337I NAS volume N01169 mounted in drive LTO2-36 (c64t0l0). (SESSION: 22291, PROCESS: 367) 09/26/06 01:50:57 ANR8806E Could not write volume label N01201 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 367) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8806E Could not write volume label N01200 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:01 ANR8337I NAS volume N01200 mounted in drive LTO2-57 (c96t0l0). (SESSION: 22291, PROCESS: 368) 09/26/06 01:51:52 ANR8806E Could not write volume label N01203 on the tape in library NASLIB. (SESSION: 22291, PROCESS: 368) 09/26/06 03:15:46 ANR8337I NAS volume N01221 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:15:46 ANR8806E Could not write volume label N01221 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:16:00 ANR8337I NAS volume N01230 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:16:00 ANR8806E Could not write volume label N01230 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:43 ANR8337I NAS volume N01231 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:43 ANR8806E Could not write volume label N01231 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:17:51 ANR8337I NAS volume N01232 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:17:51 ANR8806E Could not write volume label N01232 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8337I NAS volume N01234 mounted in drive LTO2-37 (c96t0l0). (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:23 ANR8806E Could not write volume label N01234 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 408) 09/26/06 03:19:24 ANR8337I NAS volume N01233 mounted in drive LTO2-5 (c64t0l0). (SESSION: 22147, PROCESS: 407) 09/26/06 03:19:24 ANR8806E Could not write volume label N01233 on the tape in library NASLIB. (SESSION: 22147, PROCESS: 407) 09/26/06 03:44:56 ANR83
