You don't have to restart.
You can set it to run as a server side scheduled task.
I would ask the people who are suggesting the verify to do a proper Root Cause Analysis of the server crash and implement the corrections/mitigation's that result from the RCA.
You can certainly set up operating system processes to do that. However, it there a reason why the FIleMaker Server verification process doesn't meet your needs?
Beatrice Beaubien, PhD
FileMaker Business Alliance
FileMaker 15 Certified Developer
Knowledge Translation Certified Professional
Planning an additional daily backup at 2 AM with integrity checking turned on should be enough.
No the verification process DOES meet my needs but I just wanted to verify on a daily basis to avoid any data loss due to the time in between the crash and the time of the latest backup. For example we set the backups to run at 10pm and if users come in early the next morning and enter in a lot of information, before the next night's backup then all that data entered would be lost if the database get corrupted during that day.
However, if I could verify the databases at 1pm then loss would be minimized.
Why not set to backup more often and with verification checking turned on?
I think we had a situation in the past where backing up causing a bog in the workflow of people using the system. I was not at the organization then though.
You should look into Progressive Backup. You can set the iThe first time it runs it will create a full backup. After that it only backs up the changes.