5.3 client - Replication issue
Here is another outstanding issue with the 5.3 client that I have not seen documented anywhere. The 5.3 client does not honor the Replication schedule or changes to the bandwidth used by Replication. This is a major issue for us since we replicate MI's and patches to 50 locations. According to support, this is a known issue with 5.3 and will not be fixed until 5.4 is released.
0 Comments
[ + ] Show comments
Answers (21)
Please log in to answer
Posted by:
matt.may
12 years ago
So in a n00b term, what is the issue, we haven't set up replication but we were going to after the upgrade to 5.3?
Posted by:
matt.may
12 years ago
I just followed up with Dell Kace about this and there is a work around. Once you update to the newest version of the server (5.3) and update the clients to match. You will need to install the 5.1.38724 agent and things should be good.
Posted by:
svierneisel
13 years ago
Thanks for posting. I have about 15 servers Globally and I have not installed the agent onto the remote servers. I was going to after the 5.3 upgrade but I guess I will wait. :-(
Posted by:
darkhawktman
13 years ago
Thanks for the post. This would be a huge issue for me also. I'm glad that I haven't upgraded to 5.3 yet. Guess I will shelve this upgrade until 5.4 comes out.
Posted by:
airwolf
13 years ago
Whoa. I was unaware of this. Thank you for posting! This is a deal breaker for us... Looks like we'll be waiting for 5.4. We replicate to 80 sites and we MUST have accurate throttling.
Posted by:
afzal
13 years ago
Thanks, we are operating 200 replication shares and some are on 256 K link, It can become a very big issue for us. I am sorry to say that, This issue will make release 5.3 useless for most of the customers. we are running centralized ERP across the branches, and replication is scheduled in the evening.
Thanks again for sharing, you saved our centrilized ERP
Regards,
Thanks again for sharing, you saved our centrilized ERP
Regards,
Posted by:
airwolf
13 years ago
... we are operating 200 replication shares and some are on 256 K link...
Wow! You're the first person I've heard with more than me (we have 80). I have several sites at 256 Kbps, so I feel your pain. Sadly, we'll be waiting for the fix in 5.4.
Comments:
-
airwolf : do you really think 200 replicates is a lot? try 1300 then the fun starts! - Mariusja 12 years ago
Posted by:
GillySpy
13 years ago
We are planning to fix the bandwidth issue with the 5.3 L10N AP1 release. You can use the 5.1 agent on a replicating PC if bandwidth today is important for you, but upgrading to 5.3 server is also important.
Posted by:
airwolf
13 years ago
So upgrading to 5.3 server won't impact existing replication agents; It's only when we upgrade the agents themselves?
What is the ETA on the 5.3 L10N AP1 release?
What is the ETA on the 5.3 L10N AP1 release?
Posted by:
GillySpy
13 years ago
ORIGINAL: airwolf
So upgrading to 5.3 server won't impact existing replication agents; It's only when we upgrade the agents themselves?
Correct
ORIGINAL: airwolf
What is the ETA on the 5.3 L10N AP1 release?
End of November is the plan
Posted by:
afzal
13 years ago
Hi Everyone,
I have tested the replication schedule on WinXP machine with latest Client 5.3.47657 and Server v5.3.47927. It works fine for me. I have checked it several times every time it worked as required.
Please let me know the exact scenario.
Regards,
I have tested the replication schedule on WinXP machine with latest Client 5.3.47657 and Server v5.3.47927. It works fine for me. I have checked it several times every time it worked as required.
Please let me know the exact scenario.
Regards,
Posted by:
cdeal
13 years ago
Yes, you are correct. It appears a simple on/off replication schedule does work on Windows 7 and XP clients. The problem seems to be limited to bandwidth throttling.
Posted by:
darkhawktman
12 years ago
Just wanted to check and see if this issue is fixed in the new 5.3 release. I looked through the release notes and didn't see any mention of this being fixed.
Posted by:
ncsutmf
12 years ago
ORIGINAL: darkhawktman
Just wanted to check and see if this issue is fixed in the new 5.3 release. I looked through the release notes and didn't see any mention of this being fixed.
Any word on whether or not this has been fixed yet? We have been waiting since the Konference to do much with replication until this issue is resolved.
Posted by:
sfigg
12 years ago
Just getting into replication today for the first time - and good thing the machine I'm testing is on the same switch as the K1000 - I'm limiting to 10000 bytes on LO, yet it's going at 50MB/sec. When is this going to be fixed?
Posted by:
ncsutmf
12 years ago
I have a ticket open with support, is the replication machine you have using the 5.3.53177 Agent?
ORIGINAL: sfigg
Just getting into replication today for the first time - and good thing the machine I'm testing is on the same switch as the K1000 - I'm limiting to 10000 bytes on LO, yet it's going at 50MB/sec. When is this going to be fixed?
Posted by:
ncsutmf
12 years ago
ORIGINAL: sfigg
I'm on 5.3.47173
That version is two versions back, support tells me it should be fixed in 5.3.53177 which was released about a month ago. From what I can tell, it appears to be working again but I am not 100% certain.
Posted by:
Mariusja
12 years ago
Can someone please help me with this:
I get this message under the k1000 logs and this specific replicate is very slow:
[2012-08-17 13:28:38 +0200] KBOX [info] Inventory received after 955 seconds, but inventory interval is 86400. (2008Enterprise32bit 11.208.8.158 23C50227-789E-4268-AFFE-8B02884016D7)
For the people who thinks 200 replicates is alot try 1300 replicates!
Posted by:
matt.may
12 years ago
WOW! That is huge! That puts my upgrade plans on halt. Are they for sure not looking into it until 5.4?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.