Lawson server reboot

We run on Windows and Reboot our Lawson Server every night. It shouldn't hurt anything. Just make sure no Batch Jobs are running.(Even then a Recover Job might fix it)

Rebooting the server will kick everyone out and may cause issues with running batch jobs. We only reboot or restart services during the day if the system goes down hard. If it's still running, we do the restart overnight if at all possible. If you do restart during the day, be sure all batch jobs are ended, as Ari mentioned.

Can the reboots of S3 and Landmark be done with a script? If so, can someone share with me a script. We seem to be running into issues with auto reboots with dependencies set up.

Our 3 Lawson Servers(LSF9 Lawson, BI and SQL Server Databases) are all Virtual Machines on a Physical Host. The Host is set up on a Failover Cluster. Each Virtual Machine gets shut down, exported and rebooted every night. The exports are then backed up to tape. In addition the SQL Server databases are backed up and then the backups are sent to tape. We also back up various directories form the Lawson Server to tape. This whole process is automated including the Powershell script that shutdowns, exports and reboots the Virtual Machines. It all works pretty well as long as the timing of the processes is coordinated correctly.

Thank you very much for your quick responses. We scheduled after work hours. I just stopped the EDI connections and will resume once the system is backup. I will ask the server guy if we do reboot the servers on a regular basis, I am assuming we do.

When we installed Lawson several years ago we discovered we were having various memory type issues with Windows. We found it was just easier to reboot each night rather than chase the problems. Windows generally doesn't manage memory as well as Unix and Lawson has some complex and unique needs for memory. When you add in all of the WebSphere java virtual machine memory requirements and the Lawson AGS memory pool and port requirements along with all the Lawson servers like lase, lajs, latm etc., it ends up making sense to just reboot regularly.

There were times when I tracked down problems that caused by our crystal report writers. Once I ended the report processes, Lawson behaves normally again. I guess we are the lucky Window shop here. We don't have need to reboot our servers until the monthly Microsoft security patch day.