Systematics and Configuration

SUMMARY

CONTENTS

  1. Systematics of data archiving
  2. Destination drives (DestDrv/ZipDrv)
  3. Copy settings
  4. archive.dbf: Use of object number instead of PointId
  5. Encoding
  6. Vision2000.ini

Systematics of data archiving

At the end each cycle the data of the latest interval is archived from the log table to an interval table (naming convention: <MMDD_hh>.dbf), e. g. the last 3 hours, if a 3-hour interval was configured. This interval table is then compressed to a day archive (naming convention: <YYYYMMDD>.zip) at a given destination.

At start-up all data, which is found in the tables, but not in any of the compressed archives in the zip drive, will be archived before the cyclic process starts:
ZipDrv Data archiving at start-up
No zip files All data found in the log tables is compressed and saved in the corresponding files
Zip files up to date (a interval table for the current interval is already compressed) The compressed interval table for the current interval is deleted, as it will be written completely at the end of the interval.
Zip files are not up to date, there is still data found in the log tables for the latest compressed interval table The data belonging to the latest compressed intervall table is added to this table, as far as it is missing. All more recent data is compressed and saved to the corresponding newly created day archives.
Zip files are not up to date, no data found in the log tables for the latest compressed interval table All data is compressed and saved to the corresponding newly created day archives.
Zip files can not be accessed All found zip files are saved as '.zip.bak', after that all data found in the log tables is compressed and saved to the corresponding newly created day archives.
Zip files, which do not follow the naming conventions Ignored

At shut down the data of the currently running interval is saved and compressed.

It is possible to save the UT and LT of each cycle in a text file associated to the day archive, to make a later analysis easier.

Destination drives (DestDrv/ZipDrv)

The day archives are stored in the location given by the ZipDrv entry in the Vision2000.ini. If there is no path given in the ini file, the files are stored in a folder named 'ZipArchives' in the directory, where ALPHA-VISION®AvZipArchives is found.

Note:
If there is not enough space for the current day archive, the oldest day archive is deleted.

Additionally there is the possiblity to copy the files from the zip directory to another directory given by the DestDrv entry.

The storage capacity of DestDrv may be displayed by 3 ACI objects (used memory in MB and percent and a flag to indicate 90% used memory).
There is also an ACI object to monitor the ZipDrv (used memory in percent).

Copy settings

Default
After each compression the day archive is copied from the ZipDrv to the DestDrv.
In case of a successful copy process, the day archive in the ZipDrv will be deleted at midnight, to make space for the next day archive.

Copy on demand
The automatic copy process can be deactivated. The copy process may then be started manually by the use of the data object _COPYDEMAND. If the value of this data object is set to 1 during Runtime, ALPHA-VISION®AvZipArchives starts to copy and resets the value to 0 after the copy process has finished.

Erasing of day archives
The erasing of the day archive in the ZipDrv at midnight may be deactivated.

Note:
In this case it is the responsibility of the user to remove the day archives regularly from the ZipDrv to avoid data loss.

archive.dbf: Use of object number instead of PointId

In the day archive it is possible to replace the PointId used in the _archive.dbf log table with the according object number. The number is saved as string in the PointId data field.

Encoding

Next to compressing ALPHA-VISION®AvZipArchives also offers a option to encode the saved data. See encryption functionality

INI-FILES

Vision2000.ini

Section [ZipArchives]

See also ALPHA-VISION®AvZipArchives
Entry Type Description / Example Default
DestDrv string
Backup directory for the long-term storing of day archives. The here defined path/folder keeps the subdirectories "_ARCHIVE", and/or "_EVENTLOG" and/or "_DCLOG" in which the according Day-Archives will be stored.
If "DestDrv" is diffrent to "ZipDrv", the day archives are copied from the "ZipDrv" to "DestDrv" at the end of each interval.
ZipDrv string
The day archives are compressed and saved in this directory. The here defined path/folder keeps the subdirectories "_ARCHIVE", and/or "_EVENTLOG" and/or "_DCLOG" in which the according Day-Archives will be stored.
If no path is given, the directory of "ZipArchives.exe" is used as default.
WARNING
If there is no space for the new day archive, the oldest day archive is deleted.
directory of ZipArchives.exe
UseBinArch boolean
1: Use binary version of archive log as data source.
0: Use standard data source for archive log (_archive.dbf).
0
BinArchSaveOldInterval integer
?????????????????????????????????????????????????????????????? In case of start-up in binary archive log mode, AvZip2Dbf checks and, if necessary saves, the archive log data backwards for the given interval (in hours). ?????????????????????????????????????????????????????????????????
0
CheckTimeInterval integer
Cycle (in minutes), in which AvZipArchives.exe is testing for interval end. Possible values: 1 to 30.
10
WriteInterval integer
Interval for data archiving (in hours).
Possible values:1, 2, 4, 6, 8, 12, 24
24
Dbf_<n> string
Log table to be saved.
<n> is a consecutive numbering ranging from 1 to max. 3.
Possible values: _archive, _eventlog, _dclog.
Example
[ZipArchives]
Dbf_1=_archive
Dbf_2=_eventlog
					
Path_<n> string
According paths to the log tables given in entries 'Dbf_'.
<n> is a consecutive numbering ranging from 1 to max. 3.
Example
[ZipArchives]
Path_1=c:\bin\ArchiveDir
Path_2=c:\bin\EventlogDir
					
ErrorObjId string
Name of the ACI object (of type integer), which receives the error number in case of zip failure.
ErrorFlagObjId string
Name of the ACI object (of type bool), which serves as an error flag (1 in case of zip failure).
ProjectObjId string
If the name of an ACI object (of type string) is given here, its string value is written to a newly generated text file at each creation of a new day archive. The name of this text file equals the name of the created day archive except for the extension .txt.
At each compression interval a UT and LT entry is written to this file.
DestDrvFullFlagObjId string
Name of an ACI object (of type bool) that is set to 1, if more than 90% of the memory space of DestDrv are assigned.
Note:
If no name is given, AvZipArchives.exe will try '$MOFULL' as default.
$MOFULL
DestDrvMbUsedObjId string
Name of an ACI object (of type integer), that holds the assignment of memory space of DestDrv in MB.
Note:
If no name is given, AvZipArchives.exe will try '$MOGB' as default.
$MOGB
DestDrvPercentUsedObjId string
Name of an ACI object (of type float), that holds the assignment of memory space of DestDrv in percent.
Note:
If no name is given, AvZipArchives.exe will try '$MOPROCENT' as default.
$MOPROCENT
ZipDrvPercentUsedObjId string
Name of an ACI object (of type float), that holds the assignment of memory space of ZipDrv in percent.
UseObjNoInArchive boolean
1: The PointId entry used in the _archive.dbf is replaced by the object number before the data is compressed to the day archive.
0: The _archive.dbf structure is saved unmodified in the day archives.
0
DeleteZipsAfterCopy boolean
1: Self-acting erasing of the day archives in the ZipDrv at midnight.
0: Self-acting erasing of the day archives in the ZipDrv is disabled.
WARNING
DANGER OF DATA LOSS!!!
1
CopyOnDemand boolean
1: Self-acting copying of the day archives from ZipDrv to DestDrv is disabled.
WARNING
DANGER OF DATA LOSS!!!
0: Self-acting copying of the day archives from ZipDrv to DestDrv.
0
DeletedFileCntObjId string
Name of an ACI object (of type integer), that holds the number of old day archives deleted from ZipDrv due to lack of memory space for new day archives.