Re: Normal # of failures on tape libraries
We have multiple IBM 3583s and IBM 3584s with LTOs 1,2, and 3s... we have not seen any issues or problems... some of them in remote sites are running without our attention for 6 months or longer. LTO is pretty solid and straight forward, you need to read the vendors manuals and recommendations and most important follow them to the last sentence. We also had to support a couple environments with LTO2s in HP libraries, we had issues with one of them, and guess what there was not the LTO technology at fault it was the rookie engineer that installed them... after a few weeks of grief he brought in a top gun correct the problem and we never had any issues since then. If DLTs worked fine, for sure LTOs will work fine as well, you might want to update your drivers, firmware, and follow the Vendor's recommendations, key element here. Happy Holidays. Othonas len boyle [EMAIL PROTECTED] M To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Normal # of failures on tape libraries 12/14/2005 08:47 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hello James What make/model of libraries/drives and the firmware levels are you using. We have an 3584 with lto-2 drives that were very free of problems for the first year or so. But now we are seeing more and more errors. The errors change as we change the firmware level on the drives. len - Original Message - From: Brents, James [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, December 14, 2005 8:30 AM Subject: Re: [ADSM-L] Normal # of failures on tape libraries That is my experience. We went from DLT libraries to LTO libraries at our remote sites and now we are working on libraries every week! James Brents -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Melburn W IT743 Sent: Tuesday, December 13, 2005 1:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Normal # of failures on tape libraries Ahh, so it's the fact that they are LTO drives. So as far as LTO drives go then, what I am experiencing is normal? Mel Dennis -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, December 13, 2005 2:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Normal # of failures on tape libraries I agree. My 3590's (both B and E1A models) have been through major pounding, for many, many years, and like the Energizer Bunny, keep going and going. Yes, they do need some repairs/maintenance, but considering the amount of data/mounts/tapes they go through on a daily basis, they are like tanks. Never had a whole drive, replaced. Usually things like cleaning brushes, sometimes R/W heads, 2-3 card-packs, stuff like that. This in contrast to my [EMAIL PROTECTED]* IBM 3583/3580 LTO2 drives, which over the 1.5-years I have been using them, all 8-drives have been replaced, at least once, some more. I haven't kept strict tabs on them, but considering I just had 3-replaced over the past 2-weeks, from my experience, LTO2 drives are garbage. They require weekly, if not daily, attention. The 2-LTO libraries have 300-tapes between them, the 3494 library with the 3590 drives has over 3700, with 400+ mounts a day ! FWIW, when I went to a storage show-and-tell-and-try-to-sell, the ADIC folks told me they OEM their drives from IBM ! Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 12/13/2005 02:01 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Normal # of failures on tape libraries On Dec 13, 2005, at 11:31 AM, Dennis Melburn W IT743 wrote: Our sites use ADIC Scalar 1Ks as well as one ADIC 10K. The Scalar 1Ks have 4 LTO1 drives in each and the 10K has 34 LTO2 drives. We experience occasional failures on these drives and have to replace them. My question is, is it normal for a site that has alot of drives to experience drive failures about every 1-1.5 months? My manager is rather annoyed at the fact that it seems that we are constantly replacing drives even though it doesn't cause any downtime for our TSM servers while they are being replaced. If this is a normal part of having tape libraries then that is fine, but I don't have enough experience in this field to say either way, so that is why I am asking all of you. Customers with 359x drives (which are never replaced) would certainly find that replacement frequency
Re: TSM/Veritas
Yes, is possible, we have a couple installations running where the same library supports both backup products, with IBM3584, and with L700. I am pretty sure you can do it with all the large scale libraries provided that the library supports true sharing and zoning. Brgds, Othonas Xixis IBM Global Services/Strategic Outsourcing Gill, Geoffrey L. GEOFFREY.L.GILL@ To SAIC.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject [EMAIL PROTECTED] TSM/Veritas .EDU 05/05/2005 05:11 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU I was wondering if anyone out there is, or has dealt with this. We know that it is physically possible to attach 2 TSM servers to a library and run each independently of the other. The question I have is, is it possible to run 2 systems to the same library, knowing each will have their own dedicated drives, when one is running TSM and the other Veritas? Thanks for any info you can provide, Geoff
Re: Can't define IBM3583-L72 LTO library to TSM
Zoltan, are you also the AIX admin ? per what your are stating in yr emails that you have performed all the TSM steps by the book, then there is something from the library interface to AIX that is not allowing TSM to properly handshake and access /dev/smc0... does AIX has all the latest ptfs (scsi, fiber, etc.) ? the fact that lsdev works is not securing 100% that you have the proper ptfs... have you rebooted the physical AIX server ? also have you tried to change the main/1st cable that connects the library with yr physical AIX server ? Have you called IBM hardware support, has a CE reviewed yr problem ? Good luck. Othonas
Dublicate TSM's DB or Data Tapes (3590, LTO) ... not within TSM
Hello TSM'ers, Does anyone know of a way or a company where the TSM DB or Data Tapes can be duplicated (in a hardware level) ? I do understand the duplication methods within TSM and I am not interested at this time because I can't use them. We are in a real disaster recovery situation, not where we lost the TSM server, but where we lost portions of the data on the tapes, and now we have legal requirements that we need to fulfill. Thanks in advance for yr assistance. Brgds, Othonas Xixis
Re: Using Backupsets for Disaster Recovery
Mike, backupsets... back in version 3.7... where mainly designed for server/network less restores, if these restores are part of the everyday workload/design then fine, they will do the job, if they are part of the DR scheme/design then again is fine, it all depends on yr overall design. Backupsets are reliable and they are working as advertised and designed, maybe not as user/admin friendly as we would like to have them, however reliable. The excessive number of objects can be resolved in the Operating System level and design, with a packaging/zipping tool. Also, since I was part of the TSM 5.1 Beta testing, I would like to inform you that in TSM 5.1.x there are a couple performance enhancements for the backupset processing, therefore the future is there as well. Cheers. Say Hi to Brad Virgil... Othonas Xixis Intelligence, imagination, and knowledge are essential resources, but only effectiveness converts them into results. By themselves, they only set limits to what can be attained, Peter F. Drucker. Michael Moore [EMAIL PROTECTED]@VM.MARIST.EDU on 05/01/2002 01:28:31 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: Using Backupsets for Disaster Recovery John, To answer your questions.: Yes, MPThreading is turned on. Yes, it is getting plenty of processor. Region is set at 512M. I have sent to IBM dumps that were taken during the hung periods. What I have been told, is that there is a large number of locks being generated during that period, and that everything is working as designed. I can see why there are a large number of locks. The backupset that causes this has 1.6+ million objects (and growing daily). I have also been told that soon there will be another client node the same size (200+gb). The biggest hurdle for me to overcome is the reliance on these backupsets for DR purposes. As far as I can tell, they were not originally designed for DR purposes. If they were, I believe they would be managed under DRM. Michael Moore VF Services Inc. 121 Smith Street Greensboro, NC 27420-1488 Voice: 336-332-4423 Fax: 336-332-4544 Seay, Paul seay_pd@NAPTH To: [EMAIL PROTECTED] EON.COM cc: Sent by: Subject: Re: Using Backupsets for Disaster Recovery ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 05/01/02 11:59 AM Please respond to ADSM: Dist Stor Manager My situation is very different from many TSM sites. I have no tape drives in my servers so I have no way to create backupsets that can be read by the client because 3590 is not supported based on what I know. And, anyway, it would not be feasible. Sorry, I did not fully explain why they are too cumbersome for my environment. When you have as many servers as I do and they all have hundreds of gigabytes it is just not feasible. Different strokes for different folks. That is the beauty of TSM. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 5:49 AM To: [EMAIL PROTECTED] Subject: Re: Using Backupsets for Disaster Recovery Michael, At last, something I do not entirely agree with from Paul. I would not use backupsets for everything, but they are excellent for speading up the restore of large data servers. Provided you take them regularly and I think twice weekly is overkill, then the fromdate overhead to bring in subsequent backups is not too great. I think weekly or every two weeks would be adequate, but I suppose the answer for you is to test to see what meets your recovery requiremnts. I do not think that your server should be hanging. Are you running MPThreading Yes ? If you are satisfied that TSM is getting enogh processor,check with your OS390 performance person, then the other thing to check is how long since TSM was recycled, It is common for OS390 systems not to need an IPL for months at a time and for TSM only to be recycled when these IPLs come along. In my experience TSM does get slower if not regularly recycled, and I would suggest that this should be done on a monthly basis. Hope this helps, John Seay, Paul [EMAIL PROTECTED] on 05/01/2002 09:20:13 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Using Backupsets for Disaster Recovery We do not because it is too cumbersome. The answer is what were Backupsets really created for? When Tivoli Sales comes in they sell backupsets as a way to send a remote user/site (laptop users are the main ones) a place
Re: Anyone seen this ABORT/COREDUMP on AIX 4.3.3 TSM Server 4.
Camplell, as Henk inform you, you should consider going to 4.2.1.11. There were a lot of fixes between 9 and 11. Cheers. Othonas Xixis Intelligence, imagination, and knowledge are essential resources, but only effectiveness converts them into results. By themselves, they only set limits to what can be attained, Peter F. Drucker. Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: Anyone seen this ABORT/COREDUMP on AIX 4.3.3 TSM Server 4. Henk, thanks...I located the URL on the Tivoli website taking you to the same FTP site you use in the note below. It is a one-liner on the web-page for the TSM server downloads/fixes page. Had been unable to get to the Tivoli pages for a day or two. Thanks Campbell Origin-Original Message- OriginFrom: Henk ten Have [mailto:[EMAIL PROTECTED]] OriginSent: Tuesday, March 12, 2002 3:09 PM OriginTo: [EMAIL PROTECTED] OriginSubject: Re: Anyone seen this ABORT/COREDUMP on AIX Origin4.3.3 TSM Server Origin4. Origin Origin Origin Campbell: Origin Origin Henk, thanks. ..please identify where I can get Originthis 4.2.1.9 code and Origin README's? Origin Origin service.boulder.ibm.com, which you can find in one of Originyour (old) Origin README's, also a couple of mirror sites. Origin Origin I can only see 4.2.1.7 AIX server code on the Tivoli Websites. Origin Origin I never use the Tivoli Websites for server code. Origin Origin Cheers, Origin Henk. Origin
Re: 3494 through SAN Data Gateway
Eric, in case Adolph's recommendation don't work, or cfgmgr gives you another error then the problem is with your 2108 SAN Data Gateway (SDG). Go into the SDG (SAN Data Gateway) firmware and execute the following actions: 1) disableCC 2) setHost 0, aix or setHost 0 AIX 3) setHost 1, aix or setHost 1 AIX 4) and reboot the device. 5) remove the tape drives (rmdev -dl rmt?), the fiber object (rmdev -Rdl fcs?), and then rerun cfgmgr. This action should let see the SDG transparent to the cfgmgr routine. Cheers. Othonas Xixis Loon, E.J. van - SPLXM [EMAIL PROTECTED]@VM.MARIST.EDU on 02/05/2002 01:00:33 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3494 through SAN Data Gateway Hi Adolph! Thank you very much! I will install it tomorrow. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Adolph Kahan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 05, 2002 18:54 To: [EMAIL PROTECTED] Subject: Re: 3494 through SAN Data Gateway This is part of AIX. It will be on the AIX install CDs. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Loon, E.J. van - SPLXM Sent: Tuesday, February 05, 2002 12:41 PM To: [EMAIL PROTECTED] Subject: 3494 through SAN Data Gateway Hi *SM-ers! I have just connected a 3494 library through a SAN Data Gateway. When I run cfgmgr is detects the drives: rmt5 Available 10-68-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt6 Available 10-68-01-4,0 IBM 3590 Tape Drive and Medium Changer (FCP) But it also returns the following error: cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.fcp.array This driver, is it a AIX driver or is it part of the TSM devices package? Thanks in advance!! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: Compression Ratio ?
Andy, what is the official TSM Client (4.2.n +) compression ratio ? I know that it can vary depending of the type of the data, however there should be an announcable number that admins can use to project. Thanks in advance for yr response. Brgds, Othonas Andrew Raibeck/Tucson/IBM@[EMAIL PROTECTED] on 01/22/2002 09:12:17 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject: I forgot to mention: Starting with the 4.2 client, you can now use include.compression and exclude.compression client options. For example: exclude.compression *:\...\*.zip will prevent any *.zip file from being compressed, even if COMPRESSION YES and COMPRESSALWAYS are in effect. However, the 4.2 client is not supported with the 3.1 server. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. - Forwarded by Andrew Raibeck/Tucson/IBM on 01/22/2002 07:10 - Andrew Raibeck 01/22/2002 07:04 To: ADSM: Dist Stor Manager [EMAIL PROTECTED] cc: From: Andrew Raibeck/Tucson/IBM@IBMUS Subject:Re: ADSM and TSM do not know that a file is compressed, per se. However, it does detect if the file is growing during compression (which is most likely because the file is already compressed). If the file grows during compression and COMPRESSALWAYS YES (the default) is in effect, then it will keep compressing the file anyway. This is causing the negative compression that you are seeing. If COMPRESSALWAYS NO is in effect and the file grows during compression, then all files in the current transaction will be resent to the server, but the file that grew wll be sent uncompressed. The trade-off is that in resending all the other files in the current transaction, you may see a performance degradation in over-all elapsed time, especially if there are lots of files that grow during compression. Regard, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Wolfgang Rest [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 01/22/2002 06:04 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject: 01/21/2002 21:41:55 ANE4952I (Session: 196, Node: APOLLO) Total number of objects inspected: 129,216 01/21/2002 21:41:55 ANE4954I (Session: 196, Node: APOLLO) Total number of objects backed up: 43,830 01/21/2002 21:41:55 ANE4958I (Session: 196, Node: APOLLO) Total number of objects updated: 0 01/21/2002 21:41:55 ANE4960I (Session: 196, Node: APOLLO) Total number of objects rebound: 0 01/21/2002 21:41:55 ANE4957I (Session: 196, Node: APOLLO) Total number of objects deleted: 0 01/21/2002 21:41:55 ANE4959I (Session: 196, Node: APOLLO) Total number of objects failed: 4 01/21/2002 21:41:55 ANE4961I (Session: 196, Node: APOLLO) Total number of bytes transferred: 5.11 GB 01/21/2002 21:41:55 ANE4963I (Session: 196, Node: APOLLO) Data transfer time: 911.71 sec 01/21/2002 21:41:55 ANE4966I (Session: 196, Node: APOLLO) Network data transfer rate:5,886.47 KB/sec 01/21/2002 21:41:55 ANE4967I (Session: 196, Node: APOLLO) Aggregate data transfer rate:992.76 KB/sec 01/21/2002 21:41:55 ANE4968I (Session: 196, Node: APOLLO) Objects compressed by: -16% 01/21/2002 21:41:55 ANE4964I (Session: 196, Node: APOLLO) Elapsed processing time:01:30:05 Objects compressed by: -16% ?!?!?! How can this be? There are many .zip Files on this Server.. but i thought ADSM will check if a File is already compressed and dont compress it again. I am running on Client side 3.1.0.8 and Server 3.1.2.90 best regards
Re: Automated procedure/ script to perform Checkout of dailydbbackup vol
Richard, does the REMove=Yes eject all the tapes out to the I/O bin of the 3583/4 LTO Library ? have you test your script on LTO libraries ? Pls adv. Brgds, Othonas Richard Sims wrote: Here is my request : I would like to perform a daily checkout of my dbbackup(full) volume from the tape library (LTO 3583) without having the operator issue the checkout libv command. All I want the operator to do is to open the I/O station and remove the tapes. Is there any solution ??? I've set up a procedure/script to perform the automated checkout of volumes from the library but unfortunately, I've hit a wall on how TSM can pass a list of volumes to the checkout command . Here is an example of my script : Lee - I faced the same thing in implementing our poor man's DRM, and after a lot of brain-wracking came up with the solution of having our morning administration Server Script dynamically create, plant, and execute a subsidiary Server Script to do the deed, like: - /* Get the volname of that backup and create a secondary script to eject it... */ Query DRMedia DBBackup=Yes COPYstgpool=NONE BEGINDate=TODAY Format=Cmd - CMd=CHECKOut LIBVolume OurLibName VOL CHECKLabel=No REMove=Yes CMDFilename=/tmp/ADSM-DBB-EJECT-SCRIPT APPend=No if (RC_OK) goto query_drm_eject_ok DEFine CLIENTAction OurNode ACTion=Command - OBJects='mail -s Query DRMedia failed for todays dbbackup adsm-admin@OurFairCity /dev/null /dev/null' goto query_drm_eject_bottom query_drm_eject_ok: DELete SCRipt TEMP-DBB-EJECT-SCRIPT DEFine SCRipt TEMP-DBB-EJECT-SCRIPT File=/tmp/ADSM-DBB-EJECT-SCRIPT RUn TEMP-DBB-EJECT-SCRIPT query_drm_eject_bottom: - Note that you don't have to have DRM to use Query DRMedia: it's one of those generally exploitable resources, which came in handy for us. Richard Sims, BU
Latest LTO firmware levels ?
Hi, does anyone know the latest firmware levels for the 3584 LTO library, and 3580 LTO drives ? My tape drives are at version: 16E0 , and my 3584 is at version: 1450 . Pls adv. Brgds, Othonas Xixis
Re: NT Performance issues
Hi Tony, did you used the same crabby network with arcserv ? or you were backing up to local drives ? Seems like there is network issue in yr environment... have u tried to ftp from the TSM server to any TSM client ? how is the performance there ... rubbish ? probably... It is not a TSM issue friend, its a resources issue outside of TSM (network, memory, etc...). GLuck. Cheers. Othonas Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: NT Performance issues Hi All, I run the NT TSM 4.1.x.x at client (43 clients) and Server and performance is rubbish... Arcserve was 100 times faster!!! (Min.) I have applied all the tuning covered in the Tivoli Adv.Mgmt course... and can't get much past 1MB/sec So that I can justify (or not) retaining Tivoli Any ideas where its all gone wrong I will send details of my setttings/hardware to anyone interested Is it really just a crabby product??? Rgds Tony Morgan Fortis Bank UK
Re: MediaW, Tape drive availability,Disk STGpool space and understan ding what TSM is doing....
Hi John, First let me comment on yr first question/observation: "I am seeing times that a TSM server has more tapes mounted than would be necessary for Administrative tasks like migration and backup of storage pools." answer TSM (without migration settings, client schedules, admin schedules, etc.) does not initiate any jobs that will require mounting tapes and copying data etc. everything is controlled by the configuration layout. You might have a few issues in yr installation: a) Looks like that your environment lacks of sufficient scheduling. 1) You need to start from your requirements, then evaluate your existing resources (libraries, drives, tapes, network, etc.), 2) then prioritize the activities, 3) then create the schedules that have been designed on your environment, 4) then run them for 1 to 3 weeks and monitor your server very closely, 5) then go back and make any necessary adjustments to your scheduling strategy, (you might have to repeat steps 3 to 5 a couple times, until you get the best fit setting. b) Do you control the migration processes with administrative schedules or not ? looks like that you don't... What you can do is: create admin schedules that set the migration thresholds to higher numbers like 89, 90, etc. and when you four tape drives are not busy, then you set another set of admin schedules that will set the migration threshold to zero and will start the migration processes. c) Prioritization. You need to make the decision what activities have higher priority, and use the scheduling time in conjunction with TSM's priorities levels to accomplish your goal. d) In a normal/standard TSM environment TSM operations need to occur in a sequence that will satisfy yr customized requirements. Below is a basic sequence of events that works... 1) Run your backups (Incr/Arch/TDPs/etc/). From 4:00-7:00 pm to something like 1:00-3:00 am. (You can also have TDP Databases' archive logs, and backups running through out the whole day, but if you can control and influence... try to have and set a recovery timeline or next day cutover point, especially if you are using DRM and have offisite requirements and DR tests... "the works"... ). 2) Activate your migration processes and empty yr disk pools. From 2:00-3:00 am to 4:00-5:00 am. 3) Make copies (backup) of your tape storage pools (onsite/offsite). From 4:00-06:00 am to 07:00-10:00 am. 4) Make a database backup (offsite copy). Around 10:00 am. 5) Run your Disaster Recovery stuff (DRM)... if applicable. 6) Eject the DRM offsite tapes. Around 11:00 am. 7) Make another database backup (snapshot) to keep on site... if applicable. Around 12:00 pm. 8) Expire inventory. Around 01:00 pm. 9) Start your "controlled" reclamation processes. Around 02:00 pm. If you have two many storage pools, and you think that 3 to 5 hours is not enough for your whole reclamation process, you might want to group yr storage pools and spread them across the week ( 1 group on Mondays, 1 group on Tuesdays, etc.) This last step will bring you to the 4:00 to 6:00 pm time frame, where you nightly backups start, go back to step 1. The above times are imaginary, but they work fine in most of our TSM installations, again the scheduling times depend on your local customized backup and restore requirements. e) Limited resources. At the end of the day... you might realize that you don't have enough resources to accommodate your requirements, then you have two options: 1) either go back and modify or rethink yr business requirements, or 2) add some extra $$$ on next year's budget and add more tape drives to your library. Since, now you are getting 2 more tape drives... and you will have a total of 6 tape drives, is a good opportunity to take some time and redesign your TSM internal scheduling scheme. I always like to have an odd number of tape drives: like 5 or 7 or 9 etc... because the backup storage pools processes occupy 2 drives per process, so if you run 2 or 3 processes it will occupy all your drives (2x2=4, 3x2=6,)... and you will not have any drives available for any other TSM activities or restore requests... just a thought. f) Network. The network is another great variable on your scheduling environment, because if you have the best TSM structure and you have a poor network then you will still have problems. I hope that you have dealt with the network issue. g) TSM and Operating System tuning. From what I see from the NT sessions some ran for a long time, and is hard to identified by only the below report, but you might have some tuning issues in your environment, provided that your network is fast enough. Finally, I don't think that there are classes that deal with customized requirements and scheduling issues, however you might find consulting firms that they can come in for a day or so and help you out. Cheers. Othonas "Talafous, John G." wrote: This is more
Re: URGENT ? ABOUT DB RESTORE
Steve, you don't need to check in the db tape. Since the tape is in the library, make sure that the devconfig file and the dsmserv.dsk are present in the TSM installed path: and then issue the following command from the OS prompt: dsmserv restore db volumename=VOLSER devclass=DEVCLASS commit=??? todate... ... You can acces the manual online: http://www.tivoli.com/support/storage_mgr/pubs/v4pubs/v1_html/aix/guide/anratfrm.htm Part#5, Chapter#21 and see what type of restore do you need, and customize the above command according to your environment and needs. If u r using DRM and the prepare command, then find the last prepare file and follow it thru... GLuck. Othonas -Original Message- From: Steve Hicks [mailto:[EMAIL PROTECTED]] Sent: jeudi 22 fvrier 2001 17:11 To: [EMAIL PROTECTED] Subject: URGENT ? ABOUT DB RESTORE Need to restore out TSM database but the volume that the DB backup in on is listed as VAULT. I have the tape in the automated library, how do I check it in to restore from it??
Re: Trying to define a 3494 Library
Eric, 1) can u ping 171.21.121.5 ? 2) after u ran the # cfgmgr did u check if the lmcp0 is available ? 3) can u ask yr CE toi make sure that the library is online and ready for operations ? 4) before u define the library in TSM, issue the following command: # mtlib -l/dev/lmcp0 -qL if that works u r ready for TSM, if not then u have other issues that u need to resolve first... Cheers. Othonas Tom Melton [EMAIL PROTECTED]@VM.MARIST.EDU on 02/20/2001 11:28:06 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Trying to define a 3494 Library Try talking to the library from outside ADSM. Use the mtlib command to query the library, to get some status info from it. That will verify the necessary serial/ethernet connectivity to the library. I see that you are talking ethernet to the library. Have you authorized your ADSM machine access in the library controller. I think you have to give the ip address of the ADSM server in the IP setup of the ATL. Tom Melton Emory HealthCare Emory University [EMAIL PROTECTED] 02/20/01 11:20AM Hi *SM-ers! I am trying to add a 3494 library to our TSM 3.7 server on AIX 4.3.3. I have performed the following steps: 1) I have installed Atape 5.4.4.0. 2) I have installed atldd 4.1.5.0. 3) I have defined the library in the /etc/ibmatl.conf file by adding the following line: 3494-L1 171.21.121.5 3494-L1 4) I used SMIT to configured the LMCP by using the "Add a Tape Drive" option. I selected the "atl library LAN/TTY Library Management Control Point". I selected the Library Name 3494-L1 which was retrieved from the /etc/ibmatl.conf file and it created a lmcp0 with the status defined: lmcp0 Defined LAN/TTY Library Management Control Point 5) I used the SMIT option "Configure a Defined Tape Drive" to make the drive available. It's now listed as: lmcp0 Available LAN/TTY Library Management Control Point 6) I ran CFGMGR which loaded the deamon. 7) I went to TSM to define the library by using the command: def libr 3494-L1 libt=349x device=/dev/lmcp0 This returns the following error: ANR8444E Internal Operation: Library 3494-L1 is currently unavailable. ANR8418E DEFINE LIBRARY: An I/O error occurred while accessing library 3494-L1. I'm stuck here. Can anybody help me by pointing me to the right place for more information? Am I forgetting something? Thanks in advance for any reply!! Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: TCP Session lost during restore
Stefan, I have seen these errors before in Informix Oracle TDP environments: actually, I was getting the same socket # (4294967295)and (sessRecvVerb: Error -50 from call to 'readRtn'). From a first look, I believe that you are getting these timeout errors due to the application or due to the network/TCPIP. A quick and dirty remedy to this problem is to increase the commtimeout parameter in your server. Now is set to 15 minutes (900), set it to either 20 (1200) or 30 (1800). You don't have to have to recycle TSM, just do a setopt commtimeout 1800 . Also you can check the network (dropped pockets ? etc.) or at the application level (Exchange) to see why you are getting a delay of more than 15 minutes, and if is correctable... Cheers. Othonas Stefan Holzwarth [EMAIL PROTECTED]@VM.MARIST.EDU on 02/20/2001 07:27:00 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TCP Session lost during restore During Restore of a large File (30GB Exchange DB - production) the client (3.7.2.01 and 3.7.2.17) gets the following error in the errorlog: (Server 3.7.3.8 @ OS/390) 02/20/2001 12:24:05 sessRecvVerb(): Invalid verb received. 02/20/2001 12:24:05 sessRecvVerb(): length=, verb=26,magic=00 02/20/2001 12:24:05 TcpFlush: Error 10038 sending data on Tcp/Ip socket 4294967295. 02/20/2001 12:24:05 sessRecvVerb: Error -50 from call to 'readRtn'. 02/20/2001 12:24:05 ANS1809E Session is lost; initializing session reopen procedure. 02/20/2001 12:24:20 ANS1810E TSM session has been reestablished. A test restore in the same environment (NT 4 Server, SP6a, Madge ATM, 3.7.2.01) some weeks ago did not show this problem. A test over Tokenring (instead of ATM on the same machine) had the same problem. Client Option file:--- TCPBUFFSIZE 512 TCPWINDOWSIZE 63 -End client option file -- Server Options- COMMTIMEOUT : 900 IDLETIMEOUT : 90 Server Options End - Who has seen this before? -- Stefan Holzwarth ADAC e.V. (Rechenzentrum, Produktionsplanung und Organisation) Am Westpark 8, 81373 Mnchen Tel.: (089) 7676-5212, Fax: (089) 76768924 -BEGIN GEEK CODE BLOCK- Version: 4.0 GCM/S d- s+: a C+(++) ULA++ P+++ L+(++) E--- W+++ N++ o-- K? w+(++) O+ M V? PS+ PE Y+ PGP-+ t+ 5+ !X R tv b !DI D G e+++ h--- r z? ---END GEEK CODE BLOCK-
Re: Delete single file
Have you try to exclude the file ? In the dsm.sys file (AIX example): ... ... Inclexcl /usr/tivoli/tsm/client/ba/bin/inclexcl.txt ... ... In the inclexcl.txt file: ... exclude /filesystem/directory/filename.ext ... That will take care yr problem in the next backup and the next expire inventory process. There is a way to digg in the TSM database and delete the file, but is very sensitive and easy to destroy yr database integrity... and at the end of the day is not going to help you much, if the next night you back it up again, so you have to deal with the root case of yr problem, just don't back it up. Cheers. Othonas Joe Spade wrote: Does anyone know of a way to manually delete one file off backups. I don't want to change the management policy on retention. We have a single big file that gets backed up daily. It also gets deleted daily. The name changes on a daily basis, so we start taking up a lot of tape space in the deleted retention. I need to delete the one file manually.
Re: Activity log
What R U trying to hide LOL Look in the following two server settings: Activity Log Retention Period Activity Summary Retention Period Rgds, Othonas Shekhar Dhotre wrote: Hi all , How i can clear all activity log entries till today from TSM database ? Thanks in Advance . shekhar
Re: actlog
Hi Shekhar, I know where you are coming from... being there a few times myself... therefore personally, I believe that any human resources issues need to be resolved outside of the TSM technical domain... one day you guys will need the activity report to troubleshoot or solve a problem and you will not be able to go back and see what happened. If you allow me a friendly advice, set your Actlog Retention Period back to 7 or 32, and solve the human resources issue outside TSM or any other tool or business process. On the technical question, I don't know of any other way to delete the events immediately, maybe the Tivoli developers can help you on this one. Cheers. Othonas
Re: Migration Processes from Diskpools to Tape Devices
Hagen, 1) how many nodes/clients do you have (backup) ? 2) how many disk stg pools do have ? 3) what is yr collocation setting on the tape stg pools ? 4) How many tape stg pools do you have ? 5) what type of network to you have between the clients and the TSM server ? Additionally, disk pool is not always the best fit solution for an environment, you might want to reconsider and distribute the load between the tape drives and the disk pool. You might want to send your "haviest" node to the disk pool and have your other clients go directly to tapes. Or if you have TDP modules and you have a lot of logs, you also might want to consider sending only your logs to disk stg pool. Regards, Othonas Hagen Finley [EMAIL PROTECTED]@VM.MARIST.EDU on 02/17/2001 12:37:23 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Migration Processes from Diskpools to Tape Devices We recently added 40 GBs to our backup diskpool in an effort to speed up our backup processes. In large part that has worked, however, now we find the tape devices sit idle all night and, to make matters worse, the migration process from the diskpool to tape (a six 3590 3494 library) does not seem to engage more than one drive. So I believe we are actually worse off now because we have merely moved the bottleneck from the client to the server to the diskpool to the tape device and now our tape drives sit idle most of the night. I have contacted TSM support (we are at 4.12) and they indicated that the migration processes setting (which has been set as high as 6) does not translate to tape drive mounts as I might have imagined. Instead in a logic I found difficult to follow, processes are linked to nodes or at least node filespaces in the backup pool. From their perspective there appears to be no way to specify migration tape mounts. What we are aiming for is a large enough diskpool to buffer the entire night's backup volume and then to run our copypool process for offsiting our copy tapes followed by a migration of the data from the diskpool to the resident tapes in the library (disk caching is not really a goal at this time). We can throw a couple hundred GBs at the diskpools, but that is no help if we can't get the data off the disks in a timely manner. If we could get the offload to both the copypool and the local library to take place on multiple drives I think our plan could succeed. Can anyone shed any light on how we might achieve our aims? Kind regards, Hagen Finley Longs Drugs
Re: 3590E
Debbie Hi, You are correct, there is sensitivity nature issue with the 3590 E (Extended length) tapes or "K" type or Condor. I was told that if you drop a "K" cartridge from a height as short as 4 inches would cause the tape to be unusable. I've not seen this in print but this indicates how seriously important good tape handling practices are. If you encounter a problem with the IBM "K" tapes exhibiting errors you should call 1-888-IBM-MEDIA and ask for replacement under warranty due to the fact that they will not "initialize" new out of the box. (this is important). Be sure to stress to yr tape operators (especially if you have off-site requirements) that the increased density of the K media (there are 256 lengthwise data tracks) DEMANDS proper handling. With the 3 to 1 compaction algorithm, these cartridges can contain over 100+ Giga Bytes of data, so the data lost risks are very high. As far as off-site shipment for vaulting purposes, it is suggested "turtle boxes" as outlined in the 3590 Tape Care and Handling Guide but are asking that these boxes also be double boxed with bubble pack to absorb any impact the cartridge might receive during shipment. Brgds, Othonas Debbie Lane wrote: oops, The drive is a 3590-E1A. The tapes in question are the "K" higher capacity tapes. -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 14, 2001 1:27 PM To: [EMAIL PROTECTED] Subject: Re: 3590E We recently started using 3590E tapes. Several of them are damaged. We talked to IBM support, and it sounds like other customers have had similar problems. I am wondering if any of you have experienced 3590E damaged in shipment? Have you had other problems with the 3590E? I think you mean 3590E drives. We had one upgrade kit damaged in shipment, thanks to the trucking company. One upgrade kit had a defective card pack, and it took over three weeks for the replacement to arrive - from Mexico. From what I hear, the defect rate from that plant is pretty bad, with drives misconfigured or otherwise inoperable, and has become an issue within the company. Richard Sims, BU
Re: expiring Informix logs ...?
Arnaud hi, I am a little troubled understanding why you say that "TSM is unable to expire those logs". If you use a separate mgmt class and copygroup for your logs, and your copygroup parameters are set properly, TSM will expire your logs. Maybe if you want to give us some more details of yr installation... Cheers. Othonas PS: I bet Basel is beautiful this time of the year... Arnaud Brion [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 11:01:42 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: expiring Informix logs ...? Hi everybody ! I come back on something that seems to be an old subject for *SM'ers : we're using the Onbar API to ensure the backup of our informix logs, what works really nicely, except we're facing a huge increasing of the number of tapes used for this storagepool, due to the fact that TSM is unable to expire those logs. We tried to install the onsmsync utility a few month ago, which was supposed to give us a rid of this problem, but I just saw today that it isn't working at all ! Does anybody know if Informix or Tivoli found a solution to this problem (new version of onsmsync ?), or if there is any other way expiring those #@#@@... logs ? I saw there is a c programm existing but I have no idea of c language so if you know something easier, just let me know ! Thanks in advance ! ;-) Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78/Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: TDP for SAP R/3 compression vs. TAPE DRIVE compression
Demetrius, you are fine... the RL_COMPRESSION should be set to YES, while the 3590s are doing their own compression. The RL_COMPRESSION is more likely a SAP "software" compression, therefore is improving yr overall compression packaging. You will be surprise of the reduction rate after you set the RL_COMPRESSION to yes, of-course also depends of the database that you use for SAP (Oracle, Informix, etc...), and how empty (null and zeros) are your tables and dbspaces. Cheers. Othonas "Malbrough, Demetrius" [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 12:54:05 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: TDP for SAP R/3 compression vs. TAPE DRIVE compression Good Afternoon, *SMers SAPsters! I wanted to see if I could pick your brains for a second! What happens if you are performing null block compression before sending the data over the network to the TSM server (RL_COMPRESSION YES in the SAP R/3 profile) and also using Tape Drive compression (3494 ATL w/ 3590 drives on Solaris FORMAT=3590C via device=/dev/rmt/#stc)? Will the data grow due to being compressed twice or compression on the SAP R/3 side is so simple it does not affect Tape Drive compression? Thanks, Demetrius A. Malbrough ADSM/TSM Consultant Texas Instruments 6550 Chase Oaks Blvd. Plano, TX 75023 (972) 927-9869 Office (214) 314-3350 Pager [EMAIL PROTECTED]
Re: expiring Informix logs ...?
Hi George, I am fine, busy as always... thanks for asking, how is San Antonio ? On this Informix issue, I guess Arnaud did not mentioned, and I didn't realize at first that he was using SQL-BackTrack. Tivoli nowadays has a new TDP for Informix 4.1 and works fine. We had three Informix installations lately and we installed the TDP for Informix on all of them (onbar - online, full, L0, L1 backups) and things are working great, without using SQL-BackTrack. Again, and even with the TDP, all the DB data and the log data is expired via TSM management and copygroup configuration because Informix can't control and pass the expiration information to the API. Informix, *SM API, and SQL BT versions is the main factor to tune and make all three products to work appropriately. Thanks. Othonas George Lesho [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 03:21:12 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: expiring Informix logs ...? Howdy Othonas! Hope you are doing well... haven't heard from you in a while... I think the problem with doing expiration and reclamation of backups made with SQL-BackTrack for Informix lies in the fact that if you use an older version of the product, the agent places a long time stamp on the filespace name making each name UNIQUE. Thus, you are left with a zillion unique filespaces, each being an ONLY version of a db backup. This truly complicates expiration you basically must go in and erase filespaces manually. With the newer version of SQL-BackTrack for Informix, it has the ability to delete back generation of a database. The generations term is used by BMC to distinguish between versions as each Informix backup is actually unique. It appears you can only retain 9 unique generations at most; meaning if you backup up daily, the most you can retain, using the agent is 9 days worth. You can also expire using a date. These features only became available on V.3... we are testing it now and it is a pain to install... BMC's directions are not great ;-(. Anyway, I am far from an expert in these matters but I do have some experience with deleting filesets which is necessary, even if you put backups into their own management class/copy group. BTW: I have completed implimenting all the recommendations you made and just finished documenting the whole mess. During the course of the documentation, I redid all management classes, copy groups and schedules to make them work the way we wanted and have everything revolving around our logical business day as you suggested. The redbook has some good tips on scheduling stuff so that our admin processes are not overlapping with backups and such. Thanks- hope my rambling made some sense... George Lesho Storage / System Admin AFC Enterprises Othonas Xixis [EMAIL PROTECTED] on 02/13/2001 10:28:39 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: expiring Informix logs ...? Arnaud hi, I am a little troubled understanding why you say that "TSM is unable to expire those logs". If you use a separate mgmt class and copygroup for your logs, and your copygroup parameters are set properly, TSM will expire your logs. Maybe if you want to give us some more details of yr installation... Cheers. Othonas PS: I bet Basel is beautiful this time of the year... Arnaud Brion [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 11:01:42 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: expiring Informix logs ...? Hi everybody ! I come back on something that seems to be an old subject for *SM'ers : we're using the Onbar API to ensure the backup of our informix logs, what works really nicely, except we're facing a huge increasing of the number of tapes used for this storagepool, due to the fact that TSM is unable to expire those logs. We tried to install the onsmsync utility a few month ago, which was supposed to give us a rid of this problem, but I just saw today that it isn't working at all ! Does anybody know if Informix or Tivoli found a solution to this problem (new version of onsmsync ?), or if there is any other way expiring those #@#@@... logs ? I saw there is a c programm existing but I have no idea of c language so if you know something easier, just let me know ! Thanks in advance ! ;-) Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78/Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: TDP for Informix 4.1 - Expiring Informix logs ...?
George, here is the answers to yr questions: Question1: Can the TDP 4.1 restore from one machine to another??? Answer1: Yes, it can, we just refreshed a 380 GB Lawson DB from the production server to the QA server this past weekend, no problem at all. Question2: Also can the TDP 4.1 backup individual data bases or tables from an application server ??? Answer2: Yes, it can, via onbar. Not only backup them, but also restore them as well. Of-course, on both cases DBA expertise are needed, however TSM works as designed. Cheers. Othonas George Lesho [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 05:38:57 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: expiring Informix logs ...? That's great info. Many thanks... will look into the TDP 4.1... didn't know it existed and SQL-BackTrack for Informix is quite an art to get it to actually work. Can the TDP 4.1 restore from one machine to another??? our developers are always wanting to put the production application server (either PeopleSoft, Lawson or DataMart) onto a test box to recreate things. Seems to me that this capability would not be affected by going to the TDP 4.1 as it is done via a virtual host entry in the dsm.opt file. Also can the TDP 4.1 backup individual data bases or tables from an application server? That is one advantage the new SQL-BackTrack has over the older version there the Informix server had to be DOWN to do this and that is seldom acceptable in a 24 hours production environment... Thanks for any info - George George Lesho Storage/System Admin AFC Enterprises Othonas Xixis [EMAIL PROTECTED] on 02/13/2001 04:27:48 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: expiring Informix logs ...? Hi George, I am fine, busy as always... thanks for asking, how is San Antonio ? On this Informix issue, I guess Arnaud did not mentioned, and I didn't realize at first that he was using SQL-BackTrack. Tivoli nowadays has a new TDP for Informix 4.1 and works fine. We had three Informix installations lately and we installed the TDP for Informix on all of them (onbar - online, full, L0, L1 backups) and things are working great, without using SQL-BackTrack. Again, and even with the TDP, all the DB data and the log data is expired via TSM management and copygroup configuration because Informix can't control and pass the expiration information to the API. Informix, *SM API, and SQL BT versions is the main factor to tune and make all three products to work appropriately. Thanks. Othonas George Lesho [EMAIL PROTECTED]@VM.MARIST.EDU on 02/13/2001 03:21:12 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: expiring Informix logs ...? Howdy Othonas! Hope you are doing well... haven't heard from you in a while... I think the problem with doing expiration and reclamation of backups made with SQL-BackTrack for Informix lies in the fact that if you use an older version of the product, the agent places a long time stamp on the filespace name making each name UNIQUE. Thus, you are left with a zillion unique filespaces, each being an ONLY version of a db backup. This truly complicates expiration you basically must go in and erase filespaces manually. With the newer version of SQL-BackTrack for Informix, it has the ability to delete back generation of a database. The generations term is used by BMC to distinguish between versions as each Informix backup is actually unique. It appears you can only retain 9 unique generations at most; meaning if you backup up daily, the most you can retain, using the agent is 9 days worth. You can also expire using a date. These features only became available on V.3... we are testing it now and it is a pain to install... BMC's directions are not great ;-(. Anyway, I am far from an expert in these matters but I do have some experience with deleting filesets which is necessary, even if you put backups into their own management class/copy group. BTW: I have completed implimenting all the recommendations you made and just finished documenting the whole mess. During the course of the documentation, I redid all management classes, copy groups and schedules to make them work the way we wanted and have everything revolving around our logical business day as you suggested. The redbook has some good tips on scheduling stuff so that our admin processes are not overlapping with backups and such. Thanks- hope my rambling made some sense... George Lesho Storage / System Admin AFC Enterprises Othonas Xixis [EMAIL PROTECTED] on 02/13/2001 10:28:39 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [
Atape download sites
Ganu, here are a few sites that you can download from the Atape and atldd drivers for the 3590 E drives: ftp://index.storsys.ibm.com/devdrvr/ ftp://service.boulder.ibm.com/storage/devdrvr/ ftp://ftp.software.ibm.com/storage/devdrvr/ Cheers. Othonas
Re: Archive command filespec
You should try something like this: # dsmc archive -subdir=yes "/apps/mfgdata/swprod1/*" "/home../*" Cheers Othonas Richard Sims [EMAIL PROTECTED]@VM.MARIST.EDU on 01/31/2001 03:01:14 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Archive command filespec dsmc archive /apps/mfgdata/swprod1/*.* /usr/ownlog/archiveswprod1 ANS1102E Excessive number of command line arguments passed to the program! Henrik - Interesting. The client manual description of the Archive command specifies no limit to the number of files that may be given on the command line; but the message description says that no more than 20 may appear. (I'll report this discrepancy to the documentation people.) Your asterisks were out in the open, so were expanded by the shell. Try quoting the filespec such that TSM expands the wildcard characters itself. Richard Sims, BU
Re: maintenance window/database backup
Definitely prior to halt and your system maintenance, because if the changes made to the system destroy something from your TSM structure... You will be able to restore from that last DataBase backup. Also you might want to monitor this DB backup, make sure it finishes successfully, and write down yr Volume Serial (Volser) number just in case... What about System Backups (AIX: sysback, mksysb) ? depending how important is the changes made to the system you might want to take a system backup as well. Cheers. Othonas Xixis "Malloy, Kevin" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/19/2001 11:04:22 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: maintenance window/database backup New to the TSM environment,,,so thanks for the forum and thanks in advance for any assistance. We have a maintenance window carved out roughly between 14:00 and 18:00. Maintenance to our storage environment next week, which facilitates a TSM down between those hours. Should I perform that DB-BACKUP prior to the 14:00 HALT or run the DB-BACKUP after I bring the system back up?
Re: deleting rman data
*sm show versions nodename * Brgds, Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:31:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Re: deleting rman data
It sounds like a problem at the API level between TSM and Oracle, either upgrade yr RMAN module, or the TSM Client API, or both... it seems to me that they don't hook up appropriately. Do you receive any errors on the dsierror.log file ? if yes... you might want to troubleshoot them and you will probably find the end. Finally, I trust that all your management classes/copygroup stuff are set properly... Good luck... Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 01:18:05 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data Othonas thanks for your reply thats exactly what I was looking for but I guess I still have a problem. My DBAs run this command change backuppiece tag 'TRIB20001215' delete. and it says the files are deleted from ORacle . I run expiration, expiration completes and yet the files are still in TSM Can anyone see if I'm still missing something or have I encountered a bug? "Othonas Xixis" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:59:15 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data *sm show versions nodename * Brgds, Othonas "James healy" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/16/2001 11:31:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data How do I verify the state of the objects? "Michel Engels" [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 08:51:28 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: deleting rman data You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Re: Atape device driver upgrade require reboot?
Richard, the answer to your question is no, you don't need to reboot. However, and I trust you know this, you need to: 1) delete the tape definitions ( # rmdev -dl rmt? , and also lmcp0), 2) install yr Atape atldd drivers, and 3) then run config manager ( # cfgmgr ), config manager will rebuild yr rmts. PS: Also since u are changing the tape drives from Bs to Es you would need to delete the drives in TSM and redefine them once everything is ready in AIX. I just converted also 4 tape drives to Es this weekend, and everything when fine. No problem. Good Luck. Othonas Richard Sims [EMAIL PROTECTED]@VM.MARIST.EDU on 01/08/2001 01:51:11 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Atape device driver upgrade require reboot? I'm approaching upgrading the 3590 drives in a 3494 to 3590E, extended length capable, where the server level is 3.1.2.50 in an AIX 4.1 system. What I would like to do is boost the Atape and Atldd drivers ahead of the hardware upgrade, so as to have that much work done and assured before the hardware people arrive. If anyone has recently installed the current Atape driver to an AIX system, could you tell me if you were able to achieve that without an AIX reboot? In the past I had been able to upgrade without a reboot, but things may be different in current Atape levels, so I'd like to know what I face. thanks, Richard Sims, BU
Re: Drivers
ftp://service.boulder.ibm.com/storage/devdrvr/ Cheers. Othonas Diana Noble [EMAIL PROTECTED]@VM.MARIST.EDU on 12/19/2000 03:26:00 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Drivers I'm about to upgrade to TSM 4.1. Some of the recommendations were to make sure atape and atldd are at the correct level, although I don't see the level specified in the doc anywhere. I was going to upgrade them anyways and was told I could download them from ibm.com somewhere, but I've not yet to been able to find them. Can anyone give me a clue as to where to look for the upgrades to atape and atldd? Thanks.
Re: ANR 8413E UPdate Drive : Drive is currently in use
Mahesh, this is a known TSM problem with version 3.7.3 . You will need to upgrade your code to be at 3.7.3.6 or higher, this has been resolved at these versions. Good Luck. Othonas Mahesh Babbar [EMAIL PROTECTED]@VM.MARIST.EDU on 12/18/2000 04:36:39 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: ANR 8413E UPdate Drive : Drive is currently in use Hello WIZs, I have following issue: At times, the tape volume is not able to unload it self from a 3590 E1A tape drive ( for any reason) and the drive becomes 'unavailable" for TSM. Though the problem gets rectified in the library but I "have" to restart the TSM server to make it available again in TSM. When I manually try to update the status of the drive , using "update drive .." command it gives me error: ANR8413E UPDATE DRIVE : Drive RMT1 is currently in use I don't know where it gets locked? Is there any way I can make it 'online' w/o restarting the TSM Server. Details are: OS: AIX 4.3 TSM : TSM 3.7.3 Library : 3494 Drive : Magstart 3590 E1A Thanks in advance Best Regards Mahesh
Re: LOG usage over 100% - backups failing
Vijay, actually u have three options: 1) Introduce the incremental TSM database backups. 2) Stop logging all together and maybe take 2 or 3 full daily database backups. 3) Ask from Tivoli support (I believe we all need to do that..) to increase the log maximum size from 5.4 to something like 10 GB... Yes Mr Developer this is a "hot" and "fuzzy" issue that has been giving us grief for a long... long... time. Cheers. Othonas Vijay Havaralu [EMAIL PROTECTED]@VM.MARIST.EDU on 12/11/2000 08:36:26 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: LOG usage over 100% - backups failing Hello every one, We are running tsm-server ver 3.7.20 on aix 4.3.2 with about 400 gb per day backup. Our adsm db-size is close to 100 gb and growing daily. Almost each day log is overflowing with 100%, all backups fails, and server recovers continues We are already using max 5.4 gb of log and can not increase any more on log volume. I appreciate, if anybody has any solutions this problem to reduce log usage or extend log beyond 5.4gb. Thanks, vijay.
TDP for Informix to TSM 4.1.1 Performance
Hi, I am looking for some good performing (as far as speed of backup is conserned) onconfig values for the following two variables: BAR_NB_XPORT_COUNT (Number of data buffers of each onbar_d process - Default value is: 10) BAR_XFER_BUF_SIZE (PageSize of each transfer buffer - Default value is: 15) My API TDP for Informix is 4.1 , ServerClient: AIX4.3.3 , 100Mbps FDX Network, backing up to 3 3590 tapes drives. Memory and Paging space is: 3GB My DB is about 500+ GB and my BAR_MAX_BACKUP is set to 3. Any AIX fast performing AIX settings are also welcomed. Thanks in advance for yr assistance. Bgds. Othonas
Re: TDP for SAP in a HA environment
Geoff, Yes... u r correct, u will need to configure 3 nodenames/clients (2 for the cpu's and one for the SAP/data). All depends how the cluster is configured... like: what filesystems are failing over... and also how SAP is installed, you always have to "follow yr data". Probably also you will need a couple different TSM Server quotas (for the same server) to cover yr client security stuff when the cluster has been failed over. Tivoli, as you probably already know doesn't support this type of endeavours, but I have installed more than 5 diff environments and they all work fine. It takes a couple scripts to stop and restart your schedulers, move the the TDP/configuration around, and of-cource it takes a couple real-time tests/failovers to get it adjusted. Good luck. Othonas Geoff Pusey wrote: Hi, Has any one out there configured a TDP for SAP in a HACMP environment? This is the configuration I will try and keep it simple. I have two TSM clients in a HACMP cluster one on CPU "Production" and the other on CPU "Standby" and Between the two I have a large SAP database which will fall over between cpu Production and CPU Standby. I have the TSM clients software configured so that it falls over OK, using a new Options file and the security. Now for the question: I need to backup local files on both the Production CPU and the Standby CPU plus the SAP database. Do I need to configure three TSM clients One on each CPU and one on the CLUSTER where the SAP database resides? Or is there a trick where I can use the SAP options file to redirect the SAP date to the client which is up ether CPU production or CPU standby? I have read the red book on HACMP chapter 9 "HACMP and TSM" but it dose not cover this topic Any help would be appreciated Regards, Geoff Pusey Tivoli Advisory Consultant Tivoli Systems. Office : +44 (0)1753 896896 Mobile : +44 (0) 780 8203704 Email: [EMAIL PROTECTED]
Re: configure LTO Ultrium 3581 on tsm 4.1
Giuseppe, what operating system r using ? do you have all the current Atape drivers ? does yr operating system has all the necessary (up to date) scsi drivers installed ? do you have the proper cabling and support scsi adapters ? Is this a new library ? has the CE properly install/setup the library ? What is the exact command that u r trying to define the library in TSM... and what is the exact error that u r getting in TSM and the operating system level ? Cheers. Othonas Giuseppe Taccone wrote: Please, is there anybody that have already configured this library(LTO 3581) with TSM 4.1? i don't have any possibility to configure this library with TSM scsi device drivers, infact when the system start gave to me error in TSM scsi driver. many thank's in advance Giuseppe Taccone TSM Manager I.A.N. s.rl. V.le Fulvio Testi, 11 20092 Cinisello Balsamo (Mi) Tel +390261866362 Fax +390261866315 Email: [EMAIL PROTECTED]
Re: TSM 3.7 Disaster Recovery Manager - what is shipped?
Yes it does. Cheers. Othonas Eric Winters wrote: Would someone kindly confirm for me that TSM 3.7 Disaster Recovery Manager functionality resides wholly within the TSM 3.7 server product? We've just taken delivery of an order for TSM 3.7 server plus DRM and have no separate CD for the DRM. The announcement letter seems to confirm that all you'll get if you actually order DRM is a documentation CD (which we did get) but I'd like to hear this from someone who has been there and done that. Thanks, Eric Winters IBM Global Services Australia ZE06 (Zenith Centre - Tower A) Level 6, 821 Pacific Highway Chatswood NSW 2067 Sydney Australia Ph: +61-2-8448 4104 Fax: +61-2-8448 4006
Re: I/O Station
Saad, The optional Convenience Input/Output Station feature is available for inserting or ejecting cartridges without interrupting the normal automated operations. You have three options: 1) No Convenience Input/Output Station 2) A 10-cartridge Convenience Input/Output Station feature (reduces the overall library cartridge capacity by 30 cartridges). 3) A 30-cartridge Convenience Input/Output Station feature (reduces the overall library cartridge capacity by 80 cartridges). The best manual for yr case is the following: Title: Magstar 3494 Tape Library Introduction and Planning Guide Document Number: GA32-0279-11 My recommendation is: If you have off-site and DR requirements functions in a daily basis then you need at least the 10-cartridge I/O Station. The 3494 library can grow really big... I don't know yr installation but if you have a large 3494 installation with frequent tape I/Os then you should consider the 30-cartridge I/O Station. Good Luck. Othonas Saad Al-Sakran wrote: Hi...All we are planning to have Magstar Tape library 3494. We have an option to have it with I/O station or not...please if any one know an online documentation about I/O Station and its features and cababelities please send me the url. Best Regards Saad Al-Sakran LAN Administrator KFSH
Re: licensing of TSM
Shekhar, do an # ls -al /usr/tivoli/tsm/server/bin/drm.lic to see if the file is there... and if it has in it what it supposed to have... also u can do an # file /usr/tivoli/tsm/server/bin/drm.lic maybe the file is not there, or corrupted, or... On yr TSM Server when u issue the q lic what do you get for "Server License Compliance:" status is: Valid or Invalid... maybe yr whole licencing stuff need deeper attention. Cheers. Othonas Shekhar Dhotre wrote: # dsmadmc Tivoli Storage Manager Command Line Administrative Interface - Version 3, Release 7, Level 0.0 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Enter your user id: admin Enter your password: Session established with server TSM: AIX-RS/6000 Server Version 3, Release 7, Level 0.0 Server date/time: 01/01/70 16:07:32 Last access: 01/01/70 16:06:49 tsm: TSMregister license file=/usr/tivoli/tsm/server/bin/drm.lic ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. "[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/22/2000 02:45:20 AM Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400 To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400 cc: Subject: Re: licensing of TSM Try using full path of license file... Thanks Marc _ Marc Layne Product Manager - Storage and Software Solutions Faritec Mobile: +27 82 4169086email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Office: + 27 21 7629702 http://www.faritec.co.za _ -Original Message- From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]] Sent: 22 November 2000 09:33 To: [EMAIL PROTECTED] Subject: licensing of TSM hi all , Installed TSM 3.7.0.0 , started server , working ok , updated server to 3.7.4.0 , tested working ok . problem using following two command does not make any changes to licenses registered? where i am wrong ? tsm: TSMregister lic file(drm.lic) ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. tsm: TSMregister license file=drm.lic ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2.
Re: licensing of TSM
With the reinstallation and all... can u check if you have the "nodelock" in the /usr/tivoli/tsm/server/bin directory. Othonas Shekhar Dhotre wrote: yesterday i did that only i upgraded to 3.7.4and tried there it failed , then again removed TSM , removed /usr/tsm directory , reintsalled , tried ..no luck .. Installed AIX from scratch assuming some ODM problem for previous installtion , Again reinstalled TSM today morning same thing .. I am having current maintainnace patches on my Box.. # cd /data # ls .toc IP22130.bff IP22123.bffTSM3740SRV_AIX-BFF.tar IP22124.bffTSM3740SRV_AIX.README.DEV IP22125.bffTSM3740SRV_AIX.README.Install IP22126.bffTSM3740SRV_AIX.README.SRV IP22127.bffTSM3740SRV_AIX.tar IP22128.bfflost+found IP22129.bff "[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/22/2000 10:27:10 AM Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400 To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400 cc: Subject: Re: licensing of TSM I wouldn't even bother trying to get 3.7.0 to work. Go ahead and upgrade to the current maintenance, then try to figure it out. -Original Message- From: Shekhar Dhotre [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, November 22, 2000 9:28 AM To: [EMAIL PROTECTED] Subject: Re: licensing of TSM # dsmadmc Tivoli Storage Manager Command Line Administrative Interface - Version 3, Release 7, Level 0.0 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Enter your user id: admin Enter your password: Session established with server TSM: AIX-RS/6000 Server Version 3, Release 7, Level 0.0 Server date/time: 01/01/70 16:07:32 Last access: 01/01/70 16:06:49 tsm: TSMregister license file=/usr/tivoli/tsm/server/bin/drm.lic ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. "[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/22/2000 02:45:20 AM Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400 To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400 cc: Subject: Re: licensing of TSM Try using full path of license file... Thanks Marc _ Marc Layne Product Manager - Storage and Software Solutions Faritec Mobile: +27 82 4169086email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Office: + 27 21 7629702 http://www.faritec.co.za _ -Original Message- From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]] Sent: 22 November 2000 09:33 To: [EMAIL PROTECTED] Subject: licensing of TSM hi all , Installed TSM 3.7.0.0 , started server , working ok , updated server to 3.7.4.0 , tested working ok . problem using following two command does not make any changes to licenses registered? where i am wrong ? tsm: TSMregister lic file(drm.lic) ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. tsm: TSMregister license file=drm.lic ANR2852I Current license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2. ANR2853I New license information: ANR2835I Server is licensed for 1 clients. ANR2854I Server is licensed for device support module 2.
Re: problem
Shekhar, What does your TSM Server error log file is showing ? You probably will need to upgrade yr code since I see that u r in the 2.0 version. Probably the problem is with the device class, but I am pretty sure that the error log will have some information that will help you investigate this issue further. Do also, a # df command (if u running unix) to see if u have a full filesystem. Gluck. Rgds, Othonas Shekhar Dhotre wrote: I am issuing following command , but TSM SERVER terminating immediately... what could be the problem ? tsm: TSMgenerate BACKUPSET MEDRS2 MEDRS2BACKUP DEVCLASS=STK9710 SCRATCH=YES VOL UMES=MED599 RETENTION=60 Session established with server TSM: AIX-RS/6000 Server Version 3, Release 7, Level 2.0 Server date/time: 10/10/00 16:37:20 Last access: 10/10/00 16:24:43 ANS8003I Process number 1 started. ANR7833S Server thread 12 terminated in response to program abort. ANR7833S Server thread 13 terminated in response to program abort. ANR7833S Server thread 14 terminated in response to program abort. ANR7833S Server thread 15 terminated in response to program abort. ANR7833S Server thread 16 terminated in response to program abort. ANR7833S Server thread 17 terminated in response to program abort. ANR7833S Server thread 18 terminated in response to program abort. ANR7833S Server thread 19 terminated in response to program abort. ANR7833S Server thread 20 terminated in response to program abort. ANR7833S Server thread 21 terminated in response to program abort. ANR7833S Server thread 22 terminated in response to program abort. ANR7833S Server thread 23 terminated in response to program abort. ANR7833S Server thread 24 terminated in response to program abort. ANR7833S Server thread 25 terminated in response to program abort. ANR7833S Server thread 26 terminated in response to program abort. ANR7833S Server thread 27 terminated in response to program abort. ANR7833S Server thread 28 terminated in response to program abort. ANR7833S Server thread 29 terminated in response to program abort. ANR7833S Server thread 30 terminated in response to program abort. ANR7833S Server thread 32 terminated in response to program abort. ANR7833S Server thread 33 terminated in response to program abort. ANR7833S Server thread 34 terminated in response to program abort. ANR7833S Server thread 35 terminated in response to program abort. IOT/Abort trap shekhar
Re: Would you buy TSM again.
Been in the industry for more than 18 years, and especially in the storage and backup/recovery business for more than 7 years... I have seen, tested and worked on a lot different storage products here in the States and abroad, so here are the answers to yr questions: How good do you rate TSM on a scale of 1 to 10. (10 being best) ? I will give TSM a 9.4 because I believe it is the best available storage solution in its category... as you can see I use the word "solution" and not program or package, because TSM is a solution... you just have to do your homework and put it to work as most appropriate for yr environment. 9.4 because I believe there is still room for improvement... always... We just finished a 6.8 TB TSM 3.7.3.6/8 / SAN (Fibre/1Gb Ether) solution and it worked like a "swiss clock", and most important... it worked the first time (no reinstallations, no reconfigurations, no voodoo) , the only special thing that I did was... to read the manual and instructions line by line. Would you definitely buy it again, or would you shop around ? Yes, I would buy it again... most definitely... and for various reasons, but especially for the functionality, scalability, and support. Good luck on yr decision. Cheers. Othonas "Sattler, Lynn" wrote: We are reconsidering our backup software. We are a pretty large unix shop (5 Terrabytes to backup nightly) and are using some HP Omniback and a lot of Veritas Netbackup. Mostly HP-UX. We have a large Lotus Notes Rel 5 implementation on AIX (600 gig on its way to 1.2 Terrabytes). We are studying robot technology and SAN's. Tivoli is selling and Netbackup is trying to stay in the shop. How good do you rate TSM on a scale of 1 to 10. (10 being best). Would you definately buy it again, or would you shop around. My gut feeling is that everybody has some complaints with their backup solution. Lynn Sattler Dana Corp Toledo Oh [EMAIL PROTECTED]
Re: Is TSM 3.7.3.6 Stable?
Yes, it is stable, we are using it for about 3 months with no problems. Make sure yr atape, atldd, and SAN euipment are in their latest version/firmware. Cheers. "T.Y. Wu" wrote: To support Fibre Channel 3590 interface, I need to go up to 3.7.3.6. Is this a stable level for production? One entry dated 7/17 stated that tape reclaim or del vol would crash the server at this level. Has anybody else bad experience with 3.7.3.6? Our server environment: M80/3494/3590, AIX 4330-ML04, TSM 3.7.2.0. Atape and atldd are all current. Thanks, T.Y.
