Is it possible to make redundant copies with different schedule and retention period? #613

New issue

Closed

opened 2022-11-21 20:09:59 +00:00 by lamyergeier · 1 comment

lamyergeier commented 2022-11-21 20:09:59 +00:00

Copy link

What I'm trying to do and why

I read How to make backups redundant and I want to make redundant copies with different schedules. On portable external SSD I want to backup every day. On Non portable HDD I want to backup every week with different retention plan. Is it possible to do it in a single config file?

Steps to reproduce (if a bug)

Include (sanitized) borgmatic configuration files if applicable.

Actual behavior (if a bug)

Include (sanitized) --verbosity 2 output if applicable.

Expected behavior (if a bug)

Other notes / implementation ideas

Environment

borgmatic version: [version here]

Use sudo borgmatic --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: [e.g., Debian package, Docker container, etc.]

Borg version: [version here] 1.7.4

Use sudo borg --version

Python version: [version here] 3.10.8

Use python3 --version

Database version (if applicable): [version here]

Use psql --version or mysql --version on client and server.

operating system and version: [OS here] Ubuntu 22.04

#### What I'm trying to do and why I read [How to make backups redundant](https://torsion.org/borgmatic/docs/how-to/make-backups-redundant/) and I want to make redundant copies with different schedules. On portable external SSD I want to backup every day. On Non portable HDD I want to backup every week with different retention plan. Is it possible to do it in a single config file? #### Steps to reproduce (if a bug) Include (sanitized) borgmatic configuration files if applicable. #### Actual behavior (if a bug) Include (sanitized) `--verbosity 2` output if applicable. #### Expected behavior (if a bug) #### Other notes / implementation ideas #### Environment **borgmatic version:** [version here] Use `sudo borgmatic --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** [e.g., Debian package, Docker container, etc.] **Borg version:** [version here] 1.7.4 Use `sudo borg --version` **Python version:** [version here] 3.10.8 Use `python3 --version` **Database version (if applicable):** [version here] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** [OS here] Ubuntu 22.04

witten commented 2022-11-21 21:17:05 +00:00

Owner

Copy link

In order to create backups to different repositories on different schedules, I recommend using separate borgmatic configuration files and then invoking borgmatic separately for each configuration from your scheduler.

For instance, you could set up your schedule to run this every day:

borgmatic --config your_external_ssd_config.yaml

And then once a week, you could ask your scheduler to run:

borgmatic --config your_non_portable_hdd_config.yaml

Each of the configuration files could have its own distinct repositories configuration along with specific retention options for that repository. And then if you want to reduce duplication across those two configuration files, you can optionally use configuration includes and merging to share common configuration.

See How to make per-application backups for more information.

Hope this helps! Let me know if you have any other questions.

In order to create backups to different repositories on different schedules, I recommend using separate borgmatic configuration files and then invoking borgmatic separately for each configuration from your scheduler. For instance, you could set up your schedule to run this every day: `borgmatic --config your_external_ssd_config.yaml` And then once a week, you could ask your scheduler to run: `borgmatic --config your_non_portable_hdd_config.yaml` Each of the configuration files could have its own distinct `repositories` configuration along with specific retention options for that repository. And then if you want to reduce duplication across those two configuration files, you can optionally use configuration includes and merging to share common configuration. See [How to make per-application backups](https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/) for more information. Hope this helps! Let me know if you have any other questions.

witten added the

question / support

label 2022-11-21 21:17:26 +00:00

witten referenced this issue from a commit 2022-11-21 21:33:14 +00:00

Clarify documentation about multiple repositories and separate configuration files (#613).

lamyergeier closed this issue 2022-11-26 12:06:46 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

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   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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#613

No description provided.