Re: tape mount retention behaviour
I have had problems with tapes that won't dismount immediately and in fact take over 1/2 hour to dismount... they will show "dismounting" if you do a 'q mount'. Basically, there is a problem with the thread processes and this was a known bug that was supposed to be fixed with TSM 3.7.4 (supposedly). I am runnin 3.7.3.6 and have this problem if I halt / start the system and reclamation puts all 6 of my drives in my 3575 L32 into use at once. Then , as I said, they will not dismount until the thread processes time out... I asked Tivoli support what alternatives I had and they suggested upgrading to 3.7.4 or newer version of TSM. George Lesho Storage Admin AFC Enterprises Joel Fuhrman [EMAIL PROTECTED] on 02/05/2001 08:17:44 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: tape mount retention behaviour I'm using ACSLS (STK). When I'm doing something like a simultaneous migration of 3 storage pools to 2 tape drives, the behavior I observed, in the past, is that when the first migration completes, it tape was not unmounted until the mount retention period expires. Thus the third migration has to wait the mount retention period before it could get a tape. I get around this by reducing the mount retention to zero during those process that create tape queueing. I will have to check if this behavior still exists in my current level. On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
I also have a 3575 and most of thsi "dismounting" may be due to rebuilding the VCR on the tape header. (This is something used by Magstar tapes). If you check actlog during this time you will propbably see an entry for the tape that "dismount may be delayed" due to rebuilding the VCR on the tape. I have easily seen this take 10 minutes when it happens. I have probably had a few go 20-30 minutes. Priorities can't bypass this - I think it is more a tape media/drive issue than *SM and it has to complete or your tape may not be usable. David B. Longo System Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 02/08/01 02:38PM I have had problems with tapes that won't dismount immediately and in fact take over 1/2 hour to dismount... they will show "dismounting" if you do a 'q mount'. Basically, there is a problem with the thread processes and this was a known bug that was supposed to be fixed with TSM 3.7.4 (supposedly). I am runnin 3.7.3.6 and have this problem if I halt / start the system and reclamation puts all 6 of my drives in my 3575 L32 into use at once. Then , as I said, they will not dismount until the thread processes time out... I asked Tivoli support what alternatives I had and they suggested upgrading to 3.7.4 or newer version of TSM. George Lesho Storage Admin AFC Enterprises Joel Fuhrman [EMAIL PROTECTED] on 02/05/2001 08:17:44 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: tape mount retention behaviour I'm using ACSLS (STK). When I'm doing something like a simultaneous migration of 3 storage pools to 2 tape drives, the behavior I observed, in the past, is that when the first migration completes, it tape was not unmounted until the mount retention period expires. Thus the third migration has to wait the mount retention period before it could get a tape. I get around this by reducing the mount retention to zero during those process that create tape queueing. I will have to check if this behavior still exists in my current level. On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley "MMS health-first.org" made the following annotations on 02/08/01 15:09:55 -- This message is for the named person's use only. It may contain
Re: tape mount retention behaviour
...the tape that "dismount may be delayed" due to rebuilding the VCR on the tape. Priorities can't bypass this - I think it is more a tape media/drive issue than *SM... Good thought, David. As you say, the Activity Log should reflect such a problem. If a Volume Control Region problem, be aware that it is always due to defective drive microcode, and so you'd need to have your CE boost the microcode to a known-good level to rid yourself of the problem. (Once a year or so, a defective microcode release seems to make it out into the field, causing problems like these.) Richard Sims, BU
Re: tape mount retention behaviour
Next time it is hung, do run the undocumented 'show threads' command and you will see the hung drives waiting for the thread to be released on the hung drive before the next mount can occur. This was written up pretty well and can be found in a search of the www.tivoli.com/support information base whatever is occuring is annoying George Lesho Storage Admin AFC Enterprises David Longo [EMAIL PROTECTED] on 02/08/2001 02:05:01 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: tape mount retention behaviour I also have a 3575 and most of thsi "dismounting" may be due to rebuilding the VCR on the tape header. (This is something used by Magstar tapes). If you check actlog during this time you will propbably see an entry for the tape that "dismount may be delayed" due to rebuilding the VCR on the tape. I have easily seen this take 10 minutes when it happens. I have probably had a few go 20-30 minutes. Priorities can't bypass this - I think it is more a tape media/drive issue than *SM and it has to complete or your tape may not be usable. David B. Longo System Administrator Health First, Inc. I/T 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5525 [EMAIL PROTECTED] [EMAIL PROTECTED] 02/08/01 02:38PM I have had problems with tapes that won't dismount immediately and in fact take over 1/2 hour to dismount... they will show "dismounting" if you do a 'q mount'. Basically, there is a problem with the thread processes and this was a known bug that was supposed to be fixed with TSM 3.7.4 (supposedly). I am runnin 3.7.3.6 and have this problem if I halt / start the system and reclamation puts all 6 of my drives in my 3575 L32 into use at once. Then , as I said, they will not dismount until the thread processes time out... I asked Tivoli support what alternatives I had and they suggested upgrading to 3.7.4 or newer version of TSM. George Lesho Storage Admin AFC Enterprises Joel Fuhrman [EMAIL PROTECTED] on 02/05/2001 08:17:44 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: tape mount retention behaviour I'm using ACSLS (STK). When I'm doing something like a simultaneous migration of 3 storage pools to 2 tape drives, the behavior I observed, in the past, is that when the first migration completes, it tape was not unmounted until the mount retention period expires. Thus the third migration has to wait the mount retention period before it could get a tape. I get around this by reducing the mount retention to zero during those process that create tape queueing. I will have to check if this behavior still exists in my current level. On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending
Re: tape mount retention behaviour
thanks. IBM says the same, go to 3.7.4 or 4.1 and upgrade Atape to .50 (?) I wanted to confirm this by getting theirs and your comments. We are on a 3466 and its harder to go to a new level because 3466's are supposed to be maintained by IBM but they say the only do the 'major' upgrades (EC's kinda like hardware maintenance) and my management doesn't want me spending time on the learning curve. sigh. .. joe.f. Its a shame. The previous upgrade was to 3.1.2.0 and the CE put 3.1.2.20 on top of it because of know problems with anything prior. I didn't get so lucky the next time. Even though the readme says avoid 3.7.2 with 3494's ...!!! Joseph A Faracchio, Systems Programmer, UC Berkeley On Wed, 7 Feb 2001, Sheelagh Treweek wrote: Joe, Why don't you try 3.7.4.0 the latest 3.7 version? I believe you won't see this behaviour at that version, but like 3.1. I'm not sure there was an APAR but I do think I observerd this at early 3.7 versions. Regards, Sheelagh -- MIME-Version: 1.0 Date: Tue, 6 Feb 2001 14:13:13 -0800 From: Joe Faracchio [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour To: [EMAIL PROTECTED] ... snipped... Now with 3.7.2 I'm not seeing this 'nice' behaviour but the now the tape sits there blockin another request until the full mount retention expires. This is inefficient in a 2 drive system. ... snipped... Sheelagh Treweek Oxford University Computing Services Email: [EMAIL PROTECTED] Phone: +44 (0)1865 273205 Fax:-273275
Re: tape mount retention behaviour
Its a lot of bother to be changing the mount retention down to zero willy nilly. ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Mon, 5 Feb 2001, Joel Fuhrman wrote: I'm using ACSLS (STK). When I'm doing something like a simultaneous migration of 3 storage pools to 2 tape drives, the behavior I observed, in the past, is that when the first migration completes, it tape was not unmounted until the mount retention period expires. Thus the third migration has to wait the mount retention period before it could get a tape. I get around this by reducing the mount retention to zero during those process that create tape queueing. I will have to check if this behavior still exists in my current level. On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
thanks Kent, at least I've verified that I'm not going crazy and imagining this stuff. IF/WHEN you upgrade to 3.7.x let me know if it changes behaviour on you. Better yet let IBM know! :-) ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Mon, 5 Feb 2001, Kent J. Monthei wrote: We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
Alex, I don't know if I'm using EXTERNAL library types. How would I tell? I have a 3466-C10 that was originally internal (rack) DLT changer (15 slots) We '"down"graded' it to a C00 and bought 3494 w/3590s. Would that be considered a 'third' party media even though its both IBM? What difference should it make anyway? The *SM software should handle it the same. And I don't care about the status after mounting I care about the status of the tape and drive after the tape is "IDLE" and no longer in use but still mounted. thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
Steffan , Joek, no, not really. As I stated originally, previously in 3.1.2.20 I observed the tapes being dismounted as soon as another request of any kind was pending regardless of their retention period. And I've observed tapes staying mounted for the full retention period when there's no need for the drive by a pending mount request. Now with 3.7.2 I'm not seeing this 'nice' behaviour but the now the tape sits there blockin another request until the full mount retention expires. This is inefficient in a 2 drive system. And I'm not pointing to restore request only I'm pointing out this behaviour for all mounts. Setting it to 1 or zero is not the answer. THere are times when I want a tape to stay mounted until the drive is needed for something else, two I can think of are THE offsite/COPYPOOL tape because I run backup diskpool copypool every so often and , more importantly, when a user is running successive restores and keeps requesting the same tape. Has there been previous discussion of this? I can't find it on adsm.org. .. joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley On Mon, 5 Feb 2001, arhoads wrote: It does work that way. If a client is backing up to tape, directly or not, keeping the mount avoids thrashing. Steffan Joel Fuhrman wrote: I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
AW: tape mount retention behaviour
We are on 3.7.2 and we see the same "ugly" behavior. Does anyone know if TSM 4.1 acts the same way? Kind regards Thomas Rupp Vorarlberger Illwerke AG MAIL: [EMAIL PROTECTED] TEL:++43/5574/4991-251 FAX:++43/5574/4991-820-8251 -- Dieses eMail wurde auf Viren geprueft. Vorarlberger Illwerke AG --
tape mount retention behaviour
I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
Re: tape mount retention behaviour
I'm using ACSLS (STK). When I'm doing something like a simultaneous migration of 3 storage pools to 2 tape drives, the behavior I observed, in the past, is that when the first migration completes, it tape was not unmounted until the mount retention period expires. Thus the third migration has to wait the mount retention period before it could get a tape. I get around this by reducing the mount retention to zero during those process that create tape queueing. I will have to check if this behavior still exists in my current level. On Mon, 5 Feb 2001, Alex Paschal wrote: Joseph, Joel, out of curiosity, is there any chance are you using EXTERNAL library types? I know TSM will dismount an idle volume if it needs a mountpoint in 3494's as Kent has pointed out. I think it may behave the same way with a SCSI library type also. In fact, on a hunch, I just now checked my TSM 3.7 Admin Guide, Appendix A, External Media Management Interface Description. The valid return codes for a Volume Mount Request are: SUCCESS DRIVE_ERROR LIBRARY_ERROR VOLUME_UNKNOWN VOLUME_UNAVAILABLE CANCELLED TIMED_OUT INTERNAL_ERROR There is nothing that indicates waiting for a mount point. That could account for idle volumes not being dismounted; TSM doesn't know that the External Library Manager is waiting for a mount point. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Kent J. Monthei [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 5:20 PM To: [EMAIL PROTECTED] Subject: Re: tape mount retention behaviour We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have observed behavior consistent with that described by Joseph in the original email - an idle mount will be immediately dismounted if/when there is another mount pending and no other drive is available. However, we also recently dropped the mount retention from the default 60 minutes down to just 5 minutes. Under what scenarios (or rationale) does it make sense to force tapes to remain mounted more than 5 minutes after a client backup session has completed? -Kent M., GSK [EMAIL PROTECTED] on 05-Feb-2001 19:57 Please respond to [EMAIL PROTECTED] To: ADSM-L cc:(bcc: Kent J Monthei/CIS/PHRD/SB_PLC) Subject: Re: tape mount retention behaviour I thought it always worked this way. At one time I was going to put in a request to have two mount retention times. One for when there are no pending request for a drive and the other for when there are pending request. On Mon, 5 Feb 2001, Joe Faracchio wrote: I recently upgraded from 3.1.2.20 to 3.7.2.0 and notice a very annoying behaviour. The system keeps an idle tape mounted for the full retention period specified despite the pending mounts that are waiting. when / where will this be fixed??? thanks ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley
