![]() ![]() ![]()
So if a Quick Update task hasn't run successfully in the last two weeks, it will now proceed with a full audit of the source and destination. We were finding some cases where macOS managed to have retained multiple weeks of FSEvent records, and it was taking longer to slog through all of those records than it would take to simply re-enumerate the source and destination. CCC now applies a two-week sanity limit on the Quick Update feature.Likewise, the Dashboard will open CCC if corruption in CCC's task database has been detected. The CCC Dashboard will now proactively open CCC if CCC's helper tool lacks Full Disk Access.The minimum data threshold is now 0 when set to 0, CCC will start an event when changes have been made to a file on the source (and the time threshold is met). The minimum time threshold for "When files are modified on the source" tasks is now 1 minute, but the default is now 5 minutes.Fixed the presentation of a snapshot creation failure in cases where the destination is in the midst of encryption conversion.Users are welcome to run backup tasks manually while a restore task is running, this change only affects automated tasks. ![]() Automated tasks will now be skipped any time a restore task is running to remove any possible conflict between a restore task and a backup task.Fixed an unrelated progress indication issue in the same scenario. Resolved an issue in which a task would appear stalled when converting a disk image to a read-only format.Command+Delete) and via the "Additional Actions" menu in the sidebar. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |