How Argent Job Scheduler Codebase Backup Engine Works

In the configuration of main engine, the tab ‘Backup Node‘ specifies the failure-proof path. The main engine writes a live status file ‘TAJSALIV.SVC‘ to the directory, and updates its timestamp in the frequency specified in the same tab.

In the configuration of backup engine, the tab ‘Backup Node‘ specifies the failure-proof path as well. IT SHOULD POINT TO THE SAME PHYSICAL LOCATION AS THE FAILURE-PROOF PATH SPECIFIED BY THE MAIN ENGINE. If the backup engine cannot see the live status file being updated in the past X minutes as specified in the checking frequency, the backup engine will think the main engine is dead and start to take it over.

During the takeover the backup engine restores the data from a backup file generated by main engine in the failure-proof path to a local database and continues functioning.

When the primary engine is restored, the primary engine restores the data from a backup file generated by backup engine in the failure-proof path to a local database.

Your Argent Job Scheduler is a critical production system, the well-being
of which directly affects large segments of your IT operation.

Feel free at any time, day or night, 24 hours-a-day, 365 days-a-year to contact Argent
if you have any questions at all about your Argent Job Scheduling environment.