aXsGUARD Identifier 3.0.2.0 Product Guide v1.5
Replication
15.5.2
Replication Forwarding
Replication forwarding is required and activated automatically where more than two aXsGUARD Identifiers are
replicating. The ID of the source aXsGUARD Identifier and the target aXsGUARD Identifier(s) to which it is sending
the information are added to the replication entry. This allows the receiving aXsGUARD Identifier to check which
other aXsGUARD Identifiers have already been sent the replication entry. It only forwards the entry to aXsGUARD
Identifiers which are not listed.
15.5.3
Multiple Changes to a Single Data Record
The replication method used by the aXsGUARD Identifier involves replication of entire records, for example all
settings of a specific DIGIPASS User Account, rather than an individual User Account setting, such as a password.
This means that data clashes can occur when a single record is updated at the same time from different sources.
If this occurs, the later change is written to the database and earlier changes are ignored.
15.5.4
Connection Handling
When the Identikey Server service is started, the aXsGUARD Identifier establishes a connection to each destination
aXsGUARD Identifier configured for replication. It keeps this connection open until the service is stopped or the
connection is broken. If the connection is broken, it attempts to reconnect after a standard minimum reconnect
interval has elapsed. If this fails, it continues to attempt reconnection at increasing time intervals until it reaches a
maximum reconnect interval. It then continues to attempt reconnection at the maximum reconnect interval, until it
succeeds.
The aXsGUARD Identifier ceases replication efforts to the target aXsGUARD Identifier until the connection is re-
established. This means that entries in the queue are not lost because of a broken connection. Replications to
other aXsGUARD Identifiers are not affected, i.e. each replication link is independent.
15.6
Replication Monitoring
15.6.1
Replication Auditing
Audit messages (viewable in the live audit viewer of the Configuration Tool, see section
) are recorded when:
connections succeed or fail
a replication send is successful
a replication send fails
a replication is received and the receiving server returns a data update success message
a replication is received and the receiving server returns a data update failure message
©
2009 VASCO Data Security
93
