[MGNLBACKUP-92] Let the backup app be configurable as to whether include versions or not Created: 11/May/15  Updated: 29/Mar/22  Resolved: 26/May/15

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

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Evzen Fochr
Resolution: Won't Fix Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
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   

The backup module already prepares the ground for this (BackupManager, BackupSubAppDescriptor, BackupPresenter, ...) but setting /modules/backup/apps/backup/subApps/main@keepVersions is not reflected runtime.



 Comments   
Comment by Evzen Fochr [ 25/May/15 ]

Just FYI keepVersions property was renamed to mgnlKeepVersions. (see MGNLBACKUP-85)

Comment by Jan Haderka [ 26/May/15 ]

IIRC there was good reason for disabling this config option and keeping versioning on at all times. Without it, version store is irrevocably corrupted at restore time and it is then never possible to create new version on previously created content ... consistent with what is reported in support ticket. Thus I would suggest to remove this option from all other places where it is present and make sure that version store is always included in the backup.

Comment by Evzen Fochr [ 26/May/15 ]

Default value for mgnlKeepVersions set to true was done in MGNLBACKUP-85.

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