Backups may run in transaction, causing CR backlog
Normally, when doing a fullBackup*, the session is initially placed in auto transaction mode and in-transaction while some preliminary structures and shadowed pages are written to the backup file. The session then switches to manual transaction mode and outside of transaction for the rest of the backup while writing out the data pages.
But if there are no shadowed pages (indicated by VSD stat PagesNeedReclaimSize equal to zero), there is a small chance that the session will stay in auto transaction mode and in-transaction during the entire backup, which could cause problems with CR backlogs.
Also note that if you take a backup while the stone is still in restore mode (before executing the commitRestore), then the session will also stay in auto transaction mode and in-transaction during the entire backup
Workaround
1. Don't take a backup while in restore mode.
2. Shutdown the reclaim GcGem before starting the backup. You can restart the reclaim GcGem when you see the VSD stat ProgressCount increasing.
Last updated: 1/17/19