search

marsbard / puppet-alfresco

A puppet build script for Alfresco
MIT License
25 stars 11 forks source link

Update the solr backup options #87

Open douglascrp opened 9 years ago

douglascrp commented 9 years ago

Since you are using Alfresco BART to perform backup, it doesn't make sense to disable the solr backup schedules in alfresco-global.properties:

These options should be removed

#Effectively turn off solr backup
solr.backup.alfresco.cronExpression=0 0 2 * * ? 2099
solr.backup.archive.cronExpression=0 0 4 * * ? 2099

And these should be included

solr.backup.alfresco.numberToKeep=1
solr.backup.archive.numberToKeep=1

Only one snapshot is required in order to Alfresco BART to have something to backup.

More about the topic at Alfresco Backup and Disaster Recovery – White Paper.pdf

Unless we are doing a cold backup we must copy the Solr from its own backup. Its backup configuration is already planned; these are the default values that can be modified by adding them into alfresco-global.properties:

solr.backup.alfresco.cronExpression=0 0 2 * * ?
solr.backup.archive.cronExpression=0 0  4 * * ? 
solr.backup.alfresco.remoteBackupLocation=${dir.root}/solrBackup/alfresco   
solr.backup.archive.remoteBackupLocation=${dir.root}/solrBackup/archive 
solr.backup.alfresco.numberToKeep=3 
solr.backup.archive.numberToKeep=3

Configuration above means that the Alfresco core (workspace://SpaceStore) is done every day at 2:00 AM creating its files in ${dir.root}/solrBackup/alfresco. The Alfresco archive core (archive://SpacesStore) is done every day at 4:00AM. In both cases 3 copies of the last 3 backups are kept. Information stored in those folders are what we have to copy to our backup target. If we have a backup strategy we may only need to keep one backup and also make the backup in a different periodicity.