I would love an answer to this too! On Fri, Aug 7, 2020 at 12:18 AM Bram Van Dam <bram.van...@intix.eu> wrote:
> Hey folks, > > Been reading up about the various ways of creating backups. The whole > "shared filesystem for Solrcloud backups"-thing is kind of a no-go in > our environment, so I've been looking for ways around that, and here's > what I've come up with so far: > > 1. Stop applications from writing to solr > > 2. Commit everything > > 3. Identify a single core for each shard in each collection > > 4. Snapshot that core using CREATESNAPSHOT in the Collections API > > 5. Once complete, re-enable application write access to Solr > > 6. Create a backup from these snapshots using the replication handler's > backup function (replication?command=backup&commitName=mySnapshot) > > 7. Put the backups somewhere safe > > 8. Clean up snapshots > > > This seems ... too good to be true? I've seen so many threads about how > hard it is to create backups in SolrCloud on this mailing list over the > years, but this seems pretty straightforward? Am I missing some > glaringly obvious reason why this will fail catastrophically? > > Using Solr 7.7 in this case. > > Feedback much appreciated! > > Thanks, > > - Bram > -- ** ** <https://www.canva.com/>Empowering the world to design Share accurate information on COVID-19 and spread messages of support to your community. Here are some resources <https://about.canva.com/coronavirus-awareness-collection/?utm_medium=pr&utm_source=news&utm_campaign=covid19_templates> that can help. <https://twitter.com/canva> <https://facebook.com/canva> <https://au.linkedin.com/company/canva> <https://twitter.com/canva> <https://facebook.com/canva> <https://au.linkedin.com/company/canva> <https://instagram.com/canva>
