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
Is your feature request related to a problem? Please describe.
In the lifetime of an ownCloud instance, it can happen that users delete data which should not be deleted. Even despite the "two
-step" process through the trashbin, it has happened and will happen again. In these cases, a sysadmin team is often ask to restore only a part of the storage snapshot without a full "overwrite from backup"
Describe the solution you'd like
Inside the product, which means a new backend feature
Additional tooling to work with the storage
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Referencing: #5351 (Add mechanism to commit and freeze writing to storage for taking a backup)
When one has a consistent snapshot available, which is in reality a path to a frozen ressource (more easily with POSIX as all in one, a bit more work with S3 as split), the tool should access a given snapshot, provides a list of available spaces and a method to restore a selected one.
Is your feature request related to a problem? Please describe.
In the lifetime of an ownCloud instance, it can happen that users delete data which should not be deleted. Even despite the "two
-step" process through the trashbin, it has happened and will happen again. In these cases, a sysadmin team is often ask to restore only a part of the storage snapshot without a full "overwrite from backup"
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: