Server Snapshot Logs

[Anonymous user]

📖 Home  Back  
ClearSCADA 2007 introduced support for taking regular 'snapshots' of the ClearSCADA server. The snapshot contains information normally available in the server status dialog, e.g. memory, CPU, internal threads etc., and logs it to a file.

Snapshots can be particularly useful in circumstances where server problems are thought to be the result of memory issues. In this case, exceptions may not be captured properly due to the lack of memory, and so the snapshot file may give an indication that memory issues are the problem. The series of snapshots before the crash can be used to determine the change in memory usage of the server over time.

By default, snapshots are enabled on a server and log at a frequency of every 30 minutes. The settings for the snapshots are controlled in the registry. The settings are:

Registry Section	Key Name	Comments
DB	SnapshotEnable	True (default) or False. This should always be set to True, unless the automatic snapshot facility is to be disabled.
DB	SnapshotInterval	The interval between snapshots in minutes. This is synchronised to the hour boundary (Default: 30 minutes)
DB_Snapshot	LogEnable	True (Default) or False. This should always be set to True.
DB_Snapshot	LogFileBase	The location of the snapshot log files. This defaults to the standard Log files directory for ClearSCADA.
DB_Snapshot	LogLevel	This defaults to 1.
DB_Snapshot	LogLinesPerFlush	This defaults to 1.
DB_Snapshot	LogMaxFiles	The number of snapshot log files to keep for each server session (Default: 2)
DB_Snapshot	LogMaxSize	The maximum size of each snapshot log file in bytes (Default: 2048).
DB_Snapshot	LogOldFiles	The number of previous server session log file sets to keep (Default: 1)

The Server Status dialog now also allows for a manual snapshot of each page of information displayed. This can be accessed by selecting 'Save Snapshot...' from the File menu. Only the currently displayed page of information will be logged to the snapshot file.

Each snapshot log file will contain more than one snapshot.

Changing a snapshot interval in the registry does not change it immediately. In versions prior to ClearSCADA 2009 R1, a server restart was required. In 2009 R1, the new timing will be used AFTER the next snapshot is completed.

Go: Home Back