after some testing, we're currently setting up our Alfresco environment and writing backup scripts. I know that the Solr indexes are backed up automatically and that we can change that schedule. But in from our experience backups are much more reliable, when you're able to make a fresh backup from something, before saving it in a backup repository.
According to the official documentation for the community edition this is acomplishable by using JMX:
This is an optional step before initiating a hot backup.
- Trigger a Solr index backup using a JMX client.
JConsole (MBeans tab -gt Alfresco/Schedule/DEFAULT/MonitoredCronTrigger/indexBackupTrigger/Operations - executeNow button)
- After completing this operation, the solr4Backup directory contains an up-to-date cold copy of the Solr indexes, ready to be backed up.
We actually managed to attach with jmxterm locally, but couldn't find a fitting MBean. Then after days of searching we found this question:Unable to connect with JConsole
And in the answer section we did read this:
JMX has always been an Alfresco Enterprise feature. But on Community you could still access tomcat's JMX features.
With the EOL of the RMI services in 5.0. Community no longer binds a RMI registry to port 50500
You can still access Tomcat's JMX features but not via Alfresco's connection. See Tomcat's docs for further details.
I must say, it is a bit disturbing that the official documentation refers to a feature, which is no longer supported.
Since that was the only documented way to make a fresh backup of the Solr indexes, how can I backup them without it?