Options to help replication to catch up if behind?

Have you considered seeding the fallen-behind-clients' data to the target Avamar system?  This will work for replication besides regular initial backups. 

More detail here:-

108535 - Best practices when backing up remote clients via a WAN

nr - well trouble is, there is already several backup jobs that have been replicated to the DR node, for the clients in question, so the data is already there....plus some local backups that go to the DR Avamar node that the Avamar node's could use.

I was hoping maybe there might be a way to do something similar like the article you mentioned describes, but with the Avamar nodes.  Some sort of way to copy the data to a storage device somehow, and then I go to the DR node and "import", for lack of a better word, to help get the DR node caught up.

I have adjusted the replication jobs a little so the servers I am behind with will get to replicate longer than what they had been before.  Previously the clients in question would replicate maybe 4-5 hours each night, due to just when Avamar get's to the client to replicate the data.  Now the clients are at least running for 24 hours before they have to restart due to timing out.

It would be great if there was a way in Avamar to where I could see the progress overall.  Such as here is the client to replicate, what data is already at DR and what is left.  Unless I don't know about it, I don't know of a way to get that information.  The replication logs provide a lot of information, but I am still learning how to read and understand the logs and what they mean.

Brent - Replication works through clients in alphabetically so if it doesn't manage to complete within the allotted time it's likely that the clients with most to replicate would come later in the dictionary.  You can get an idea by checking the activity screen or the replication log (for cron replication).

Alternatively, use the replcnt.sh script to identify progress.  Bear in mind that the script this isn't part of the supported Avamar product, it's purely a support tool but it can be useful nonetheless.

KB 175604 - Avamar replication monitoring with replcnt.sh script

Also be aware of:-

KB 194867 - Avamar replcnt.sh script fails when run from a system using plugin type replication

Hope that helps..

Nick

You're very welcome..  KB 194867 is currently set to partner visibility but since we may rethink that I'll describe the contents..

When running the script, if you get an error "No dpnname or dstaddr found" or an account / authentication related error it could be due to a /usr/local/avamar/etc/repl_cron.cfg file or bad parameters in that file.

You can either fix the file or specify the parameters over the command line when running the script.

--dpnname=

--dstaddr=

--dstid=

--dstpassword=

Funny that is what the article was about, I ran into that yesterday because I forgot to provide the DR Nodes password, only after I provided it earlier when running the command but then forgot later on. Sometimes it takes me a minute but I eventually get with the game 

thanks!