Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: More information for user on backup creation feature #1152

Closed
patschi opened this issue May 27, 2023 · 1 comment
Closed

FR: More information for user on backup creation feature #1152

patschi opened this issue May 27, 2023 · 1 comment

Comments

@patschi
Copy link
Contributor

patschi commented May 27, 2023

Is your feature request related to a problem? Please describe.
Without further details, it's hard to know when backups take place.

Describe the solution you'd like
The new backup feature is nice, but I'm missing a few essential information like when the backup is approx. scheduled/performed at. When creating a backup entry, it just says "It is being processed" but there is absolutely no indication when this is the case.

image

I guess the backup job is ran daily as per the cronjob settings within the Froxlor UI. This would be a great chance to retrieve the date there and show it on this specific page.

Additionally, it is not clear if the backup process is done once or automatically on a daily basis.

Describe alternatives you've considered
n/a

@envoyr
Copy link
Member

envoyr commented May 30, 2023

Hello patschi,

The "Backup" feature is not really new, but it has mostly functioned as a one-time export option for users.

Since there have been frequent requests for an enhanced backup function, I am currently working on a comprehensive rewrite for version 2.1 to address this.

The new implementation will offer more detailed information about when and how backups are created. Additionally, it will allow for regular automated backups, which will bring added value to both administrators and customers.

By the way, I will close this matter as it will be resolved as part of issue #1033. Feel free to provide feedback and continue the discussion there.

Best regards,
envoyr

@envoyr envoyr closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants