The cbbackupmgr documentation is out of date and confusing to how the service actually functions.

Documents:

• The strategies page mentions that the service is incremental only and a full backup only exists as the concept of the first backup in a repository. However, this is incorrect as we are able to force a full backup, in this case cbbackupmgr only uses this new complete backup to restore files.

Metadata

• Unlike the files the full metadata for a document is downloaded in the process of restoration, this includes incremental changes prior to any full backups in a repository. We should recommend more prominently that customers should switch repositories when they attempt a full backup to reduce the accumulation of metadata. Such as in the backup documentation potentially with the force backup command and restoration. To provide advice to users as they are attempting these features.