Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Benchmarks\s+for\s+MOVE\s+DATA\s+vs\s+MIGRATION\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Benchmarks\s+for\s+MOVE\s+DATA\s+vs\s+MIGRATION\s*$/: 3 ]

Total 3 documents matching your query.

1. Benchmarks for MOVE DATA vs MIGRATION (score: 1): Author: Debra Jeanette Young <djyoung AT VOYAGER DOT NET>; Date: Tue, 2 Jul 1996 17:26:21 -0400; I am looking for information for using MIGRATION vs MOVE DATA on MVS storage pools. Our current MOVE DATA takes about 35 minutes to move about 915M. I want to convert this to migration and was curiou; /lists/html/ADSM-L/1996-07/msg00039.html (8,464 bytes)
2. Re: Benchmarks for MOVE DATA vs MIGRATION (score: 1): Author: "Pittson, Timothy ,Corp,US" <tpittson AT HIMAIL.HCC DOT COM>; Date: Wed, 3 Jul 1996 07:38:53 -0400; Debra, I would think the performance would be similar as they're both performing the same function. The advantage to using migration is that you can kick off multiple concurrent migration processes a; /lists/html/ADSM-L/1996-07/msg00045.html (9,828 bytes)
3. Re: Benchmarks for MOVE DATA vs MIGRATION (score: 1): Author: Dave Cannon <dcannon AT VNET.IBM DOT COM>; Date: Wed, 3 Jul 1996 10:13:10 MST; In addition to the considerations mentioned by Tim, there is an additional advantage to using migration if you are transferring data from a disk storage pool to a collocated storage pool. If this is; /lists/html/ADSM-L/1996-07/msg00050.html (10,394 bytes)

Current List: 1 - 3
Page: [1]