On Prem Technology Issues - How do you handle?

unknown

We are on prem, Windows NT LSF v10.0.11 ESP/MSP, we are VMs for all Lawson servers. We recently had some issues with connection failures in the ladb.log along with application issues. These didn't present as I would have expect a typical DB Disco, where the application becomes unresponsive and a restart of the services is needed to reconnect to the database. We had some S3 jobs, not all, go into Needs Recovery and we could recover them and they would complete. We did restart the Lawson services, and this remedied the issues, but then the same thing happened two days later. No issues since that last restart of the services over a week ago. Has anyone else seen this behavior? Our leadership is interested in speaking with other Lawson LSF/Landmark on prem clients that are LSF v10.0.11 ESP/MSP and V11.0.01.45 Landmark (or similar) to see how you navigate any database disconnects or other various Lawson outages.

unknown

We had some similar issues about 2 years ago, where Lawson job and other logs would record "general network errors" on SQL connect attempts. Was able to eventually line up error timestamps with VM snapshot backups that were occurring throughout day, which is also a documented issue on KB 1200361. I'd probably check that out to start with. I'd also take a look and make sure the transaction logs are being truncated on SQL routinely, that drive space isn't filling up, etc.,