[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 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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 |
|
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. |
| Comments |
| Comment by Jan Haderka [ 02/Sep/08 ] |
|
r17793 |
| Comment by Jan Haderka [ 24/Jun/11 ] |
|
Closing all previously resolved and released issues. |