Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*server\s+restore\s+behavior\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*server\s+restore\s+behavior\s*$/: 7 ]

Total 7 documents matching your query.

1. server restore behavior (score: 1): Author: Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>; Date: Fri, 18 Aug 2006 11:22:34 -0500; 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; /lists/html/ADSM-L/2006-08/msg00284.html (10,125 bytes)
2. Re: server restore behavior (score: 1): Author: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>; Date: Fri, 18 Aug 2006 12:30:08 -0400; 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; /lists/html/ADSM-L/2006-08/msg00286.html (11,413 bytes)
3. Re: server restore behavior (score: 1): Author: Laura Mastandrea <lmastand AT CHOOSEBROADSPIRE DOT COM>; Date: Fri, 18 Aug 2006 11:41:04 -0500; 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 A; /lists/html/ADSM-L/2006-08/msg00288.html (13,272 bytes)
4. Re: server restore behavior (score: 1): Author: Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>; Date: Fri, 18 Aug 2006 11:46:37 -0500; 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 session; /lists/html/ADSM-L/2006-08/msg00289.html (12,433 bytes)
5. Re: server restore behavior (score: 1): Author: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>; Date: Fri, 18 Aug 2006 13:19:14 -0400; 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, t; /lists/html/ADSM-L/2006-08/msg00291.html (14,443 bytes)
6. Re: server restore behavior (score: 1): Author: Robin Sharpe <Robin_Sharpe AT BERLEX DOT COM>; Date: Fri, 18 Aug 2006 16:12:36 -0400; 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; /lists/html/ADSM-L/2006-08/msg00294.html (11,825 bytes)
7. Re: server restore behavior (score: 1): Author: "Allen S. Rout" <asr AT UFL DOT EDU>; Date: Fri, 18 Aug 2006 18:47:38 -0400; 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 cha; /lists/html/ADSM-L/2006-08/msg00296.html (10,554 bytes)

Current List: 1 - 7
Page: [1]