You don’t need a backup for this. 1. Wait for a period of low or no traffic, because this will use some CPU and disk io. 2. Use SPLITSHARD to split the shards and create new ones on the same nodes: https://solr.apache.org/guide/8_8/shard-management.html#splitshard <https://solr.apache.org/guide/8_8/shard-management.html#splitshard> 3. Make new replicas of the shards on the new machines. 4. Delete the replicas you no longer want.
wunder Walter Underwood [email protected] http://observer.wunderwood.org/ (my blog) > On May 10, 2021, at 8:25 AM, Eric Pugh <[email protected]> > wrote: > > The Solr Ref guide has some details > https://solr.apache.org/guide/8_8/making-and-restoring-backups.html > > Also, there are a number of firms that providing training around Solr > operations, just google “Solr training”. Learning Solr Ops will make you a > lot more comfortable supporting a significant setup! > >> On May 10, 2021, at 5:26 AM, FIRST STEP <[email protected]> wrote: >> >> Hi >> >> >> >> Can anyone let me know how can I take backup of solr data and change the >> solr configuration. >> >> Example: >> >> Currently I have 2 nodes and each solr collection 2 shards per node. i.e 1 >> collection 4 shards >> >> >> >> Now I would like to increase the nodes I mean add 2 more nodes and increase >> the shards for all the collections. >> >> For this I don’t want to lose the existence data and want to change the >> configuration. >> >> >> >> Please provide a suggestion. >> >> >> >> Thanks in Advance >> >> >> >> Regards, >> >> Srihitha > > _______________________ > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | > http://www.opensourceconnections.com <http://www.opensourceconnections.com/> > | My Free/Busy <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless of > whether attachments are marked as such. >
