[MGNLBACKUP-13] Unable to startup after the restore due to corrupted versions Created: 01/Sep/08  Updated: 29/Mar/22  Resolved: 02/Sep/08

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

Type: Bug Priority: Critical
Reporter: Oliver Lietz Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Backup: mgnl 3.6.1, mysql simple PM, external blobs
Restore mgnl 3.6.1, mysql bundle PM, external blobs


Attachments: Text File error.txt    
Issue Links:
relation
is related to MGNLTOOLS-24 Don't expect workspace name when reqi... 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   

When testing the backup both backup and restore ran without any problems, however we failed to startup the instance after the restore. Problem might be related to the fact that we changed the persistence manager configuration before running the restore.
Error message attached.



 Comments   
Comment by Jan Haderka [ 02/Sep/08 ]

r17793
After removal of the version selection checkbox from the UI, option to backup version was incorrectly defaulted to false, causing all the backups to be made without versions which in turn made restored instances not fully working (empty versions tables and invalid references in restored nodes).

Comment by Jan Haderka [ 24/Jun/11 ]

Closing all previously resolved and released issues.

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