Support Center > Search Results > SecureKnowledge Details
Check Point Private ThreatCloud - Manual Copy Deployment Mode Instructions Technical Level
Solution

Follow these steps:

  1. Install the Private ThreatCloud (PTC) and the Download Agent (DA) on separate machines as described in sk149692 - R80.20 Private ThreatCloud. For R77.30 version and below, use the following: Private ThreatCloud Installation Guide - chapter "Deploying and Configuring Private ThreatCloud" - section "Initial Configuration of a Unidirectional Deployment". 

  2. When setting up the Download Agent, select "using a local copy".
    This way, the DA will be configured as if it is on the same appliance as the PTC and will keep all downloads locally in the /var/log/uploads/ directory.

  3. After the DA finishes downloading all files, use the updates_helper script ($TMSDIR/cur/scripts/updates_helper.sh) to export/import the files between the DA and the PTC. 

    • To export all uploads, use the syntax: updates_helper.sh -m x -f my_export.tgz -u /var/log/uploads
    • To import your uploads: updates_helper.sh -m i -f my_export.tgz -u /var/log/uploads
  4. Allow a few hours for the PTC to load all the copied updates. Monitor the progress on the web monitoring interface https://<IP_ADDRESS_of_PTC>/ptcd/report.html.

Notes:

  • You can repeat the process as often as you like. Keep in mind that each blade has a threshold, and if it does not get new updates as often as it expects to, it will display the blade as not up to date.
  • The updates_helper script maintains the timestamp of the last file exported so the administrator doesn't need to maintain track of it or remove any files from the DA

Related solutions:

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment