Skip to main content
All CollectionsKnowledge BaseEnterprise WorkloadsTroubleshooting - Enterprise Workloads
Possible causes for Phoenix backups failing to Linux CloudCache
Possible causes for Phoenix backups failing to Linux CloudCache
Updated this week

Problem Description:

Understanding the flow of Linux Cloudcache backups

  • If the backup Job Log shows the below line, it means the backup is mapped to Linux CloudCache.
    Attempting to connect to cache...
    Communication from Server / Backup Proxy to Linux Cloudcache is configured on port 443.
    u'cacheaddr': u'DRUVA-CC:443'

  • If unable to connect to Linux CloudCache, there is a re-attempt every 30 Seconds. (Total 10 attempts)
    Error Connecting to cache server. Error:[Errno -2] Name or service not known Retrying...[9]
    Error Connecting to cache server. Error:[Errno -2] Name or service not known Retrying...[0]

  • Once the 10 attempts are exhausted and if:

    • Option - Backup to Cloud if unable to backup to Cache is selected in Phoenix CloudCache configuration then backups are uploaded on Cloud
      Setting cache state as retried after retry cycle
      'Could not connect to CloudCache. Backup operation falling back to Cloud.'

    • Option - Backup to Cloud if unable to backup to Cache is not selected in Phoenix CloudCache configuration then backups will fail.
      'Could not connect to CloudCache. Failing the cache-only backup operation.’

Resolution

To ensure the Phoenix Linux CloudCache server is functioning correctly and connected to the Druva Console, follow these steps:

  • Confirm that the Phoenix Linux CloudCache server is in a connected state on the Druva Console.

  • Use the following commands on the Linux CloudCache server to manage or check the service status:

    • /etc/init.d/PhoenixCacheServer start / stop / restart / status

  • Ensure the Phoenix Linux CloudCache is upgraded to the latest version.

  • Test connectivity from the Backup Server/Backup Proxy to the Phoenix CloudCache server using:

    • telnet <cloudcache-name> 443

  • Check for DNS issues by pinging the Phoenix CloudCache server using its IP, short name, and FQDN:

    • ping <cloudcache-fqdn/cloudcache-ip/cloudcache-shortname>

  • If there are connection issues, add the Phoenix Linux CloudCache server entries to the Hosts file of the Backup Server/Backup Proxy in the format:

    • IP FQDN Short_name

  • Verify that the time on the Phoenix Linux CloudCache server is correctly set according to the selected time zone.

  • Ensure the data volume (PhoenixCacheStore) path configured during setup is accessible on the Phoenix CloudCache server.

  • Confirm that port 443 is not being used by any other application on the Phoenix CloudCache server. Use the following commands to verify:

    • netstat -an

    • netstat -an | grep 443

  • Check the PhoenixCloudCache.log file for errors:

    • /var/log/PhoenixCloudCache/PhoenixCloudCache.log

Did this answer your question?