![]() The “Advanced” tab contains a handful of advanced ChronoAgent options, notably the options to set up WAN Accessibility. The “General” tab contains all of the controls for setting up the agent. The “License” and “Status” panels are self-explanatory. The ChronoAgent system preference pane has 4 tabs. You can find ChronoAgent in the System Preferences, at the bottom of the panel, in what used to be the “Other” section. ![]() This tip explains the first step, how to configure ChronoAgent. There are two steps in connecting ChronoSync to ChronoAgent: setup ChronoAgent on the destination Mac and then, using ChronoSync, setup a Connection Profile on the source Mac that communicates directly with ChronoAgent. So answering your question about 's not an integral part of my Lightroom workflow, rather it's an integral part of my system-wide backup routine.ChronoAgent for Mac is a utility that runs on the destination Mac and communicates directly with ChronoSync on the source Mac, giving you full root access, faster synchronizations, and automatic backup options to a destination Mac. That creates backups of all my specified "important data" to 3 separate drives (two of which are connected only for the backup and disconnected immediately after). And I use Chronosync at least once per week (more often if I have a lot of new data such as photos). I also use Crashplan, which is a cloud-backup system, much like TM it runs persistently in the background doing its thing.ģ. As you're using a Mac, I would think that's the first backup procedure you should implement, especially as it's free.Ģ. it runs in the background backing up all changes and new data (so new photos get backed up automatically). I use Time-Machine to do a persistent system-wide backup, i.e. Chronosync is part of that, but we really should focus on a system-wide backup process, not just focus on photography.there's probably plenty of other non-photography data on our systems which should also be backed up.ġ. No matter that it's not in the same folder structure as the main copy, it'll do for me in an emergency until my "proper backups" are run. I also use the "Make Second Copy" during import, which I also recommend to others.that gives you two immediate copies (which should be on different drives) following the import. My plan is to backup to both of these using Chronosync and store one offsite which I would periodically bring up to date with new photos.Ĭan someone tell me where in my workflow I should execute the Chronosync back-up process? Are the photos on the NAS the source for Chronosync? What I do not understand is where in my workflow do I place the Chronosync back-up? Or is it an entirely separate process? I have 2 large hard drives sufficient to hold my entire photo library for the foreseeable future. Discussion in the Forums here has persuaded me that I should be using Chronosync. I was using LR “Save a Second Copy to” on import assuming that I was making a good back up copy. ![]() All of this is working perfectly I’ve never had any problems. I save roughly the last 10 catalogues and I periodically go in and delete those that are aged 20 days or more. The Catalogue is backed up every time I exit LR. I have the LR catalog on my MacBook of course and my primary photo library is on a NAS. I am just learning how to do things correctly so please be patient with me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |