Details
-
Bug
-
Resolution: Fixed
-
Critical
-
3.0
-
Security Level: Public
-
None
-
OS X Mavericks, 10.9.5, CBServer Version: 3.0.0 Enterprise Edition (build-1209-rel)
-
Untriaged
-
MacOSX 64-bit
-
Unknown
Description
When backing up a large DB from CB server, cbbackup exhausts the resources of the backing up machine. The DB in question has 124 million documents and is 218 GB in size. The machine doing the backing up is only running cbbackup and has 16 GB of RAM and is writing to a large attached drive with roughly three times the available free space as the source DB. I have tried the backup twice and the first time the OS protected itself by pausing the backup process. The second time it just locked up. In both cases, the database had saved only 32.6% and 35.3%, respectively. On the second attempt, I was hoping that the backup would pick up where it left off. Instead it appears to have ignored the versions of the already saved documents and written them again … and crashed at about the same point. The CBServer machine was unaffected by the lockup but I've restarted it to be safe.
It would be quite weird to require that a machine doing the backups be as powerful as the CBServer cluster.
I would very much like to back this data up. It takes days to insert this much data into CBServer. With server 2.5.1, it takes roughly 8 hours to backup and restore this data. Then the view calculations kick in. In other words, this is a critical feature.