Our C:\ProgramData\Online Backup\Data folder is at 80GB.
78GB of this is within one folder C:\ProgramData\Online Backup\data\conn-191cba92-1dee-408a-ae2b-4f88a03fb27f\bunch-68cdc316-a587-42ed-aa57-f020b8e9df99\g0
The other subfolders have nowhere this amount. We only have 4 backup jobs running.
Is this normal? Have we configured something wrong? What is recommended practice? How can I relate the folder name to the backup job?
My second main question is do I need to back up this cache? If we lost access to the cache, would we still be able to restore the data from the cloud?
Hi,
You are correct, this is a local cache used for backup deduplication. Its size depends on the amount of data in the backup. The cache affects performance, but its unexpected loss is not critical, so it does not need to be backed up. In case it is lost, the data will be rebuilt from the backup, but this will take time.
We’d like to investigate this further. Unexpected database/cache growth can be related to a combination of factors, so we’ll need to review your specific case in more detail.
Could you please open a support ticket and provide the following information:
Destination storage type/provider
Backup type
Approximate backup size (in TB)
Approximate number of files
It would also be very helpful if you could include the backup logs with the ticket so we can analyze the cache and deduplication behavior more thoroughly.
Once we have this information, we’ll be able to investigate the issue further and provide more specific recommendations.