Backups arent pruned #692

New Issue

Closed

opened 2023-05-08 18:28:16 +00:00 by DevloperAmanSingh · 11 comments

DevloperAmanSingh commented 2023-05-08 18:28:16 +00:00

Copy Link

hey
i am making the backup using borgbase.

so i use borg create command to create backup every 4 hour.
Backups older than 12 hours are pruned .
so when they are pruned their data should be deleted from the repo.
but the data is still thier and it is consuming the space.
i am using hetzner storage box as it support borg

below are the following evidences

thier is only 3 backups in the firemcbackupreo . The repo info is given below

But when i check the repo size then it shows 1024 gb

Pls help i have only 1 tb and the backups are max 60gb to 70gb pls help

this is how i prune the backups

hey i am making the backup using borgbase. so i use borg create command to create backup every ***4 hour.*** Backups older than ***12 hours*** are pruned . so when they are pruned their data should be deleted from the repo. but the data is still thier and it is consuming the space. i am using hetzner storage box as it support borg below are the following evidences  thier is only 3 backups in the ***firemcbackupreo*** . The repo info is given below  But when i check the repo size then it shows 1024 gb  Pls help i have only 1 tb and the backups are max 60gb to 70gb pls help this is how i prune the backups 

image.png

20 KiB

image.png

15 KiB

image.png

13 KiB

image.png

12 KiB

witten commented 2023-05-08 18:50:19 +00:00

Owner

Copy Link

A few questions that will help me understand what's going on:

• When you're running prune, what is the full borgmatic command you're running?
• What is in the consistency section of your borgmatic configuration?
• What version of borgmatic are you running? (borgmatic --version)
• What version of Borg are you running? (borg --vesrion)
• Are you seeing more backup archives than you expect? Or are you just seeing more space consumed by the repository than you expect?

Thanks!

A few questions that will help me understand what's going on: * When you're running `prune`, what is the full borgmatic command you're running? * What is in the `consistency` section of your borgmatic configuration? * What version of borgmatic are you running? (`borgmatic --version`) * What version of Borg are you running? (`borg --vesrion`) * Are you seeing more backup archives than you expect? Or are you just seeing more space consumed by the repository than you expect? Thanks!

witten added the

question / support

label 2023-05-08 18:50:29 +00:00

witten commented 2023-05-08 18:51:36 +00:00

Owner

Copy Link

I see you added a screenshot of your prune command. Have you tried running borgmatic compact as well? Depending on your version of Borg, no space is actually freed up until you run compact.

I see you added a screenshot of your `prune` command. Have you tried running `borgmatic compact` as well? Depending on your version of Borg, no space is actually freed up until you run `compact`.

DevloperAmanSingh commented 2023-05-08 18:55:00 +00:00

Author

Copy Link

• i am not using borgmatic because hetzner only allows borg
• my linux server borg version is borg 1.2.0
• my hetzner box borg version is 1.2.1
• archives are 3 all time but the space consumed is increasing after each backup . and when backup is pruned the space doesnt get less

- i am not using borgmatic because hetzner only allows borg - my linux server borg version is borg 1.2.0 - my hetzner box borg version is 1.2.1 - archives are 3 all time but the space consumed is increasing after each backup . and when backup is pruned the space doesnt get less

witten commented 2023-05-08 19:04:29 +00:00

Owner

Copy Link

Thanks for providing those details. I think the problem is almost certainly that you need to run borg compact! That's the thing that will actually free up space after a prune.

Also note that this issue tracker is for borgmatic support, not for Borg itself. For that, check out: https://github.com/borgbackup/borg/issues/

(Just FYI, borgmatic works fine using Hetzner as a Borg server. borgmatic does not need to be installed on the remote server side to work.)

Thanks for providing those details. I think the problem is almost certainly that you need to run `borg compact`! That's the thing that will actually free up space after a `prune`. Also note that this issue tracker is for borgmatic support, not for Borg itself. For that, check out: https://github.com/borgbackup/borg/issues/ (Just FYI, borgmatic works fine using Hetzner as a Borg server. borgmatic does not need to be installed on the remote server side to work.)

witten closed this issue 2023-05-08 19:04:29 +00:00

DevloperAmanSingh commented 2023-05-08 19:06:17 +00:00

Author

Copy Link

so i can use borgmatic in hetzner storage box right?

so i can use borgmatic in hetzner storage box right?

DevloperAmanSingh reopened this issue 2023-05-08 19:06:17 +00:00

DevloperAmanSingh commented 2023-05-08 19:06:17 +00:00

Author

Copy Link

so i can use borgmatic in hetzner storage box right?

so i can use borgmatic in hetzner storage box right?

witten commented 2023-05-08 19:07:41 +00:00

Owner

Copy Link

You can use borgmatic on a non-Hetzner server or workstation to backup to a Hetzner storage box.

You can use borgmatic on a non-Hetzner server or workstation to backup _to_ a Hetzner storage box.

DevloperAmanSingh commented 2023-05-08 19:09:27 +00:00

Author

Copy Link

will it fix the storage box increased size issue

will it fix the storage box increased size issue

witten commented 2023-05-08 19:11:46 +00:00

Owner

Copy Link

The only thing that will fix the size issue is running compact, either explicitly with Borg or borgmatic or implicitly with borgmatic. (By default, when no action is specified, borgmatic runs create, prune, compact, and check.)

The only thing that will fix the size issue is running `compact`, either explicitly with Borg or borgmatic or implicitly with borgmatic. (By default, when no action is specified, borgmatic runs `create`, `prune`, `compact`, and `check`.)

DevloperAmanSingh commented 2023-05-08 19:12:31 +00:00

Author

Copy Link

so if i run borg compact the backups in borg will not suffer data loss right?

so if i run borg compact the backups in borg will not suffer data loss right?

witten commented 2023-05-08 19:13:16 +00:00

Owner

Copy Link

Correct. It's only reclaiming space that was already freed up by prune. More here: https://borgbackup.readthedocs.io/en/stable/usage/compact.html

Correct. It's only reclaiming space that was already freed up by `prune`. More here: https://borgbackup.readthedocs.io/en/stable/usage/compact.html

witten closed this issue 2023-05-09 06:01:41 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#692

No description provided.