I also want to add a script here which deletes old Lightroom backup files from the source (original) drive (not the backup drive). Skip the preview and other files which aren't essentialĭocument #2: back up all the Lightroom backup catalog files (ZIP compressed, in a dated folder). I'm actually working on a two-part backup strategy for my Lightroom catalogs using a Chronosync container:ĭocument #1: back up all current Lightroom catalogs (if there's no "lrcat.lock" file alongside them). In other words: if Chronosync sees a file with the ending "lrcat.lock" it will skip the backup. Oh, I asked around and got confirmed that only a file with the "lrcat.lock" extension is always used to show that a Lightroom catalog is in use, so I can skip "lrcat-journal" for this rule. I could of course always right-click on said files in the Chronosync "Analyze" section, telling them to be ignored, but I figure a general filter would be more practical in case I create a new Lightroom catalog or move things around. For instance, I never want to back up the Lightroom preview files ( Previews.lrdata and Smart previews.lrdata extensions). If they're not met Chronosync will go ahead with the backupĪctually I think I might have messed up here as my "Ignore files." criteria isn't about determining to back up or not, but I want to have the entire backup document ignore specific files. The use the Data container and create a backup that includes both your regular, which will exclude the LR library at all times and the 2nd backup with the.
It would ignore the files IF both files exist. I believe this mean that Chronosync will NOT do a backup if the conditions here are met. in the rules for the ingored files, put the lock file and the LR library file and use an AND condition. " Ignore files if these conditions are met:" If the conditions aren't met I assume Chronosync won't backup, but stop. I believe this means that Chronosync will perform a backup as long as those conditions are met. " Scan files if these conditions are met:" , ls -l, to see the permissions on the directory. It asks for my password, I provide it and the Results: chmod: cannot access 'cfdnahcbam.bam': Permission denied. rsyncuser ALL NOPASSWD:/usr/bin/rsync Then, we use rsync-path to make rsync works with the sudo. So that, the user can execute the rsync command without password. Second try: sudo chmod 775 cfdnahcbam.bam. This can create problems and lead to error rysnc permission denied root in Rsync In such cases, our Support Engineers create a rsyncuser and add it to the /etc/sudoers file. Is my following assumptions correct in Chronosync: Result: chmod: changing permissions of 'cfdnahcbam.bam': Permission denied. Yes, I think it does, but I think I need to understand the concepts a little better first.
0 kommentar(er)
