Backup files should be generated and stored on a offsite machine in case of failure.
Scheduled cleanup of unnecessary files will keep drives from becoming full.
The following MySQL commands will help to insure that a remote database my be recovered if storage media or a machine fails.
If the database machine is different from the EASA Server, it must have independent backups.
The folder '<EASAROOT>\db\mysql-5.7.17-win32\bin\' contains useful commandline executables.
Commands to make database backups:
Commands to restore databases from a backup (delete any existing database of that name and create a new one):
Use 'cron' (Cygwin or Linux) or Windows 'Task Scheduler' to automate database backup.
We suggest two possibilities to protect EASA data in the event of hardware failure:
|Minimal||All files in the admin folder will be backed up|
|All Author Data||All files in the admin and applications folders will be backed up|
|All Data||All files in the admin, applications and users folders will be backed up|
EASAPs that submit themselves to the EASA Server create a folder for themselves to work in on the server side. If the files are not handled in any way, they can build up and eventually occupy a large portion of the drive space.
To enable automated cleanups, uncomment and adjust the following line in: <SERVERDATA>/easa/admin/config/System.properties
By default this option is disabled.
Batch software often generates large files so EASA may be set to automatically delete historic Results.