The upgrade process Dave refers to is the correct way to upgrade. Another option, if both instances are still running, would be to proxy each of the old instance's repositories from the new instance (create a remote repository on the new 3.1.1.1 instance that is directed to a local repository on the old 1.2.5 instance), this way, every time you resolve an artifact from the remote repository, it will be downloaded from the old instance and cached locally in the new instance, this way you make sure that stale artifacts (ones that are not in use) will not be transferred. This process will require keeping the old instance running for some time, to make sure that all needed artifacts are transferred.
Hope this helps, Itamar. -- View this message in context: http://forums.jfrog.org/Exporting-artifacts-from-v1-2-5-then-importing-into-v3-1-1-1-tp7579666p7579669.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
