Group replication in Avamar v7

because the cron base is being replaced..

because NON UNIX people can manage it with out having to know vi

easier to 'see' in the gui - for some going cat-ing files is confusing, flipping in the gui can be easier for some.

its the same thing just you manage it in the gui...

that is my thought as an end user  -

my big quesiton is what root/pw is it looking for when you try to setup the destination (cannot get past that part)

my big quesiton is what root/pw is it looking for when you try to setup the destination (cannot get past that part)

It's asking for the "DPN" root password which is the root password for the Avamar server software (as opposed to the root password for the shell account). The default DPN root password is 8RttoTriz.

We used repluser and it worked fine.

How can we use exclude option in policy based replication ? just to exclude one client

And the big reason I think:  so tech support does not have to spend as much time helping everyone

(Thought this needed explaining so took me a while to write it up)

By default replication is one stream kicked off by cron.

It runs down the Avamar domains – in order – from top to bottom.

It has a time limit as that it cannot run when GC is running in 6.x.

For small companies one stream may be enough, for others not.

In my case the replication was never getting to the bottom of the list, and I found I was behind in replication in the 1000’s.

To fix this you have to call support.  They have to make 2 new files, vi a third one, and create a new cron entry for a second replication stream.  They break up your domains into groups.  Says top half in one stream and bottom half in another stream.  And if lucky the 2 streams work.

In my case we had to break it up into 15 streams.  A support tech spent a month webexing in every day to change the order in the streams trying to get them caught up. 

But then domains change, they grow with new servers, or shrink with retired servers.  And a stream that may have been finishing before now does not. And one that use to take a long time now finishes early.

So now you need to modify the groups of what sub-domains are in each and try to even the streams out again. So another call to support to spend time tuning your replication jobs. 

But who knows your system the best, you can monitor it every day.  You have a good clue has to what needs to be changed.  So why not let you monitor and manage it.  Put it into the gui so you can do it without having to go to command line, learning the files, and knowing vi.

By putting it in the gui you can have a better handle on your replication.  Can change it easy.  And the support tech can work on emergency calls.

Now that is just my opinion, the way I see it…

(and thanks Ian - i will try that today)

JH, your explanation is good,but I don't get answer for my question

Here is the scenario, I have 5 domains to replicate,but i dont want to run replication for one domain (say L )in a group

So if i select root check box,that replicates every thing , how can i exclude only particular domain ?

I can select all other domains under root and leaving L , but what if any new domains added under root in future ?do we have to check replication/manage replication groups whenever we add domains ?

If you  go read the 7.0 Administration guide and the part on how to setup replication.

there is a part that talks about exclude  - but it is by type - not by client name.

you should call support and find out if there is a way to exclude one domain.