This topic outlines the limitations of the smart archiving feature.
Current Limitations of Archive Policies
Supported Repositories
Supports Local and Federated repositories. Does not support Remote and Virtual repositories.
Note
When archiving Federated repositories, the run (dry or actual) can take significantly longer compared to Local repositories. This is because the archive workflow must check the last download status of each package across all federation members. The more members involved, the longer the process will take.
Recommendations to Optimize Archive:
Adjust Policy Conditions: Narrow the scope of your archive policies to reduce the number of packages to be archived in each run. This can significantly speed up the run.
Increase Run Frequency: Run archive policies more often to process smaller sets of packages. This helps prevent large backlogs and improves long-term performance.
Package Verification
There is no verification if packages are part of a Release Bundle or build. A package-level Archive policy may impact build or release bundle promotion.
Archive Limits
An archive policy can archive up to 100,000 packages in a single run.
Progress Notifications
Notifications on the progress of an archive policy run and restore run are unavailable.
Visibility of Run Results
Run results for global policies are visible only to Platform admins globally.
Archive Policy
The Archive policy does not execute when an ongoing mandatory task is in progress (for example, Garbage Collection).
Search
A project admin can only perform searches within their project context and does not have access to the global scope.
Concurrent Execution and Queuing of Archive Policies
Archive Policies can run concurrently up to a specified maximum. When this limit is reached, additional triggered policies are queued. Any further triggered policies will be skipped entirely if the queue reaches its maximum capacity.
In the current version of Artifactory, queued or skipped policy runs do not appear in the Runs view. You can find a log of skipped policies in the Artifactory Service log. For example, you might see a message like:
"Policy: test_policy run: 1 has been rejected since allowed 3 concurrent runs are already in progress."
Supported Topology
1-to-1 Connection
Only one Active Artifactory Instance can be paired with one Archive Artifactory Instance.
Active Artifactory Configuration
Active Artifactory Instance can only be a Platform or a Mothership, not an Edge
No Hybrid Topology
An Archive Artifactory Instance (cloud) cannot connect to an Active Artifactory Instance (self-hosted).
Provider and Region Restriction
Archive Artifactory Instance must be of the same provider and region as the Active Artifactory Instance.
No Unbinding
Unbinding an Archive Artifactory Instance is not supported.
Conversion Restriction
Archive Artifactory Instance cannot be converted to other JPD types.
Self-hosted Platform - Not Supported
Currently, we do not support the Self-hosted Platform. It will be supported in the upcoming releases.
Unbinding Deleted/unavailable Archive Artifactory Instance
When an Active Artifactory Instance and an Archive Artifactory Instance are paired, and the Archive Artifactory Instance is no longer available (for example, it has been decommissioned or is unreachable), the usual binding revocation may fail. This is because the revocation request relies on the existence of the Archive Artifactory Instance to complete. If the Archive Artifactory Instance no longer exists, the binding cannot be deleted through standard means.
Workaround: Refer to the Solution.