Hi,
Replication between the 2 servers is shown as successful via BESAdmin and in FillDB logs.
However, the BESServer folder sizes differ with about 73 GB.
wwwrootbes\bfmirror\downloads\sha1 folders have a difference of 65.6 GB.
Is this expected behaviour or all media should be automatically cached on DSA server?
Is this affected by the manual cache that is only performed on main server?
Thank you!
Only SQL is replicated, and not all tables so the DB may differ in size too.
All other binaries including SHA1 folder will need to be copied/scripted if required.
To add to Nick’s reply, while the downloads/sha1 folder is not replicated, the wwwrootbes/Uploads folder is replicated automatically. So any Client Uploads, SWD Dashboard uploads, or OSD Imaging uploads are available on both servers.
What is the SQL replication type used between Main Server & DSA Server?
Snapshot? Transactional? Merge?
Thank you in advanced!
It doesn’t use SQL replication at all. The FillDB services on each DSA server, query the partner server’s SQL database and then updates its local SQL database accordingly.
I am having a new issue regarding the replication between the 2 servers.
It seems it got broken, but only one way (replication main-> back-up is ok, replication back-up -> main shows as connection broken, "Unexpected HTTP response: 404 not found).
Last successful replication was completed earlier today.
Any ideas what might cause this?
You’ll probably need to open a PMR to troubleshoot your specific servers.
Have you tried the basics - restarting the BESRootServer and FillDB services?
Yes, we did reboot the services - nothing changed.
I find it weird that this happens only in one direction and the other one works as expected.
Also ran netstat -ab on both but I am unable to find communication between the 2 servers (i was expecting to find something on at least one since in one of the direction, the replication works)