[MGNLBACKUP-102] Implement Retry Mechanism for backup execution using REST Created: 17/May/16  Updated: 29/Mar/22  Resolved: 30/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: Neutral
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: backup
Remaining Estimate: 0d
Time Spent: 4d
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLBACKUP-100 Test stability of RepositoryCopier im... 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 47
Story Points: 13
Team: Nucleus

 Description   

With the version of 2.0, backup module is using RepositoryCopier API MGNLBACKUP-99. While testing the new implementation MGNLBACKUP-100, we encountered an issue with versioning.

The issue is that, if one tries to version a node while the backup is ongoing. There is a possibility of having the version node in InconsistentVersionStateException.
After some further observation, it is clear that one may encounter the situation only if the node to be versioned had not been versioned before. In other words, versioning a node which will be a first version may causing the exceptions while the backup is ongoing.

Proposed Solution

Integrating backup with REST and having it execute backup request with a REST call which will provide us to observe mgnlVersion workspace and therefore, we will have the knowledge of if something had changed meanwhile the backup operation was ongoing.


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