We stagger our replication during the morning, to avoid locking the node too 
long.  Some things that we have seen:

1.  If the node has a current backup session running and you attempt to 
replicate it, the backup session gets killed since replication takes priority.  
This has been a problem with our TDP nodes that backup during the day.

2.  We have a long running backup job (NODE LONG) that is taking 20 hours to 
complete.  We don't collocate and some data may be written to a tape/file from 
another node (NODE NORMAL) in the evening.  When issuing the replicate NODE 
NORMAL, it waits for the tape that is currently tied up by NODE LONG.  So we 
have 20-30 replication sessions tied up by one long backup job.

This could be fixed with some colocation changes but we are going to container 
pools very soon and this problem gets a work-around by using protect container 
command.



---------------------------------------------------
David Nixon
System Programmer II
Technology Services Group
Carilion Clinic
451 Kimball Ave.
Roanoke, VA 24015
Phone: 540-224-3903
cdnixon AT carilionclinic DOT org

Our mission: Improve the health of the communities we serve.



________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] on behalf of Henrik 
Ahlgren [pablo AT SEESTIETO DOT COM]
Sent: Friday, December 18, 2015 10:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Node replication information?

On Fri, Dec 18, 2015 at 07:42:55AM -0800, Robert Clark wrote:
> I think I'll be running some basic network performance tests
> first. The throughput I'm seeing doesn't appear to match people's
> glowing descriptions of how big the pipes are.

If you have a decent network (10 Gbit), your problem might not be
network performance alone. Can your storage pools handle the
load? Are you simultanously running things like reclamations on the
same disks?

Tuning ReplBatchSize and ReplSizeThresh might also help, and I assume
you've already maxed out TCPWindowSize.

________________________________

Notice: The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. Carilion Clinic 
shall not be liable for the improper and/or incomplete transmission of the 
information contained in this communication or for any delay in its receipt.