Re: LTO-5 Experience?
We installed 12 LTO5 drives a couple of months ago We have a mixture of LTO2, LTO4, and LTO5 drives in our library. LTO5 drives are only using LTO4 media, but we haven't had any issues as of yet. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ochs, Duane Sent: Wednesday, January 19, 2011 9:31 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] LTO-5 Experience? I'm installing a Spectralogic T950 with 14 LTO5 drives next week. I'll let you know if I have the same issues. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Gary Bowers Sent: Wednesday, January 19, 2011 9:28 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: LTO-5 Experience? I have a customer that is running 6 LTO-5 drives in a 3310 using IBM LTO5 media. They have had many issues with LTO5. In the past 6 months, they have replaced 4 drives mostly due to stuck tapes. Several engineering firmwares have been added, and they are now finally able to eject tapes more consistently. I would say that this customer is not happy with the transition at this point (LTO3 previously). They run an HSM environment, and tapes getting stuck in the drives prevents restores of their HSM data. This makes unhappy doctors. I know that they sent at least 2 of their drives to IBM with a tape still stuck in it to perform diagnostics. I really have never seen anything like this in the 10+ years I've been doing TSM. If you have not upgraded to the latest firmware, make sure you do so. Gary Bowers Itrus Technologies On Jan 19, 2011, at 5:51 AM, Christian Svensson wrote: Hi, Does anyone run LTO-5 libraries today? How are your experience of LTO-5? I have only installed one library and we got a lot of problem with does drives. Just wonder if that is only one timer or if many other also have problems with LTO-5 I don't care what TSM version you are running. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: TSM 6 database space performance question
Ours is designed the same, I asked the same questions and was given the following advice: The alternative to specifying multiple database directories is to use hardware RAID controller or LVM to assemble multiple disks into a single filespace/directory, You don't get the benefit of DB2's stripping when you do this, but what you loose is often made up for by the hardware's stripping. The other consideration is when doing this is that DB2 would normally throttle its I/Os going to the single directory (on the assumption that it represents a single disk), but there's a DB2 tuning parameter you can use to tell DB2 that the directory is backed by multiple disks, and to schedule its I/O accordingly. In fact, TSM sets this parameter by default, so out of the box, DB2 will assume its database directories are backed by multiple disks Rod -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Andrew Carlson Sent: Tuesday, May 11, 2010 3:45 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6 database space performance question It would probably not be a problem with it working, but with the two lun's concatenated, there is probably little to no chance DB2 will be able spread the I/O out among the 2 lun's. If it's in a separate filesystem, DB2 will spread the data out across them. It will be even worse with 3, 4, 5, or more lun's. On Tue, May 11, 2010 at 3:21 PM, John D. Schneider john.schnei...@computercoachingcommunity.com wrote: Greetings, I have a customer running TSM 6.1.3 on a Linux RedHat 5.4 server. They are using high-performance SAN attached disk for the TSM database and logs. They have created the TSM database all in one directory under one filesystem. Recently then needed to add more space, and they carved out a lun from another RAID group, and then added that lun to the existing filesystem. TSM shows that it now has the additional space, but it is still all under one directory. In reading the Performance Guide and Admin Guide, they both recommend spreading the data out over multiple directories, putting each directory behind separate disks/luns. This certainly makes sense to spread the I/O out over multiple luns, and I get that. But is there anything wrong with the way my customer has done it? They are using multiple luns from different RAID groups, but they are all put together behind one directory. Is this going to become a problem as they add more and more load to this instance? If TSM has lots of separate directories and they are across multiple luns, does TSM do it's database I/O differently? Best Regards, John D. Schneider The Computer Coaching Community, LLC Cell: (314) 750-8721 -- Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: volumes in a collocation group?stg
Ok, we've never collocated our copy pools because I was under the impression that TSM consolidates each node to a small subset of tapes which in turn makes restores very fast/less mounts blah blah blah, but if you're writing out new backup data for each node from the night before out to a copypool tape, how does TSM keep it collocated? It seems like it would have to move that data around every day to keep a nodes data to a small subset of tapes and each day it would keep moving the same data and the next day's new data to another subset of tapes. Please correct me if I'm wrong and point me in the right direction because we do have the same issue at our DR test with multiple mounts and multiple nodes requesting the same tapes. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Larry Clark Sent: Tuesday, March 17, 2009 1:54 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] volumes in a collocation group?stg Yes, the underlying problem is they are not collocated and they have experienced delays because of: - multiple platforms requesting the same volumes concurrently - multiple servers on the same platform requesting the same volumes concurrently - too many mounts to restore a server hence collocation, which is not cheating but using the features of TSM to address volume contention and wait times on mounts. A mechanical mount that takes 3 minutes is a lot of time if your data is spread across 30 volumes versus 10: 20 x 3 x #number of servers. Larry Clark - Original Message - From: David E Ehresman deehr...@louisville.edu To: ADSM-L@VM.MARIST.EDU Sent: Tuesday, March 17, 2009 2:39 PM Subject: Re: [ADSM-L] volumes in a collocation group?stg That's cheating. If your DR test restore times are unexceptable you need to address the underlying problem because you don't get to prep for real disasters! Larry Clark lclar...@nycap.rr.com 03/15/09 2:48 PM Hi Alex, Yes, this is related to improving restore times in a DR senario...so these are offsitevols from a copypool. Larry Clark (518) 712-5138 Home Office - Original Message - From: Alex Paschal apasc...@msiinet.com To: ADSM-L@VM.MARIST.EDU Sent: Sunday, March 15, 2009 2:37 PM Subject: Re: [ADSM-L] volumes in a collocation group?stg Hi, All. The critical piece that Larry mentioned is that he's interested in a copypool. If your primary pool is collocated by anything, but your copypool is not collocated at all, then your copypool data will be mixed up with no regard for collocation groups. Nick, if you really want to mix data on tapes (I have no idea why you would want to, but the beautiful thing about TSM is you can do nearly anything you want), the first way I can think of is to temporarily reduce MAXSCRATCH (or temporarily disable collocation), set to Unavailable the volumes you do _not_ wish to write to, then issue move [node]data. Alex Alex Paschal Storage Solutions Engineer MSI Systems Integrators Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Sunday, March 15, 2009 5:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] volumes in a collocation group? On Mar 14, 2009, at 10:23 PM, Larry Clark wrote: What you say is curious..only nodes that are in a collocation group should have data on the volumes in that collocation group. At least that is my understanding. Your saying more than one collocation group can store data on the same volume? I know for collocation by node that would not be true Paul already mentioned the scenario in which TSM has to put a a collocation group member's data on a tape that has data from another group on it, due to resource constraints. You can get similar results if a node's collocation group membership changes from one group to another. In that case, data stays where it is, meaning the tapes now contain data from two groups on them, even though TSM behaved exactly as predicted. I keep wondering if there's a way to mix groups' data on a volume using MOVE DATA or MOVE NODEDATA, but since neither lets you specify a target more exactly than a storage group, I haven't seen how yet. Larry Clark Nick This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an
copypool volumes requested instead of primary pool
We have a situation where dba's are doing a full db restore to a client. The client is requesting and using primary tapes, but it is also requesting copypool tapes that are offsite. All of the primary tapes are online r/w in the library and some are actually in use that has the same db file that the restore is requesting but the restore never asks for the primary tape, it goes for the copypool tape immediately. AIX, sever version 5.3.3.1, oracle/tdp version 5.3anybody else seen this, why would it request the copypool if primary tape is available and read/writable in the library? Thanks, Rod. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: copypool volumes requested instead of primary pool
yes, that appears to be the case, damaged files on tapes. Not sure why so many on that particular day but we have identified somethanks for your help. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Monday, January 14, 2008 2:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] copypool volumes requested instead of primary pool On Jan 14, 2008, at 2:53 PM, Park, Rod wrote: ... why would it request the copypool if primary tape is available and read/writable in the library? Rod - The most common reason is that a file on the volume is Damaged. Use the Query CONtent VolName ... DAmaged=Yes command to so determine. Also watch out for files spanning volumes where the companion volume is not available. There should be evidence of problems in the Activity Log. I regular administration tasks, perform do 'Query Volume ACCess=UNAVailable,DESTroyed' to look for anomalies. Richard Simshttp://people.bu.edu/rbs/ This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
sql tdp hang issue
I have a dba that has one sql server that has tsm hang issues according to him. They have a full backup job that backs up 7 sql db's. The size is about 80GB total. Sometime it backs them all up with no issues, sometime it says waiting on tsm server but if I look at q se there are no active sessions. Right now there is one running from last night and it has only backed up 12.5GB in 9 hours. below are some client details and log details. Anyone have any ideas. Other sql backups run just fine along with the other 15TB that backup each night, but of course DBA's say it's a TSM issue. Here is what they see when it hangs: Full: 3 Read: 658505728 Written: 65536 Rate: 480.95 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 480.59 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 480.23 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 479.87 Kb/Sec Waiting for TSM server.. .. clint info: Node Name: WHQWPSQLCL1RS01_SQL Platform: TDP MSSQL Win32 Client OS Level: 5.02 Client Version: Version 5, Release 3, Level 3.0 Policy Domain Name: SQL Last Access Date/Time: 12/14/07 08:00:05 Days Since Last Access: 1 thanks, Rod This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: sql tdp hang issue
I don't see anything in the activity log. The backups are going straight to diskpools and the backups are single threaded. I did add disk space to my diskpool this week in case that was the issue. Looking at my diskvols, data doesn't seem to be striped across all disk evenly, would that be that problem if some fill up and others don't, causing it to wait on tsm? tsm: TSMCORP1q vol stg=sql_diskpool Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - /dev/rsqldiskvol1SQL_DISKPO- DISK51,072.0 0.2 On-Line OL /dev/rsqldiskvol10 SQL_DISKPO- DISK51,072.0 31.4 On-Line OL /dev/rsqldiskvol11 SQL_DISKPO- DISK51,072.0 100.0 On-Line OL /dev/rsqldiskvol12 SQL_DISKPO- DISK51,072.0 36.6 On-Line OL /dev/rsqldiskvol13 SQL_DISKPO- DISK51,072.0 100.0 On-Line OL /dev/rsqldiskvol14 SQL_DISKPO- DISK51,072.0 92.8 On-Line OL /dev/rsqldiskvol15 SQL_DISKPO- DISK51,072.0 98.8 On-Line OL /dev/rsqldiskvol16 SQL_DISKPO- DISK51,072.0 81.9 On-Line OL /dev/rsqldiskvol2SQL_DISKPO- DISK51,072.0 3.2 On-Line OL /dev/rsqldiskvol3SQL_DISKPO- DISK51,072.0 91.3 On-Line OL /dev/rsqldiskvol4SQL_DISKPO- DISK51,072.0 21.0 On-Line OL /dev/rsqldiskvol5SQL_DISKPO- DISK51,072.0 11.5 On-Line OL /dev/rsqldiskvol6SQL_DISKPO- DISK51,072.0 69.4 On-Line OL /dev/rsqldiskvol7SQL_DISKPO- DISK51,072.0 15.4 On-Line OL /dev/rsqldiskvol8SQL_DISKPO- DISK51,072.0 99.9 On-Line OL /dev/rsqldiskvol9SQL_DISKPO- DISK51,072.0 44.3 On-Line -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Del Hoobler Sent: Friday, December 14, 2007 9:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] sql tdp hang issue Did you examine the TSM Server activity log closely? Was there a problem where a tape did not get mounted in time? How many stripes are you using for the backup? If you are using multiple stripes and one of those stripes is waiting for the TSM server to mount a tape, it can cause this. I have seen this when the TSM Server does not have enough available tapes mounted to satisfy the DP/SQL request. The Waiting on TSM server indicates that DP/SQL is waiting for some event on the TSM Server to occur before it can continue sending any more data. Is it possible that some TSM Server event pre-empted the DP/SQL backup and took one of the tapes that was needed to satisfy a multiple stripe DP/SQL backup request? You should start on the TSM Server... in the activity log to find out what it thinks happened. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 12/14/2007 09:52:59 AM: I have a dba that has one sql server that has tsm hang issues according to him. They have a full backup job that backs up 7 sql db's. The size is about 80GB total. Sometime it backs them all up with no issues, sometime it says waiting on tsm server but if I look at q se there are no active sessions. Right now there is one running from last night and it has only backed up 12.5GB in 9 hours. below are some client details and log details. Anyone have any ideas. Other sql backups run just fine along with the other 15TB that backup each night, but of course DBA's say it's a TSM issue. Here is what they see when it hangs: Full: 3 Read: 658505728 Written: 65536 Rate: 480.95 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 480.59 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 480.23 Kb/Sec Full: 3 Read: 658505728 Written: 65536 Rate: 479.87 Kb/Sec Waiting for TSM server.. .. clint info: Node Name: WHQWPSQLCL1RS01_SQL Platform: TDP MSSQL Win32 Client OS Level: 5.02 Client Version: Version 5, Release 3, Level 3.0
Long running expire inventory
I posted this before, not sure if it made it out there. I have a TSM server version 5.3.3.1 on AIX with a 70GB database. I recently moved my db/log vols from 500GB sata drives to internal drives along with mirrored vols on separate internal drives on the aix box. My backups went from 2 hours to 30 minutes, my startup went from about 2 hrs to 20-30 minutes, and I've seen other performance gains. Everything seems better except for my expire inventory in went from running in a couple of hours to several hours, and my current expiration has been running since yesterday morning at 10:00 a.m.. Does anybody know why my expire inventory run times would have gotten worse. I can't really tell from the activity log. Any suggestions? This has been running for almost 24 hours: tsm: TSMCORP3q pr Process Process Description Status Number - 2,301 Expiration Examined 1600 objects, deleting 1568 backup objects, 0 archive objects, 0 DB backup volumes, 0 recovery plan files; 0 errors encountered. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: Good or bad idea?...offsite disk.
I have a TSM server version 5.3.3.1 running on AIX. Database is 70GB, I recently moved the db and log vols off of 500GB SATA drives to internal drives on the AIX box. I have the dbvols spread across 8 disks and mirrored within TSM on 8 separate internal disks. Everything is much faster now with the exception of expire inventory, it runs for several hours now as opposed to just a couple hours before. Right now, my expire inventory has been running for an hour and has been stuck where it is in the example below. I don't see anything in the activity logs. Any idears? tsm: TSMCORP3q pr Process Process Description Status Number - 2,301 Expiration Examined 304 objects, deleting 272 backup objects, 0 archive objects, 0 DB backup volumes, 0 recovery plan files; 0 errors encountered. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: Recovery Log Pinned
Kinda weird...i had the exact same thing happen yesterday and I've never seen it before either. We had to halt/restart to fix the problem.. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stapleton Sent: Wednesday, February 07, 2007 11:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Recovery Log Pinned From: ADSM: Dist Stor Manager on behalf of Choudarapu, Ramakrishna (GTI) Looks like this pin is 'stubborn', as the successful completion of the database backup for last three days, did not clear the log. AFAIK, this has not happened before. What would happen to the uncommitted transactions if the TSM service is recycled? [SNIP] Can't say, although I've never lost any TSM db data when forced to run HALT on the server; I suspect that forces a log commit as part of an orderly shutdown. If you've got time, I'd log a call with Tivoli support and set a ticket for this. They may want to gather some data on the situation, time and your situation permitting. This is the first stubborn log pin with no obvious cause I've heard of since 5.3 came into being. What size is your recovery log? -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Delete copypool data
We might have a change in policy where we no longer need a 2nd copy of certain storage pools. If this were the case, would it be ok for me to just delete volume with discarddata=yes on those volumes, or when I discarddata does that affect my primary tape pool also. Looks like I'll be able to free up about 4,000 offsite tapes, but I don't want to affect my primary tapes. I am running version 5.3.3.1.can anybody advise please? This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
insufficient space in subordinate storage pool
I have a tsm server at level 5.3.3.1. I have a disk pool that does migrations to tapepool for any data 90 days or older. I have been getting the following message: 10/23/06 08:34:27 ANR1025W Migration process 109294 terminated for storage pool NT_DISKPOOL - insufficient space in subordinate storage pool.(SESSION: 142746) My tapepool looks like this: tsm: TSMCORP3q vol stg=tapepool Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - T03420 TAPEPOOLLTO381,468.0 10.1 Filling T08313 TAPEPOOLLTO381,468.0 8.6 Filling T08409 TAPEPOOLLTO381,468.0 24.5 Filling T08412 TAPEPOOLLTO381,468.0 2.2 Filling T08420 TAPEPOOLLTO381,468.0 2.0 Filling T08424 TAPEPOOLLTO381,468.0 3.1 Filling T08473 TAPEPOOLLTO381,468.0 2.3 Filling T08499 TAPEPOOLLTO381,468.0 1.2 Filling T08528 TAPEPOOLLTO381,468.0 0.8 Filling T08554 TAPEPOOLLTO381,468.0 3.2 Filling Tapepool is not set to collocate. If I set maxscr=15 then my migration will continue and use the tapes listed above, it doesn't go out and grab scratches and label them in the tapepool and use those. Question is, why isn't the migration processes using the 10 tapes I have out there that are filling before I update maxscr. I checked them and they are all read-write. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: FW: Tape Drive Choices: What, and why?
Yeh...i agree Joe. We have the same situation here. We have a 3583 with LTO2 in a test/DR environment and it is painful to work with it, load failures, locks up, you name it, just very inconsistent behavior. No drive failures though and we have LTO2 in it. We also have a 3584 in our production environment with 5 frames and 60 LTO2 drives and very little problems. Like you eluded to, I just don't believe 3583 was ever meant to be a real enterprise backup workload type library. We are very please with our 3584 and LTO2 though. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joe Pendergast Sent: Wednesday, August 09, 2006 9:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] FW: Tape Drive Choices: What, and why? As soon as you said 3583, I felt the pain in my backside twinge. It is of no wonder that they discontinued the 3583 [EMAIL PROTECTED]* garbage (as you put it). The drives we have used in it are very stable, but the loader, and library are constantly having problems. Of course, IBM continuously blames the drive for the problems, but after swapping drive after drive, the loader replacement is the thing that usually fixes the problem. We have a 3583 library that I would not suggest for anyone except in very light duty (currently has LTO1 drives). It goes out once every month (or less). Then we have a 3584 library with full redundancy and the service bays running as 4 logical libraries on two backup softwares. It is very rare that we have any problems. Occaisionally, we get a stuck LTO1 tape, but with care have not lost any. Our LTO1 and LTO2 drives are workhorses. They are busy for up to 22 hours a day. I am very pleased with the 3584 technologies. Zoltan Forray/AC/VCU [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 08/08/2006 01:45 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: FW: Tape Drive Choices: What, and why? You won't get that sentiment from me. As I have said in the past, my experience with LTO2 and 3583 library is that they are [EMAIL PROTECTED]* garbage. Even IBM stated that LTO was never designed to handle the load we are putting through them (we have over 400 tapes in use per 3583-L72 library). Every drive we purchased has been replaced AT LEAST twice, in the past 1.5-years we have had LTO drives/libraries. The libraries need to be power cycled at least once a week, sometimes more (absolutely every piece of firmware/software between the AIX systems and the libraries themselves, have been updated to the latest available - no it's not power - everything is on UPS/battery/conditioned). This is why we are moving to 3592-E05 drives. Besides the capacity difference, the reliability we have seen with 3590 drives (even those that are 10+ years old), far exceeds the LTO's. We mount 1000's of 3590 tapes, daily. If we have 1-failure in 2-3 weeks, that is rare. Granted the 3592-E05 drives are new and disposable/FRU technology vs. field-repairable, so time will tell. Allen S. Rout [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 08/08/2006 02:08 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] FW: Tape Drive Choices: What, and why? On Tue, 8 Aug 2006 11:37:37 -0400, Paul Zarnowski [EMAIL PROTECTED] said: This was more true with LTO-1 than with -2 or -3. The later generation drives can vary their speed to try to match the data rate, thus avoiding some backhitching. But Tom is correct that the motors in the 3592 drives are probably bigger and more powerful, and can thus backhitch more quickly. (this is my guess, not fact) If I recall correctly, the superior 3592 backhitch was related to a special track (servo track?) which permitted precise high-speed positioning. This also aids general purpose seek behavior. The varying speeds would certainly help. The basic summary of the responses I've gotten offline is that LTO is doing much better than it had initially; it seems that the current 3592s still have an edge, but not nearly so broad as was the case. Most interestingly, I didn't see any particular discussion about any tech _other_ than LTO or 3592, apart from one Pulled back a bloody stump story about helical-scan. This meshes neatly with a campus-level query I sent out a few weeks back; to my surprise, LTO utterly dominated that list of tape techs, too. Discussion of other tech lines was all in the past tense. It appears that the LTO alliance has kicked tush and taken names. Rawk On. - Allen S. Rout
Re: Another D/R question
We do a daily sysback to tape which also goes offsite which has all of the DRM info and volhist,devconfig,dsmserv.dskall pertinent files needed for restore. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Wednesday, July 12, 2006 1:47 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Another D/R question We've never used the DRM module in TSM -- it was far too expensive when we first started, so we rolled our own procedures (which work quite well, I might add :-) but I'd like to look at DRM now that it's part of the suite. So -- for those of you using DRM -- how do you get the plan file and associated scripts off-site? I'm running on AIX; the system has the TSM tape library and a DVD-RAM drive. The hotsite system is in the same boat -- so floppy is out. And a mksysb to the DVD drive takes about 4 hours to write, so that won't be a daily occurance. TIA Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Dsmc memory leak
I'm sure this has been discussed in past...the dsmc sch process slowly has a memory leak over time and the only way to free it up is to kill the process and let it respawn. We are at version 5.2.2.9 on AIX 5.3.3 Does anybody know if this has been fixed on any later versions of the ba client...thanks Rod
Migdelay explanation
Could someone in the group please explain to me how migdelay works. I am wanting to setup a disk pool to migrate data 90 days old. I was under the impression that when data was 90 days or older it would automatically migrate to next pool. I was told that one thing that would happen is, as soon as data became 90 days old, it could migrate at anytime during the night, so I wanted to control that, so I setup a job to set migdelay 90 in the mornings and then set it back a few hours later to 0. So far, I haven't seen it migrate anything off. I was then told NO you have to set you hi/lo thresholds down to kick migration off but then that gets your oldest data first but it doesn't stop there it will keep migrating until your low threshold is met so it could migrate data newer than 90 days. Clear as mud? This is our 3rd tsm server, but a new one. I am on AIX 5.3TL4 TSM 5.3.3.1. Sorry if this has already been covered at some point by this group. Thanks in advance.Rod. Rod Park Tyson Foods, Inc. [EMAIL PROTECTED]
Re: Migdelay explanation
Yeh...that was it. Mark got me set straight. Thanks for the help. Rod -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gilbert, Guillaume Sent: Friday, July 07, 2006 3:15 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migdelay explanation You have to check the migcontinue parameter. If it is at YES (the default) it will not take into account the migdelay parameter when doing migrations Guillaume Gilbert Storage Architect Storage Group, Sun Microsystems [EMAIL PROTECTED] 514.866.8876 Office 514.290.6526 Cell -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Remeta, Mark Sent: July 7, 2006 14:44 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migdelay explanation I have that setup on one of my pools. Hi and lo are set to 0 and never change, and it only migrates data over the migdelay value... -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Park, Rod Sent: Friday, July 07, 2006 2:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Migdelay explanation Could someone in the group please explain to me how migdelay works. I am wanting to setup a disk pool to migrate data 90 days old. I was under the impression that when data was 90 days or older it would automatically migrate to next pool. I was told that one thing that would happen is, as soon as data became 90 days old, it could migrate at anytime during the night, so I wanted to control that, so I setup a job to set migdelay 90 in the mornings and then set it back a few hours later to 0. So far, I haven't seen it migrate anything off. I was then told NO you have to set you hi/lo thresholds down to kick migration off but then that gets your oldest data first but it doesn't stop there it will keep migrating until your low threshold is met so it could migrate data newer than 90 days. Clear as mud? This is our 3rd tsm server, but a new one. I am on AIX 5.3TL4 TSM 5.3.3.1. Sorry if this has already been covered at some point by this group. Thanks in advance.Rod. Rod Park Tyson Foods, Inc. [EMAIL PROTECTED] Confidentiality Note: The information transmitted is intended only for the person or entity to whom or which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please delete this material immediately. Please be advised that someone other than the intended recipients, including a third-party in the Seligman organization and government agencies, may review all electronic communications to and from this address.
Re: Random Access Disk Pools
So, can someone explain the difference at the TSM level and aggregate level. Really I'm trying to understand, if I have a primary disk pool that does not migrate, it will be the final onsite resting place of data. As data expires and fragmentation occurs. That space is unusable if I'm not migrating to another primary area? Eventually I'll have to allocate more? Below is what comparison doc showed as consideration of fragmentation for random access pools. Guess I'm not sure what the diff is between tsm level and aggregate level. TSM level - fragmentation will occur as TSM allocates and frees space within the Storage Pool. Migration tends to relieve this fragmentation Aggregate level - fragmentation occurs as files expire within an aggregate. DISK pools cannot reclaim this wasted space until all files in the aggregate have expired -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rushforth, Tim Sent: Tuesday, April 04, 2006 11:21 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools See http://www-1.ibm.com/support/docview.wss?rs=0uid=swg21218415 for comparison of disk vs devclass=file -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Tuesday, April 04, 2006 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Let me ask again because I didn't get much feedback. How do we find the thread limit, and can people weigh in on whether they use big disk pools (50TB-200TB). The advantages/disadvantages of big disk pools versus devclass=file any gotchas either way. We are looking at buy a lot more disk and creating big diskpools to land data on and be the primary pool instead of tape. Thank in advance. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Monday, March 27, 2006 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We found the limit. There are some posts in this forum from the first of the year about the problem we ran into. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Monday, March 27, 2006 6:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We use random access pools, how do you know what your thread limit iswe've never had any issues with ours but we're thinking about adding a lot more. What's the biggest reason you do/don't use devclass=file over disk storage poolsarguments either way? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Friday, March 24, 2006 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Be careful with how many disk pool volumes you create. Each volume uses 1 thread, add this to all of the other threads in use, our TSM server would die at around 1800 active threads. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Friday, March 24, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Random Access Disk Pools I have heard in the past that random access disk pools can become fragmented and practically unusable after a while. I was wondering if anyone sees this in the real world? I posted the other day about managing predefined volumes in a file type devclass, and the only answer I got said they were using random access pools. I would MUCH rather have a random access pool, so if there is no problem with this, I will convert over to random access. Thanks for any input. TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from
Re: Random Access Disk Pools
Let me ask again because I didn't get much feedback. How do we find the thread limit, and can people weigh in on whether they use big disk pools (50TB-200TB). The advantages/disadvantages of big disk pools versus devclass=file any gotchas either way. We are looking at buy a lot more disk and creating big diskpools to land data on and be the primary pool instead of tape. Thank in advance. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Monday, March 27, 2006 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We found the limit. There are some posts in this forum from the first of the year about the problem we ran into. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Monday, March 27, 2006 6:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We use random access pools, how do you know what your thread limit iswe've never had any issues with ours but we're thinking about adding a lot more. What's the biggest reason you do/don't use devclass=file over disk storage poolsarguments either way? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Friday, March 24, 2006 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Be careful with how many disk pool volumes you create. Each volume uses 1 thread, add this to all of the other threads in use, our TSM server would die at around 1800 active threads. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Friday, March 24, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Random Access Disk Pools I have heard in the past that random access disk pools can become fragmented and practically unusable after a while. I was wondering if anyone sees this in the real world? I posted the other day about managing predefined volumes in a file type devclass, and the only answer I got said they were using random access pools. I would MUCH rather have a random access pool, so if there is no problem with this, I will convert over to random access. Thanks for any input. TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM server automation products
I believe ServerGraph and TSMManager both say they have the functionality. We have a pretty sizable TSM environment here...3 TSM servers 10TB b/u a night, 3584 1700 slots 60 drives and we do not have scripts to do any of the daily housekeeping. We use tsm scripts and scheduler and it runs fine. What do you have that is so complex that it has to be scripted outside of TSM's functionality. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: Friday, March 31, 2006 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM server automation products My site has a rather large Perl script that controls the daily housekeeping cycle (storage pool backups, database backups, tape movement, and so on). The script also detects a variety of error conditions and reports them to our operations staff. My management is convinced that we can buy an off the shelf product that will replace 80 percent of the Perl code. Does such a product exist? In particular, does ServerGraph provide this kind of functionality? Their Web site mentions automation, but does not seem to have any information on the automation features beyond the assertion that they exist. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: 5.3.2 server
Andy, That's interesting. Did this level actually fix your problem. We are at 5.3.2.3 and still have the repair stgvol problem. We have on open pmr with them, but supposedly there is still an open apar to address repair stgvol. We had this problem again just yesterday.really a pain because it does not send any errors anywhere...everything just kinda gets hung and waits around for mounts and so forth. Anyway, we are putting some alerts out there to tell us when a repair stgvol kicks off so we can see if it completes successfully or hangs but just curious if your issues went away completely. Thanks, Rod -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Thursday, March 30, 2006 2:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 5.3.2 server I don't know what level you came from, but we had to put on 5.3.2.3 to fix repair stgvol hanging TSM. --- Lawrence Clark [EMAIL PROTECTED] wrote: I just upgraded to 5.3.2 on our DR server. Any required maintenance at this level? Session established with server BACKUP: AIX-RS/6000 Server Version 5, Release 3, Level 2.0 Server date/time: 03/30/06 15:27:21 Last access: 01/06/06 09:46:47 The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments. Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
5.3.2.2 volume question
I recently upgraded to 5.3.2.2 server level, about 2 1/2 weeks ago. I have 2 tsm servers, tsm1 and tsm2, each share a 3589 library with 5 frames 60 drives. tsm1 is the library manager. We have been noticing lately that when we run a report to show private, scratches, dbb vols, we have a column of private tapes that increases everyday that are really supposed to be scratch tapes. What I have found is, when reclamation runs on tsm2 for primary tape pools, it marks the tape as deleted and ready for scratch like it should, but on tsm1, it still shows the tape as private, if you q vol on either tsm server, they know nothing about the tape, but again q libvol shows the tape as private like below: TSMLIB1 T01779 PrivateTSMCORP1 1,054 LTO I can check the tape out and recheck it in as scratch and it will be used as scratch from there out. I went back and checked our reports, and before the upgrade, we had 3-5 tapes in the status, now we have 140, If I look at the daily reports each day, it grows each day from the day we did the upgrade. So, has anybody else seen this with 5.3.2.2 or any other ideas on what might be causing this. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: 5.3.2.2 volume question
Sorrythat was a typo on previous message, we have a 3584, not a 3589. _ From: Park, Rod Sent: Thursday, February 16, 2006 7:53 AM To: 'ADSM-L@VM.MARIST.EDU' Subject: 5.3.2.2 volume question I recently upgraded to 5.3.2.2 server level, about 2 1/2 weeks ago. I have 2 tsm servers, tsm1 and tsm2, each share a 3589 library with 5 frames 60 drives. tsm1 is the library manager. We have been noticing lately that when we run a report to show private, scratches, dbb vols, we have a column of private tapes that increases everyday that are really supposed to be scratch tapes. What I have found is, when reclamation runs on tsm2 for primary tape pools, it marks the tape as deleted and ready for scratch like it should, but on tsm1, it still shows the tape as private, if you q vol on either tsm server, they know nothing about the tape, but again q libvol shows the tape as private like below: TSMLIB1 T01779 PrivateTSMCORP1 1,054 LTO I can check the tape out and recheck it in as scratch and it will be used as scratch from there out. I went back and checked our reports, and before the upgrade, we had 3-5 tapes in the status, now we have 140, If I look at the daily reports each day, it grows each day from the day we did the upgrade. So, has anybody else seen this with 5.3.2.2 or any other ideas on what might be causing this. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
AIX 5.3 upgrade issues?
Hello all, I recently upgrade my tsm servers to AIX 5.3 ML1 running tsm 5.2.3.3 since our aix upgrade, our database backups went from 20-35 minutes per server to about 2-4 hrsanybody else experienced this and any suggestions? This is the only significant event that has happened to lead me to believe maybe it was the aix upgrade that. Actually expiration seems to run longer...more b/u sessions still running every morning when I come in than normal...so overall tsm system performance seems to be suffering...thanks in advance for any help This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Re: TSM migration from 5.1 to 5.2
Just curious Why would you not do an audit DB and what all does an audit DB do? -Original Message- From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:34 AM To: [EMAIL PROTECTED] Subject: Re: TSM migration from 5.1 to 5.2 No! I would not do an audit db if I dont have been told to do one by IBM support, or if I have strong evidence that I need to do an audit. The upgrade itself does not require an audit db! //Henrik |+- || Lawrence Clark | || [EMAIL PROTECTED]| || ATE.NY.US | || Sent by: ADSM: Dist | || Stor Manager | || [EMAIL PROTECTED] | || | || | || 2004-08-26 15:09 | || Please respond to | || ADSM: Dist Stor | || Manager | || | |+- --- | | | | To: [EMAIL PROTECTED] | | cc: (bcc: Henrik Wahlstedt) | | Subject: TSM migration from 5.1 to 5.2 | --- | Hi: We are getting set for the migration from TSM 5.1 to 5.2. For people who have already done this, did you precede the install of the 5.2 software with an 'audit db fix=yes'? --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
Passwords for client restores
Right now we have about 800 clients and to do a restore, the password is the same for all clients. How are others doing this. We don't want to be in the business of password generation/maintenance to change passwords all the time. We also don't want just anybody being able to do a restore on any box because the passwords are the same everywhere. We are probably going to get hammered by auditors before long about having the same password. Any suggestions would be appreciated. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email.
