New build 5.3.1.59332 - issues and bugs discussion

Do to the catastrophic loss of my remote replication core, I decided to start from scratch and install the latest build (5.3.1.59332) on new hardware.

I wanted to create a thread where we can consolidate all of the bugs and other issues for this new version in one place.

So far I have discovered the following issues:
1) UI response time is now very slow with some operations. It's similar to how the old 5.2 used to be and possibly even slower. This can be very frustrating since it takes 30 to 60 seconds or more per click in the UI.

2) The option to pause / un-pause replication jobs is now gone in this version. The option is no longer in the menu. This is a problem and leaves you no control over replicating machines.

3) The well-known attachability checking and log truncation bug still exists in this version. Nightly attachability checks and log truncation still constantly fail as before in older builds.

Please post any other issues or bugs you find and possible solutions if you have them.

Parents
  • My newly installed replication core has been running full tilt for about 5 days with no issues. It's been receiving traffic from my primary core all that time and still has a little way to go. Surprisingly, neither core has crashed in all that time (unlike previous versions which wouldn't even go 24 hours before becoming non-responsive).

    I should point out that I've moved both cores to Server 2012 and have noticed a huge improvement in speed and stability. Previously, they were on Server 2008 R2.

    This is the most stable the system has been in a while. My only real issues so far are the inability to pause / unpause replication, slow UI and Exchange log truncation failing. All minor issues compared to what some of you are dealing with.

Reply
  • My newly installed replication core has been running full tilt for about 5 days with no issues. It's been receiving traffic from my primary core all that time and still has a little way to go. Surprisingly, neither core has crashed in all that time (unlike previous versions which wouldn't even go 24 hours before becoming non-responsive).

    I should point out that I've moved both cores to Server 2012 and have noticed a huge improvement in speed and stability. Previously, they were on Server 2008 R2.

    This is the most stable the system has been in a while. My only real issues so far are the inability to pause / unpause replication, slow UI and Exchange log truncation failing. All minor issues compared to what some of you are dealing with.

Children
No Data