WARNING: what I currently understand about the limitations of AWS could fill volumes so I might be completely out to lunch.
If you ADDREPLICA with the new replica's data residing on the new EBS volume, then wait for it to sync (which it'll do all by itself) then DELETEREPLICA on the original you'll be all set. In recent Solr's, theres also the MOVENODE collections API call. Best, Erick On Tue, Aug 1, 2017 at 6:03 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 8/1/2017 4:00 PM, Mahmoud Almokadem wrote: >> I'm using ubuntu and I'll try rsync command. Unfortunately I'm using one >> replication factor but I think the downtime will be less than five minutes >> after following your steps. >> >> But how can I start Solr backup or why should I run it although I copied >> the index and changed theo path? >> >> And what do you mean with "Using multiple passes with rsync"? > > The first time you copy the data, which you could do with cp if you > want, the time required will be limited by the size of the data and the > speed of the disks. Depending on the size, it could take several hours > like you estimated. I would suggest using rsync for the first copy just > because you're going to need the same command again for the later passes. > > Doing a second pass with rsync should go very quickly. How fast would > depend on the rate that the index data is changing. You might need to > do this step more than once just so that it gets faster each time, in > preparation for the final pass. > > A final pass with rsync might only take a few seconds, and if Solr is > stopped before that final copy is started, then there's no way the index > data can change. > > Thanks, > Shawn >
