Major Description
Problem
in 6.5.0 cbbackupmgr makes use of DCP compression however there are cases where it will receive a document that is not compress, i.e when it comes directly from memory. For high resident ratio this will be the case.
Suggestion
There is a DCP flag to force the server to compress all documents before sending. This will use more CPU on the cluster but will save network band and CPU resources on the client. It would be good to expose this as an option to the end user. The --value-compression option could have an extra option called "force-server-compressed"