Like others, I backup Catalog, Images, Presets - everything - via SuperDuper in my case.
I have wondered about the anatomy of the Catalog File when backing up: If so much as a single change is made to my main catalog (>200K images, 38GB catalog file size), SuperDuper sees the entire catalog file as having changed, and the backup requires the time one would expect to backup up 37GB of data. Mind you, an edit as modest as changing a single keyword for one image out of 200,000 images, causes the backup software to treat the entire catalog file as newly changed: 37BG of data is seen as having been altered.
Knowing nothing about file architecture, I'll ask if there is an alternative to this sort of file handling, or file structure, such that future versions of the LR Catalog could bee seen differently? Could there ever be a catalog file where a backup process would see only components of that file as having been altered, and therefore offer much quicker backup process?
John Caldwell