Thanks for the rapid replies. I've opened https://issues.apache.org/jira/browse/SOLR-16326 and will proceed with scripting a scheduled backup instead.
On Fri, Aug 5, 2022 at 11:36 AM Shawn Heisey <apa...@elyograg.org> wrote: > On 8/5/22 10:06, Thomas Woodard wrote: > > That is exactly what I was afraid of. Not being able to configure where > > automated backups go seems like a pretty major oversight, though. Is > anyone > > aware of a solution other than creating a bunch of soft links? > > The symlink idea I had (but haven't mentioned) would work pretty well if > you were calling http://server:port/solr/CORE/replication with a script > or manually, but not for the triggered backups. Maybe in the meantime > you can switch to a scheduled script and provide location and name > params on the URL instead of configuring backupAfter. Then you could do > anything you want to do and won't have to compile it yourself or wait > for a new version. > > FYI, if your index is not very small, you should probably not be > optimizing it frequently. If the optimizes are not frequent, or an > optimize completes very quickly, then ignore that. > > Please open an enhancement issue in the Apache Jira on the SOLR > project. You are right that the location should be configurable as well > as something that can be provided on the URL. I think we need to take a > close look at all the parameters for the replication handler and decide > which ones should be configurable in solrconfig.xml. > > When I have some free time I will look into improving the handler. An > issue in Jira makes that work easier to track, and would also get your > name in the changelog. > > Thanks, > Shawn > >
