[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: |
|
||||||||
| 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: | |||||||||
| Description |
|
With the version of 2.0, backup module is using RepositoryCopier API 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. Proposed SolutionIntegrating 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. |