How To Set Up Replication to a Remote Database

  1. Identify a target machine with MySQL installed

  2. Make sure the SafeConnect manager node has a clear logical route to this machine

  3. Create the database and table

    Setting up the database table

    Use the following script to set up the clienthist table in your database.

    CREATE TABLE clienthist (
    clientHistId bigint(20) unsigned NOT NULL auto_increment,
    PRIMARY KEY (clientHistId),
    transType char(15) NOT NULL ,
    transDate timestamp NOT NULL ,
    --client header info
    clientId bigint(20) unsigned NOT NULL default '0',
    sessionUID varchar(32) NOT NULL default '',
    currentIpAddress char(15) NULL ,
    principal text,
    ugroupId mediumint(9) unsigned NULL,
    ugroupLabel varchar(255) ,
    hostreftypeId mediumint(9) unsigned NOT NULL default '0',
    hostreftypeLabel varchar(255) NOT NULL default '',
    policyCompliance text,
    winMachineName varchar(85),
    macaddress varchar(25) ,
    localIpAddress char(15) NULL ,
    routerIpAddress char(15) NULL ,
    webMessageId mediumint(9) unsigned NULL,
    webMessageLabel varchar(150) ,
    webMessageViewName varchar(50) ,
    osName varchar(25) NULL,
    --client state
    outCompliancePolicyId mediumint(9) unsigned NOT NULL default '0',
    outCompliancePolicyLabel varchar(255) NULL,
    outComplianceadminMsgIds varchar(255) null,
    groupUpdated tinyint(1) NOT NULL default '0',
    quarantined tinyint(1) NOT NULL default '0',
    ilan tinyint(1) NOT NULL default '0'
    ) ENGINE=InnoDB;
  4. Grant the SafeConnect appliance privileges to the database


    Assuming your database is named "backupDB", the MySQL commands would be:

    use backupDB
    grant all privileges on backupDB.* to 'USERNAME'@'%' identified by 'PASSWORD';
    flush privileges

    Note that you can set the username and password to be whatever you want.

  5. Forward the database name, username, and password to, along with the target machine's IP.

  6. A support engineer will finish the set up and contact you for verification.


  • The replication cyclke is configurable, defaulting to every 5 minutes.

  • It's a good idea to thin the table periodically, as data volume can grow quite large over time.

  • Storage size should be allocated at 1 GB per year, for every 1000 concurrent users.

  • Due to a third party dependency, MySQL 5.6.x or greater is currently unsupported for this feature.

Guide to table fields




Primary key for the clienthist table.Typically not used for troubleshooting or reporting.


How SafeConnect interacted with the endpoint.


Time at which this interaction occurred.


Primary key from the internal table that tracks an endpoint’s status while it’s online.Typically only used by Impulse Support.


Unique identifier for a Policy Key device.Rotates with each active session.Will read “NEW” for non-Policy Key devices.


Endpoint’s IP address, as reported by the network.


Combination of network authentication username, plus any applicable role information from AD, LDAP, or Safe•Connect device enrollment.Format: “USERNAME,ROLE1,ROLE2,ROLE3,etc.”


Identifies the endpoint’s Safe•Connect policy group.


SafeConnect policy group name, as displayed in the Policy Manager.


Numerically represents SafeConnect’s current assessment of an endpoint’s device type.


The common name associated with each hostreftypeId.


Lists all policies applicable to a given endpoint, along with their compliance state.


Endpoint’s device name as received from DHCP or the Policy Key.


Endpoint’s mac address as received from DHCP, Radius accounting, or the Policy Key.


The IP address reported by the Policy Key.Will differ from the currentIpAddress 1) if the endpoint is downstream of a home router using NAT, or 2) temporarily, if the device is switching from wired to wireless, or vice versa.


IP address of the Layer 3 switch that forwarded the endpoint’s flow (eg, Netflow, Sflow, Aruba mirrored traffic) data to SafeConnect.This is the device where enforcement will take place if the endpoint should be quarantined.A blank routerIpAddress indicates that 1) no relevant flow data has been received, and consequently 2) the device cannot be quarantined.


Identifies which enforcement message was displayed to the endpoint, if any.


Common name associated with the webMessageId. This is also how the message will be displayed in the Policy Manager’s Custom Messaging module, if applicable.


Enforcement message’s location on the enforcer’s file system.Typically useful for customers who have direct SSH access to edit the messaging.


Reported by the Policy Key if applicable, a more detailed variant of the hostreftypeLabel.


Identifies the topmost non-compliant policy in the endpoint’s policy tree.This is the policy for whichthe endpoint will receive any applicable messaging or enforcement actions.


Common name associated with the outCompliancePolicyId.This is the policy name as displayed in the Policy Manager and Dashboard.


Identifies supplementary messaging associated with a given policy.


A value of “1” indicates that a Policy Manager upload has occurred since the last time the endpoint communicated with SafeConnect.


A value of “1” indicates that the endpoint is due to be blocked at the Layer 3 switch for policy compliance.


A value of “1” indicates that the endpoint is due to be blocked using the Policy Key’s ILAN technology for policy compliance