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
Kopia only allows one user to perform maintenance.
This has potential for issues if that specific user stops doing so.
I had gone 2 months without maintenance before noticing that no maintenance is occurring.
Because the only user allowed to do maintenance was me on an old OS for a drive that has since been reformatted and replaced.
I would like to suggest:
KopiaUI should notify non maintenance providing users if more than a week has passed since last maintenance. but only if maintenance is set to true. possibly with an option to disable the warning.
KopiaUI should list which user is responsible for maintenance in the Repository page. This could also allow for KopiaUI to change said user via a drop down menu.
The text was updated successfully, but these errors were encountered:
We are using command line only on some servers here and we had the same issue recently.
We didn't notice the maintenance was running from one server that was stopped and reinstalled until recently our s3 buckets was really big (like 5 times the normal size) where we started to investigate and discovered the maintenance task wasn't running.
I think the maintenance owner stuff should be re-worked to have an automatic election.
For example, if 3 full maintenance cycle were not executed in a row, the next client that perform a backup to the repository should take the lead automatically and perform maintenance task.
Kopia only allows one user to perform maintenance.
This has potential for issues if that specific user stops doing so.
I had gone 2 months without maintenance before noticing that no maintenance is occurring.
Because the only user allowed to do maintenance was me on an old OS for a drive that has since been reformatted and replaced.
I would like to suggest:
The text was updated successfully, but these errors were encountered: