Skip to main content


 

 

druva_logo.pngDruva
|
Documentation

How can we help you?

Trending articles:

 

Druva Documentation

Possible causes for Phoenix backups failing to Linux CloudCache

  1. Last updated
  2. Save as PDF
Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

 

Title: Possible causes for Phoenix backups failing to Linux CloudCache

 

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

Below are the possible solutions to overcome the Linux CloudCache connectivity issues

  • Phoenix Linux CloudCache server should be in a connected state on the Druva Console.

  • Verify status of Phoenix CloudCache service in Linux Cloudcache server

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

  • Upgrade the Phoenix Linux CloudCache version to the latest.

  • Try telnet from the Backup Server\Backup proxy to the Phoenix CloudCache server using below command

              telnet <cloudcache-name> 443

  • To verify if DNS issues, try to ping using  IP/Short name/FQDN to Phoenix CloudCache server from the Backup Server/Backup proxy using below command

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

  • Add the entries of the Phoenix Linux CloudCache server under the Hosts file of the Backup Server/Backup proxy, if there are connection issues. (Format IP FQDN Short_name)

  • Time should be correctly set on the Phoenix Linux CloudCache server as per the selected Time Zone.

  • The data volume(PhoenixCacheStore) path configured during the Linux Cloudcache configuration must be accessible on the Phoenix Cloudcache server.

  • Port 443 should not be used by any other application on the Phoenix CloudCache server. It can be checked using the below command

              netstat -abno

  • Verify any errors under the PhoenixCloudcache log file from below location:

              /var/log/PhoenixCloudCache/PhoenixCloudCache.log