What I do is stack processes. Both my offsite and local LTO-class pools run their reclamations at the same time, so if one gets cancelled, it's just extra resources for the other. That brings the question - are those 10 drives in one library? If so, tell me what possible benefit can come from segregating them?
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bos, Karel Sent: Tuesday, November 04, 2008 10:22 AM To: [email protected] Subject: Re: [ADSM-L] Offsite reclamation problem No :) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: dinsdag 4 november 2008 18:14 To: [email protected] Subject: Offsite reclamation problem We have a 5.4.2.0 TSM server running under mainframe Linux. We have five tape drives available for our primary tape storage pool and five tape drives available for our copy storage pool. We run offsite tape reclaimation with 'maxproc=5'. If a client runs a restore while off reclamation is going on, TSM will take a tape drive away from reclamation. This is done by cancelling a reclamation process, rather than having a process go into mount point wait. TSM does not start a replacement process when this happens. A restore that runs for a couple of minutes can leave a pair of tape drives sitting idle for hours. Is there any configuration setting or release level upgrade that will cause TSM to handle this situation more intelligently?
