[Feature] Split system snapshots and add configurable chunk sizes to prevent disk overflow during SFTP uploads

1Panel Version

latest

Please describe your needs or suggestions for improvements

Hello 1Panel team,

First of all, thank you for developing and maintaining this incredible control panel. I am currently using the System Snapshot feature, but I have encountered a major storage issue when dealing with large applications.

---

🚀 The Problem

When backing up apps whose size exceeds roughly half of the total available disk space, the local storage fills up completely.

• Container Crashes: Because the disk runs out of space, running containers crash unexpectedly.
• Backup Failure: The backup process fails to finish writing data.
• System Instability: The entire system becomes unstable ("goes wild" / freezes or behaves erratically due to 100% disk utilization).

This issue specifically occurs when using the FTP/SFTP backup method, as I am routing all my backups to an external storage server, but the creation and handling locally still exhaust the disk.

---

💡 Proposed Solutions

To mitigate disk space overflows and make system snapshots much safer for production environments, I would like to propose the following features:

1. Split System Snapshots:
   Implement a mechanism to split the snapshot archive into smaller parts during creation rather than generating one massive monolithic file. This will drastically reduce the peak local disk space requirement.
2. Customizable Chunk Sizes:
   Add a configuration option in the backup settings to let users define a custom split size for the backup archives (e.g., options like 512 MB, 1 GB, or 5 GB).

---

Additional Context

Having this flexibility would ensure that even servers with tighter disk margins can safely perform full system snapshots and stream them via SFTP without risking local storage exhaustion and container downtime.

It would be amazing if you could consider implementing this architecture in a future update!

Thank you for your time and hard work!

Please describe the solution you suggest

No response

Additional Information

No response