You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably via ZFS sync, now that I have 500+ Gbps upload from the office. My idea is I can have that directory synchronize between my home and office, maybe with a Pi and a 2 or 4 TB NVMe SSD at home (maybe two in RAID 1?).
Ideally I could edit off either home or office and work that way, but if not, one-way sync to backup at home via ZFS replication would be nice.
I've never had this before for my 'scratch' disk but it would be nice insurance to have, since I have two local backups, but nothing offsite, for works in progress (I do have a manual backup disk I carry with me, but if I have to run out of the building in a fire... I ain't running back in to grab it!).
The text was updated successfully, but these errors were encountered:
Another option would be to use a standard S3 bucket (instead of Deep Archive) and sync that way using the same rclone setup from #14, but that would be a little messy since so many files change all the time.
Probably via ZFS sync, now that I have 500+ Gbps upload from the office. My idea is I can have that directory synchronize between my home and office, maybe with a Pi and a 2 or 4 TB NVMe SSD at home (maybe two in RAID 1?).
Ideally I could edit off either home or office and work that way, but if not, one-way sync to backup at home via ZFS replication would be nice.
I've never had this before for my 'scratch' disk but it would be nice insurance to have, since I have two local backups, but nothing offsite, for works in progress (I do have a manual backup disk I carry with me, but if I have to run out of the building in a fire... I ain't running back in to grab it!).
The text was updated successfully, but these errors were encountered: