Best Practices: Real-Time Backup

CloudBerry Backup enables you to perform real-time cloud backup for your utmost important documents that must remain intact regardless of emerging circumstances. In this article we wanted to clarify the use-cases for the feature as well as scenarios in which it's advisable to avoid using it.

Introduction

The usual scenario for configuring a backup plan is to simply schedule it to run daily or weekly. While that use-case is perfectly fine for your image-based and large-file backups, you may perhaps need something more frequent for your most important files or the files you share with other people. For instance, let's say you're in the middle of writing a research paper or developing a monumental framework. A few hours in, Microsoft Word, Visual Studio, or Windows itself die on you, or the hard drive starts malfunctioning, and all your work is basically gone. Cloud will not save you here, as all your backup plans are scheduled for daily execution at 9 p.m. Clearly, such scenarios are quite common and must be avoided at all costs. Thankfully, CloudBerry Backup has you covered here with a feature we call real-time backup.

Real-time Backup

Unlike conventional backup plans, which are executed at the designated time, real-time cloud backup is constantly observing and collecting the changes made to the files. Further, every minute CloudBerry Backup performs backups to mirror those changes in the cloud. It is similar to the way Google Drive works in that files in the cloud are always up-to-the-minute with your local files. That way you can be sure that your files are always secure and accessible from the cloud.

As we've mentioned earlier, real-time cloud backup is not your best option when it comes to large files, particularly pst files; conventional backup plans are more suitable for this role. Also, it doesn't work properly with shared folders and NAS storages at the moment, so it's recommended to use the feature only with local folders. Real-time backup utilizes a FileSystemWatcher API, which tracks the changes made to files and importantly has a limited buffer. If there are many changes in a short time, the buffer can overflow. This causes the component to lose track of changes in the directory. Therefore, if you perform a large number of changes to files within a minute, CloudBerry Backup might not pick them up until after you restart the computer or CloudBerry Backup services. Finally, purging occurs hourly, and the email notifications—daily.

Every 60 seconds the backup procedure will commence, uploading to the cloud all the changes made in the last minute. Needless to say, you can close the app window altogether, and the services will perform a real-time backup in the background.

Perhaps you want to dig deeper into the real-time backup. For that, we will refer you to one of our older articles that explains how you can tinker with the app settings to configure backup, purge, and notification intervals and the like.

Real-time Backup Alternatives

Finally, note that using real-time backup is not the only way of expediting backup plan executions. Many users choose to use real-time backup because the regular backup routine sometimes necessitates scanning the entire disk or large folders with millions of files which might take a while. To help fix this issue, do consider using CloudBerry Backup's Fast NTFS scan that significantly reduces the disc scanning time and might serve as a decent alternative for real-time backup.