Shawn, Indeed, we're probably already in catastrophe territory in this case. A complete replace does indeed seem like the best option in that case.
Client is just the default solr client, ` org.apache.solr:solr-solrj:<version>` Mikhail, Sounds possible, but I wonder about the cases where I would need a restore now. Most of these will probably be a catastrophic event in which a complete re-setup is needed. I guess it would be useful in restoring an older version for a specific reason. Thanks. On Fri, Oct 4, 2019 at 10:59 PM Mikhail Khludnev <m...@apache.org> wrote: > Hello, Koen. > What about switching "query" alias to restored collection, and then nuking > the old one? > > On Fri, Oct 4, 2019 at 10:52 PM Koen De Groote < > koen.degro...@limecraft.com> > wrote: > > > Greetings. > > > > Solr 7.6, cloud. > > > > From what I've researched, backup and restore is pretty straightforward. > > BACKUP and RESTORE are collection commands and the backup is to be put > on a > > shared filesystem. > > > > So far so good. > > > > I'm a bit concerned about the RESTORE action. A RESTORE command will > create > > a new collection, meaning either I need to pick a new name or delete the > > old one first. > > > > And if I pick a new name, that would still mean restarting all clients > that > > have to connect to it. > > > > The documentation speaks or using ALIAS, but I don't see how that works. > > > > I can only create an alias for an existing collection, so I'd first have > to > > restore the backup to a different name, verify it is correct, delete the > > old collection and then give it an alias that is the name of the old > > collection? > > > > Or how is this supposed to work? > > > > Because honestly, deleting the existing collection first is rather scary > > and sounds like downtime for a restore is unavoidable. > > > > So, how to properly restore? > > > > Kind regards, > > Koen De Groote > > > > > -- > Sincerely yours > Mikhail Khludnev >
