Easiest way is just to copy the entire directory that contains
core.properties to the second Solr's SOLR_HOME directory (I'd have the
Solr instanced down). The core discovery Shawn mentioned just
recursively descends from SOLR_HOME and whenever it encounters a
core.properties figures out that this is a core and loads it. So you
have some directory like
blah/core1
that has core.properties in it. Just move core1 to SOLR_HOME for solr2.

But this really seems like an XY problem. What do you hope to gain by
this? Why not just create a new core on Solr2 and start using that? Or
do you have a lot of cores on this machine and are just balancing the
number of them? In the latter case, why not just use SolrCloud and
ADDREPLICA/DELETEREPLICA to move cores around?

Best,
Erick

On Wed, Sep 13, 2017 at 6:09 AM, Shawn Heisey <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB