-
Task
-
Resolution: Fixed
-
Major
-
1.6.1
-
-
Empty show more show less
-
Empty show more show less
-
Basel 44
-
8
This issue is addressing test-phase of new RepositoryCopier API used implementation of backup module which is done with MGNLBACKUP-99.
Acceptance Criteria:
- Make sure we will not have corrupted data upon concurrent modification to data.
- Deadlocks will not be an issue.
- Testing the implementation with various PersistenceManager s therefore DataSource s.
Findings;
- Tested with Mysql, Postgres, and Derby.
- Below is tested with Mysql with DataStore (Dataset =~ 3gb)
- Tried to remove data while backing up -> Seems to be working well, basically deletion happened after backup
- Tried to add data while backing up -> Seems to be working well as well, backups up basically everything which is present.
- Tried to version a node while backing up -> Found problematic situation that might cause inconsistent versions and tackled it with
MGNLBACKUP-102.
Acceptance criteria
- depends upon
-
MAGNOLIA-6658 Handle versions suffering from InconsistentVersioningState exceptions
- Closed
-
MGNLBACKUP-102 Implement Retry Mechanism for backup execution using REST
- Closed
- is depended upon by
-
MGNLBACKUP-99 Refactor backup module to use RepositoryCopier API in order to achieve stability
- Closed