Avoid cache overflow in Atempo LiveBackup

Question

When attempting the initial backup of a new client, Atempo LiveBackup seems to require a very large cache. For instance, a 20 GB cache is not enough to back up a computer that has 100 GB of data. It appears that LiveBackup is adding new files to the cache at a faster rate than it can send them to the server. When the cache fills up, the backup fails.

Aside from removing most data from the computer and then add them back gradually after the initial backup, is there a good workaround? Is it possible to make LiveBackup slow down its scan so as to not fill the cache? Or is it possible to place the cache on an external drive?

Answer 1

When the cache fills up, the scan is paused. When it clears enough data, it'll resume. The question is, doe you really need it to record every change during the time its filled and when it resumes? The concept is that once its done, it'll keep everything up-to-date and backed up. The time during the initial scan should not be counted as "live". The other question is, why is it taking so long to push the data to server? With 100BaseT ethernet we took days to fully offload a typical client, roughly 100GB. Now that we have Gigabit it only takes about a day. Also, the server specs seem to matter quite a bit as well. We have a 4core 4GB server running in a virtual machine with 8GB of memory with RAIDed drives.