[MGNLBACKUP-16] Restore Script for Magnolia EE 3.6.3 Created: 07/Oct/08  Updated: 29/Mar/22  Resolved: 13/May/09

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jon Larson Assignee: Jan Haderka
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Java 1.5
Tomcat 5.5.25
Magnolia 3.6.3
BDB


Issue Links:
dependency
depends upon MGNLBACKUP-15 Bundling of 1.0.1 was wrong - no scri... Closed
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: Nucleus

 Description   

Not sure how to run a restore after an automated backup. The documentation below refers to a restore script from the backup module bundle, which file or script is it referring to?

http://documentation.magnolia.info/modules/backup.html



 Comments   
Comment by Magnolia International [ 07/Oct/08 ]

This is unfortunately another of the release issues we've had with 3.6.2/3.6.3: see MGNLBACKUP-15
Will release a new version of the backup module shortly.

Comment by Magnolia International [ 07/Oct/08 ]

New release of the backup bundle available at
http://files.magnolia.info/backup/

Comment by jlarson@ussa.org [ 09/Oct/08 ]

I ran the script with the folowing parameters and I'm getting the following errors:

./restore -backup /pathtobackup -webapp /pathtomagnoliaAuthorwebapp

ERROR org.apache.jackrabbit.core.RepositoryImpl.java(<init>:343) 10.0.10.2008 failed to start Repository: Cannot instantiate persistence manager

Comment by Magnolia International [ 09/Oct/08 ]

moving to the backup project.

Comment by Jan Haderka [ 09/Oct/08 ]

Hi Jon,
could you please attach whole log from the restore?
could you let me know on what OS did you run it?
Couly also provide exact parameters you used to invoke the restore script?
It would be also great if you can provide repoConfig.gz file from the backup you are trying to restore. Please note that this file contains copy of repositories.xml with the passwords to connect to your database so you might want to open the archive and edit repository_xml file in it to remove the password.
Alternatively, you can send the repoConfig.gz by mail to support account.
Thanks.
Jan

Comment by Magnolia International [ 09/Oct/08 ]

Alternatively, you can send the repoConfig.gz by mail to support account.

Or better yet, move the issue to the Support project - your jlarson account already has the necessary permissions.

Comment by Jan Haderka [ 13/May/09 ]

Reopen and move to support if needed.

Generated at Sun Feb 11 23:24:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.