Solved Using Rclone from a server to backup multiple volumes from different SSH hosts
-
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
In addition to that, I would have to enable cron on every apple workstation, which while doable, is a pain in the rear should I ever need to make any changes to the backup operation.
Centrally managing this makes way more sense rather than the ad hoc approach.
And since when has cron been disabled in macOS?
-
@marcinozga said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
In addition to that, I would have to enable cron on every apple workstation, which while doable, is a pain in the rear should I ever need to make any changes to the backup operation.
Centrally managing this makes way more sense rather than the ad hoc approach.
And since when has cron been disabled in macOS?
For quite some time, it's still there, but you have to enable it, grant it root access etc.
-
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
@marcinozga said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
In addition to that, I would have to enable cron on every apple workstation, which while doable, is a pain in the rear should I ever need to make any changes to the backup operation.
Centrally managing this makes way more sense rather than the ad hoc approach.
And since when has cron been disabled in macOS?
For quite some time, it's still there, but you have to enable it, grant it root access etc.
That's simply not true. You don't have to enable it. And you don't have to give it root access unless you're writing somewhere you shouldn't be in first place.
-
Anyways I figured this out.
Having multiple rclone sources like
https://i.imgur.com/SKtlxrr.pngand running
Works
-
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
Anyways I figured this out.
Having multiple rclone sources like
https://i.imgur.com/SKtlxrr.pngand running
Works
The /Volumes/<path to external> would change for each system, wouldn't it?
Could you back up to
b2-rclone:/<username>/external? -
@dafyre said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
@DustinB3403 said in Using Rclone from a server to backup multiple volumes from different SSH hosts:
Anyways I figured this out.
Having multiple rclone sources like
https://i.imgur.com/SKtlxrr.pngand running
Works
The /Volumes/<path to external> would change for each system, wouldn't it?
Could you back up to
b2-rclone:/<username>/external?Possibly, but what I was thinking I would do is simply connect to the administrative user on each of these workstations, hit the volume that way. The Volume name may change (as spaces make everything more difficult). But yeah I think this'll work.
-
To clarify for anyone else in the future, you need to have multiple apple-# sftp connections.
The b2 connections could also be custom as you can create multiple buckets and simply connect to that bucket via rclone.
-
This is what the b2-rclone remote setting looks like for my needs, obviously this could be adjusted with the advanced configuration menu.
https://i.imgur.com/sj858rr.png
And this is the Apple workstation
-
Ideally when this is all said and done, what I think would make the most sense is to create multiple buckets for each of these apple workstations.
So apple-bucket-1, apple-bucket-2 and so on.
From there, simply have cron run the sync commands for each of these and have it run hourly.
-
Worth noting on this that while sync works, copy is the much safer option.
So
rclone copy source:/path dest:/pathis what I'll likely end up using. In any case, the resulting solution still works.Still need to tweak OSX a bit as it seems to kill the SSH session after some time for sporadic reasons - still testing but I may end up having to add
ServerAliveInterval 120to/etc/ssh/ssh_configto resolve that issue.
