That would've been me ;) Since this:
"Specifies the maximum number of parallel processes to use for moving data. This parameter is optional. You can specify a value from 1–999, inclusive. The default value is 1. Increasing the number of parallel processes should improve throughput" is mentioned under "Move Node Data - Moving selected filespaces for one node" I would assume that the process handles 1 filespace per process, not like migration & backup storagepool, 1 node per process. Regards Daniel Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 [email protected] http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -----"ADSM: Dist Stor Manager" <[email protected]> skrev: ----- Till: [email protected] Från: Sascha Askani Sänt av: "ADSM: Dist Stor Manager" Datum: 10/11/2011 13:39 Ärende: Re: [ADSM-L] Weird move nodedata with maxproc? Am 11.10.2011 13:31, schrieb Richard Sims: > The TSM documentation fails to say just how Maxprocess is honored in the Move > Nodedata context. In other commands, such as Backup Stgpool, it is known > that operation is by "clusters" - a non-grouped node or a collocation group > of nodes. Whereas your task involves a single node, it looks like you are > getting a single thread. > > Richard Sims, at Boston University Richard, thanks for your reply. I also got a mail from a fellow listmember suggesting that the problem could also arise from the node only having one (1) filespace. Best, Sascha
