practically test the "from borg" importer

Open
#71 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend, testing-qa

Research direction

Start with borg-import borg -h and inspect the existing automated test that exercises the importer. Add practical tests for importing archives between Borg 1.x repositories, including extraction, recreation, and cleanup, while being careful with real backup data.

Written by the indexing model from the issue text.

Description

help wanted

I have just added some code to import backups from a borg 1.x repo into a new borg 1.x repo.

borg-import borg -h  # read this!

Importing an archive does:

  • for each archive in the source repo
  • extract archive to the extraction directory (subdirectory of cwd)
  • create a new archive from the extracted data
  • delete all files from the extraction directory

This is useful when there is some reason to rebuild the repo:

  • use a new AES key (e.g. if your old key might be compromised)
  • you can also transfer archives from multiple source repos into a single destination repo
  • (add more reasons here)

There is a automated test that succeeds doing this, but more practical tests are definitely needed. Be careful!

Dominant language
Python
Stars
48
Forks
31
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from borgbackup/borg-import

All issues in borgbackup/borg-import

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.