CloudCache is an optional component that stores backups locally up to 30 days to enable quick local restores. The CloudCache then periodically synchronizes this data to the Druva Cloud. Because the Hybrid Workloads agents can communicate with the CloudCache on a local network, the speed of the backups and restores increases significantly. Moreover, administrators can schedule synchronization operations from the CloudCache to the Druva Cloud during the off-peak hours, thus ensuring an optimized utilization of the WAN bandwidth.

The following are the major differences that deploying CloudCache will make in your environment:

CloudCache does not have any associated cost component. For licensing information, contact Support.

CloudCache does not have any associated cost component. For licensing information, contact Support.

CloudCache feature is available free of cost as a part of the Enterprise and Elite Druva license. For more information about the licensing details, refer to Druva Plans and Pricing.
For more information about licensing, contact your account executive or Support.

You can configure the number of days for which you want the CloudCache to hold your data. At the most, you can set a retention period of 30 days for your data. For more information, see Configure CloudCache.

CloudCache supports File Servers, NAS, SQL, Oracle Direct to Cloud (DTC), Hyper-V, Nutanix AHV, and VMware workloads.
File Servers and NAS devices that contain a large number of small files may affect the CloudCache performance because of intensive I/O operations. For other workloads, the backup and restore operations contain extensive block size data that does not impact performance.

CloudCache R3 is built on a new architecture that supports the File Servers, NAS, SQL, Oracle Direct to Cloud (DTC), Hyper-V, VMware, and Nutanix AHV workloads on Linux only. CloudCache, labeled R1, continues to support other workloads, that is, File Servers, NAS, SQL, Oracle Direct to Cloud (DTC), Hyper-V, and VMware on Linux. Instant Restore of VMware virtual machines is not supported on CloudCache R3.

CloudCache R1 for Linux is an OVA package and cannot be installed on Physical servers currently. For CloudCache R3, it is recommended to use the Debian package for installing on Physical servers running Ubuntu 22.04.

CloudCache R1 for Linux has 1 Disk with LVM volume of 1TB, by default. The CloudCache R3 OVA and QCOW2 packages for Linux have two disks for OS and Data with size 60GB and 1TB, respectively, by default.

CloudCache R1 OVA package comes with Ubuntu version 20.0.4. CloudCache R3 OVA package comes with Ubuntu version 22.04.

To ensure that the CloudCache can handle multiple backup and restore requests, you must set an optimum size for the CloudCache. You must also plan for the number of the CloudCache instances that you require at your remote office locations.
The size of CloudCache and the number of CloudCache installations that you require depend on the factors, such as:

The Cache Used/Allocated field on the CloudCache details page provides the consumed CloudCache storage details.

CloudCache R1 for Linux is offered as an OVA for vCenter. CloudCache R3 for Linux is offered as OVA, QCOW2, and .deb packages.

When the CloudCache storage is consumed, Druva notifies you with the following alerts:

While configuring CloudCache or editing the CloudCache details, if the Backup to Cloud if unable to backup to Cache option is selected, the Hybrid Workloads agent backs up the data directly to the Druva Cloud. Otherwise, the backup operation fails.

No. The disk space becomes free according to the retention period configured for the mapped backup set.

Yes, customers can increase the compute & disk size. CloudCache R1 and R3 for Linux is an OVA package that offers LVM partition the size of which can be increased directly.

Consider the following scenarios:

No, this functionality is not yet supported by Druva.

Yes, the data backup will continue to the cloud.

The following are the stages of decommissioning the CloudCache:

While configuring CloudCache or editing the CloudCache details, we recommend that you do not select the Backup to Cloud if unable to backup to Cache option.

When the decommission operation is initialized, the CloudCache first removes the mapping of all the backup sets from the CloudCache and then synchronizes all data to the Druva Cloud. After that, the backup and restore tasks are performed directly from the Druva Cloud.

If the connection to CloudCache is interrupted at the time of a backup, the Hybrid Workloads agent backs up data directly to the Druva Cloud. Since the deduplication data is available on the Druva Cloud, Hybrid Workloads agent requires a connection to Druva Cloud and CloudCache to restore data. Ensure that the Hybrid Workloads agent can connect to Druva Cloud and CloudCache.

During a CloudCache disconnection, if a few data blocks remain in CloudCache and are not fully transferred/flushed to the Cloud, any attempts to restore a warm snapshot will fail.

If you increase the number of days of retention, say from 5 to 10, we will start retaining the data for days 6-10 incrementally and will subsequently have data for all required 10 days from day 11 onward. However, if this count is reduced from 5 to 3, the excess 2 recovery points will be compacted as per the schedule.

The selected recovery point needed scanning for UDA Encryption check, which is why the unscheduled upload job was triggered. If an unscheduled upload is triggered, the scheduled upload job will not be initiated till the unscheduled upload completes.

If you request restore of data for the days for which data is already in cache, it will be quick and seamlessly restored. In case data that has been flushed from the cache to the cloud is required to be restored, the data which is present in the cache will be restored faster and the restore of data from the cloud will take slightly longer.