Feature #84
rsync.net integration
| Status: | New | Start: | 2011-09-15 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 1 |
Description
How feasible is it to allow customers to request that either their daily, weekly or monthly backup gets copied to their rsync.net (or other) space when it is made?
I imagine that as a customer I ask you to copy my daily backup to a given location, you update some config file and I allow access to the space from bitfolk's backup public key. What I'm about to manually setup is a cron job to do this through my vps (mount daily.0, copy, unmount).
This should probably be considered for implementing after the encrypted backups so all that gets copied is the files on the backup server.
History
Updated by admin over 13 years ago
What is the downside to the customer doing it for themselves? i.e. other than "I can't be bothered", what does BitFolk doing it for you achieve?
The only thing I can really think of is that it will be slightly faster for BitFolk to do it vs. the customer doing it over NFS.
Updated by vps01 over 13 years ago
Let's say I want to ensure that rsync.net always has the latest daily.0. I set up a cron job to touch a file every minutes and use the backed up copy of that file to establish when my daily backups happen, lets assume 0200.
I establish a cron job for 0300 to copy the contents of daily.0 to rsync. Now imagine that something delays the bitfolk backup until 0301. I am now copying a backup over which is older than I wish, 6 hours later instead of having the most recent daily.0 I instead essentially have daily.1 copied. Of course any method by which bitfolk can execute a script on my vps would also protect against the same potential issue, for example do the rsync backup and then run "/root/backup_complete hourly", "/root/backup_complete daily", "/root/backup_complete monthly" as well as being a more adaptable solution for other people.
To be honest this is posted imagining it's a case of adding a few lines into a script file on the backup server (check if customer also wants it sent somewhere else, copy it somewhere else).
Updated by atomicx over 13 years ago
I've only skimmed your response so I might be missing something, but this sounds like its mainly a cron/scheduling issue.
I'd also be hesitant to make a backup of a backup - doesn't this introduce another point of failure for both backups? For instance if the bitfolk backup became corrupt or was misconfigured in some way then this would be mirrored off-site and both backups would have the same fault.