[MGNLBACKUP-31] Backup of a Magnolia instance with a split repository only backs up the primary repository Created: 02/Dec/10  Updated: 29/Mar/22  Resolved: 25/Aug/21

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: 1.2.x

Type: Bug Priority: Major
Reporter: Rico Jansen Assignee: Richard Gange
Resolution: Workaround exists Votes: 1
Labels: backup, enterprise, vpro
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File jackrabbit-bundle-mysql-search.xml     XML File jackrabbit-mysql-cluster-search.xml     File magnolia.properties     XML File repositories-cluster.xml    
Issue Links:
relation
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   

We are running a setup with one author instance and 2 public instances. For the use of commenting we
have clustered the forum workspace. This means sthe repository is split using the repositories.xml, which
specifies which workspace goes where. However when we run the backup using the backup module it only
backs up the default magnolia repository and not the magnoliacluster repository which we also have.

We do get a backup of the forum workspace, but it is an empty one which probably gets created on
bootstrapping.

Workaround
Use backup extended for multiple repository support.



 Comments   
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.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Comment by Richard Gange [ 20/Aug/21 ]

Hello rico.jansen-

I know this issue is super old but I wanted to let you know there is a new module in the incubator which can help this situation. See https://wiki.magnolia-cms.com/display/SERVICES/Backup+Extended. Open a support ticket should you like to talk more about this.

Cheers
Rich

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