Environment:
Application A: Artifactory version 7.41.13, started using docker run, utilizing the built-in Derby database.
Data Size: Approximately 10TB.
New Setup: Migrating to a new server and starting Application B using Docker Compose with Artifactory version 7.41.13.
Steps Taken:
Shutdown:
Closed Application A (Artifactory).
Closed Application B (Artifactory).
Data Migration:
Copied the var directory from Application A to the var directory of Application B on the new server.
Startup:
Started Application B.
Verification:
Checked Artifactory’s repository information, user information, and artifact properties. All appeared normal and functional.
Reference: I referred to the following link:[ How to move from the Derby database to any external database in Unified Platform (Artifactory 7.x) without losing data](https://jfrog.com/help/r/how-to-move-from-the-derby-database-to-any-external-database-in-unified-platform-artifactory7-x-without-losing-data/versions-applicable-7.x)
Observation: I noticed that the migration was successful without using the Artifactory UI steps: Administration -> Artifactory -> Import & Export -> System
Question: Why was the migration successful without performing the Import & Export step through the Artifactory UI? Is there something I might have missed?
Additional Information:
Both Application A and B are running the same Artifactory version (7.41.13).
The built-in Derby database was used for Application A.
The var directory contains all necessary data for Artifactory to function correctly.
Request: Please help me understand if this approach is recommended or if there are any potential issues I might encounter by not using the Import & Export feature.
Environment:
Application A: Artifactory version 7.41.13, started using docker run, utilizing the built-in Derby database.
Data Size: Approximately 10TB.
New Setup: Migrating to a new server and starting Application B using Docker Compose with Artifactory version 7.41.13.
Steps Taken:
Shutdown:
Closed Application A (Artifactory).
Closed Application B (Artifactory).
Data Migration:
Copied the var directory from Application A to the var directory of Application B on the new server.
Startup:
Started Application B.
Verification:
Checked Artifactory’s repository information, user information, and artifact properties. All appeared normal and functional.
Reference: I referred to the following link:[ How to move from the Derby database to any external database in Unified Platform (Artifactory 7.x) without losing data](https://jfrog.com/help/r/how-to-move-from-the-derby-database-to-any-external-database-in-unified-platform-artifactory7-x-without-losing-data/versions-applicable-7.x)
Observation: I noticed that the migration was successful without using the Artifactory UI steps: Administration -> Artifactory -> Import & Export -> System
Question: Why was the migration successful without performing the Import & Export step through the Artifactory UI? Is there something I might have missed?
Additional Information:
Both Application A and B are running the same Artifactory version (7.41.13).
The built-in Derby database was used for Application A.
The var directory contains all necessary data for Artifactory to function correctly.
Request: Please help me understand if this approach is recommended or if there are any potential issues I might encounter by not using the Import & Export feature.