Re: DELETing a volume from a DB backup
Iain, I agree with you. I don't think this is a place where we should just say RTFM. I hope my tone was not that at all. I was simply trying to encourage him to get the skills needed. The real problem is management doesn't always understand that tech people need training! I don't care what Backup/Restore solution you are using today, none of them just work right out of the box and they all need a degree of skill to effectively manage them. And you are right I am glad for this list as well. It is an excellent resource with many very talented people out here and for the most part they are all trying to help. While I am on my soap box, I'll mention another area that seems to be a problem lately. This isn't just TSM now it applies to a large degree to all enterprise level software. More and more companies are purchasing software and then hiring consulting services to come in and set it up. What I am finding is there are a number of consultants out there that do what I call hit and run services. They come in they set it up and then they are gone. They never did any training or even explanation of the entire environment with the customer. And the one who winds up looking the fool is the tech guy, because management says hey we just paid big bucks to have this set up and now you can't keep it running. I have come in behind a number of consultants and had to clean up after them. When I do services part of the contract is training both the administrators and the operators (if they are different). I provide written documentation about their specific environment. I give them an SLA describing the level of service they are providing their customers. I give them a manual that describes the day to day operation of their TSM environment and not only does it tell them what to do, but why they are doing it. It is a lot more work and it cost a bit more money, but in the long run I think I have happier customers as a result. OK, I am done patting myself on the back. The real point of this is that if your are going to administer a TSM environment you are going to have to acquire the skills to do it. Now, you can get those skills in a variety of ways, formal training, technology transfer from a consultant, even read the manual, or you can get it from the "school of hard knocks". If you are forced into the latter choice it can be quite an expensive proposition! -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Iain Barnetson wrote: Mark, I don't know Rob's situation, but I know that a year a go I had TSM 'dumped' on me, having never had any dealings with the product previoulsy. It was 4 months before my company finally got me on the basic TSM course, after much tears & tantrums. During that 4 months I struggled severly - even having had RTFM. Unfortunately for me I didn't know about this email group back then, I wish I had, it's an invaluable source of information. Mostly people here are very understanding, but occaissionally, and I'm not referring to you, people simply say RTFM which is less than helpful. Some need to understand that there are people out there for whom TSM is just one of their responsabilities and there are only so many hours in a day which means not always enough to read, digest and grasp the intricacies of TSM. Especially when the manuals can be at times, it's got to be said, less than clear and unequivocal. It's not usually a case of the person not having read the manuals, for some including myself, it's an uphill struggle to get to grips with TSM. After having worked with TSM for around a year now, I only consider myself beginning to fully understand it now. And I'd say that I'd picked up more from this email group than from any other avenue. Whilst DB backups and tape management maybe fundamental, it doesn't make it obvious. Regards, Iain -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: 25 March 2005 20:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DELETing a volume from a DB backup Rob, Please don't take this wrong, I certainly don't mind the question. However, I must say that this is such a fundamental part of TSM I am wondering about your basic level of training here. This product does require some basic training in order to operate it correctly. I recommend taking one or even two of the available TSM classes from IBM to get the basic skills needed. If you can't take the formal classes IBM has on line self paced classes as well. Or you can do it the
Re: DELETing a volume from a DB backup
Mark, I don't know Rob's situation, but I know that a year a go I had TSM 'dumped' on me, having never had any dealings with the product previoulsy. It was 4 months before my company finally got me on the basic TSM course, after much tears & tantrums. During that 4 months I struggled severly - even having had RTFM. Unfortunately for me I didn't know about this email group back then, I wish I had, it's an invaluable source of information. Mostly people here are very understanding, but occaissionally, and I'm not referring to you, people simply say RTFM which is less than helpful. Some need to understand that there are people out there for whom TSM is just one of their responsabilities and there are only so many hours in a day which means not always enough to read, digest and grasp the intricacies of TSM. Especially when the manuals can be at times, it's got to be said, less than clear and unequivocal. It's not usually a case of the person not having read the manuals, for some including myself, it's an uphill struggle to get to grips with TSM. After having worked with TSM for around a year now, I only consider myself beginning to fully understand it now. And I'd say that I'd picked up more from this email group than from any other avenue. Whilst DB backups and tape management maybe fundamental, it doesn't make it obvious. Regards, Iain -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Rodriguez Sent: 25 March 2005 20:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] DELETing a volume from a DB backup Rob, Please don't take this wrong, I certainly don't mind the question. However, I must say that this is such a fundamental part of TSM I am wondering about your basic level of training here. This product does require some basic training in order to operate it correctly. I recommend taking one or even two of the available TSM classes from IBM to get the basic skills needed. If you can't take the formal classes IBM has on line self paced classes as well. Or you can do it the old fashion way and cozy up to the TSM Administration Guide and give it a few hours of your time. Now in regards to your question, DB backup volumes regardless of whether they are full, incremental or snapshot do not expire on their own (with the exception of those managed by DRM, which is a whole separate chapter in the Admin Guide!) and therefore require you to take action. You must issue the DELete VOLHistory command in order to expire those tapes and have them become scratch tapes again. Please look in the documentation for the DELete VOLHistory command in order to see the correct syntax. Also, please note you won't be able to delete your most recent DB backup set, nor should you, if that is what you are trying to do. Again, please don't take my comments at the beginning as an insult. I am merely trying to encourage you to develop the basic skill needed to run a TSM environment. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Rob Berendt wrote: >When I use a tape volume to perform >backup db devclass=3581dev type=full scratch=yes wait=no How do I >prepare it for later reuse? > >Rob Berendt >-- >Group Dekko Services, LLC >Dept 01.073 >PO Box 2000 >Dock 108 >6928N 400E >Kendallville, IN 46755 >http://www.dekko.com > > >
Re: Experience with mixing LTO drives in a single library
Bill, One other thing you might recommend to them is to get 2 LTO3 drives. If not, you are going to have problems doing space reclamation on the LTO3 volumes. Now if they do that you could then consider partitioning the library (3583 does support that, although I think it is an additional option) and not having to deal with the mixed formats with in the library. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === William Boyer wrote: I know it's supported, and the Admin Guide doesn't say very much about the actual mechanics and pros/cons of doing it, but I have a client that has a 3853 with 3-LTO1 drives. They have a very specific application that requires large capacity, but a limited budget. They are looking at adding a single LTO-3 drive to the existing library and an additional storage column. Searching the archives I did run across a post about having to use the specific FORMAT=ULTRIUMx instead of FORMAT=DRIVE to create 2 separate device classes. Then define a storage pool for the LTO-3 and direct this high capacity application to that stgpool. Anyone willing to share real-world experiences on defining the environment and any problems encountered?? They are running 5.2.3.0 on AIX 5.2. I know I need to bring them up to 5.2.4.0 for LTO-3 support plus upgrade the Atape drivers. Bill Boyer "Growing old is mandatory, growing up is optional" - ??
Re: Preparing a tape storage pool volume for reuse
Rob, Again this is a fundamental concept in TSM as I stated in my previous post I think you will need to develop your skill set in the TSM area. No, you do not want to do DELete VOLume! What you should be doing on some regular basis is running reclamation on that storage pool. Reclamation will then empty the partially used tapes. Please refer to the admin guide where you will find several sections discussing managing storage pools and volumes. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Rob Berendt wrote: Unlike my previous post regarding a BACKUP DB volume, now I have a question about a Copy Storage Pool tape volume. After I used a tape volume for backup stg backuppool lto_3581_week2 I want to reuse it. Do I just: delete volume 12wk2 discarddata=yes wait=no Are there any other steps I need? If I am running TSM 5.2.2 on OS/400 V5R3 under PASE, do I need to INZTAP also? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
Re: DELETing a volume from a DB backup
Rob, Please don't take this wrong, I certainly don't mind the question. However, I must say that this is such a fundamental part of TSM I am wondering about your basic level of training here. This product does require some basic training in order to operate it correctly. I recommend taking one or even two of the available TSM classes from IBM to get the basic skills needed. If you can't take the formal classes IBM has on line self paced classes as well. Or you can do it the old fashion way and cozy up to the TSM Administration Guide and give it a few hours of your time. Now in regards to your question, DB backup volumes regardless of whether they are full, incremental or snapshot do not expire on their own (with the exception of those managed by DRM, which is a whole separate chapter in the Admin Guide!) and therefore require you to take action. You must issue the DELete VOLHistory command in order to expire those tapes and have them become scratch tapes again. Please look in the documentation for the DELete VOLHistory command in order to see the correct syntax. Also, please note you won't be able to delete your most recent DB backup set, nor should you, if that is what you are trying to do. Again, please don't take my comments at the beginning as an insult. I am merely trying to encourage you to develop the basic skill needed to run a TSM environment. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Rob Berendt wrote: When I use a tape volume to perform backup db devclass=3581dev type=full scratch=yes wait=no How do I prepare it for later reuse? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
Re: del volhist problem
Yep, increasing the recovlog is doing the job. Thanks to all! Thanks for not just saying RTFM too. I really do plan to read it front2back when I get some time to do so. I need 3 months off just to read the 100 or so manuals I want to absorb better. A well planned setup saves time, I do know that. Alex On Fri, 25 Mar 2005, Mark D. Rodriguez wrote: Alexander, TSM won't let you delete those volumes since they are all part of the most recent DB backup set. It appears that you are doing incremental DB backups at random times which indicates that the DB backup trigger is causing these backups. The DB backup trigger happens when the log space starts to be over committed. Therefore there are several suggestions I can make to you. 1. Increase the size of your log file, This should cut down on the number of triggered DB backups. 2. Consider changing your strategy for DB backups. I recommend that your "on site" DB backups should be full/incremental and should be done to a device type of file. Typically I do a full once a week and do incremental the rest of the week. There is no performance hit since it is to a device of type file. Also, set your DB backup trigger to use this device and set the number of incremental to the max. BTW, with a DB of 15GB using 1 full and six incremental plus keeping the full previous set (i.e. the previous weeks) you should need less than 50GB of disk space. 3. For off site DB backups use a snapshot backup to tape. Only run this on the days that you take tapes off site. I have given you the basic concepts of what I would do. If you need more specific commands on how to implement this please feel free to ask. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: HEre's the output: tsm: TSM>q volh t=dbb Date/Time: 03/21/2005 11:00:48 Volume Type: BACKUPFULL Backup Series: 112 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG044L2 Volume Location: Command: Date/Time: 03/24/2005 18:16:08 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 1 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG010L2 Volume Location: Command: Date/Time: 03/25/2005 06:01:13 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 2 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG033L2 Volume Location: Command: My issue with that idea is the database is only 13-14GB, so how could it need 3 tapes for the DB backup? I've been backing up the DB for 2 years, and it never needed more than 1 tape for it: tsm: TSM>q db Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 32,000 32,000 018,028 4,096 8,192,000 2,846,578 34.7 43. Thanks! On Fri, 25 Mar 2005, Mark D. Rodriguez wrote: It would help if we could see the output of the following command: q volh t=dbb It might be that this is the most recent DB backup in which case it won't let you delete it. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast Use Home --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbacku
Re: del volhist problem
Alexander, TSM won't let you delete those volumes since they are all part of the most recent DB backup set. It appears that you are doing incremental DB backups at random times which indicates that the DB backup trigger is causing these backups. The DB backup trigger happens when the log space starts to be over committed. Therefore there are several suggestions I can make to you. 1. Increase the size of your log file, This should cut down on the number of triggered DB backups. 2. Consider changing your strategy for DB backups. I recommend that your "on site" DB backups should be full/incremental and should be done to a device type of file. Typically I do a full once a week and do incremental the rest of the week. There is no performance hit since it is to a device of type file. Also, set your DB backup trigger to use this device and set the number of incremental to the max. BTW, with a DB of 15GB using 1 full and six incremental plus keeping the full previous set (i.e. the previous weeks) you should need less than 50GB of disk space. 3. For off site DB backups use a snapshot backup to tape. Only run this on the days that you take tapes off site. I have given you the basic concepts of what I would do. If you need more specific commands on how to implement this please feel free to ask. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: HEre's the output: tsm: TSM>q volh t=dbb Date/Time: 03/21/2005 11:00:48 Volume Type: BACKUPFULL Backup Series: 112 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG044L2 Volume Location: Command: Date/Time: 03/24/2005 18:16:08 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 1 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG010L2 Volume Location: Command: Date/Time: 03/25/2005 06:01:13 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 2 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG033L2 Volume Location: Command: My issue with that idea is the database is only 13-14GB, so how could it need 3 tapes for the DB backup? I've been backing up the DB for 2 years, and it never needed more than 1 tape for it: tsm: TSM>q db Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 32,000 32,000 018,028 4,096 8,192,000 2,846,578 34.7 43. Thanks! On Fri, 25 Mar 2005, Mark D. Rodriguez wrote: It would help if we could see the output of the following command: q volh t=dbb It might be that this is the most recent DB backup in which case it won't let you delete it. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast UseHome --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error: ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. I need an answer fast as I've o
Re: del volhist problem
Is your database in "roll forward" mode or normal? If it's in roll forward, what's your database backup trigger set at? You may simply be filling the log to the trigger, making incremental backups happen. If this is what's happening, maybe you could expand the size of your log? [EMAIL PROTECTED]
Re: del volhist problem
HEre's the output: tsm: TSM>q volh t=dbb Date/Time: 03/21/2005 11:00:48 Volume Type: BACKUPFULL Backup Series: 112 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG044L2 Volume Location: Command: Date/Time: 03/24/2005 18:16:08 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 1 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG010L2 Volume Location: Command: Date/Time: 03/25/2005 06:01:13 Volume Type: BACKUPINCR Backup Series: 112 Backup Operation: 2 Volume Seq: 1 Device Class: LTOCLASS1 Volume Name: ITG033L2 Volume Location: Command: My issue with that idea is the database is only 13-14GB, so how could it need 3 tapes for the DB backup? I've been backing up the DB for 2 years, and it never needed more than 1 tape for it: tsm: TSM>q db Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 32,000 32,000 018,028 4,096 8,192,000 2,846,578 34.7 43. Thanks! On Fri, 25 Mar 2005, Mark D. Rodriguez wrote: It would help if we could see the output of the following command: q volh t=dbb It might be that this is the most recent DB backup in which case it won't let you delete it. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast UseHome --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error: ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. I need an answer fast as I've only got 1 scratch tape left because the dbbackups keep stealing tapes. The database is only 14MB so it should fit on one tape easy. Thanks in advance, Alex
Re: del volhist problem
Alex - You need to follow through by doing: Query VOLHistory Type=DBBackup It may be that all the dbbackups are in the same, latest series, and the last series must remain. And, certainly, you need to look into why all the dbbackup tapes are being produced. They are probably incrementals, suggesting that your Recovery Log is too small. See your Activity Log. Richard Sims On Mar 25, 2005, at 2:58 PM, Alexander Lazarevich wrote: TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast UseHome --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error: ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. I need an answer fast as I've only got 1 scratch tape left because the dbbackups keep stealing tapes. The database is only 14MB so it should fit on one tape easy. Thanks in advance, Alex
Re: del volhist problem
It would help if we could see the output of the following command: q volh t=dbb It might be that this is the most recent DB backup in which case it won't let you delete it. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Alexander Lazarevich wrote: TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast UseHome --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error: ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. I need an answer fast as I've only got 1 scratch tape left because the dbbackups keep stealing tapes. The database is only 14MB so it should fit on one tape easy. Thanks in advance, Alex
del volhist problem
TSM 5.1.9.0 on win2K server. I'm failing to delete the volume histories on the following volumes (LTO-2 tapes): tsm: TSM>q libv Library Name Volume Name Status OwnerLast UseHome --- -- -- - LB6.0.0.3 ITG010L2 Private DbBackup41 LB6.0.0.3 ITG033L2 Private DbBackup64 LB6.0.0.3 ITG044L2 Private DbBackup48 The command I run is: tsm: TSM>del volhist type=dbbackup todate=today Do you wish to proceed? (Yes (Y)/No (N)) yes ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. None of the dbbackup volumes are deleted though. Why? This has always worked in the past. Anyone have any idea? Logs don't give any error: ANR2017I Administrator DUDE issued command: DELETE VOLHISTORY type=dbbackup todate=today ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. I need an answer fast as I've only got 1 scratch tape left because the dbbackups keep stealing tapes. The database is only 14MB so it should fit on one tape easy. Thanks in advance, Alex
tracking archived data
I need ideas on how to maintain records of data that has been archived, the file name, mgtm class, when the data is due to expire. I need to be able to show proof of when the data was archived and expired in the case where a customer asks for data that we did initially archive but it has since expired and automatically been deleted. Thanks, [EMAIL PROTECTED]
TSM 5.3 new goody 03/25/2005
(from the Windows Administrator's Guide, page 132) Validating your LAN-free Configuration Once you have configured your Tivoli Storage Manager client for LAN-free data movement, you can verify your configuration and server definitions by using the VALIDATE LANFREE command. This command allows you to determine which destinations for a given node using a specific storage agent are capable of LAN-free data movement. The VALIDATE LANFREE command can also be used to determine if there is a problem with an existing LAN-free configuration. You can evaluate the policy, storage pools, and path for a given node using a given storage agent to ensure that an operation is working properly. To determine if there is a problem with the client node FRED using the storage agent FRED_STA, issue the following: validate lanfree fred fred_sta The output will allow you to see which management class destinations for a given operation type are not LAN-free capable. It will also report the total number of LAN-free destinations. See the VALIDATE LANFREE command in the Administrator's Reference for more information. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: 2 node names 1 server
On Friday 25 March 2005 18:27, Meadows, Andrew wrote: > I was wondering if anyone could help me with this. > > I have 2 oracle Database instances on one AIX 4.3 (yes I know its old) > server. This is DR Critical Data and all of our Dr critical data is > colocated onsite and off. Since this data is colocated I can only have 1 > tape moint point at a time when I am backing this data up, (I believe I > am correct here). I would like to make separate nodes for the Oracle > sessions - non TDP and back them up. I have been testing how to do this > with the following command: > dsmc -virtualnodename=aixoracle -pass=password q session > Every time I try this I am logged into tsm but no q se is run. I am > wanting to run an archive, but if I cant even do a q se I know I wont be > able to do an archive. Any help you could give me on how to do this > would be great. I will be scripting this out in ksh. The client level is > 5.2.0.0 with a server level of 5.2.1.1. Easy, create mutliple Servername stanzas in dsm.sys. Like: SErvername default nodename node1 SErvername ora-server nodename node2 In dsm.opt you can specify the default servername. You can use dsmc -se=ora-server to select a servername in dsm.sys and it will connect the nodename specified in dsm.sys. Stef
Re: 2 node names 1 server
Andrew - The dsmc command wants the subcommand to appear right after the 'dsmc', and before options and filespecs; so you should try: dsmc q session -virtualnodename=aixoracle -pass=password Richard Sims On Mar 25, 2005, at 12:27 PM, Meadows, Andrew wrote: I was wondering if anyone could help me with this. I have 2 oracle Database instances on one AIX 4.3 (yes I know its old) server. This is DR Critical Data and all of our Dr critical data is colocated onsite and off. Since this data is colocated I can only have 1 tape moint point at a time when I am backing this data up, (I believe I am correct here). I would like to make separate nodes for the Oracle sessions - non TDP and back them up. I have been testing how to do this with the following command: dsmc -virtualnodename=aixoracle -pass=password q session Every time I try this I am logged into tsm but no q se is run. I am wanting to run an archive, but if I cant even do a q se I know I wont be able to do an archive. Any help you could give me on how to do this would be great. I will be scripting this out in ksh. The client level is 5.2.0.0 with a server level of 5.2.1.1. Thanks, Andrew This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: Move NodeData and copypools
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Cory Heikel >I have 2 copypools, one for high priority DR required nodes, and the >other for everything else. The DR copypool is collocated. >Every month or >so, I get a request to move a node into the DR pools. I can >use the move >nodedata command to move things between the non-copypools, but >I need to >find a way to move data between the two copypools. If I can't get the >data moved for a node from the "regular" copypool into the >"dr" copypool >then I have to take about 500 extra tapes when we do our dr >testing, and >the multitude of tape mounts required for recovery really slows the >process down. > >Does anyone have any idea how this could be accomplished? Data cannot be moved from one copy pool to another; this is a design feature of TSM. However, there is a workaround. 1. Move MOVED_NODE's data from NORM_TAPEPOOL to DR_TAPEPOOL by running MOVE NODEDATA MOVED_NODE FROMSTG=NORM_TAPEPOOL TOSTG=DR_TAPEPOOL 2. Run BACKUP STG DR_TAPEPOOL DR_COPYPOOL This will copy all data in DR_TAPEPOOL to DR_COPYPOOL, including MOVED_NODE. MOVED_NODE's data in NORM_COPYPOOL will then be collected onto a single tape. 3. Deny access to all volumes belonging to NORM_COPYPOOL and residing in the tape library by running UPDATE VOLUME * ACCESS=READONLY WHERESTG=NORM_COPYPOOL WHEREACC=READW This will force step #4's action onto a new empty tape volume. 4. Run MOVE NODEDATA MOVED_NODE FROMSTG=NORM_COPYPOOL When finished, all of MOVED_NODE's data in NORM_COPYPOOL will reside on their own tape volume. Make a note of this new volume's number (tape 000324, for example). 5. Correct the access statuses changed in step #3 command above by running UPDATE VOLUME * ACCESS=READWRITE WHERESTG=NORM_COPYPOOL WHEREACC=READONLY 6. Now delete MOVED_NODE's data from NORM_COPYPOOL by running DEL VOLUME 000324 DISCARDDATA=YES You now have all of MOVED_NODE's data in DR_TAPEPOOL and DR_COPYPOOL. If you're naturally paranoid (like myself) you won't perform step #6 until all tapes belonging to DR_COPYPOOL are residing in your vault. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
2 node names 1 server
I was wondering if anyone could help me with this. I have 2 oracle Database instances on one AIX 4.3 (yes I know its old) server. This is DR Critical Data and all of our Dr critical data is colocated onsite and off. Since this data is colocated I can only have 1 tape moint point at a time when I am backing this data up, (I believe I am correct here). I would like to make separate nodes for the Oracle sessions - non TDP and back them up. I have been testing how to do this with the following command: dsmc -virtualnodename=aixoracle -pass=password q session Every time I try this I am logged into tsm but no q se is run. I am wanting to run an archive, but if I cant even do a q se I know I wont be able to do an archive. Any help you could give me on how to do this would be great. I will be scripting this out in ksh. The client level is 5.2.0.0 with a server level of 5.2.1.1. Thanks, Andrew This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Move NodeData and copypools
I have 2 copypools, one for high priority DR required nodes, and the other for everything else. The DR copypool is collocated. Every month or so, I get a request to move a node into the DR pools. I can use the move nodedata command to move things between the non-copypools, but I need to find a way to move data between the two copypools. If I can't get the data moved for a node from the "regular" copypool into the "dr" copypool then I have to take about 500 extra tapes when we do our dr testing, and the multitude of tape mounts required for recovery really slows the process down. Does anyone have any idea how this could be accomplished? Thanks in advance! cory *E-Mail Confidentiality Notice* This message (including any attachments) contains information intended for a specific individual(s) and purpose that may be privileged, confidential or otherwise protected from disclosure pursuant to applicable law. Any inappropriate use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. If you have received this transmission in error, please reply to the sender indicating this error and delete the transmission from your system immediately.
Experience with mixing LTO drives in a single library
I know it's supported, and the Admin Guide doesn't say very much about the actual mechanics and pros/cons of doing it, but I have a client that has a 3853 with 3-LTO1 drives. They have a very specific application that requires large capacity, but a limited budget. They are looking at adding a single LTO-3 drive to the existing library and an additional storage column. Searching the archives I did run across a post about having to use the specific FORMAT=ULTRIUMx instead of FORMAT=DRIVE to create 2 separate device classes. Then define a storage pool for the LTO-3 and direct this high capacity application to that stgpool. Anyone willing to share real-world experiences on defining the environment and any problems encountered?? They are running 5.2.3.0 on AIX 5.2. I know I need to bring them up to 5.2.4.0 for LTO-3 support plus upgrade the Atape drivers. Bill Boyer "Growing old is mandatory, growing up is optional" - ??
Re: New redbook on TSM in clustered environments
It would be nice if they included clustering in a Solaris environment in this or another Redbook. At 04:52 PM 3/21/2005, Stapleton, Mark wrote: http://www.redbooks.ibm.com/redpieces/pdfs/sg246679.pdf -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627 -- Paul Zarnowski Ph: 607-255-4757 719 Rhodes Hall, Cornell UniversityFx: 607-255-8521 Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
Re: Library sharing problem (device 3581-2U L28) TSM v. 5.2
If SCSI is directly attached to only one server and the other cannot see at all, I don't see how you will make it shared. Both servers must see any shared drive at OS level. If FC drive on LTO libr is too expensive, you can take a look at IBM 2108 SAN Data gateway router. Gus >>> [EMAIL PROTECTED] 03/25/05 8:53 AM >>> Hello! I'm trying to set up library sharing among two servers (named LM and LC) as described in IBM Tivoli Storage Manager for Linux: Administrator's Guide (http://publib.boulder.ibm.com/tividd/td/ITSML/GC23-4690-01/en_US/HTML/anrlgd5147.htm). Device I try to share: LTO 3581 Ultrium 2U tape autoloader library SCSI attached to LM server only. (Library: http://www-1.ibm.com/servers/storage/support/lto/3581-2u/index.html) On LC server is storage pools hierarchy that use library. When I'm trying to force disk storage pool data flush to tape i get following error: (on LC server) ANR8779E Unable to open drive /dev/IBMtape0, error number=2. ANR8965W The server is unable to automatically determine the serial number for the device. ANR8873E The path from source LC to destination DRIVE1 (/dev/IBMtape0) is taken offline. I realized that the configuration that I'm trying to set up IS NOT SAN! The library is attached only to one server (LM server) by SCSI and LC server does not see library special file /dev/IMBtape0 in own file system. Is possible to share that type of library among TSM servers that way? LM server: Linux/i386 Server Version 5, Release 2, Level 2.0 LC server: as above Thanks, hb
Preparing a tape storage pool volume for reuse
Unlike my previous post regarding a BACKUP DB volume, now I have a question about a Copy Storage Pool tape volume. After I used a tape volume for backup stg backuppool lto_3581_week2 I want to reuse it. Do I just: delete volume 12wk2 discarddata=yes wait=no Are there any other steps I need? If I am running TSM 5.2.2 on OS/400 V5R3 under PASE, do I need to INZTAP also? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
DELETing a volume from a DB backup
When I use a tape volume to perform backup db devclass=3581dev type=full scratch=yes wait=no How do I prepare it for later reuse? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
Library sharing problem (device 3581-2U L28) TSM v. 5.2
Hello! I'm trying to set up library sharing among two servers (named LM and LC) as described in IBM Tivoli Storage Manager for Linux: Administrator's Guide (http://publib.boulder.ibm.com/tividd/td/ITSML/GC23-4690-01/en_US/HTML/anrlgd5147.htm). Device I try to share: LTO 3581 Ultrium 2U tape autoloader library SCSI attached to LM server only. (Library: http://www-1.ibm.com/servers/storage/support/lto/3581-2u/index.html) On LC server is storage pools hierarchy that use library. When I'm trying to force disk storage pool data flush to tape i get following error: (on LC server) ANR8779E Unable to open drive /dev/IBMtape0, error number=2. ANR8965W The server is unable to automatically determine the serial number for the device. ANR8873E The path from source LC to destination DRIVE1 (/dev/IBMtape0) is taken offline. I realized that the configuration that I'm trying to set up IS NOT SAN! The library is attached only to one server (LM server) by SCSI and LC server does not see library special file /dev/IMBtape0 in own file system. Is possible to share that type of library among TSM servers that way? LM server: Linux/i386 Server Version 5, Release 2, Level 2.0 LC server: as above Thanks, hb
Re: Devclass type=generictape !!?help
Please check 'q libr f=d', 'q path f=d'. Gus >>> [EMAIL PROTECTED] 03/25/05 6:31 AM >>> Hi all When I define drive in a 3582 library . I get the following : Tsm> q dr Library Name Drive Name Device Type On-Line --- --- 3582 RMT1 GENERICTAPE Yes 3582 RMT2 GENERICTAPE Yes But my devtype is defined as LTO in the "define devclass command" as shown bellow : Tsm>q devclass Device DeviceStorageDevice Format Est/Max Mount ClassAccess PoolType Capacity Limit Name StrategyCount (MB) --------- -- DISK Random 3 LTO Sequential 0LTO ULTRI-204,800. DRIVES UMC 0 What should be done to have "LTO" in device type in "q dr" command Thank in advance Ucf. === Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. === This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ===
Re: Devclass type=generictape !!?help
Define Drive associates a drive with a Library, which in turn is associated with a Devclass. Use the Format=Detailed form of Query DEVclass to verify your "3582" library definition. The Admin Guide manual can guide you in establishing your related definitions. Richard Sims On Mar 25, 2005, at 6:31 AM, AMHOUCHE Youssef wrote: Hi all When I define drive in a 3582 library . I get the following : Tsm> q dr Library Name Drive Name Device Type On-Line --- --- 3582 RMT1 GENERICTAPE Yes 3582 RMT2 GENERICTAPE Yes But my devtype is defined as LTO in the "define devclass command" as shown bellow : Tsm>q devclass Device DeviceStorageDevice Format Est/Max Mount ClassAccess PoolType Capacity Limit Name StrategyCount (MB) --------- -- DISK Random 3 LTO Sequential 0LTO ULTRI-204,800. DRIVES UMC 0 What should be done to have "LTO" in device type in "q dr" command Thank in advance Ucf. === Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. === This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ===
Devclass type=generictape !!?help
Hi all When I define drive in a 3582 library . I get the following : Tsm> q dr Library Name Drive Name Device Type On-Line --- --- 3582 RMT1 GENERICTAPE Yes 3582 RMT2 GENERICTAPE Yes But my devtype is defined as LTO in the "define devclass command" as shown bellow : Tsm>q devclass Device DeviceStorageDevice Format Est/Max Mount ClassAccess PoolType Capacity Limit Name StrategyCount (MB) --------- -- DISK Random 3 LTO Sequential 0LTO ULTRI-204,800. DRIVES UMC 0 What should be done to have "LTO" in device type in "q dr" command Thank in advance Ucf. === Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. === This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ===
Re: ANR8963E - AGAIN
On Thu, 24 Mar 2005 08:05:58 -0500, William Boyer <[EMAIL PROTECTED]> wrote: > I've had issues with replacing LTO drives in a 3583 library. Unless I > shutdown the Windows server, then power cycled the library and > brought Windows back up I would get error trying to define the drive. It > would tell me that the ELEMENT= was not found. > > Have you verified that the MTx.x.x.x device is still the correct one? I've > had Winders recognize the replaced drive as a NEW drive > and created a different name. > > Also verify that the correct device driver is loading for the drive. If this > is Windows2000, make sure that the drive is being > controlled by the TSM device drive. For Windows2003, make sure that the tape > is using the TSM device driver. I've also seen where > Windows thinks it's a new or replaced device, assigning the same device name, > but not retaining or reloading the device driver for > it. > > Bill Boyer > "Some days you're the bug, some days you're the windshield" - ?? I had one instance where I swapped a drive on a 3583 and had Windows renumber *all* the drives, not just the one swapped; this resulted in TSM requesting tape mounts into drive 2 but then reading from drive 1 (for example) with all sorts of bizarre consequences. I had to delete all the drives from TSM, delete all the devices from Windows, reboot Windows, let Windows rediscover the drives, and then add them back to TSM before it would work correctly. Kelly
