Steps for Setting Up Cold Artifact Storage Using the Platform UI
Step 1: Set up a Live Artifactory Instance
The Live Artifactory instance can be a newly installed instance or an existing instance that must be configured as follows.
- Open the Artifactory System YAML file of the instance.
shared.jfrogColdStorage.coldInstanceEnabledproperty and set it as
falseto configure the instance as the Live instance.
Step 2: Create a Cold Artifactory Instance
On the Artifactory instance that you are designating as the Cold instance, perform the following steps:
Update the Artifactory System YAML file:
shared.jfrogColdStorage.coldInstanceEnabledproperty and set it as
trueto configure the instance as the Cold instance.
Configure the Archive Binary Provider:
When setting up the Cold instance, you will need to connect it to a binary storage provider. You can use one of the following storage options:
Self-hosted Storage: If you wish to use the local file system, see Configuring the Filesystem Binary Provider.
Amazon S3 Glacier Cloud Storage: If you wish to use Amazon S3 Glacier, follow these steps:
binarystore.xmlconfiguration file located in the
- Specify the
Within the chain, define the standard Amazon S3 Binary Provider template as outlined in the section Amazon S3 Official SDK Template and configure the parameters as per your requirements.
Restart the Cold Artifactory instance:
After making the above changes, restart the Cold Artifactory instance for the changes to take effect.
Disabling Cold Artifact Storage feature
The Cold Artifact Storage feature is enabled by default. If you wish to disable the feature, in the Artifactory System Properties file, set
Custom Base URL
It is recommended that you configure a Custom Base URL for this Artifactory instance. A custom URL base is especially useful when the system is running behind a proxy. For more information, see General System Settings.
Step 3: Add the Live and Cold Artifactory Instances to Mission Control
In this step you will need to add both instances to Mission Control. If Mission Control is enabled in the instance that you have designated the Live instance, then you will only need to do this step for the Cold instance.
- First, create a binding token for Mission Control by following the steps in Pairing Tokens (available from Artifactory 7.29.7).
Next, add the Cold Artifactory instance to Mission Control by following the steps detailed in Registering a Platform Deployment.
When you enter the JFrog Platform URL in step 6, this will generate the token you will need to pair the instance with Mission Control.
- If the Live Artifactory instance you set up above is not the JPD that has the Mission Control enabled it it, add the Live Artifactory instance to Mission Control in the same way.
Remember to copy the token you generate to a location where you will be able to find it easily.
Step 4: Bind the Live and Cold Artifactory Instances
Available from Artifactory 7.38.4
After completing the previous two steps, your Platform Deployments will have two JPDs that are both connected to the Mission Control microservice: the Live instance and the Cold instance. The next step will be to bind the two instances to each other so that the Cold Artifactory instance will trust and receive requests from the Live Artifactory instance. You can only bind one Live instance to one Cold instances, and this is a one-way trust.
Important: Wait at least 5 minutes
After registering a new instance (Register JPD) and binding it using Cold Storage binding, it will take 5 minutes for the new instance to be identified in the JFrog Platform as a Cold instance (this is based on the polling configuration in Mission Control and the default is 5 minutes). As a result, it will take 5 minutes for the Cold instance to appear in the Target JPD so you should wait before proceeding with the instructions below.
Perform the following steps on the Artifactory instance that you have set as the Live instance.
- From the Administration module, click Platform Deployments | Bindings.
- Click the Cold Storage tab. In the top right corner, click + Add Binding, and select Cold Storage from the dropdown list.
This displays the Create Binding window.
- From the Source JPD dropdown, select the Live instance.
- From the Target JPD dropdown, select the Cold instance.
- Click Apply.
The Summary displays the target and source you selected.
Click Create to create the new binding.
The binding results are displayed.
Setting Up Cold Artifact Storage Using APIs
The preferred method of binding the two instances is using the flow described above. However, you can also bind them using the API steps described below.
- First generate the Pairing Token to connect the Live and Cold instances.
On the Cold instance, execute the following POST request.
This generates the pairing token. For example:
Next, on the Live instance, use the generated pairing token to execute the following PUT request. This sets up trust between the Live instance and the Cold instance:
If the two instance are paired successfully, the request returns the following status:
Managing Cold Storage Bindings
Revoking a Binding Using the Platform UI
Important Note on Revoking Bindings
You cannot remove the binding between the Live instance and the Cold instance in cases where the Cold instance is not available anymore.
- To revoke the binding between a Live and Cold instance, from the Administration module, click Platform Deployments | Bindings and then click the Cold Storage tab.
- Select the checkboxes for the bindings you wish to remove, and then click the Delete button to the right of the binding.
- If you are deleting multiple bindings, select all checkboxes, and at the bottom of the window, select Delete.
This displays a confirmation message that asks if you are sure you wish to remove the binding.
- Click OK to confirm.
Your action is applied and the results of the unbinding are now displayed.
Each connection between a Live instance and a Cold instance is bound to a namespace in the Cold instance, which is generated during the paring process. The namespace is unique and the trust is established for that specific namespace.
This namespace is required when you need to re-establish the trust between the Live and Cold instances, for example, after the token was revoked by mistake. In such scenarios:
- Retrieve the namespace.
- Regenerate the pairing token by providing the namespace as an argument in the POST request.
curl -u admin:password -X POST https://<cold_instance_ip_address>/artifactory/api/v1/service_trust/pairing/artifactory-cold/gbbxmcuj
gbbxmcuj is the namespace.
Optimizing Cold Artifact Storage Performance
Cold Artifact Storage includes several properties that can be used to configure and optimize its performance.
The list of parameters and their corresponding values that are shown below are for reference only. It is highly recommended that you do not change these values.
Live Artifactory Properties
The following properties can be configured in the Live Artifactory's
Number of threads that will be used per policy to archive items.
Number of threads that will be used to restore items.
Number of http connections that are allowed to deploy artifacts from the Live instance to the Cold instance.
Maximum socket timeout for an http connection.
Number of http peers per route that are allowed to deploy artifacts from the Live instance to the Cold instance.
Setting for how often the Live instance will try to pull restored items from the Cold instance.
Setting for how many restored items will be pulled from the Cold instance to the Live instance.
Approximate maximum allowed bandwidth for all restore operations.
Error threshold to stop restore operation.
Setting for how many items are fetched from the database during archive policy execution.
Approximate max allowed bandwidth for a single archive policy execution.
Stop execution if there are 10% errors during an archive process.
Cold Artifactory Properties
The following properties can be configured in the Cold Artifactory System YAML.
Number of threads that will be used when processing the restore request.
By default, on the Cold Artifactory instance, the cron job rate to check the restore status for each archived artifact is 120 seconds (2min). This can be reconfigured for cost optimization.
Interval for the cleanup job.
The following property can be configured in the Cold Artifactory's
The maximum number of artifacts that can be restored during a single run is 30k. This value can be configured using the