This section will provide some suggested maintenance tasks for an EASA Server. The main aim of these suggestions is to ensure the availability of the EASA Server for a User’s needs.
Events that could pose a problem to the availability of an EASA Server include loss of power, hard disk failure, insufficient disk space, network outage, among many other faults.
This section contains three suggestions to keep EASA running reliably.
An important maintenance task is to perform regular file backups of the important EASA data. This can be to any file media, for instance tape, CD, or hard disk. The important folders containing data created by your organization that should be regularly backed up are: admin, applications and users under:
Within EASA, there is a backup facility for writing this data to another hard disk drive location. Select:
On the Backup page, there are two types of backups available:
To perform an Immediate Backup, please follow the instructions given below:
The data requested in Type will be copied to the specified Backup Directory at this time. To better understand the choices available in the Type choice list, please see the explanation provided in the table below.
|Data Type Choice
|Explanation of Data
|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 files in the admin, applications and users folders will be backed up
Configure regular periodic or Scheduled Backups below:
The Backup page also provides messages on a couple of things to let you know the state of your data backup and storage:
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.
The option to enable automated cleanups is present in a property file located on the file system on the server in the EASA server data folder:
The following line is already present in the file::
By default this option is disabled.
Stopping the EASA service, removing the hashtag (#) from the start of the line and restarting the EASA service will enable the feature. The number of days can be customized by replacing the pre-populated option of 90 before restarting the service.
When working with batch software that generate relatively large files as a result, the folder in the EASA folder structure that houses these results can grow out of proportion over time. If these historic results can be removed after a certain amount of time, EASA can be configured to do that automatically.
This option is disabled by default and enabling it involves editing a
context.properties file on the EASA Servers file system. The path of the file is the following:
<EASA SERVER DATA>\easa\admin\config\context.properties
Once opened with a text editor, find the following line
and remove the hashtag (#) from the front. The value (30 above) will specify the amount of days a Result will be kept, any older Results will be deleted automatically. The other related parameter
sets the time after which the EASA server rechecks if there are Results to be deleted. This is set to 1 hour by default.