borgbackup / borgbackup/backupdata

consider merging with others

Open
#2 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
13
Forks
6
PR merge metrics
No merged PRs in 30d

Description

restic has a similar project, called [fakedatafs](https://github.com/restic/fakedatafs), with similar goals. fakedatafs works as a FUSE filesystem to provide a dataset to benchmark backup software.

obnam has its own tool to generate backup data called... [genbackupdata](http://liw.fi/genbackupdata/). the design is similar to borg's, but like fakedatafs, it is also deterministic.

i was wondering if any thought has been given to reviewing or even merging with those projects instead of maintaining (now at least) 3 different projects in parallel?

if we want a standardized test suite for backup software, it seems to me we should aim at standardizing the corpus generation as well! :)

a similar issue was opened against the restic project in https://github.com/restic/fakedatafs/issues/3

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the existing backupdata project alongside restic's fakedatafs and obnam's genbackupdata, starting with the linked fakedatafs issue for related discussion. Determine whether their goals and designs can be combined or standardized; the work is done when the project has a documented decision and scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.