Service-Generated Files

Service-generated files are those files created by the service upon startup and maintained thereafter by the service (for example, the data files). Unless otherwise specified, once the files are created you cannot delete them without losing data.

The following table describes the files you will find in your service directories.

File

File Extension

Description

Backup files

*.bak

*.bk#

Several non-DBS files require automatic backup and have a *.bak extension, for example, CasPersist.bak, CVS.Persist.bak, SvcDef.RSX.bak.

The service configuration files use a *.bk# file naming system for archiving backups, with # being the instance of the file. See Restoring Backup Files for more information.

Data files

*.dat

*.DAT.edb

*.DAT.pat

*.db

*.edb

CygNet service data files.

For DBS-based services, the main database file name is <ServiceName>.DAT.edb (for example, DDS.DAT.edb) unless otherwise specified in the service’s configuration file.

The .DAT.pat file is the patch file for the .DAT.edb file. This file keeps track of updated pages while the backup is running to make sure that pages that are modified during the backup are also backed up, for example, <ServiceName>.DAT.pat (for example, DDS.DAT.pat). See ESE File Types for more information about DBS-based service file types.

Other services have specific names for their data files as listed in the following rows:

Other Data Files

File Name	Description
activation.1024.db	ARS host activation data file. If the file name is preceded by a tilde (~), that instance of the file is from the previous session of the service.
AlmHistPersist.dat	CAS persisted data file
CAS.PointCache.dat	CAS persisted point cache file
CasMetaData.dat	CAS persisted metadata file
CasPersist.dat	CAS persisted data file
ChangeQueueTranslator.dat	DBS change queue translaor. A file that keeps track of incremental changes to a DBS-based database.
CVS.Persist.dat	CVS persisted data file containing the last known value for each point in the service’s current value table. The service must be configured to persist values.
CygNetMeter.db	ARS license information
EACHistory.bin	This file is used to store any pending writes of any alarms that were impacted by Enhanced Alarm Configuration choices. The EACHistory.bin file is located in the service directory for each CVS (HSS, OPCIS, SVCMON, and UIS). See EAC_TO_ALARM_HISTORY for more information.
GnsAckFile.dat	GNS metadata file containing user details for the GNS Pin Manager required to acknowledge notifications.
HeadersToBeUpdated.dat	AUD and NOTE service data file
History.edb	History (VHS) data file
HistoryForwardQueue.dat	CVS persisted history forward queue data file
MaintenanceTasks.dat	This file is created only by the VHS. It allows the VHS to persist current or queued maintenance tasks so that they can be resumed if the service is restarted. Current maintenance tasks include expiring values past the retention date, sealing live journal files, deleting expired journals older than the configured retention period, and reading an archived "dirty" change queue file to import recent changes. The VHS write its queue of maintenance tasks every 5 minutes and also right before the service shuts down.
MetaData.dat	AUD, ELS, ELSALM, FAC, GRP service metadata files. For the FAC service, this file contains the user-defined names of facility attributes.
NotifQueuePersist.dat	GNS persisted data file
PendingDeletes.dat	NOTE service data file containing notes marked for deletion
PntMetaData.dat	PNT data file containing custom default configurable bits and configuration states for points.
Pop3PersistUidls.dat	GNS persisted data file for POP3 mail server
RedundancyDefs.db	RSM redundancy definitions data file
ReSendQueuePersist.dat	GNS persisted data file
ServiceDefs.[domain].db	ARS definition data file for each doain. If the file name is preceded by a tilde (~), that instance of the file is from the previous session of the service.
VhsChangeQueue.dat	VHS change queue file that keeps track of incremental changes to a VHS

Domain definition file

CygNetDomainDefs.xml

ARS domain defintion file

Index files

*.INX.edb

*.INX.pat

For DBS-based services, the .INX.edb file is the index file containing database indexes. The file name is <ServiceName>.INX.edb (for example, MSS.INX.edb) unless otherwise specified in the service’s configuration file.

The .INX.pat file is the patch file for the .INX.edb file. This file keeps track of updated pages while the backup is running to make sure that pages that are modified during the backup are also backed up, for example, <ServiceName>.INX.pat (for example, MSS.INX.pat). See ESE File Types for more information about DBS-based service file types.

If the index file requires optimization or gets corrupted it can be regenerated using the ReIndexESE utility.

Log files

*.log

~*.log

The .log file contains service information. The file name is <ServiceName>00#.log, with # being the instance of the file. The number of files and the length of each file are based on the service configuration. If the file name is preceded by a tilde (~), that instance of the file is from the previous session of the service. The information written to the log file is specified in the .cfg file using the LOGMASK_FILE keyword.

Note: .lgb and .lgb are obsolete DBS-based service log file extensions. they have been superseded by .log files.

Replication notification files

*.REPLNOTIFY

The service replication notification file, which stores replication information for DBS-based services.

Service definition file

SVCDEV.RSX

The RSM database file. This file, which is an XML file, lists the services in the order that the RSM starts them.

Temporary storage files

*.TS.edb

*.TS.pat

For DBS-based services, the temporary storage file contains uncommitted changes. The file name is <ServiceName>.TS.edb (for example, FAC.TS.edb) unless otherwise specified in the service’s configuration file.

The .TS.pat is the patch file for the .TS.edb file. This file keeps track of updated pages while the backup is running to make sure that pages that are modified during the backup are also backed up, for example, <ServiceName>.TS.pat (for example, FAC.TS.pat). See ESE File Types for more information about DBS-based service file types.

Transaction log files

\txlogs\edb.jtx

The transaction log file containing the operations on the database files for DBS-based services. The default directory location for the transaction log files can be overridden with the DBS_TRANSACTION_LOG_DIR and VHS_TRANSACTION_LOG_DIR keywords. See ESE File Types for more information about transaction log files.