Skip to main content
Druva Documentation

Phoenix CloudCache FAQs

Phoenix Editions: File:/cross.png Business File:/cross.png Enterprise File:/tick.png Elite

 

► 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? 
The Phoenix CloudCache license is based on the storage space that you require for the data that you want to back up. For more information about licensing, contact your account executive or Druva Support.

► What difference will deploying Phoenix CloudCache make? 
You will see two major differences with the Phoenix CloudCache. The backup window will reduce significantly because the Phoenix agents can back up large volumes of data to the Phoenix CloudCache via your network. Secondly, the data saved to the Phoenix CloudCache can be restored at any time during the pre-defined retention period. Such local restores are faster, and they reduce the demand for the WAN bandwidth. In addition, data can be sent to the cloud during the off-peak hours, which is ideal for sites with the limited available 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 a good size for my Phoenix CloudCache?
The size of the Phoenix CloudCache that you require depends on 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, contact Druva Support

► How many instances of Phoenix CloudCache do I need?
The number of the Phoenix CloudCache instances that you require depends on the factors such as:
  • The number of resources that you want to back up
  • The type of data backed up
  • The size of backup data including the incremental backups

For more information, 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? 
When a decommission operation is initialized, the Phoenix CloudCache removes the mapping of all the backup sets and then synchronizes all data to the Phoenix Cloud. This entire process can take more time based on the available network bandwidth. Therefore, configure the CloudCache synchronization schedule for 24 hours for 7 days. This will ensure that the decommission in not interrupted.

► 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.
  • Was this article helpful?