![]() ![]() Instead, I focus specifically on whether ChronoSync can serve as an effective offsite backup system.īecause of ChronoSync’s extreme flexibility and the complexity of understanding and setting up cloud storage services, the discussion below gets quite involved. In this article, I’ll offer just an overview of ChronoSync’s features, as it would require a book to explore them at any depth. We also like that the $50 price includes lifetime updates (better yet, TidBITS members receive 20 percent off!). ChronoSync 4.7 also added support for SFTP (Secure FTP), which gives you even more remote file storage options.ĬhronoSync has a bazillion options, and we generally like how it works. We at TidBITS were excited to see ChronoSync add options to use Amazon’s Simple Storage System (S3) and Google Cloud Storage as sources or destinations. The nominal successor to Apple’s Backup app may be the 4.7 release of Econ Technologies’ ChronoSync, a long-standing Mac app that offers on-demand and scheduled synchronization and backup. (CrashPlan can also perform local and LAN-based backups.) Independent cloud backup options, like Backblaze and CrashPlan, back up your data for a recurring fee. Time Machine filled the gap for local backups but has never offered a cloud-based option. ICloud eliminated the Backup app’s iDisk option, and iCloud Drive took years to materialize after that, but only for general file storage. Although it was never a good backup app, Backup went through several versions, and in its best-remembered incarnation, it could selectively copy files from your Mac to a MobileMe iDisk, a Finder-mountable version of what would later be called “cloud storage.” Some Mac users remember Apple’s Backup app more fondly than it deserves because nothing quite took its place. Investigating ChronoSync 4.7 for Cloud Backup #1656: Passcode thieves lock iCloud accounts, the apps Adam uses, iPhoto and Aperture library conversion in Ventura.#1657: A deep dive into the innovative Arc Web browser.#1658: Rapid Security Responses, NYPD and industry standard AirTag news, Apple's Q2 2023 financials.#1659: Exposure notifications shut down, cookbook subscription service, alarm notification type proposal, Explain XKCD.#1660: OS updates for sports and security, Drobo in bankruptcy, why TidBITS doesn't cover rumors.Therefore, if preventing DEL commands has no repercussions other than preventing client-initiated prunes, this would be a possible route. To keep the number of archives from growing, the user may set up a cronjob or the like on the trusted server (or even a different trusted client, if the server is also untrusted) to prune archives. If borg serve could deny DEL commands, the user could set up an ssh forced command, that only ever allows the clients to add archives. Say, the user has a server she -for whatever reason- trusts. Is the only drawback of forbidding all DEL commands, that no prune or delete can be issued from the client?īecause in that case, for experienced users and guarded well by documentation this could be a useful feature, e.g. ![]() Sorry to dig up such an old thread, but this looks promising to me. Even intermediary checkpoint archives would show up or not work as they do now. If it would reject all DEL, you could not use prune or delete and your archive list would grow to unmanageable lengths. ![]()
0 Comments
Leave a Reply. |