Previously we were avoiding running the script in this case (despite running that script in other error conditions), but we've since decided that there isn't any good reason for not running it. CCC will now run the postflight shell script (if specified on a task) in cases where the source or destination dropped offline, thus causing the task to abort.Fixed the behavior of the Task Filter window when working with a Remote Macintosh source.Made some adjustments to the pruning of CCC's Task History database so it consumes less space.Network change events are now listed in the Activity tab of the CCC Dashboard application if any CCC tasks require network resources.Errors that occur due to a disagreement between the source and (typically NAS) destination filesystems on how composed characters should be stored are now presented with more specific advice and a link to a new Kbase article.This should offer an easy indication to the end user of "When was the last CCC backup made to this volume?". when the user last made changes to that root folder on the source (which is typically long ago). The modification date of the destination root folder has more value as an indication of when CCC last made changes to the destination vs. At the end of a task event, CCC now sets the destination root modification date to "now", rather than preserving the source root folder modification date. what specific file or folder is involved in the stall).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |