Replication reporting

Thanks Ian, I'll give those a try and get back if I have any issues.

Side question if you don't mind answering on this thread.  On replication in general, I read where it is serial and only uses one thread at a time running thru each client one-by-one, I think that's what I remember reading, though I may be wrong, watching Activity Monitor that does look the way it works.

In that case, if replication doesn't finish in the replication window, say it gets clients 1-50 done and hits the end of the replication window, when the next scheduled replication window opens, does it know to start at client 51 and keep going or does each window start at client 1 again?  This is AVE so this is kind of where my reporting question came in.  Thanks again.

In DPA 6.2, you may find the "Avamar Replication Summary", "Clone SLA Status", and "Backup Replication Sync Times by Client" reports do what you need.

If not, there is a script called dump_root_hashes.rb that can be used to check the list of backups on a source system against a replication target and produce a report in CSV format. For example, to compare the list of backups on avamar1.example.com with the list of backups on avamar2.example.com, you would run the following from avamar1:

./dump_root_hashes.rb --dstaddr=avamar2.example.com

The CSV file can then be imported into Excel where it can be sorted, filtered, sliced, and diced. The "key" column specifies whether a backup is on the (S)ource only, the (D)estination only, or (B)oth so it's usually my go-to for easy filtering.

The script has a number of options that are described in the help. If you have any questions about it, please let me know.

In case Ian doesn't get back to you, Avamar 7.1 and later, EMC introduced multi-threaded replication.  In the Avamar replication GUI, you can change the policy to use more or threads.  That is, it will try and replicate the specified number of clients in parallel.  This policy-based replication is a major improvement over the old cron-based replication. Click on More Options inside of the replication policy to change the number of concurrent threads.

And more to your case, you have additional ways to ensure you can get all your backups replicated in a time fashion.  First, you can tell AVE to only replicate a fixed number of backups, say, the last three.  That means AVE will replicate fewer backups per-client, to get them all backed up faster.  If you have a slow link, you can use this method to get all the backups done each day, then slowly increase the number of backups per client, until you have all your backups replicated, and are able to replicate all new backups within your window.

Second, you can also specify Allow Overtime on larger clients, to ensure replication continues until the backup is copied. This can sometimes work against you, if you have lots of large clients that have large, daily replication needs.

Let us know if that helps!

Karl