Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Why\s+does\s+reclaim\/migrate\s+use\s+only\s+1\s+drive\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Why\s+does\s+reclaim\/migrate\s+use\s+only\s+1\s+drive\s*$/: 3 ]

Total 3 documents matching your query.

1. Why does reclaim/migrate use only 1 drive (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Mon, 26 Feb 2001 15:49:59 +0100; Hi *SM-ers! I have a new 3494 library with two 3590 drives attached to my existing TSM server. I'm trying to move the data from the "old" 3575 library to the 3494. I tried two methods: migrate and re; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-02/msg00997.html (11,759 bytes)
2. Re: Why does reclaim/migrate use only 1 drive (score: 1): Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>; Date: Mon, 26 Feb 2001 10:00:30 -0500; To start ultiple migration processes use: upd stg <stgpool_name> migpr=x where x = number of migration processes you want to start. I don't think there is a way to have more than one reclamation proc; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-02/msg01000.html (14,196 bytes)
3. Re: Why does reclaim/migrate use only 1 drive (score: 1): Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT NL>; Date: Mon, 26 Feb 2001 16:17:07 +0100; Hi David! Tried that, but the 3570 storage pool is a sequential storage pool and the MIGPR parameter isn't valid for sequential storage pools ;-(( Kindest regards, Eric van Loon KLM Royal Dutch Airli; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-02/msg01003.html (10,477 bytes)

Current List: 1 - 3
Page: [1]