On 10/4/2019 1:41 PM, Koen De Groote wrote:
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.
The basic use case of backup/restore is that you create a backup, and
then you lose your Solr install. So you set up a brand new one ...
which has no collections. So the fact that the restore command must
create the collection is not really a problem.
And if I pick a new name, that would still mean restarting all clients that
have to connect to it.
That would depend on how those clients work, and we have no way of
knowing anything about your clients.
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?
If you are testing restore on a SolrCloud install that has NOT died and
been rebuilt, then that would be what you need to do to use an alias.
Because honestly, deleting the existing collection first is rather scary
and sounds like downtime for a restore is unavoidable.
In most situations where a backup is useful, you're already down.
Thanks,
Shawn
