Archive not being created more than 2 times #646
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#646
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
i runned brogmatic command 4 times and all 4 times i have changed my data but only i can see only 2 archives how can i rectify this .
i have run 4 times brogmatic soi should see 4 archives but it stuck at 2 only.
Can I get a look at your configuration? For instance, what is your configured retention policy? Perhaps borgmatic is pruning the oldest archives as new ones are created, and that's why you're seeing fewer archives than you expect?
yes sure
Thanks for posting your configuration. I'm pretty sure that the
keep_daily
option is what's causing your archives to get pruned. From the Borg prune documentation:Therefore your
keep_daily: 3
means Borg retains three backups, one made each day. When you run borgmatic repeatedly, it runsborg prune
, which prunes all backups except one because a day hasn't passed since the last backup.So why are you seeing two archives? Because borgmatic currently prunes first—before creating a new backup. It prunes down to one backup and then immediately creates another one.
I hope that makes sense! This all can be a little tricky. There are several examples in the Borg docs that should hopefully provide inspiration if you'd like to tweak your prune settings.
So what value should i write so that it doesnt prune ?
i have set this but still i see 2 archives . pls help
Currently, the way to do that is to run borgmatic on the command-line without an explicit or implicit
prune
action. So for instance:borgmatic create
orborgmatic create check
depending on which actions you want to run. See the documentation for more information.But be advised that without any pruning (or compacting), your repository will grow without bound!
Thnaks it worked . Thanks
May i know how to connect to sftp so that i can manage archives fro thier itself
Borg doesn't support sftp directly as far as I know, but the details of connecting to your repository server via sftp would depend on your hosting provider. However you wouldn't see very much if you did that; the Borg repository isn't intended to be viewable without using Borg to view it.
If you just want to browse your archives though, you can use
borgmatic rlist
to list your archives orborgmatic list
to list the contents of an archive or evenborgmatic mount
to get a file-level view into one of your archives.So if i want to extract a
file
orfolder
from archive how this can be done specifically.Check out the documentation on that topic and let me know if anything's not clear!
yeh thanks
another question is it possible that like i have archive but i want that the
test
folder in that archive should replace my othertest
folder in the /home/ubuntu directory .how can i achive this
Here's an example that will do that:
Note however that it will overwrite
/home/ubuntu
on file-by-file basis. Meaning it won't delete any files already in that directory. If you want that behavior, I recommend manually deleting/home/ubuntu
first before extracting.@witten Can you elaborate on this issue a bit, I'm also experiencing it but I have
keep_daily
set to30
Shouldn't this keep up to 30 backups rather than 3?
If so, wouldn't this be a bug?
Nope!
keep_daily
doesn't mean Borg will keep 30 archives per day. It means it'll keep 30 archives taken at a cadence of once per day. So if there are more archives than one per day, they'll get pruned down to the last archive taken each day. But if you're looking to keep archives more frequently than that, check out thekeep_hourly
orkeep_within
options. For more information, see Borg's prune documentation.Oh interesting, thank you @witten
I'm going to call this original questions addressed for now, but please feel free to file any follow-up questions as additional tickets. You may also be interested in #304, which changes the default ordering to prune second rather than first.