bckfile

This table is typically used by Unicenter Asset Management. It contains the contents of various files scheduled for configuration file history. When the Agent scanner detects a change in one of the monitored configuration files, it sends a raw copy of the file to the database. The file is stored in this table. Usually more than one version of the file will be stored here to keep a history of changes. The BKVER field contains the version number the backup contents belongs to. How many files should be kept in the history, is defined in the BCKDEF table. The BDOMID and BCKID fields are foreign keys to this table. The raw backup file is stored in the BKFILE field. This table only accepts textfiles and NOT binary files. The backup file is split into more database entries if the file takes up more space than one field can hold. The field part number is stored in the BKNR field.

Column Name Column Datatype Column Null Option Column Comment
bdomid integer not null Backup Domain ID. Foreign Key to BCKDEF
bckid integer not null Backup ID. Foreign key to BCKDEF
bknr integer not null Number. Makes multiple rows contain files larger than BKFILE max size.
bkver integer not null Backup Version. 1=Current
object_uuid byte(16) not null Object Uuid. Foreign key to either ca_discovered_hardware or ca_discovered_user depending on object_type (1=ca_discovered_hardware,2=ca_discovered_user)
bkfile nvarchar(15000) with null Contents
bkdate integer with null Backup Date. Seconds since 1970.1.1
object_type integer with null Object Type. 1=ca_discovered_hardware,2=ca_discovered_user
object_domain_uuid byte(16) with null Object domain uuid. Foreign Key to ca_n_tier. Used for replication purposes.
auto_rep_version date with null Used for replication only, version of the replicated object

Product Name: Unicenter Desktop and Server Management

Table Type: Table


Copyright © 2006 CA. All rights reserved.