"They're just files, man". If you can afford a bit of down-time, you can shut your Solr down and recursively copy the data directory from your source to destingation. SCP, rsync, whatever then restart solr.
Do take some care when copying between Windows and *nix that you do a _binary_ transfer. If you continually have a problem with transferring between Windows and *nix we'll have to investigate further. And I'm assuming this is stand-alone and there's only a single restore going on at a time..... Best, Erick On Thu, Jun 22, 2017 at 9:13 AM, Moritz Michael <moritz.mu...@gmail.com> wrote: > > > > > > > > > BTW, is there a better/recommended way to transfer an > index to another solr? > > > > > > > > > > On Thu, Jun 22, 2017 at 6:09 PM +0200, "Moritz Michael" < > moritz.mu...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > Hello Michael, > I used the backup functionality to create a snapshot and uploaded this > snapshot, so I feel it should be save. > I'll try it again. Maybe the copy operation wasn't successful. > BestMoritz > > > > _____________________________ > From: Michael Kuhlmann <k...@solr.info> > Sent: Donnerstag, Juni 22, 2017 2:50 PM > Subject: Re: Error after moving index > To: <solr-user@lucene.apache.org> > > > Hi Moritz, > > did you stop your local Solr sever before? Copying data from a running > instance may cause headaches. > > If yes, what happens if you copy everything again? It seems that your > copy operations wasn't successful. > > Best, > Michael > > Am 22.06.2017 um 14:37 schrieb Moritz Munte: > > Hello, > > > > > > > > I created an index on my local machine (Windows 10) and it works fine > there. > > > > After uploading the index to the production server (Linux), the server > shows > > an error: > ..... > > > > > > > > > >
