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.