Concurrency detection for backups and restore

Registered by Fausto Marzi

A Concurrency avoidance mechanism is necessary on freezerc when executing multiple backups on the same node with same backups name and file system path. This generate issues with lvm snapshot and in case of restore concurrency a corrupted data may occur.

Implementation thoughts:
- Manage concurrency from a lock file in /tmp/ (/tmp is good as when the node reboot /tmp is emptied).

freezerc should have an option called something like max-concurrency-time, which is the maximum wait time a new freezerc process should wait to execute, before executing the old freezerc process.

Blueprint information

Status:
Not started
Approver:
Fabrizio Fresco
Priority:
Undefined
Drafter:
Fausto Marzi
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.