[MGNLBACKUP-99] Refactor backup module to use RepositoryCopier API in order to achieve stability Created: 26/Apr/16  Updated: 29/Mar/22  Resolved: 06/May/16

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: 1.6.1
Fix Version/s: 2.0, 2.1

Type: Improvement Priority: Major
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: backup, restore
Remaining Estimate: 0d
Time Spent: 3d
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLBACKUP-100 Test stability of RepositoryCopier im... Closed
depends upon MAGNOLIA-6658 Handle versions suffering from Incons... Closed
relation
supersession
supersedes MGNLBACKUP-98 Datastore not restored properly 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)
Release notes required:
Yes
Documentation update required:
Yes
Sprint: Basel 43
Story Points: 8
Team: Nucleus

 Description   

This issue is to implement the RepositoryCopier API approach in backup module, therefore we will be setting the version to the next major one.

Having this opportunity, this issue also tackles the general cleanup of the existing codebase in the module.
For more information, please have a look at: https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=119276550&src=jira


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