This is hard to tell whithout knowing what data you index to Solr and how. If you use Data Import Handler, that is no longer part of 9.0 so you definitely need to plan for how to proceed. You'll find tons of email threads on it in the archives. If you have an external indexing process, you simply trigger that process..
Jan > 25. sep. 2023 kl. 10:54 skrev Jim Morgan <jim.mor...@nknews.org.INVALID>: > > That was my feeling as well. I could have just cloned the server, but doing > it this way, I can document the procedure (and maybe even automate it in > the future), so it never becomes an obstacle again. And also we get the > latest version of software on the latest OS. > > So one further question, if you don't mind. If I copy the config directory > over to the new server, will that trigger the re-indexing automatically? > And (oh, no, two questions) when the re-indexing starts, will there be a > flood of traffic on whatever its indexing from? I'm keen to avoid a sudden > surge which takes down our webservers. > > On Mon, Sep 25, 2023 at 4:39 PM Jan Høydahl <jan....@cominvent.com> wrote: > >> Hi, >> >> Absolutely. And if your company lacks documentation and routines for >> installing and configuring >> this piece of software, it is an excellet opportuninty to fill that gap by >> doing it step by step. >> While you're at it, you can also read the upgrade notes >> https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html >> and see if you are affected by any of the breaking changes. >> >> If you're running legacy setup (not Cloud) then you simply place your >> <myCore/conf> folder in the new Solr's SOLR_HOME folder and you don't need >> any API calls to create the core. >> >> Jan >> >>> 25. sep. 2023 kl. 10:12 skrev Jim Morgan <jim.mor...@nknews.org.INVALID >>> : >>> >>> Thanks Jan. I've read that around the internet too. Are you saying that I >>> should not use the backup/restore method, but INSTEAD, I should be trying >>> to create the core on the new server and get the data into it by running >> a >>> re-index, rather than copying it across? >>> So if that's what you're saying, what would be the steps I'd need to >> take? >>> I'm guessing create core, copy config files, .... >>> >>> On Mon, Sep 25, 2023 at 3:55 PM Jan Høydahl <jan....@cominvent.com> >> wrote: >>> >>>> I highly recommend doing a full re-index from scratch to the new >> cluster. >>>> Then, test it in your dev/test environment. >>>> And finally, switch your search app to the new server. >>>> >>>> Jan >>>> >>>>> 25. sep. 2023 kl. 09:40 skrev Jim Morgan <jim.mor...@nknews.org.INVALID >>>>> : >>>>> >>>>> Hi, >>>>> I inherited a solr installation from a previous sysadmin, and we'd like >>>> to >>>>> see if we can move it from the current server to a new one. I don't >> have >>>>> much knowledge of solr, but I know my way around Linux. Apologies in >>>>> advance for any dumb questions, and please feel free to educate me. >>>>> >>>>> Old install is Solr 8.5 running on Ubuntu 18. We're thinking that while >>>> we >>>>> are switching servers, we might as well try to upgrade to Ubuntu 22 and >>>>> Solr 9.3 (with corresponding JVM increase to 11). >>>>> First question, is that a crazy idea? Or should we be moving to the >> same >>>>> version of Solr on the new server, and then upgrade in place. We'd >> prefer >>>>> to do it with minimal downtime, so setting up parallel servers and >>>>> migrating the data across seems like the least disruptive. >>>>> >>>>> So I have tried the parallel server approach. No issues installing Solr >>>> and >>>>> JVM. From reading around the web, starting with >>>>> >>>> >> https://solr.apache.org/guide/solr/latest/deployment-guide/backup-restore.html >>>>> And several other pages, which all seem to repeat the advice, the >> backup >>>>> restore process is simple. This is a standalone install so I should use >>>>> >>>>> >>>> >> http://localhost:8983/solr/collname/replication?command=backup&location=/snapshots >>>>> >>>>> to backup, which works fine: the backup appears in /snapshots/ as >>>>> snapshot.2023xxx. All good. >>>>> >>>>> I take the backup, and copy it to the new server, and put it in the >> same >>>>> location, /snapshots/2023xxx >>>>> Then apparenly I only need to run >>>>> >>>>> >>>> >> http://localhost:8983/solr/collname/replication?command=restore&name=snapshot.2023xxx&location=/snapshots >>>>> >>>>> But this doesn't work. I've tried a lot of different variations, >>>> combining >>>>> snapshot name and location, with or without the collection name, but >> all >>>> I >>>>> get is the zen like error >>>>> Searching for Solr? >>>>> You must type the correct path. >>>>> Solr will respond. >>>>> >>>>> So that's where I'm at. I'm wondering if I've missed a step that's >>>> obvious >>>>> to Solr veterans, but which is missing from the backup/restore page. >>>>> Do I need to create the core first, for example. Or create the core and >>>>> copy config files over to the new server. >>>> >>>> >> >>
