topic Re: Problem restoring an Alfresco 3.0 Backup in Alfresco Archive

Problem restoring an Alfresco 3.0 Backup

jlabuelo — Tue, 09 Mar 2010 16:41:32 GMT

Hi allWe are using Alfresco CE 3.0 and have a problem now when trying to restore the backup of the system.We have a backup of the "alf_data" folder where the content and the indexes are, and also a backup of the MySQL Alfresco DB. To perform this backup of two items, we have stoped Alfresco, then pe

Re: Problem restoring an Alfresco 3.0 Backup

jlabuelo — Wed, 10 Mar 2010 08:34:50 GMT

Hi again

Any ideas why we are getting this error with the backups?… What tools do you use to move the information backed up from one server to anoter?. I thought using a Synchronization tool would be enough and would reduce the traffic in the net, as we are not moving all the 36 GB every day (plus the db file backed up also), just only the bytes changed.

Any ideas, suggestions??

Thanks a lot in advance

Regards

Re: Problem restoring an Alfresco 3.0 Backup

jlabuelo — Thu, 08 Apr 2010 15:49:32 GMT

Hi there

We have tried it again this time, stoping the Alfresco system installed in the C:\Alfresco folder in the Production enviroment. We made the backup of the mysql db, and also the total copy of the C:\Alfresco\alf_data folder.

Then we moved to a testing enviroment where we installed same version of Mysql and Alfresco (also in the C:\Alfresco folder), copied in C:\Alfresco the alf_data folder with the content information, and restored the alfresco DB we got from the PRD system.

If we try to launch alfresco we get this error:

GRAVE: Excepci�n enviando evento inicializado de contexto a instancia de escuchador de clase org.springframework.web.context.ContextLoaderListener
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.‍‍

I have readed that sometimes this error happens when the information stored in the DB is not synchronized with the information stored in the alf_data folder, but it is is just a copy of the PRD system and the PRD system works… dont see why this fails.

Also I made sure that the dir.root variable is pointing to "./alf_data" in the repository.properties file, so everything should be ok, shouldnt be?

Please I know I have open this post time ago, but still nobady replied back and I am affraid that if the "PRD" system fails (it is not critical as it is our internal ECM, not for a customer) we will lose all the information there.

Anything we are doing wrong please let us know

Regards

Re: Problem restoring an Alfresco 3.0 Backup

mabayona — Fri, 09 Apr 2010 07:45:54 GMT

First, don´t worry. backup and restore works OK as far as I can tell you. It sounds that you are doing someting wrong.

¿Do you use custom models? If so, be sure that the system that is being restored has the custom models (and other customisations and configurations) in place BEFORE trying to restore the data.

Hope it helps.

Re: Problem restoring an Alfresco 3.0 Backup

jlabuelo — Fri, 09 Apr 2010 07:53:58 GMT

Hi thanks a lot for the help

Yes we have some customizations done, however we make sure that we have them in place before trying to restore the data. We have the CustomModel.xml and custom-model-context.xml configured to get it, and also the web-client-config-custom.xml, so in this case we think we have it correctly.

We have readed that the have to set the "index.recovery.mode=FULL", which we did not have, and we are doing it right now in custom-repository.properties …. do you think might be this?

Thanks a lot for the answer… as I said we are quite worried to know if our backups work or not

Re: Problem restoring an Alfresco 3.0 Backup

mabayona — Fri, 09 Apr 2010 08:34:35 GMT

yes,

starting with parameter:

index.recovery.mode=FULL

will restore your indices and this could solve your out-of-sync problems.

Re: Problem restoring an Alfresco 3.0 Backup

jlabuelo — Thu, 15 Apr 2010 10:33:04 GMT

Hi there

Thanks for the info. Once we set the parameter

index.recovery.mode=FULL

we got the backup restored…ufff we started to be worried 😄

Thanks a lot