I would recommend opening a ticket with the support team for this.

Rob:

Did you ever get a resolution to your problem as we are experiencing the same issues.

Thanks

Ken

Which parameters are not being saved? Is there one specific parameter or is it all of them?

I may know what's happening but I need more detail to be sure.

It is all of them.  EMC has been troubleshooting but has not found any resoultion as of yet.

If you have a service request open, could you please send me a private message with the SR number? You can send me a private message from my profile.

Interesting.  I just did a new install and we are having the same issue.  I just opened an SR friday about this.

Jerry - hopefully I can save you some time if your configuration is the same as ours.  It took 5 days to finally find out that our issue was by-design.

We have two (2) avamar systems on totally different networks.  We had only allowed Port 29000 to our storage nodes of the replication target from the utility node of the source.  This implies ssl based replication.  This requires you to initially configure replication from the command line, NOT the Enterprise Manager.  Once it is initially configured from the command line, there are certain replication settings that you can changes from the Enterprise Manager, but others such as scheduled start time, need to be done via command line.

Hope this helps

Ken

Ken,

That is interesting.  When we did the install for this customer, we did not regulate replication other than configuring bond2 for replication from grid to grid.  The grids are on seperate networks, one at production data center and the other at DR data center.  The parameters that we are trying to get to save have to do with choosing a selective replication.  You can choose selective, bring up the list of clients, choose your clients then click save.  It just defaults back to Full and does not save any of the clients chosen.  Schedules work as configured but they are getting Full replication to the /Replicate domain on the destination.  I did not initially configure the Replication bond during installation as we were having some other issues happening with the install so I left it out when using dpnnetutil, but added it in after the fact.  I wonder if that has something to do with it.

Thanks for the input.  When EMC gives me a call I will see if by chance this issue is the same as yours.

Thanks Ian, I've seen this a couple times. It seems to happen more often with targets of different versions/hardware and also when the seperate replication bond is created.

Did you get a fix on this Rob?  I still have not heard back from support?  I know that both versions are the same, the only difference was that I did create the replication bond afterwards on the source server.