These are some of the limitations that you may encounter when using Cold Storage and any possible workarounds.
Limitation | In the event of an unexpected shutdown, archive policy execution might be interrupted. Due to this, the policy's corresponding operation record in the database will not be marked as done. |
Workaround | In this situation, items that were not archived will be picked up for archive during the next policy run. Stop policy execution before restarting the server. |
Limitation | If the restore path that the system generates during the restore operation exceeds the path limit, the restore operation will fail. |
Workaround | No workaround. The maximum path length supported is 1024 characters. The maximum repository name length supported is 64 characters. |
Limitation | Restore by folder path is not supported. |
Workaround | Select all files that are to be restored. |
Limitation | When creating a retention policy, cannot save basic search criteria as AQL, even though preview is able to identify content. |
Workaround | Create and save the retention policy using the Create an Archive PolicyAPI. |
Limitation | Archive policy cron expression validation not working. |
Workaround | Though the cron expression always appears as invalid in UI, you can still save it. So use an external cron expression validator to validate your cron expressions and then save the policy. |
Limitation | Cold storage retention policy does not persist Age settings. |
Workaround | This is a UI issue. Though the Age settings do not look like they persist, the real data is still correct and will work as expected when saved. |
Limitation | Currently there is a limitation when using Cold Storage with a Federated Repository. If a retention policy (used to archive artifacts or packages to a Cold Storage server) is configured to clear artifacts or packages from a Federated Repository, the archiving event and any restore event will not be synced with the Federation members. In addition, any deleted artifacts or packages will be recreated due to the Federation.Therefore, it is not recommended to use Cold Storage with Federated Repositories. In a future Artifactory version, the sync with the Federation Members will be enabled. |
Workaround | N/A |
Limitation | When setting up a Cold Instance for package archiving, a cloud binary storage provider such as AWS Glacier cannot be used. |
Workaround | Use a local binary storage provider. |