Changing the Allocated Space For Local Backups

Tom
2nd February 2021

1 min read

By default, we allocate 20% of server space for backups. If existing backups on the server exceed the allotted space, Borg will not create new backups or do anything else which requires a backup (staging pushes, clones, etc).

Why would that happen? Maybe you have a really large site. Maybe you take 24 manual backups on the 30 minute mark because you’re paranoid. Whatever the reason, 20% doesn’t always cut it. Fortunately, you can increase this value.

Accessing the Config File

The available space varies per server size, but you can change it with this command:

nano /opt/gridpane/backups/snapshots/config

Contents of the Config File

Once you’re in that file, it will look like this:

[repository]
version = 1
segments_per_dir = 1000
max_segment_size = 524288000
append_only = 0
storage_quota = 11000000000
additional_free_space = 0
id = (hidden for the KB, will show on your server)
key = (hidden for the KB, will show on your server)

The value you want to change is “storage_quota”. Save, write, and exit the file.

Bytes/GB Conversion

It’s in bytes and converts to GB like so:

1 GB = 10^9 bytes = 1,000,000,000 bytes

10GB	10000000000
15GB	15000000000
20GB	20000000000
25GB	25000000000
30GB	30000000000
35GB	35000000000
40GB	40000000000
45GB	45000000000
50GB	50000000000
55GB	55000000000
60GB	60000000000
65GB	65000000000
70GB	70000000000
75GB	75000000000