Usage : BACKUP is the Java Open Access Client (OAC) process which
coordinates datalogger backups. You can view log files
for BACKUP in the directory engines/files/oac.
Restart: BACKUP is restarted its DAE is restarted.
Keeper : Kevin Cahill
beams document database:
http://www-bdnew.fnal.gov/Controls_web/EngineDocs/LoggerArchive/DataLoggingArchiving.htm
from source code gov.fnal.controls.daq.oac.clients.backup:
This is the Open Access Client Backup. It coordinates datalogger backups. The
device G:BACKUP controls the process. G:BACKUP holds the last calendar day of
the year that the previous day's collection was completed. So, on day 100,
G:BACKUP should become 100 after the midnight jobs complete. Those jobs
collected data from day 99. To repeat day 99's collection, set the value of
G:BACKUP to 99 and restart the engine. Allow 5 seconds or so for the upload
of G:BACKUP to flush to the database for future download. On jobs'
completion, G:BACKUP will always be set to the current day, so only one
'catchup' is performed per engine restart. For testing with the alternate
backup logger, redirect to BACKUP using D128, instantiate, use G:BACKUZ
instead of G:BACKUP.
log files are of the form DailyFetch*DCE08.txt in engines/files/logger.
Keeper: Kevin Cahill
OAC Node: dce08
Now: Fri Aug 29 21:25:50 2008