#CHRONOSYNC SPARSE BUNDLE UPDATE#

Sparse_bundle_adjustment (jade) - 0.3.2-0 The packages in the sparse_bundle_adjustment repository were released into the lunar distro by running /usr/bin/bloom-release -r lunar -t lunar sparse_bundle_adjustment on Mon, 21:06:18 -0000 Sparse_bundle_adjustment (lunar) - 0.3.2-0 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Mon, 21:12:36 -0000 Sparse_bundle_adjustment (melodic) - 0.3.2-0 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Sun, 00:33:13 -0000 Sparse_bundle_adjustment (melodic) - 0.4.0-0 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Tue, 22:57:15 -0000 Sparse_bundle_adjustment (melodic) - 0.4.1-0 The packages in the sparse_bundle_adjustment repository were released into the lunar distro by running /usr/bin/bloom-release -r lunar -t lunar sparse_bundle_adjustment on Thu, 20:08:19 -0000 Sparse_bundle_adjustment (lunar) - 0.4.2-0 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Thu, 20:16:08 -0000 Sparse_bundle_adjustment (melodic) - 0.4.2-0 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Fri, 14:19:43 -0000 Sparse_bundle_adjustment (melodic) - 0.4.3-1 The packages in the sparse_bundle_adjustment repository were released into the kinetic distro by running /usr/bin/bloom-release -r kinetic -t kinetic sparse_bundle_adjustment on Sat, 20:42:49 -0000 Sparse_bundle_adjustment (kinetic) - 0.3.3-1 The packages in the sparse_bundle_adjustment repository were released into the melodic distro by running /usr/bin/bloom-release -r melodic -t melodic sparse_bundle_adjustment on Sat, 20:46:34 -0000 Sparse_bundle_adjustment (melodic) - 0.4.4-1 Version of package(s) in repository sparse_bundle_adjustment: The sparse_bundle_adjustment package was released. The packages in the sparse_bundle_adjustment repository were released into the noetic distro by running /usr/bin/bloom-release -r noetic -t noetic sparse_bundle_adjustment on Mon, 14:32:45 -0000 The whole DMG thing comes into play because your FTP site is not a nativeĪpple file system and thus doesn't support all the file structures, namingĬonventions, and attributes available on a local HFS+ formatted drive.Sparse_bundle_adjustment (noetic) - 0.4.4-1 I don't see a requirement to change unless you are going to use theĪdditional tools for other reasons as well. The backup service does just one thing, and appears to do it well for your Startup volume on a local external volume. I also use CS for maintaining my bootable clone of my Iįrequently need access to manipulate files at our hosts, so ExpanDrive comes But I have both those utilities around for other reasons. The best method I've found for syncing to FTP/SFTP sites is using ExpanDriveĪnd ChronoSync. 'If you are happy with the backup service, just use the backup service. my 'homemade' incremental back up solution?įrom a helpful and prompt person at Chronosync (this puts the quest to bed): Or I just keep paying Backblaze $50 a year to have backups, in the background, without me lifting a finger.?Īm I missing something (uhh, certainly likely?) or is Backblaze coming out ahead here vs. Then use Chronosync w/ something like ExpanDrive(seems like the cleaner solution, but again more money) to copy the latest version of my sparse bundle to sync (update) w/ the local sparse bundle(bundles, actually, as I will have more than one form different volumes) to the FTP site.

#CHRONOSYNC SPARSE BUNDLE UPDATE#

Then daily update the local sparse bundle w/ SD.Ĥ. Btw, these files are very big - I have lots to back up.ģ. I then upload that to my FTP site (already paying for w/ unlimited space), but I have to keep that sparse bundle locally (pretty darn big, eating up lots of disk space -I think this is quite a negative), to 'smart update' it by syncing. So, thanks to some insights I've learned here:ġ.I create a 'sparse bundle' of files (I used SuperDuper! - which I then can incrementally update it)),Ģ.

Chronosync sparse bundle