Re: server restore behavior
If at all possible, yes. But you could get into a scenario where one session is waiting for a tape drive, but not the tape in question, AND it has been waiting longer than any other session. If so, the tape will dismount and the other tape will mount for the long-waiting session. And the first tape will remount later, for some other session. But for any given session, the tape will mount once unless pre-empted by a higher priority process (IIRC, the only process with a higher priority than a restore is a TSM database backup). Back in our first three years of D/R we had four DLT-7000 drives in our hotsite contract with no library, so we configured a 'manual' library with 4 tape drives. We got intimately acquainted with the TSM tape handling process as a result. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Laura Mastandrea Sent: Friday, August 18, 2006 12:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: server restore behavior We just had a DRP test and this question came up and I'd like confirmation that I'm reading your remark correct. TSM, on a restore, will mount a tape once and take all the files off of once? thx To ADSM-L@VM.MARIST.EDU cc From Sent by Kauffman, Tom [EMAIL PROTECTED] on 08/18/2006 11:30 AM ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Subject Re: [ADSM-L] server restore behavior Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU TSM will mount and start as many sessions as possible, and the rest will be in 'wait media' state until the tape they need (or a tape drive) becomes available. Given your scenarion, you may have one session reading tape and the other four waiting for access to the same tape. When the first session has retrieved ALL the files it needs from the first tape, it will go to the second (if not in use) and the session that has been waiting the longest will now get access to that first tape. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Friday, August 18, 2006 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: server restore behavior This is more of a curiosity question than a problem. In a multiple-client restore scenario where you start up say 5 restores at once from different nodes (with 4 tape drives, and resourceutilization set to 4 on nodes), how does the server process the request? Technically, data from all 5 nodes are probably on a lot of the same tapes. Does it A) mount each tape exactly once, getting all data for all running restores off that tape before unmounting. B) Process the restores relatively serially for each node, giving each all 4 drives until completed. Unmounting/remounting the same tapes multiple times. C) Only give each node 1 tape drive to work with, which will effectively ellicit behavior very similiar to option B. Or does it do something different than any of these? Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. 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. DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender or, the sender's
Re: server restore behavior
So from the sound of it, a slightly less optimal version of Method A gets used. It will keep one tape mounted until all running or MediaW sessions get their crack at it, but while those other sessions are waiting for access to the tape they won't move on to attempt getting data from other tapes. [EMAIL PROTECTED] 08/18/06 11:30 AM TSM will mount and start as many sessions as possible, and the rest will be in 'wait media' state until the tape they need (or a tape drive) becomes available. Given your scenarion, you may have one session reading tape and the other four waiting for access to the same tape. When the first session has retrieved ALL the files it needs from the first tape, it will go to the second (if not in use) and the session that has been waiting the longest will now get access to that first tape. Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Troy Frank Sent: Friday, August 18, 2006 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: server restore behavior This is more of a curiosity question than a problem. In a multiple-client restore scenario where you start up say 5 restores at once from different nodes (with 4 tape drives, and resourceutilization set to 4 on nodes), how does the server process the request? Technically, data from all 5 nodes are probably on a lot of the same tapes. Does it A) mount each tape exactly once, getting all data for all running restores off that tape before unmounting. B) Process the restores relatively serially for each node, giving each all 4 drives until completed. Unmounting/remounting the same tapes multiple times. C) Only give each node 1 tape drive to work with, which will effectively ellicit behavior very similiar to option B. Or does it do something different than any of these? Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you. 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. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Simple ISC web interface console.
When looking at your list of TSM servers in the Storage Devices menu, click on the underlined name of the server you want adjust the script on. This will bring up the server properties screen below. There you will see a link to your scripts. Ryan Miller Principal Financial Group Tivoli Certified Consultant Tivoli Storage Manager -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: Friday, August 18, 2006 12:21 PM To: ADSM-L@VM.MARIST.EDU Subject: Simple ISC web interface console. Well, I've done it. I have upgraded all my TSM servers to 5.3 and now need to become friendly with the horrid beast called ISC. I've poked and prodded, but ~where~ do I have to go in the web interface to change a server script? (not the maintenance script). Thanks, Ben -Message Disclaimer- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to [EMAIL PROTECTED] and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act (E-Sign) unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements.
Re: Does the IBM 3584 support autosense for drive element number?
I just participated in a dr test exercise and we had to code the element number in our devconfig. To ADSM-L@VM.MARIST.EDU cc From Sent by Prather, Wanda [EMAIL PROTECTED] on 07/12/2006 11:31 AM ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Subject Re: [ADSM-L] Does the IBM 3584 support autosense for drive element number? Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I don't know where that is documented. But I didn't have to specify element numbers for mine, TSM figured it out. (We are connecting via Winders, however.) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kauffman, Tom Sent: Wednesday, July 12, 2006 11:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Does the IBM 3584 support autosense for drive element number? I'm trying to clean up my D/R scripting, and this is one area that would help -- but I'm having a heckuva time trying to track down the answer. 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. DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender or, the sender's employer, or the employer's parent company, affiliates or subsidiaries.
Re: Simple ISC web interface console.
1. First, go into the Storage Devices and select the server you want to look at the scripts for. 2. Under the server properties for that server, now select Scripts. This will bring up the list of all the scripts for that server. 3. Select the script you want to modify by selecting the box next to the script. 4. Now go to the pull-down menu, and select modify script. This will now allow you to modify the server script. At 11:21 AM 8/18/2006 -0600, you wrote: Well, I've done it. I have upgraded all my TSM servers to 5.3 and now need to become friendly with the horrid beast called ISC. I've poked and prodded, but ~where~ do I have to go in the web interface to change a server script? (not the maintenance script). Thanks, Ben Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
Re: poor performance
On Fri, 18 Aug 2006 09:23:06 -0700, Gill, Geoffrey L. [EMAIL PROTECTED] said: This is a 6h1 with 4 processors and 4Gb memory. Disks are SSA, 2 controllers and 4 full D40's for TSM DB, Logs and disk pools. All disk JBOD. GIG nic that when at it's peak only 50% utilized. 4 full D40s, JBOD, for the database? Ouchie. There's my leading candidate for performance problems. I suggest one VG with a bunch of non-raided disks in it, raw LVs one or two to a spindle, with mirrors on separate spindles, for DB and log. - Allen S. Rout
Re: TSM configuration manager
The problem is that when you nodes defined to a domain just moving a new domain from another profile into place can not be done. On the managed server you can create a new domain (temporarily). Then at the domain level you can issue the move nodes to another domain and select the temp domain. Then you can update the profile to bring down the domain from your configuration manager. Lastly, you will have to move the nodes from the temp domain back to the STANDARD domain. From that point forward any changes to the domain on the configuration manager will be replicated. The only problem is that once you move nodes out of domain you loose their schedule associations. So it is a good idea to run the q event * * to a file first so that you can recreate the schedule associations after you move the nodes back. Kyle John Bremer [EMAIL PROTECTED] wrote: All, I want to set up TSM configuration manager. I have several AIX 5.1 TSM servers 5.3.2. I have defined a profile on one server, and defined a profile association to this configuration profile for domains, using our STANDARD domain as a test to propagate additions and changes to subscribers. Configuration manager is set On to this server: tsm: DSMSERV1q profile f=d Configuration manager: DSMSERV1 Profile name: TSM SERVER PROFILE Locked?: No Description: TSM Master Server administrators: Policy domains: STANDARD Administrative command schedules: Server Command Scripts: Client Option Sets: Servers: Server Groups: On a second server I have defined subscription to the master: tsm: DSMSERV2q subscription f=d Configuration Profile name Last update manager date/time DSMSERV1 TSM SERVER 08/16/06 11:59:40 PROFILE This server has Allow Replace yes. On configuration manager I run: notify subscribers and it fails at the subscriber end: 08/17/06 08:21:53 ANR0408I Session 75279 started for server DSMSERV1 (AIX-RS/6000) (Tcp/Ip) for configuration management. (SESSION: 75279) 08/17/06 08:21:54 ANR0409I Session 75279 ended for server DSMSERV1 (AIX-RS/6000). (SESSION: 75279) 08/17/06 08:21:54 ANR0408I Session 75280 started for server DSMSERV1 (AIX-RS/6000) (Tcp/Ip) for configuration management. (SESSION: 73099) 08/17/06 08:21:54 ANR3152I Configuration refresh started with configuration manager DSMSERV1. (SESSION: 73099) 08/17/06 08:21:54 ANR3350W Locally defined domain STANDARD contains at least one node and cannot be replaced with a definition from the configuration manager. (SESSION: 73099) 08/17/06 08:21:54 ANR3171E Configuration refresh with configuration manager DSMSERV1 had to skip processing for one or more objects. (SESSION: 73099) 08/17/06 08:21:54 ANR0409I Session 75280 ended for server DSMSERV1 (AIX-RS/6000). (SESSION: 73099) 08/17/06 08:21:54 ANR3151E Configuration refresh failed with configuration manager DSMSERV1. (SESSION: 73099) Stupid question, but should I not expect the configuration manager to be able to update existing domains, etc. across my complex? Does anyone have any idea what I am doing wrong, or if I have the wrong expectations? Thank you. John Bremer __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: server restore behavior
On Fri, 18 Aug 2006 12:30:08 -0400, Kauffman, Tom [EMAIL PROTECTED] said: TSM will mount and start as many sessions as possible, and the rest will be in 'wait media' state until the tape they need (or a tape drive) becomes available. Given your scenarion, you may have one session reading tape and the other four waiting for access to the same tape. When the first session has retrieved ALL the files it needs from the first tape, it will go to the second (if not in use) and the session that has been waiting the longest will now get access to that first tape. Several important points: The session that has been waiting the longest will get access to the tape -drive-, and if the longest-waiting session desires the mounted tape, that's all good. But the chances of that aren't great: each restore will calclulate its' list of desired tapes and its' desired order independantly, and each one will walk through that order linearly. Period. (last time I checked). This means that if hosts A and B both want tapes T0 and T1, and they both pick that order, and A gets T0 first, B will not fall back to deal with T1 before it blocks on T0 access. That dynamic reordering of work is just not something TSM does at the moment, and I can't blame them too much. Sounds hard in most cases. Implications for the case Troy suggested (5 simultaneous restores, 4 tapes drives, many noncollocated tapes) are that it is extremely unlikely that any mounted tape will be cleanly passed from one restore process to another; transitions will usually require a dismount and a mount. As usual, anyone got evidence that TSM's gotten smarter since last I looked, shoot me down. - Allen S. Rout
Re: server restore behavior
AFAIK, it's first come first serve. - The different restore sessions will not talk to each other, and the TSM server will not coordinate their resource usage, so it's not A. - Since each session will compete for drives and get the next one available when they get up to bat, it's not B. - And since they all have resourceutilization 4, it's not C. In fact, I'd think it's quite unpredictable, because each client may have differing hardware capabilities, other network traffic will influence it, and what each client is restoring will affect how quickly it gets to the tape mount request(s). It would be nice, though, if the TSM server did coordinate the active sessions. Even nicer would be a facility to define a restore plan, assigning priorities and weights. I suppose you could hack something together with some fancy scripting and/or using an external scheduler like Control-M... but seems like it would be a lot of work. Robin Sharpe Berlex Labs Troy Frank [EMAIL PROTECTED] WISC.EDU To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU server restore behavior 08/18/2006 12:22 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU This is more of a curiosity question than a problem. In a multiple-client restore scenario where you start up say 5 restores at once from different nodes (with 4 tape drives, and resourceutilization set to 4 on nodes), how does the server process the request? Technically, data from all 5 nodes are probably on a lot of the same tapes. Does it A) mount each tape exactly once, getting all data for all running restores off that tape before unmounting. B) Process the restores relatively serially for each node, giving each all 4 drives until completed. Unmounting/remounting the same tapes multiple times. C) Only give each node 1 tape drive to work with, which will effectively ellicit behavior very similiar to option B. Or does it do something different than any of these? Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
