Re: Reduce DB Log Size
The only weight loss program for the TSM DB, other than getting rid of unneeded stuff, is expiration. Make sure it is started daily, and let it run a long time. I start it as soon as DB backup ends, and then cancel it with CANCEL EXPIRATION just before the next DB backup is started. With my 200GB database, tuning for expiration is a prime consideration. Either DB backup or expiration is always running. Eventually, there will be no other choice except to add a volume and EXTEND DB. If you're almost at 100% now, you most likely have to do that first, and then you can fiddle around with increasing expiration. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Thu, 20 Apr 2006, Richard Sims wrote: On Apr 20, 2006, at 9:49 AM, Norita binti Hassan wrote: My DB is nearly 100% full . Can I use the REDUCE command to solve this problem rather than extend the Db. The REDuce DB command is not a weight loss program for the TSM database, but rather a retraction of the amount of space it may consume within its allotment. You either have to get rid of unneeded stuff in your database (e.g., obsolete filespaces) or extend it. We all have to extend our databases, due to inevitable growth in demand. Richard Sims
Re: hidden flags to EXPIRE INV and CLEANUP EXPTABLE
Correction: In the SHOW NODE against the subkeys, the KEY is the NODE_NAME. Field 1 is still the node number and field2 is PLATFORM_NAME. Also, beware of using SHOW NODE on wrong or random pages. On 06.04.20 at 22:58 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 22:58:34 -0500 From: Josh Davis [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: hidden flags to EXPIRE INV and CLEANUP EXPTABLE UNDOCUMENTED OPTIONS FOR EXPIRE INVENTORY: There are two undocumented/unsupported options for EXPIRE INV; BEGINNODEID and ENDNODEID. These accept the decimal node number of a node and can be used to expire a specific node's filespaces, or a specific range. WHY WOULD YOU EVER WANT TO USE THESE? EXPIRE INV won't check for filespace lock before parsing a filespace. As such, if you're running expiration, and a node is backing up a filespace when expire inventory gets to it, expire inventory will wait indefinitely. When this happens, CANCEL EXPIRATION or CANCEL PROC will register as Cancel Pending but will hang there until the lock is released. Officially there's supposed to be a resource timeout, but IBM wasn't able to give details on how long this is. HOW TO FIND THE NODE NUMBERS: Node numbers are sequential, starting at 1, and are in REG_TIME order. Deletions leave gaps. The short way would be a SELECT statement. Supposedly this can be done, but I couldn't figure out the column name. IBM doesn't like to give info regarding undocumented/unsupported options since that might make them liable to support or defend them in the future. The long way is to use SHOW commands. Use SHOW OBJDIR to find the btree node for the Nodes table. This SHOULD be 38. SHOW NODE 38 (hopefully) will show the top level of the tree. On average, there are about 11 second-level leaf nodes per first level leaf node. If you do SHOW NODE on each subtree, and save these to a file, you'll have the raw data for the nodes table. In the data section, field 1 is the node number in hex, and field 2 is the node name in all-caps ascii. OTHER USES FOR THE NODEID: This can be used with SHOW LOCKS and SHOW THREADS to find out which node is holding the lock preventing expire inv from continuing. From there, you can kill a session so that expire inv can continue or be cancelled. This can also be converted to decimal so you can run EXPIRE INV BEGINNODE=10 ENDNODE=20 or similar to operate only on a specific subset of nodes. This could be used to avoid nodes which have long-running transactions, to quick-expire a huge bunch of data that was just deleted, or to set up scheduled expirations for heavy-expire nodes. These same flags work on CLEANUP EXPTABLE. Since there is no way to cancel CLEANUP EXPTABLE, then running it on a small subset of nodes can help if you suspect you're not expiring all that you should be, but don't want to risk having to shutdown TSM to abort it when you're 50 million objects in and it's a week after you started it. WHY I'M SHARING THIS INFO: I've opened a DCR requesting EXPIRE INVENTORY be given an option to allow detection and skipping of locked filespaces, and that it should be implemented without killing expiration or the session/process holding the filespace lock. The FITS request number is MR0420061821 if you or anyone wants to be added to the notify/me-too list for this. If your sales rep doesn't know where/how to get to FITS, it's on D03DB004.boulder.ibm.com. I think it's under m_dir (marketing). This was way longer than I anticipated, but seemed useful enough to risk sharing. -- Josh
Re: 3584 - determining available clean cycles
for the newer 1/2 tapes (LTO included), cleaning frequency is pretty rare, except in cases where you have genuinely dirty tapes. We have 36 drives, and they clean about once every year or two. I've forced cleaning #2 on several drives because they got I/O errors and out vault returns tapes with lots of external contaminants (dirt, grass bits, etc from hauling tubs around in the back of a box-truck, loading docks, etc). We have pretty heavy utilization too. On 06.04.20 at 18:46 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 18:46:59 -0400 From: Richard Rhodes [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: 3584 - determining available clean cycles Our 3494 lib with 3590H drives get cleaned about twice a day each. The new 3584 has 3592 drives . . . we're not sure what to expect for cleaning frequency. Rick Jim Zajkowski [EMAIL PROTECTED] U To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: 3584 - determining available clean cycles 04/20/2006 06:38 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU On Thu, 20 Apr 2006, Richard Rhodes wrote: Is there a way to tell from AIX the number of cleaning cycles remaining in a 3584? We ended up using TSM-managed, ASNEEDED cleaning, so that it could monitor our tapes. The web interface shows that there are 10 tapes, each with 50 cycles available - total=500. BTW, in the three years we've had our 3584 I don't think our four drives have needed to be cleaned more than five times each... --Jim - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: 3584 - determining available clean cycles
If the library is hooked up to ethernet, you could lynx in and pull the cleaning info from there. On 06.04.20 at 18:38 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 18:38:52 -0400 From: Jim Zajkowski [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: 3584 - determining available clean cycles On Thu, 20 Apr 2006, Richard Rhodes wrote: Is there a way to tell from AIX the number of cleaning cycles remaining in a 3584? We ended up using TSM-managed, ASNEEDED cleaning, so that it could monitor our tapes. The web interface shows that there are 10 tapes, each with 50 cycles available - total=500. BTW, in the three years we've had our 3584 I don't think our four drives have needed to be cleaned more than five times each... --Jim
Re: Tivoli DB limit
I've never heard of a 100million file limitation to TSM. The limits are 13.5GB for the log and 512GB for the TSM DB. It's not DB2 Lite, rather, more like a port of the 1980s version of DB2 that was part of MVS. Dave Cannon in a 2003 TSM symposium said they were considering decoupling the database and using a more current DB2 implementation. Aparently they're still considering it, but it's unk whether they'll actually do this or not. There are technical limitations in modern DB2, specifically lack of bitvector data type or equiv. Even so, the DB I'm working with is 105 million files at about 150GB. The limit here is CPU and I/O of the box to be able to process that many objects in daily admin jobs. For your server, you could look at: Image Backup Journalling (if it's Windows) VirtualMountpoint option (if UNIX) MEMORYEFFICIENT YES and also RESOURCEUTIL 10. These last two will tell it to process one dir at a time, but split out into 5 producers and 5 consumers. This will get things moving faster in the beginning, and give it alot of oomph, but at 50mil files on one client, you're still looking at some serious time for any backup solution. Another option would be to use an incremental by date. This is much faster, as it just compares the mod date of the file to the last backup. The drawback is that deleted files won't be expired, and management class rebinding won't occur. You could still use this daily, then maybe every 10 days use a regular incremental. -Josh On 06.04.20 at 16:28 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 16:28:20 -0500 From: Gaurav Marwaha [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Tivoli DB limit Hi, Problem: We have a huge file system with about 30 to 50 million files to be backed up, the incremental backup does the job, but takes too long to complete, out of these 50 million files, only 2 or so actually change. So the scanning runs sometimes into 24 hour window and the next scheduled backup starts without actually completing the previous one. I found filelist parameter where you can specify what to backup, we can use this as we know from the database what files were changed. Someone tells me that the Tivoli DB can take only 100million objects for tracking and filist might not be a correct way to do it. He says there is DB2 lite running behind TSM and that has this limit? In this scenario what is the best approach and is there is a limit at all? Even in normal incremental operation how does TSM scan the include directory list, I mean even when it runs normal incremental doesn't that 100 million limit still exist? Thank you in advance Gaurav M
Re: 3584 library
This could cause a call-home. From the front panel, or from the web gui of the library, you should be able to have it do a library inventory. It takes about 60 seconds per frame. On 06.04.20 at 15:11 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 15:11:21 -0400 From: David E Ehresman [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: 3584 library I don't think I understand how inventory audit works. When you do Audit library 3584lib checkl=barcode should I see the robotics move and read each and every tape slot and resysnc with TSM data base ? how do I get these back in sync On a 3584, an audit library 3584lib checkl=barcode does NOT cause the robotics to move and read the barcodes. It causes TSM to compare its inventory with the 3584 library's inventory which the library has stored in memory. So you first need to cause the 3484 to do an audit (openning closing the fron door will do this) and then run the tsm audit library command. David
Re: collocation groups
Directories are owned by the nodes they belong to. So, if you're using a DIRMC pool with long retention, and you implement collocation or colloc groups, then the directories will be collocated the same as files. On 06.04.20 at 13:29 [EMAIL PROTECTED] wrote: Date: Thu, 20 Apr 2006 13:29:04 -0400 From: Allen S. Rout [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: collocation groups On Wed, 19 Apr 2006 16:50:56 -0700, Gill, Geoffrey L. [EMAIL PROTECTED] said: If 10 nodes are in one group will it only mount one tape even if no other tape drives are busy? Yes; one stream per collocgroup, just like you would get one stream per node. (even if you're collocating by filespace, he grumpily grumped) If I have a directory disk pool that is cached will it still go to one tape after migration or will collocation groups affect that? What I see leads me to believe the answer is yes. I am seeing multiple tapes for the directory tape pool with little to no data. Do folks still use this option? [no clue] Why do tapes that are not full show capacity of 381GB yet when they go full only show about 200GB? Do I need to force compression on with the drives or something? (LTO2's, 3584 Lib) The unfull tapes just parrot back to you the Estimated Capacity you set on the device class. If you're getting 200G on a LTO2, might you have set the devclass FORMAT to be something other than DRIVE? It sure sounds like you're writing uncompressed. - Allen S. Rout
Re: Schedule start delayed
Schedule Randomization. Q STAT and it's in the middle On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote: Date: Tue, 18 Apr 2006 09:19:56 -0600 From: Andrew Raibeck [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: Schedule start delayed It would certainly help to see some more specifics. For example, the dsmsched.log file for one of the clients in question that did not kick off when expected, just to verify that, for sure, it is using prompted scheduling; and the activity log from the scheduled start time and on, to see what the server was doing, as well as other things like the client dsm.opt file for the aforementioned client, and the client option set definition for that client. Server-side randomization has no effect on prompted scheduling. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-04-17 22:13:06: I'm trying to remember what it is about a backup schedule that, even though scheduled for say 8PM, does not kick off right away, nodes show pending for some time. I've been comparing the 5.2 and 5.3 server settings but can't find any obvious differences, yet the 5.2 server kicks off each schedule right at the specific time whereas the 5.3 server I'm putting up does not. I have a clopt set that has schedmode as prompted, which is the same on both servers and scheduling modes is set to any, same on both servers. What am I missing that I thought I'd taken care of? I'd actually prefer to have these guys start right away. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Dell Server for TSM Server ?
Corey, IMHO I would certainly go for the pSeries. It's much more flexible and powerfull than the Intel based boxes. If you must go for the Intel box, I would choose Linux (RedHat or SuSe) as the OS. I've done lost of TSM Servers and the ones running on RS/6000 and pSeries always come out on top. I had an RS/6000 H50 (this was an old box with 4 CPU's and 3GB memory) which would outperform an Intel dual-Xeon with equal memory (running on W2K3). Richard. Van: ADSM: Dist Stor Manager namens Seliger, Corey S. Verzonden: do 20-4-2006 22:35 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] Dell Server for TSM Server ? Allow me to spin the question ever so slightly: PC Server Hardware (like Dells) --OR-- IBM p-Series Hardware? We are in the planning phases of a TSM rollout and our consultant is pushing us towards the p-Series line (somewhere in the neighborhood of a 550). We are deploying in a pretty large environment, so it sounds justifiable. I suppose I am looking for a second opinion of sorts, just to make sure we're getting the best bang for our buck. Thanks! Corey --- Corey S. Seliger Systems Administrator Web Services IT Infrastructure Information Technology at Purdue Tel: 765-496-6597 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Justin Case Sent: Wednesday, April 19, 2006 9:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Dell Server for TSM Server ? Since we have to test the Dell server with Linux OS for TSM server, I have listed questions. What size of the Dell server's are folks deploying 6850 or 2850 ? How many CPU ? How much Memory ? Thanks Justin Case Duke University
TDP SQL questions
TSM Server 5.2.2.0 5.2.4.3 on AIX 1. Is there a way of finding out the TDP version without going into each client and bringing up the gui? From my Q NODE command, it is showing me the client version of the BA client even when I am selecting the TDP nodename. 2. Why does it seem the TDP development is lagging behind? I am being pushed to replace TDP with SQL-Backtrack because: A. We want to provide the DBA's a console to perform backup/restore without giving them admin permissions on each Windows server B. The DBA's want to be able to do table level restores C. TDP does not support x64 for SQL2005 on the Xeon processors (and we use all IBM hardware!) Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: tape capacity
On Apr 20, 2006, at 2:18 PM, Gill, Geoffrey L. wrote: ... So I think the question still remains how to reach that upper limit instead of the lower? Is there a TSM setting I have missed? Is there a drive setting that needs adjusting on the drive itself? ... Geoff - You are taking the moral equivalent of a default in using FORMAT=DRIVE in your devclass. If the stars are in alignment, this will work to get the most of of your tapes drives; but there are circumstances where it won't, and in any case it's a vague specification which departs from my long term, experience based rule that it is always best to tell the system exactly what you want, rather than let it make a decision and make its result indeterminate. So, I would instead specify FORMAT=ULTRIUMC, which is explicit. (This is the approach IBM takes in their Technote 1082581.) This will provide the assurance that you are getting what you want. If, with the next freshly started and then filled tape, you see no improved capacity, it surely indicates that the data is rather incompressible. Note that you can verify that compression is on in a tape drive by issuing an OS query for its attributes. Richard Sims
Re: hidden flags to EXPIRE INV and CLEANUP EXPTABLE
UNDOCUMENTED OPTIONS FOR EXPIRE INVENTORY: There are two undocumented/unsupported options for EXPIRE INV; BEGINNODEID and ENDNODEID. These accept the decimal node number of a node and can be used to expire a specific node's filespaces, or a specific range. WHY WOULD YOU EVER WANT TO USE THESE? EXPIRE INV won't check for filespace lock before parsing a filespace. We are currently using the CLEANUP EXPTABLE cmd with the BEGINNODEID/ENDNODEID options . . . . . . UNDER THE DIRECTION OF TSM SUPPORT. We are on TSM V5.3.2. Back when we were V5.1 (last year), we were getting ANR messages that prevented us from deleted old nodes out of TSM. We did bunches of stuff with support, but the fix was to move to v5.3. This we were planning, and did. As part of migrating to v5.3 we ran the cleanup procedure for Win system objects. After upgrading we still couldn't delete the nodes out of TSM. The solution was to run the CLEANUP EXPTABLE command. We did this on our test system for each of our production databases. Once started, this command cannot be stopped without halting the TSM server. Running it against a production DB on our test server ran well over 2 weeks for one TSM server, and just about 2 weeks for our other TSM server. After running, we were able to delete the nodes. Ok, now we are told by the support center to run it on production. Remember . . . . you cannot run expiration while this is running. We told them we could not go without expiration for that long, and we can't just halt our TSM server at anytime to stop it!! The answer was to get the NODEID's for all the nodes and run CLEANUP EXPTABLE for one node at a time using the BEGINNODEID/ENDNODEID. We tried this on one node . . . it worked, but we have well over 500 nodes on each TSM server. I've writtes a script that automatically works through a file of nodeid's. After each node is cleaned up, it runs expiration for some amount of time. The longer the cleanup runs, the longer expiration runs. I run this script Monday thru Friday, cleaning up one node at a time with some normal expiration between each cleanup. On the weekend I put our normal expiration processing back in place to get a couple good full expiration runs. It took several months to work through the first TSM server. If I understand the output of the command, it fixed almost 15 million errors on this TSM server. The 2nd TSM server has been going through this process since Feb 1st is finally getting close to finishing - it's processed 509 out of 526 nodes. Anyway, this is one reason to use these options. If anyone has a similar problem, I would be happy to send them this script (ksh). It's highly specific to our environment, but could be adapted easily. rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: cannot dismount tape
Marcelo - Use Query PRocess and Query SEssion Format=Detailed to see if the tape/drive is actually in use, and Query Request to see if an associated tape is needed. A situation which goes on for days, as you have encountered, is abnormal, and may indicate that a tape mount is actually not completing, and that can be due to a drive defect or even a tape already in the drive (stuck there, after a previous dismount failed). Inspect the drive for problems. Depending upon your drive type, a Reset or power cycle may clear its condition. But thereafter keep an eye on the drive for further problems, where a technician would have to work on it. Richard Sims
Re: Pthread error on 5.3.3.0 server.
Robert - The Deployment Guide for IBM Tivoli Storage Manager Version 5.3 redbook suggests that the ANR0435W situation was supposed to be fixed at a 5.3 level earlier than yours. I'd recommend contacting TSM Support to see what's up with this. Richard Sims
Re: Tivoli DB limit
On Apr 20, 2006, at 5:28 PM, Gaurav Marwaha wrote: We have a huge file system with about 30 to 50 million files to be backed up, the incremental backup does the job, but takes too long to complete, out of these 50 million files, only 2 or so actually change. So the scanning runs sometimes into 24 hour window and the next scheduled backup starts without actually completing the previous one. Gaurav - You may be new to TSM and not realize that this question has been pursued many times in this forum. You can best review past postings at www.mail-archive.com/adsm-l@vm.marist.edu/ . This is formally known as the Many small files problem. See that entry in http://people.bu.edu/rbs/ADSM.QuickFacts or http:// www.tsmwiki.com/tsmwiki for collected information. Someone tells me that the Tivoli DB can take only 100million objects for tracking and filist might not be a correct way to do it. He says there is DB2 lite running behind TSM and that has this limit? Your information source is faulty. I'd advise more authoritative references, as found on the IBM Web site and in documented referenced in mailing list postings. It is more typically the case that the client is limited in running out of the amount of memory needed to accommodate the Active files list it gets from the server at the start of Incremental backup processing. It behooves a client which serves a highly elevated data complement like this to run a 64-bit version of the operating system for that platform, to best deal with the volumes of metadata that it needs to be able to handle. This provides the expanse needed for holding such arrays in memory. Richard Sims
Re: Tivoli DB limit
What is the OS? Could Journaling or some form of, be helpful here? _ Ian Smith SAN/TSM Specialist IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 21 April 2006 13:38 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tivoli DB limit On Apr 20, 2006, at 5:28 PM, Gaurav Marwaha wrote: We have a huge file system with about 30 to 50 million files to be backed up, the incremental backup does the job, but takes too long to complete, out of these 50 million files, only 2 or so actually change. So the scanning runs sometimes into 24 hour window and the next scheduled backup starts without actually completing the previous one. Gaurav - You may be new to TSM and not realize that this question has been pursued many times in this forum. You can best review past postings at www.mail-archive.com/adsm-l@vm.marist.edu/ . This is formally known as the Many small files problem. See that entry in http://people.bu.edu/rbs/ADSM.QuickFacts or http:// www.tsmwiki.com/tsmwiki for collected information. Someone tells me that the Tivoli DB can take only 100million objects for tracking and filist might not be a correct way to do it. He says there is DB2 lite running behind TSM and that has this limit? Your information source is faulty. I'd advise more authoritative references, as found on the IBM Web site and in documented referenced in mailing list postings. It is more typically the case that the client is limited in running out of the amount of memory needed to accommodate the Active files list it gets from the server at the start of Incremental backup processing. It behooves a client which serves a highly elevated data complement like this to run a 64-bit version of the operating system for that platform, to best deal with the volumes of metadata that it needs to be able to handle. This provides the expanse needed for holding such arrays in memory. Richard Sims _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: 3584 - determining available clean cycles
On Thu, 20 Apr 2006 18:46:59 -0400, Richard Rhodes [EMAIL PROTECTED] said: Our 3494 lib with 3590H drives get cleaned about twice a day each. The new 3584 has 3592 drives . . . we're not sure what to expect for cleaning frequency. Much. Less. Frequent. :) - Allen S. Rout - Has some 3592s 300 miles away, and is happy with that.
Re: Dell Server for TSM Server ?
IBM all the way. You get what you pay for. Vicki Verizon Business -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Seliger, Corey S. Sent: Thursday, April 20, 2006 4:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Dell Server for TSM Server ? Allow me to spin the question ever so slightly: PC Server Hardware (like Dells) --OR-- IBM p-Series Hardware? We are in the planning phases of a TSM rollout and our consultant is pushing us towards the p-Series line (somewhere in the neighborhood of a 550). We are deploying in a pretty large environment, so it sounds justifiable. I suppose I am looking for a second opinion of sorts, just to make sure we're getting the best bang for our buck. Thanks! Corey --- Corey S. Seliger Systems Administrator Web Services IT Infrastructure Information Technology at Purdue Tel: 765-496-6597 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Justin Case Sent: Wednesday, April 19, 2006 9:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Dell Server for TSM Server ? Since we have to test the Dell server with Linux OS for TSM server, I have listed questions. What size of the Dell server's are folks deploying 6850 or 2850 ? How many CPU ? How much Memory ? Thanks Justin Case Duke University
Re: Schedule start delayed
Well, of course it appears in the QUERY STATUS output. But that does not change the fact that randomization has no bearing when SCHEDMODE PROMPTED is being used, which is what Geoff says he is using. Randomization affects POLLING schedulers only (see HELP QUERY STATUS and HELP SET RANDOMIZE).. Now... having said that... my response to Geoff indicated that he should verify that PROMPTED is indeed being used, and if not, then randomization would certainly contribute to the symptom he is seeing. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/21/2006 00:45:17: Schedule Randomization. Q STAT and it's in the middle On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote: Date: Tue, 18 Apr 2006 09:19:56 -0600 From: Andrew Raibeck [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: Schedule start delayed It would certainly help to see some more specifics. For example, the dsmsched.log file for one of the clients in question that did not kick off when expected, just to verify that, for sure, it is using prompted scheduling; and the activity log from the scheduled start time and on, to see what the server was doing, as well as other things like the client dsm.opt file for the aforementioned client, and the client option set definition for that client. Server-side randomization has no effect on prompted scheduling. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm. com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-04-17 22:13:06: I'm trying to remember what it is about a backup schedule that, even though scheduled for say 8PM, does not kick off right away, nodes show pending for some time. I've been comparing the 5.2 and 5.3 server settings but can't find any obvious differences, yet the 5.2 server kicks off each schedule right at the specific time whereas the 5.3 server I'm putting up does not. I have a clopt set that has schedmode as prompted, which is the same on both servers and scheduling modes is set to any, same on both servers. What am I missing that I thought I'd taken care of? I'd actually prefer to have these guys start right away. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Dell Server for TSM Server ?
On Thu, 20 Apr 2006 16:35:20 -0400, Seliger, Corey S. [EMAIL PROTECTED] said: Allow me to spin the question ever so slightly: PC Server Hardware (like Dells) --OR-- IBM p-Series Hardware? We are in the planning phases of a TSM rollout and our consultant is pushing us towards the p-Series line (somewhere in the neighborhood of a 550). We are deploying in a pretty large environment, so it sounds justifiable. I suppose I am looking for a second opinion of sorts, just to make sure we're getting the best bang for our buck. I'll give a big Me Too on the p-series side. The I/O performance on the pseries boxes is just superb. - Allen S. Rout
Re: Dell Server for TSM Server ?
When I pushed for the pseries, the boss called it a premium platform, we went with the 9113-550 the difference between a three year old premium platform and a new one seems to justify ... [EMAIL PROTECTED] 04/21/06 08:34AM IBM all the way. You get what you pay for. Vicki Verizon Business -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Seliger, Corey S. Sent: Thursday, April 20, 2006 4:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Dell Server for TSM Server ? Allow me to spin the question ever so slightly: PC Server Hardware (like Dells) --OR-- IBM p-Series Hardware? We are in the planning phases of a TSM rollout and our consultant is pushing us towards the p-Series line (somewhere in the neighborhood of a 550). We are deploying in a pretty large environment, so it sounds justifiable. I suppose I am looking for a second opinion of sorts, just to make sure we're getting the best bang for our buck. Thanks! Corey --- Corey S. Seliger Systems Administrator Web Services IT Infrastructure Information Technology at Purdue Tel: 765-496-6597 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Justin Case Sent: Wednesday, April 19, 2006 9:16 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Dell Server for TSM Server ? Since we have to test the Dell server with Linux OS for TSM server, I have listed questions. What size of the Dell server's are folks deploying 6850 or 2850 ? How many CPU ? How much Memory ? Thanks Justin Case Duke University - CONFIDENTIALITY NOTICE: This message is confidential, intended only for the named recipient(s) and may contain information that is privileged, or exempt from disclosure under applicable law. If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender by reply e-mail, delete this e-mail from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege. This message and all contents may be reviewed by authorized parties of the Catholic Health System other than those named in the message header. The contents of this message do not bind the Catholic Health System to any contract, position, or course of action unless the sender is specifically authorized to enter into contracts on behalf of the Catholic Health System. The contents of this message do not necessarily constitute an official representation of the Catholic Health System.
Re: Dell Server for TSM Server ?
I inherited a TSM environment all running on Windows. So I was stuck with the OS. I have deployed multiple HP ML570 servers, twin xeon, 3GB memory. Big PCIe buses at the back end. Have 7 LTO2 and 7 LTO3 and have seen the server pretty much pushing them all full bore. Throughput is very good, I would say the windows boxes seem to suffer when it comes to the actual DB processing. Not sure how much the p-series box is, but the ML570 server was less than 10k GBP. _ Ian Smith SAN/TSM Specialist -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: 21 April 2006 14:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Dell Server for TSM Server ? On Thu, 20 Apr 2006 16:35:20 -0400, Seliger, Corey S. [EMAIL PROTECTED] said: Allow me to spin the question ever so slightly: PC Server Hardware (like Dells) --OR-- IBM p-Series Hardware? We are in the planning phases of a TSM rollout and our consultant is pushing us towards the p-Series line (somewhere in the neighborhood of a 550). We are deploying in a pretty large environment, so it sounds justifiable. I suppose I am looking for a second opinion of sorts, just to make sure we're getting the best bang for our buck. I'll give a big Me Too on the p-series side. The I/O performance on the pseries boxes is just superb. - Allen S. Rout _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Re: q cont Vol_Name
In the normal course of events, you should not need to change the status
of a tape from private to scratch. When all the data on a given volume
expires the tape will go into a pending state for the reuse delay time
defined for the storage pool. When the reuse delay is up, it will be
deleted from the storagepool and go to a scratch status. This assumes
it started out as a scratch tape and was not manually assigned to a
storagepool with a 'def vol' command.
The following script will list any lost tapes you might have, i.e.
tapes that are not in a storagepool or being used as a db backup but are
not in scratch status:
tsm: ULTSMq script q_lost_tapes f=l
Name Line Command
Number
-- --
Q_LOST_TA- 10 select volume_name as Private Tapes NOT in Use -
PES
20 from libvolumes -
30 where status='Private' -
40 and libvolumes.volume_name not in -
50 (select volume_name from volumes) -
60 and libvolumes.volume_name not in -
80 (select volume_name from volhistory -
90 where type in ('BACKUPFULL', -
100'BACKUPINCR', -
110'DBSNAPSHOT', -
120'EXPORT'))
[EMAIL PROTECTED] 4/20/2006 4:39 PM
We are experiencing a long wait when do q content volume_name. IS that
normal ...at times it will take over 2 hours ? what we want to do is
check if the volume has data in it if it has no data and marked Private
status then we want to change its status=Scratch but not if it has data
in it and it belongs to a Pool. I noticed q vol VOlume_name returns very
quick. IS it safe to assume that if volume doesn't belong to any pool
then it shouldn't have any data in it and we could update its
status=Scratch ?
Appreciate any input . We are on TSM server 5.3.0.0 with 3485library
Thanks
Ashok
Re: cannot dismount tape
Thanks Richard. That tape is in use in reclamation process 51 Space ReclamationVolume FZW945 (storage pool CTA-SUN-ARCHS1), Mov ved Files: 126, Moved Bytes: 3,122,093, Unreada able Files: 0, Unreadable Bytes: 0. Current Phy ysical File (bytes): 7,846,095 Current input volume: FZW945. Waiting for mount of scratch volume (180001 sec conds). There´re no sessions requesting that tape and if I excecute query request: ANR8346I QUERY REQUEST: No requests are outstanding. I´ve 2 drives, and that situation had happens with 2 drives and many tapes since many days ago. When I restart the sever the problem disappeared for a few days and happens again. There´s another test that I can make? Thanks again Marcelo. -Mensaje original- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de Richard Sims Enviado el: viernes, 21 de abril de 2006 9:05 Para: ADSM-L@VM.MARIST.EDU Asunto: Re: [ADSM-L] cannot dismount tape Marcelo - Use Query PRocess and Query SEssion Format=Detailed to see if the tape/drive is actually in use, and Query Request to see if an associated tape is needed. A situation which goes on for days, as you have encountered, is abnormal, and may indicate that a tape mount is actually not completing, and that can be due to a drive defect or even a tape already in the drive (stuck there, after a previous dismount failed). Inspect the drive for problems. Depending upon your drive type, a Reset or power cycle may clear its condition. But thereafter keep an eye on the drive for further problems, where a technician would have to work on it. Richard Sims
Re: cannot dismount tape
Check the actlog- there looks to be no scratch tapes! Or a problem mounting volumes in the library. _ Ian Smith SAN/TSM Specialist IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Marcelo Barreto Sent: 21 April 2006 15:44 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] cannot dismount tape Thanks Richard. That tape is in use in reclamation process 51 Space ReclamationVolume FZW945 (storage pool CTA-SUN-ARCHS1), Mov ved Files: 126, Moved Bytes: 3,122,093, Unreada able Files: 0, Unreadable Bytes: 0. Current Phy ysical File (bytes): 7,846,095 Current input volume: FZW945. Waiting for mount of scratch volume (180001 sec conds). There´re no sessions requesting that tape and if I excecute query request: ANR8346I QUERY REQUEST: No requests are outstanding. I´ve 2 drives, and that situation had happens with 2 drives and many tapes since many days ago. When I restart the sever the problem disappeared for a few days and happens again. There´s another test that I can make? Thanks again Marcelo. -Mensaje original- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de Richard Sims Enviado el: viernes, 21 de abril de 2006 9:05 Para: ADSM-L@VM.MARIST.EDU Asunto: Re: [ADSM-L] cannot dismount tape Marcelo - Use Query PRocess and Query SEssion Format=Detailed to see if the tape/drive is actually in use, and Query Request to see if an associated tape is needed. A situation which goes on for days, as you have encountered, is abnormal, and may indicate that a tape mount is actually not completing, and that can be due to a drive defect or even a tape already in the drive (stuck there, after a previous dismount failed). Inspect the drive for problems. Depending upon your drive type, a Reset or power cycle may clear its condition. But thereafter keep an eye on the drive for further problems, where a technician would have to work on it. Richard Sims _ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _
Database backups
Hi folks, I'm considering a database backup strategy something like this: a. Every day write incremental backups to a FILE devclass on a remote server. b. Every Friday write a full backup to the same remote FILE devclass. c. We take our copypool tapes out on Friday as well, so I would additionally generate a db snapshot to tape and remove it from the library at the same time. Does this seem to pass muster? My reasoning for the FILE backups is that I'd like to have a db backup in case the RAID/filesystem holding my online DB breaks, but I'm uninterested in buying a number of LTO2 tapes just to write a 24 gigabyte file to them. --Jim
SV: Database backups
Hi Jim, Why not buy a cheap NAS box on 250GB and keep that NAS Device always mounted in the filesystem and do the DB backups to that? So even if the RAID breaks down you still have an on-site backup of your DB for fast recover. But you still need to bring back the offsite tapes for all user data. Thanks Christian -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Jim Zajkowski Skickat: den 21 april 2006 17:57 Till: ADSM-L@VM.MARIST.EDU Ämne: Database backups Hi folks, I'm considering a database backup strategy something like this: a. Every day write incremental backups to a FILE devclass on a remote server. b. Every Friday write a full backup to the same remote FILE devclass. c. We take our copypool tapes out on Friday as well, so I would additionally generate a db snapshot to tape and remove it from the library at the same time. Does this seem to pass muster? My reasoning for the FILE backups is that I'd like to have a db backup in case the RAID/filesystem holding my online DB breaks, but I'm uninterested in buying a number of LTO2 tapes just to write a 24 gigabyte file to them. --Jim
Re: Database backups
If you are able to afford to lose up to a weeks worth of data this seems like a reasonable approach. Since you are only sending your copypools tapes off once a week, if you lose your primary pool you will only be able to restore up to the most recent Friday. [EMAIL PROTECTED] 4/21/2006 11:57:16 AM Hi folks, I'm considering a database backup strategy something like this: a. Every day write incremental backups to a FILE devclass on a remote server. b. Every Friday write a full backup to the same remote FILE devclass. c. We take our copypool tapes out on Friday as well, so I would additionally generate a db snapshot to tape and remove it from the library at the same time. Does this seem to pass muster? My reasoning for the FILE backups is that I'd like to have a db backup in case the RAID/filesystem holding my online DB breaks, but I'm uninterested in buying a number of LTO2 tapes just to write a 24 gigabyte file to them. --Jim
Re: Database backups
On Fri, 21 Apr 2006, David E Ehresman wrote: If you are able to afford to lose up to a weeks worth of data this seems like a reasonable approach. Since you are only sending your copypools tapes off once a week, if you lose your primary pool you will only be able to restore up to the most recent Friday. We did an back-of-the-envelope for recoverability to expense, and it was shown to not be worth the cost to recover more than one week or so. Our daily incrementals on our main user data servers weigh in at about 5G a day, total. --Jim
DB Volumes
I have only one mount point for a 20G TSM database which is 70% utilized. Which is more effecent one big volume, several medium sized volumes or many smaller volumes? I'm on 5.3.2. Ray Baughman TSM Engineering Systems Administrator National Machinery LLC Phone 419-443-2257 Fax 419-443-2376 Email [EMAIL PROTECTED]
Poll for error question
Good day All , I am using 3.4 on VM server , clients are about that old too. (I know, you all first advise to get something for the current millennium, Im working on that ) I am finding multiple instances where unregistered nodes contact the server and try to back up, I see them in console mode, but I don't know how many I am actually getting. Is there a command I can run where I poll the actlog for occurrences of this say for the last week? I just inherited this one, and I know some newer versions of TSM, but this one is beyond me. Any help is more than appreciated. Jeremy Cloward In this golden age of communication , means everyone talks at the same time Justin Sullivan
Atape 8.4.9.0 and LTO3 tsm 5.1.5
Dear TSMers, Does anyone know if atape 8.4.9.0 supports lto3? We want to upgrade our 3584 from lto2 to lto3. The library maanger is on aix 5.3 and has the newest atape installed (9.xx) but we still have one library client running tsm 5.1.9.3 on aix 4.3.3 and the atape 8.4.9.0. (yes we are trying to get rid of this guy). The readme is not very clear. Thanks in advance -- Otto Schakenbos System Administrator TEL: +49-7151/502 8468 FAX: +49-7151/502 8489 MOBILE: +49-172/7102715 E-MAIL: [EMAIL PROTECTED] Corporate IT Europe Teleflex Holding GmbH Fronackerstrasse 33-35 71332 Waiblingen GERMANY
Re: Poll for error question
Query the activity log for the desired period and specify the message number Example: query actlog begind=-7 begint=00:00 msgno=0422 Orville L. Lantto Glasshouse Technologies, Inc. From: ADSM: Dist Stor Manager on behalf of Jeremy Cloward Sent: Fri 4/21/2006 12:53 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Poll for error question Good day All , I am using 3.4 on VM server , clients are about that old too. (I know, you all first advise to get something for the current millennium, Im working on that ) I am finding multiple instances where unregistered nodes contact the server and try to back up, I see them in console mode, but I don't know how many I am actually getting. Is there a command I can run where I poll the actlog for occurrences of this say for the last week? I just inherited this one, and I know some newer versions of TSM, but this one is beyond me. Any help is more than appreciated. Jeremy Cloward In this golden age of communication , means everyone talks at the same time Justin Sullivan
server-to-server password expiration problem, again? Still?
Hi, all. I'm still chewing on my server-to-server password problems (my PMR has been open since the January discussion) and was wondering if anyone else had gotten any satisfaction out of IBM on this. I know at least a few of you were also encountering the same problem. To recap: When the server-to-server volume password expires, it fails to update. This means that virtual volumes stop passing, and in my case DB backups stop happening, resulting in a log-full coredump. - Allen S. Rout
Library with librtype FILE
Hi all I want to create a Library with LIBRTYPE=FILE I'm using the Admin Center ... How can I do it ... I was able to create one with TSM 5.2.X TSM server windows 2000 SP4TSM 5.3.3.0 Thanks Luc Beaudoin Administrateur Réseau / Network Administrator Hopital General Juif S.M.B.D. Tel: (514) 340-8222 ext:8254
migration processes with collocation groups
I'm a little confused as to how data is migrated to tape with collocation groups configured. Let's say I have 2 collocation groups in a single domain each with 10 computers, and I have configured the disk pool to migrate using 8 processes, how many processes should I see migrating data? What I seem to see is just 2 processes so I'm wondering what is the best way to configure the system to migrate quickly yet keep groups of computers together. I don't want to collocate each node on it's own tape but I do want to take advantage of migrating data with as many drives as possible. Maybe I'm just misinterpreting how things should work. Which wouldn't be the first time. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
encryption and lanfree ?
A couple of questions about lanfree backup: Does the standard client option 'include.encrypt' work? How about the API option 'enableclientencryptkey'? Server is TSM 5.3.3 All feedback, comments, documentation references appreciated. Thanks, Robert Moulton University of Washington Computing Communications
AW: SAN Disk for TSM diskpool for backups ?
Roger, I think that' not total correct. The speed of raid 5 depends of several things. Two of them are how big and sequential that write io's are. There are hardware vendors that implement raid 5 in their san very tricky: If the incoming data are large and sequential they are buffered by the san system in write cache until a full stripe can be written to all disks in a raid 5 group (typical 4+1). In this way a raid 5 is faster than a raid 1 since the write penalty is only 20% and not 50% as in raid 1. hope this was clear regards Stefan Holzwarth Von: ADSM: Dist Stor Manager im Auftrag von Roger Deschner Gesendet: Do 20.04.2006 19:00 An: ADSM-L@VM.MARIST.EDU Betreff: Re: SAN Disk for TSM diskpool for backups ? You will experience slower client backups with ANY configuration that is RAID5 for your disk storage pools. The reason is that client backup is 100% writes in the disk storage pools, and RAID5 is very slow at writes. The throughput difference is significant - as much as 75% in our case. After much experimentation, I have found that RAID1 is best for disk storage pools. Not RAID5, not RAID10, but RAID1. RAID5 can save you a little bit of money in disk drives, but you really pay for it in performance of something that is 100% writes. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Wed, 19 Apr 2006, Justin Case wrote: Need comments please reply We are going to be testing Apple Xserver raid disks array as the disks for backing up the clients nightly backups to diskpool. Has any one tried or even is anyone using the Apple Xserver raid disks array for TSM server's diskpools for nightly backups ??? What raid is being used ? We are in the mind set to use RAID5 (5+1) with 1 spare safety net and have a spare disks on site. What issues have come up when using Apple Xserver raid disks array ?? Any experiences that other TSM Admin's have had please reply with any issues of success or problems ? Thanks Justin Case Duke University
Re: Schedule start delayed
I actually got this working. Here is what I remember. All TSM settings, when compared to the other server, matched perfectly. PROMPTED is in fact being used. Could be related to daylight savings time but smit showed the date and time differently than when issuing the command line date through the OS, which as it turns out was 1 hour different. This did not match what TSM was showing also. An accept date said it accepted the date and changed but it still did not match what the OS was saying. I forced through the OS command line, the time to be correct, accepted the date in TSM, once they matched things cleaned themselves up. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Friday, April 21, 2006 6:06 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Schedule start delayed Well, of course it appears in the QUERY STATUS output. But that does not change the fact that randomization has no bearing when SCHEDMODE PROMPTED is being used, which is what Geoff says he is using. Randomization affects POLLING schedulers only (see HELP QUERY STATUS and HELP SET RANDOMIZE).. Now... having said that... my response to Geoff indicated that he should verify that PROMPTED is indeed being used, and if not, then randomization would certainly contribute to the symptom he is seeing. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/21/2006 00:45:17: Schedule Randomization. Q STAT and it's in the middle On 06.04.18 at 09:19 [EMAIL PROTECTED] wrote: Date: Tue, 18 Apr 2006 09:19:56 -0600 From: Andrew Raibeck [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: Schedule start delayed It would certainly help to see some more specifics. For example, the dsmsched.log file for one of the clients in question that did not kick off when expected, just to verify that, for sure, it is using prompted scheduling; and the activity log from the scheduled start time and on, to see what the server was doing, as well as other things like the client dsm.opt file for the aforementioned client, and the client option set definition for that client. Server-side randomization has no effect on prompted scheduling. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm. com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2006-04-17 22:13:06: I'm trying to remember what it is about a backup schedule that, even though scheduled for say 8PM, does not kick off right away, nodes show pending for some time. I've been comparing the 5.2 and 5.3 server settings but can't find any obvious differences, yet the 5.2 server kicks off each schedule right at the specific time whereas the 5.3 server I'm putting up does not. I have a clopt set that has schedmode as prompted, which is the same on both servers and scheduling modes is set to any, same on both servers. What am I missing that I thought I'd taken care of? I'd actually prefer to have these guys start right away. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
