-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Support for Incremental Backups in Pterodactyl Wings #5245
Comments
so you mean u want a goddamn sync button? |
Hi @LakshmiBhaskarPVL, thanks for your response! Actually, the feature request is for a full incremental backup solution, not just a simple sync button. The idea is to allow for a combination of full and incremental backups, where only changed data is saved between backups. This approach would help optimize both storage and backup time, especially valuable for large and dynamic servers. |
ohh ok |
Thanks, @LakshmiBhaskarPVL , for offering to help with an add-on! My main goal is to have an official implementation within Pterodactyl Wings itself, as it would likely receive ongoing support and compatibility updates directly from the maintainers. However, I'd definitely be interested in an add-on if it provides the incremental backup functionality we need. Let me know if you proceed with it—I'd be happy to test or provide feedback! |
I really appreciate your initiative @LakshmiBhaskarPVL to create an add-on for incremental backups! If you’d like, feel free to assign me to your repository once you’ve started working on it—I’d be more than happy to assist with testing, feedback, or contributing where needed. Let me know how I can help! |
ok |
Restic would be a really good options here. It's fast, does incremental backups, and can backup locally or to S3, so it could be basically a drop-in replacement. |
Hopefully this doesn't become one of those expensive add-ons. Technically it shouldn't even be a add-on it should be fully integrated into the panel |
I run a fork of wings on my servers that already has this, maybe I'll send in some PRs. I'd rather give back to the community than sell some expensive addon. |
Thanks for chiming in, @asineth0 and @XxXBOBBY99ASXxX! I completely agree—incremental backups would be an excellent addition to Wings as a built-in feature rather than a paid add-on. My initial request was made with the hope of adding this functionality directly to the panel for all users to benefit from, especially given how essential backups are for server management. @asineth0, it’s awesome to hear you’ve already implemented this in your Wings fork! If you’re considering submitting PRs, that would be an amazing way to give back to the community. Let me know if I can assist in any way! |
@asineth0 This has been a long-awaited feature, so if you're comfortable with making a PR for it (no pressure of course) that would be fantastic :) |
this will be free |
Is there an existing feature request for this?
Describe the feature you would like to see.
Currently, Pterodactyl Wings supports only full backups, which can be time-consuming and storage-intensive, especially for large servers with frequent data changes. Implementing incremental backup functionality would allow the system to back up only the data that has changed since the last backup, thereby saving storage space and reducing backup times.
Describe the solution you'd like.
Introduce an option within the Wings backup management interface to select between full and incremental backups. This feature would enable administrators to schedule regular incremental backups, with periodic full backups to ensure data integrity. The system should manage backup chains effectively to maintain consistency and allow for reliable restoration processes.
Additional context to this request.
Incremental backups are a common feature in many backup solutions, offering efficiency in both storage and time. By implementing this feature, Pterodactyl Wings would provide a more robust and flexible backup system, catering to the needs of administrators managing large and dynamic server environments.
The text was updated successfully, but these errors were encountered: