You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While documenting the lock file usage of BiT in v1.4.1 (currently released version as at today) I saw
that snapshot() checks if a restore is running for the same profile to avoid conflicts (esp.
when restoring directly into the original folders of the snapshot files):
logger.warning('Restore is already running', self)
return
Possible Impact
TODO to be analyzed
PS: I think this may be good issue for new BiT developers (just test by starting two instances and then try to understand the source code of the restore() function...
The text was updated successfully, but these errors were encountered:
Observation
While documenting the lock file usage of BiT in v1.4.1 (currently released version as at today) I saw
that
snapshot()
checks if a restore is running for the same profile to avoid conflicts (esp.when restoring directly into the original folders of the snapshot files):
backintime/common/snapshots.py
Lines 719 to 720 in 25c2115
I could find not a check for a running backup ("take snapshot") in ´restore()` so IMHO it may happen that
backintime/common/snapshots.py
Lines 449 to 458 in 25c2115
Possible Impact
PS: I think this may be good issue for new BiT developers (just test by starting two instances and then try to understand the source code of the
restore()
function...The text was updated successfully, but these errors were encountered: