Newbie plannig question

Getting Help
1

Hi

new to restic, I have a server with zfs exporting some spare (dataset) as nfs lets say
/shared.

I use sanoid to take snapshots and syncoid to replicate this dataset and snapshots to another server..

Now that I have my 2 one site locations I want to now send this to the cloud, I am thinking restic + wasabi

I had planned on doing another zfs sync to another server and then using restic there to backup the snapshot.

but then I thought can I run restic on the 2nd server above against a snapshot and use the 3rd server as a restic repo.

if i do that I could in theory use any server with restic and just point to my local restic repo.

How do I then sync this to wasabi

in the end I want to keep lots of stuff in wasabi (cloud) and keep minimal on site … Not sure i need to do this , but I like the idea. How easy / efficient is it to sync a restic repo from onsite to off site

or do i just use the 2nd server and use restic to backup to a wasabi repo ?

Doing some reading but would like some input into the right direction so as not waste a lot of time.

My gut says use server #2 and just use the cloud as the restic repo

2

If you want to sync a “local” repository to wasabi, thus making it available from wasabi too, you could use rclone for example.

3

Hi

I want more than just to sync whats local to cloud

so for example in my local repo I might want to keep hourly / daily / weekly / monthly and yearly
but for the cloud I might want to keep all of my yearly and say monthly

where as on prem it might only be up to 1 year old

does that make sense. and if I am resyncing daily - i don’t want to have to read the entire repo just to add this months

4

I believe that you should backup separately to local repo and to cloud repo. This has the added benefit that the two are completely separate, reducing the risk of problems with the local repo to propagate to the cloud repo.

1 Like