10-15-2008 03:59 AM - edited 03-14-2019 03:03 AM
Hi,
If Logger B down for 1 hour,once the loggerB is came online that time the historical data will be replecated from logger A to Logger B ?
Thanks,
Gnanesh.
Solved! Go to Solution.
10-16-2008 03:03 AM
Hi Gnanesh,
Yes I Have Document but unfortunately the doc in confidential which cover all the configurations of our contact center. But for your assistance I have attached the screenshot of the page in which this thing is described. Hopefuuly it will help you.
If you are satisfied with this please rate me.
10-15-2008 04:27 AM
Yes, it will be replicated. If you have made some changes in the configuration, this changes will be reolicated too.
Hope this helps,
Juan Luis
10-15-2008 04:31 AM
Hi juan,
Just I want to Know the Historical Data.
Thanks,
Gnanesh.
10-15-2008 04:44 AM
Yes, the historical data will be replicated.
Regards,
Juan Luis
10-15-2008 06:10 AM
Hi Juan,
Suppose the logger B is crashed and rebuilding again.In that sceinario the Histirical data will be replicated from the logger A to Logger B.
Thanks,
Gnanesh.
10-15-2008 06:12 AM
Hi Gnanesh,
yes it will provided the config is not too far away, it will simply take longer to replicate the entire DB content.
Regards,
Riccardo
10-15-2008 06:13 AM
Hi Juan,
Suppose the logger B is crashed and rebuilding again.In that sceinario the Histirical data will be replicated from the logger A to Logger B.
Thanks,
Gnanesh.
10-15-2008 06:25 AM
Yes, the data will be replicated, though depending on the data volume can take more or less time, but historic and configuration data is replicated.
Hope this helps,
Juan Luis
10-15-2008 06:39 AM
Hi Juan,
In one of our customer site we rebuilded the logger B.But the historical and configuration not replicated.I done manualy syn the configuration and moved the historical data from the logger A to logger B.What could be the reasion.
Thanks,
gnanesh.
10-15-2008 06:44 AM
Probably network problems if historical data was huge. I have one experience making this sync and I had to use a cross cable to set up the private network between proggers to get synchronization becuase it was no possible using the normal network.
Regards,
Juan Luis
10-15-2008 06:44 AM
Hi Gnanesh,
most likely you did not let enough time to replicate the data, it is a low priority task. If you enable a tracemask of ffff in the rpl process you will see with stamps in the log when data get replicated.
Regards,
Riccardo
10-15-2008 01:50 PM
Hi Gnanesh,
If a logger is down or offline for more than 12 hours than the system will not automaticaly resynchronize the databases. In this case resynchronization has to be done manually using the ICMDBA application. I think in your case you cross the 12 hour time limit.
10-15-2008 07:49 PM
Hi Hossain,
Thanks For your information.Do you have any document for this.
Thanks,
gnaneswaran.M
10-16-2008 03:03 AM
Hi Gnanesh,
Yes I Have Document but unfortunately the doc in confidential which cover all the configurations of our contact center. But for your assistance I have attached the screenshot of the page in which this thing is described. Hopefuuly it will help you.
If you are satisfied with this please rate me.
10-16-2008 09:06 AM
I would check the following -
1) Retention settings on both loggers to make sure they are the same. You can do this by going to registry.
2) Recovery process is responsible for keeping the loggers syncd. I would turn up tracing on the rcv process to fff for troubleshooting. Only after the loggers synchronize, will historical data be replicated.
3) ICMDBA - data - space used summary will show you the min and max values of data.
If processes are not crashing, steps above will help with your issue. Logger data will replicate from A to B provided A was up-to-date when B went down.
-Anjali
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide