You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@solr.apache.org by Katja Zinchenko <Zi...@bsb-muenchen.de> on 2022/11/25 14:29:52 UTC
Is it possible to define one certain solr server to perform backup with a local file system as a target?
Hello everybody,
I am try to do backup like
curl
'http://XXX-01:8983/solr/admin/collections?action=BACKUP&name=btestBackup&collection=btest&location=backup'
It works after performing following operations on each server:
mkdir solr-8.11.1/server/backup
mkdir -p solr-8.11.1/server/backup/btestBackup/btest/zk_backup_0
mkdir -p
solr-8.11.1/server/backup/btestBackup/btest/shard_backup_metadata
Afterwards I have backup in the file system of a random server. So, I
have to allocate enough memory on each node, which will probably stay
empty. Are there any other solutions to define which server will be used
for the backups?
Thanks a lot
Katja
Re: Is it possible to define one certain solr server to perform backup with a local file system as a target?
Posted by Shawn Heisey <ap...@elyograg.org>.
On 11/25/22 07:29, Katja Zinchenko wrote:
> Afterwards I have backup in the file system of a random server. So, I
> have to allocate enough memory on each node, which will probably stay
> empty. Are there any other solutions to define which server will be used
> for the backups?
Maybe one requirement escaped your notice: The Collections API backup
functionality requires that every server have the backup location
mounted to the same storage on the same path. If you look at the
requests shown here:
https://solr.apache.org/guide/solr/latest/deployment-guide/collection-management.html#backup
The first thing it says there is "Backs up Solr collections and
associated configurations to a shared filesystem - for example a Network
File System."
Some kind of shared storage (usually SMB, NFS, or similar) is a
requirement for that backup/restore functionality. I have never seen
anything that will specify which machine actually performs the backup.
I *think* it's probably the leader replica for each shard, and the
replica that is leader can change.
Thanks,
Shawn