David, We're able to saturate our 1Gbps link to our DR site during stgpool protect processes.
The trick is to specify a relatively high number of sessions (50 in this case) to stick-handle around the latency. We've also enabled the sliding TCP window on both source and target and raised the buffers high enough for the servers to allocate an 8M window size. Our before-dedup intake is around 15TB a day, which translates to around 1-2TB. With two protect processes scheduled to run at 1:30 am and pm, they tend to run to completion in 2-3 hours. HTH __________________________ Matthew McGeary Senior Technical Specialist - Infrastructure Management Services PotashCorp T: (306) 933-8921 www.potashcorp.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David Ehresman Sent: Thursday, December 01, 2016 1:03 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Storage container replication If you are doing directory based storage containers and using "protect stg" to replicate data from a primary site to a secondary site, what kind of throughput are you getting on the data movement? David
