Cloud Backup: How the Backup Database File Effects Backups
Based on my interactions with Jungle Disk customers on a daily basis, I am under the assumption that many customers are not aware of the Backup Database and what it entails. Essentially, the Backup Database File is the roadmap to your backup. During the backup, the data is uploaded and compressed into chunks and transferred to your designated cloud storage. Then, we store information related to this in the database. Inside the database, it will have the backup jobs, backups, blocks, chunks, directories, file blocks, retention, cleanups, and more related to the backup. These are organized in tables, table fields and field data. Without this file, we would be unable to perform a restore or interact in a meaningful way with the data.
For customers, you will see a larger file (relative to the size of the backup) uploading on the final stage of the backup. This may take some time and is why we recommend that you keep your backups below 500GB/100,000 files.
Here are some of the more common errors we see in relationship to the database:
xDatabaseCorrupt - means that Jungle Disk failed to get directory list. The solution would be to manually delete cache using the guide here.
xDatabaseFailure - Under here you can see some additional errors. Database is malformed, Disk I/O Error, Database Locked on Startup or Sync. Please refer to the guide here for additional help.
This will hopefully shed some light on the behind the scenes aspect of what is going on during your backups. If you need additional help with these errors, feel free to reach out to support.