Usage : BIGSAV initiates a periodic large save of the complex in
support of shots and is generally initiated by the sequencer
in shot setup. It is similar to SCHSAV that performs big
saves four times a day.
It monitors G:BIGSAV and will initiate a big save if the setting
of G:BIGSAV is in the range of "shots" files (1100 - 1199).
The reading property of G:BIGSAV will display the actual file number.
When the big save completes, the setting value of G:BIGSAV goes to
zero. G:BIGTIM displays the elapsed time of the big save and is
unchanging after big save is done. If G:BIGSAV is off, a big
save cannot be started. If G:BIGSAV 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.
The philosophy of BIGSAV 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
BIGSAV is a Java Open Access Client (OAC). You can view
log files for BIGSAV in the directories
'daesrv\\engines\files\saveRestore' and
'daesrv\\engines\files\oac'.
Restart: BIGSAV is restarted when its DAE is restarted.
Keeper: Kevin Cahill
OAC Node: dce28
Now: Mon Oct 13 17:59:27 2008