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

Feature Request: Support offsite-backups and restoring customers #1033

Open
envoyr opened this issue May 31, 2022 · 2 comments
Open

Feature Request: Support offsite-backups and restoring customers #1033

envoyr opened this issue May 31, 2022 · 2 comments
Assignees
Projects

Comments

@envoyr
Copy link
Member

envoyr commented May 31, 2022

Describe the solution you would like to see
It should be possible for admins & resellers to create offsite backups for customers. It is planned that customer data, web space, databases and email accounts can be backed up to an external server.

Additional context
Accordingly, it should be possible to completely backup customers and then back them up to external servers, in case of emergency, a complete restore should be possible.

This feature could also be used to move customers to another froxlor server more easily.

Planned interfaces for transfer are: S3, SFTP, FTPS, Local

Note
This will be a post-release feature for 2.x

@envoyr envoyr self-assigned this May 31, 2022
@envoyr envoyr changed the title Support offsite-backups and restoring customers Feature Request: Support offsite-backups and restoring customers May 31, 2022
@JB1985
Copy link
Contributor

JB1985 commented Jun 7, 2022

Webdav would be great to use (for example) nextcloud.

@d00p d00p added this to To do in 2.0 Jun 29, 2022
@envoyr envoyr moved this from To do to post-release feature in 2.0 Jul 1, 2022
@envoyr envoyr moved this from Post-Release feature to In progress in 2.0 May 21, 2023
@envoyr envoyr added this to the 2.1 milestone May 21, 2023
@envoyr envoyr moved this from In progress to Post-Release feature in 2.0 May 21, 2023
@d00p d00p added this to To do in 2.1 May 21, 2023
@envoyr envoyr moved this from To do to In progress in 2.1 May 22, 2023
@envoyr envoyr removed this from Post-Release feature in 2.0 May 22, 2023
@d00p d00p moved this from In progress to To discuss in 2.1 Sep 17, 2023
@d00p d00p removed this from the 2.1.x milestone Sep 17, 2023
@d00p d00p removed this from To discuss in 2.1 Sep 17, 2023
@d00p d00p added this to To do in 2.2 via automation Sep 17, 2023
@realrellek
Copy link

I think some of the "infrastructure" could be useful for the clean-migration as well (ref #1232)

So there could be an export with all the customers (assigned to their admins/resellers) and all the password hashes (for databases: playing by the same rules as the migration)

That way, you could also restore a backup from the SQL dumps and the htdocs, you know, in case of emergency.

(I know about the discussion that it may or may not be pushed even further because there are good backup solutions that froxlor will never be able to compete with... I am just writing down my thoughts on how we could re-use some of the code for another feature. So that whatever gets implemented first also thinks of the other and, well, gets designed in a way that it usable for a greater scheme)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
2.2
To do
Development

No branches or pull requests

4 participants