No matter how we slice it, cbbackup is pretty slow. We have a support contract and have spent many a precious hour with Enterprise Support trying to make it faster. We know it’s not directly hardware related since XDCR to the exact same machine we’re using as the cbbackup destination is very fast. Although it’s possible that cbbackup and XDCR use the underlying storage in different ways.
For example, the backup target is able to flush XDCR mutations to disk at 5K-10K docs/sec. But a cbbackup job can hardly achieve even a 10th of that performance, even using the “cbbackupwrapper” functionality (per recommended settings for support).
So I’d like to move on from cbbackup if possible. Our core requirement is to take standard grain backups (daily/weekly/monthly) to recover from an undetected data issue (e.g. a process that is incorrectly updating data). Does anyone have suggestions on this? Is anyone successfully using cbbackup for point in time backups and achieving decent performance?