Also forgot to mention one more method which is a little more passive than
the previous suggestions and is more helpful for keeping only the artifacts
which are in use:
Begin targeting only one of the instances when resolving/publishing and
configure that instance to proxy the second one; That way, the central
instance will be lazily populated by all the artifacts that only exist in
the secondary instance and are actually used.
After a while you can shut down the secondary instance and move the all the
artifacts that the central instance has cached to an ordinary local
repository.
On Sun, Oct 2, 2011 at 10:17 AM, Noam Y. Tenne <[email protected]> wrote:
> Hi Daniel,
>
> Since these are different installations, a simple file level merge won't
> work.
> Considering that you are interested in merging only the contents of both
> instances (only artifacts and metadata) you've got two options:
>
> - Use the Replication
> addon<http://wiki.jfrog.org/confluence/display/RTF/Repository+Replication>
> (provided
> that you are running the pro version of Artifactory) which is a perfect for
> this situation.
> - Use the repository import-export tools (see the Repositories Import
> and Export section
> here<http://wiki.jfrog.org/confluence/display/RTF/Importing+and+Exporting>)
> to export the contents repositories of one installation and import them to
> the other.
>
> As opposed to the system import-export which erases all existing content
> before importing both configurations and artifacts, the repository mechanism
> is incremental; That is, when importing a set of repositories, repositories
> by the same name must already exist in the target instance of Artifactory
> (otherwise they will be ignored) and existing artifacts will be kept.
>
> HTH,
> Noam
>
> On Wed, Sep 28, 2011 at 4:18 PM, <[email protected]> wrote:
>
>> For historical reasons, we currently have two separate Artifactory
>> servers, with most of the artifacts in both, but some artifacts in only one
>> or the other, and I'd like to "merge" them.
>>
>> The first solution that came up is to use rsync to copy all files from one
>> of them to the other, then ask Artifactory to reindex all artifacts in the
>> "merged installation" and then turning off the second instance.
>>
>> Would this approach work? Would you suggest a different approach?
>>
>> Thanks in advance,
>> Daniel Serodio
>>
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
