Running Alfresco 4.0.0 on an EC2 instance and running out of disk space made me decide to move alf_data to a EBS-volume. I followed the instructions stated in:
However those instructions will only work if you run MySql and Lucene. When running PostgreSQL the dir.root gets hardcoded into two shell scripts:
If running PostgreSQL and Lucene I guess changing the path to dir.root in the following scripts in addition to alfresco-global.properties will be enough:
However if using Solr (installed by alfresco installer) it was rather tricky to find all references to dir.root, below is my list:
- For every store in Alfresco there will be a "alf_data/solr/<store-name>-SpacesStore/solrcore.properties, where the old path to dir.root is hardcoded. Change to the new location. - In $ALF_HOME/tomcat/conf/server.xml you will have to change the hardcoded paths in the ssl-connector solr uses. - In $ALF_HOME/tomcat/conf/Catalina/localhost/solr.xml there is also a hardcoded path that needs to be changed.
After this I had to delete the solr-indexes ie removed the following folders (one per store): - alf_data/solr/archive - alf_data/solr/workspace
After starting Alfresco (finally) went back to normal.
I've found a similar situation where after using the installer I wanted to move the only the contentstore, not the full alf_data. I modified dir.contentstore and dir.contentstore.deleted in alfresco-global.properties. The directories where created on the new destination but Alfresco was still accessing to the old location.
I do not why. Here theoretically should not be involved postgresql and solr neither.
Did you found the solution for moving content store. I am getting error when moving contentstore to network location. But if I move content store to another drive then I have no problem. I need to move to network location any help