mirror of
https://github.com/borgbackup/borg.git
synced 2026-04-22 14:49:03 -04:00
48b39d878f
Some features like repository quotas rely on a server-side component that enforces them (because that shall only be controllable server-side, not client-side). So, that can only work, if such a server-side component exists, which is the case for borg 1.x ssh: repositories (but not for borg 1.x non-ssh: repositories). For borg2, we currently have: - fs repos - sftp: repos - rclone: repos (enabling many different cloud providers) - s3/b3: repos - ssh: repos using client/server rpc code similar as in borg 1.x So, only for the last method we have a borg server-side process that could enforce some features, but not for any of the other repo types. For quotas the current idea is that this should not be done within borg, but enforced by a storage specific quota implementation (like fs quota, or quota of the cloud storage provider). borg could offer information about overall repo space used, but would not enforce quotas within borg. |
||
|---|---|---|
| .. | ||
| automated-local.rst | ||
| central-backup-server.rst | ||
| hosting-repositories.rst | ||
| image-backup.rst | ||
| non-root-user.rst | ||
| pull-backup.rst | ||