CCC's Disk Center shows general volume information for each locally-attached volume mounted on your Mac, a list of snapshots and snapshot-related settings for APFS volumes, as well as read and write rate and error statistics for those volumes. Select a volume in CCC's sidebar (click "Show Sidebar" in the toolbar if it is hidden) to view that volume in the Disk Center. CCC also shows any backup tasks that are associated with the selected volume.
The Disk Center table in the sidebar displays a list of locally-attached, mounted volumes. Click on one of these volumes to display information such as the volume name, filesystem, capacity, disk usage, and a list of snapshots on the volume, as applicable.
If you would like to enable FileVault on an APFS-formatted volume, simply flip the FileVault switch to the On position. CCC will prompt for a passphrase, then will enable encryption on that volume.
If you would like to disable FileVault on a volume that is already encrypted, simply flip the FileVault switch to the Off position. CCC will prompt for a passphrase, then will disable encryption on that volume.
Full disk encryption is limited to APFS volumes, and is not available for volumes that are (or were) members of a macOS startup volume group. If you would like to enable or disable FileVault on a bootable volume, boot your Mac from that volume and change the FileVault state in System Settings.
Both encryption and decryption are conversion processes. These processes can take several hours, but will proceed in the background without your attention. CCC will indicate progress if encryption or decryption conversion is underway. Note that APFS places a moratorium on snapshot-related activity while any conversion activity is underway. If you run your backup tasks while a volume is encrypting or decrypting, errors may be reported related to creating or removing snapshots. These are harmless, and will resolve themselves when the conversion is complete.
A chart at the bottom of the window shows current read and write activity for the selected volume. Disk activity is collected by macOS at the hardware interface, so data for multiple volumes residing on the same disk will be identical.
CCC will report read and write error statistics when they are present:
Read and write errors indicate the number of read or write attempts that have failed since the disk was attached to your Mac (since startup for internal disks). Read errors often occur when files that are residing on damaged sectors cannot be automatically moved by the disk's firmware. Such files would also be unreadable by CCC, and CCC will report the failure to read these files at the end of the backup task. Read errors are not necessarily indicative of a failing hard drive. This number will rise steadily if multiple attempts are made to read the same corrupted file, for example. Read errors are, however, generally associated with physical hardware problems that will reduce the performance of a backup task. In some cases, macOS does not handle read failures well, and attempts to access the disk can lead to system-wide stalls.
Write errors are more serious. If you have a disk that is reporting write failures, there is either a hardware configuration problem with the device (e.g. bad cable, port, enclosure or USB hub), or the disk is failing.
If you select an APFS-formatted volume, CCC will display a list of volume snapshots and snapshot retention policy settings for that volume. Learn more information about Snapshot Management here.
Disk Utility and [other third-party utility] doesn't report any problems with this disk, why does CCC?
Read and write errors statistics are stored by the lower-level storage drivers, they are not specific to a volume. Usually when a read error occurs, the hard drive firmware attempts to move data on the affected sector to another sector of the disk, then spare out the damaged sector. When that is successful, it's possible for the storage driver statistics to be stale. These statistics will be reset when the affected disk is physically detached from your Mac, or upon reboot.