Usage : SCHSAV initiates periodic big saves of the complex four times
a day at 06:30, 12:30, 18:30, and 22:30. It is similar to BIGSAV
that performs big saves before shots generally initiated by the
sequencer.
It also monitors G:SCHSAV and will initiate a big save if the
setting of G:SCHSAV is in the range of archived files
(currently 900 - 999 (archive) and 1200 - 1299 (circular)).
The reading property of G:SCHSAV will display the actual file number.
When the big save completes, the setting value of G:SCHSAV goes to zero.
G:SCHTIM displays the elapsed time of the big save and is
unchanging after big save is done. If G:SCHSAV is off, a big
save cannot be started. If G:SCHSAV is turned off during a save,
the save is aborted. A big save cannot be started with a big
save in progress. Use the setting browser to determine who has
started a big save.
Big saves have several purposes:
- encompassing archives
- encompassing SRFILE redirection files
- exposure of database and front end errors
- exposure of hardware problems
The philosophy of SCHSAV is to save everything that may be
saved without error, regardless of its utility, because
big saves have other purposes than simple archiving.
Excluded from big saves are:
- Z: devices
- devices with the NEVERSAV save property
- devices with the CLEANUP save property
- properties excluded with the EXCLUDSAV save property
- devices with very big buffers
SCHSAV is a Java Open Access Client (OAC) process which
runs on DCE29. You can view log files for SCHSAV in
the directories 'daesrv\\engines\files\saveRestore' and
'daesrv\\engines\files\oac'.
Restart: SCHSAV is restarted when its DAE is restarted.
Keeper: Kevin Cahill
OAC Node: dce29
Now: Mon Oct 13 10:43:40 2008