Skip to main content
Druva Documentation

Phoenix CloudCache FAQs

 

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

► How is the Phoenix CloudCache priced? 
For exact pricing details, get in touch with your account executive. Contact Druva Support.

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

► What difference will deploying Phoenix CloudCache make? 
The following are the major differences that deploying Phoenix CloudCache will make in your environment:
  • Optimized WAN bandwidth consumption: With Phoenix CloudCache, you do not have to worry about the availability of the WAN bandwidth at your organization for the scheduled server backups. Administrators can schedule synchronization operations from the Phoenix CloudCache to the Phoenix Cloud during off-peak hours, thus ensuring an optimized utilization of the WAN bandwidth.
  • Reduced backup time: Phoenix agents can back up large volumes of data to the Phoenix CloudCache through LAN ensuring a significant reduction in the backup time while backing up servers and virtual machines.
  • Faster restores: You can restore the data residing on the Phoenix CloudCache during the predefined retention period. It also reduces the demand for the WAN bandwidth.

► How long does the Phoenix CloudCache hold my data?
You can configure the number of days for which you want the Phoenix 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 Phoenix CloudCache

► What is the sizing and setup (number of CloudCache) considerations for the Phoenix CloudCache?
To ensure that the Phoenix CloudCache can handle multiple backup and restore requests, you must set an optimum size for the Phoenix CloudCache. You must also plan for the number of the Phoenix CloudCache instances that you require at your remote office locations.
The size of Phoenix CloudCache and the number of Phoenix CloudCache installations that you require depend on the factors, such as:
  • The number of resources that you want to back up
  • The type of data backed up
  • The size of the backup data including the incremental backups

    For more information about deployment considerations, contact Druva Support

► Will the backup continues to the cloud if the CloudCache storage is full and the Backup to Cloud if unable to backup to Cache option is enabled? 
 Yes, the data backup will continue to the cloud.

► Where can I check the CloudCache usage on the Phoenix Management Console? 
 The Cache Used/Allocated field on the CloudCache details page provides the consumed CloudCache storage details.

► Will Phoenix notify about the CloudCache storage when the storage is consumed beyond a certain threshold?
When the CloudCache storage is consumed, Phoenix notifies you with the following alerts:
  • CloudCache Storage Space Low (Usage: >80%)
  • CloudCache Storage Space Full

► What happens if the CloudCache is configured but it is not available when a server triggers backup? 
While configuring CloudCache or editing the CloudCache details, if the Backup to Cloud if unable to backup to Cache option is selected, the Phoenix agent backs up the data directly to the Phoenix Cloud. Otherwise, the backup operation fails. 

► Does the CloudCache disk space become free when the data is synchronized from the CloudCache to the Phoenix Cloud? 
No. The disk space becomes free according to the retention period configured for the mapped backup set. 
 
► What happens if the CloudCache is configured but it is not available when the server triggers the restore operation?
Consider the following scenarios:
  • CloudCache has completed the synchronization of the data with the Phoenix Cloud:
    • In this case, the data is restored from the Phoenix Cloud.
  • CloudCache has not completed the synchronization of the data with the Phoenix Cloud:
    • If the CloudCache is completely down, the restore operation fails.
    • If the CloudCache and the Phoenix Cloud are still connected, then the Phoenix Cloud fetches data from the CloudCache and the data is restored directly from the Phoenix Cloud.

► My CloudCache decommission is taking a long time, what can I do to make it run quicker? 

The following are the stages of decommissioning the CloudCache:

  1. Backup sets are unmapped from the Phoenix CloudCache.
  2. Backups and restores to and from the Phoenix CloudCache stop.
  3. Phoenix CloudCache waits for the next scheduled synchronization operation to flush the unsync data from the Phoenix CloudCache to the Phoenix Cloud.
  4. Phoenix removes the data blocks from CloudCache Store.
  5.  Phoenix removes the cache entries from the Phoenix Management Console and database.
  • In order to expedite the process, configure the Phoenix CloudCache synchronization schedule for 24 hours for 7 days and ensure that you select the Max Available Bandwidth in your environment.
    Note: The bandwidth is defined in megabits per second.
 

► What extra firewall configuration/ports do I need to open for the CloudCache? 
Phoenix CloudCache uses the default 443 port and TLS protocol for all communications. For more information, see Ports and Communication Protocols for Phoenix CloudCache.

► How can I ensure that all my hot data is present on the CloudCache so that during restore all data is readily available on 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.

► Does my backup/restore tasks fail if the CloudCache is decommissioned or it is in decommissioning mode? 
When the decommission operation is initialized, the Phoenix CloudCache first removes the mapping of all the backup sets from the CloudCache and then synchronizes all data to the Phoenix Cloud. After that, the backup and restore tasks are performed directly from the Phoenix Cloud.

► What happens to the backup job if the connection to the CloudCache is interrupted at the time of the job? 
If the connection to CloudCache is interrupted at the time of a backup, the Phoenix agent backs up data directly to the Phoenix Cloud. Since the deduplication data is available on the Phoenix Cloud, Phoenix agent requires a connection to Phoenix Cloud and CloudCache to restore data. Ensure that the Phoenix agent can connect to Phoenix Cloud and CloudCache. 
  • Was this article helpful?