[MGNLBACKUP-45] Restore on Derby fails with 'Failed to persist restored nodes with message deadbeef-face-babe-cafe-babecafebabe' Created: 24/Oct/11 Updated: 29/Mar/22 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Backup |
| Component/s: | None |
| Affects Version/s: | 1.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Edgar Vonk | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MacOS X 10.6.8, Derby, Magnolia 3.6.8 |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Team: |
| Description |
|
I am trying to use the Magnolia Backup module (v1.0.2) to sync all content from our production environment running Oracle as database to a local machine running Derby as database. I understand from this discussion and from the documentation of the module that this should be possible? I have tried to do this using the following steps:
However this fails with the mentioned error. See the attached log file for details. Any ideas? I also ran into out of memory issues regarding the heap space but fixed that by increasing -Xmx to 1024M in the restore script. Another thing I noticed is that that Magnolia backup tool does not seem to recognize that for the magnoliaAuthor instance we do not use the default/magnolia.properties but instead magnoliaAuthor/magnolia.properties: Loading configuration at /Applications/Dev/apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/config/default/magnolia.properties
But I fixed that by manually re-arranging some stuff for the import. |
| Comments |
| Comment by Jan Haderka [ 24/Oct/11 ] |
ERROR info.magnolia.module.backup.Backup Backup.java(restore:383) 24.10.2011 11:18:37 Failed to restore property data of node 429fb8b6-79ce-46a1-ac9e-34205d3e925f java.io.IOException: /42/9f/b8b679ce46a1ac9e34205d3e925f/%7bhttp%3a%2f%2fwww.jcp.org%2fjcr%2f1.0%7ddata.0.bin: the specified resource does not exist Seems like inconsistency in your repo (or backup) - the binary for this node is missing from the backup and can't be restored. WARN org.apache.jackrabbit.core.persistence.bundle.AbstractBundlePersistenceManager AbstractBundlePersistenceManager.java(store:592) 24.10.2011 11:19:05 Deleted node state's parent is not modified or deleted: deadbeef-cafe-babe-cafe-babecafebabe/deadbeef-face-babe-cafe-babecafebabe That looks like if the restore was trying to recreate whole workspace as part of another workspace ( deadbeef-face-babe-cafe-babecafebabe is always UUID of the root node). |
| Comment by Edgar Vonk [ 25/Oct/11 ] |
|
Hi Jan, thanks for the quick reply! Yes, it seems you were right about the inconsistency. I think this relates to the BLOBs. When I had a look at the Magnolia source environment I found out that the links to the BLOBs (mainly PDFs in de DMS) were all broken. We tried to find the problem but failed to find anything (nothing interesting in the logs) and ended up restarting Magnolia (Tomcat) and that resolved the issue. Either the inconsistency in the repo was already there and that explains why the backup was not correct or the backup process created the repo inconsistency. My guess is that it was the former.. Unfortunately I cannot recreate the backup easily because of time constraints but will look at it at a later stage. About the second point: what I did was try to restore the backup in the default Derby database. But.. I first removed the entire repositories folder (as per documentation) which means I also removed the entire Derby database with it.. I guess that is not the idea of the restore process? Could this be the reason for the error? Should I configure Magnolia to keep the Derby DB outside of the repositories folder? cheers, Edgar |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |