Troubleshoot: ZPE Cloud scheduled Backup failures

Troubleshoot: ZPE Cloud scheduled Backup failures

  1. Verify the affected system's time is set correctly
    1. If there is a significant time difference between ZPE Cloud and the target system, the backup will not upload properly causing the job to fail.
    2. Check the system's time from the GUI:
      1. System :: Date and Time :: Local Settings
    3. Check the system's time from the CLI:
      1. show /settings/date_and_time/
  2. Ensure that all ZPE Cloud related IPs are allowed through any firewalls involved:
    1. Article with details:  Company's Firewall configuration: what resources need to be opened in Firewall for the Nodegrid appliances to connect to ZPE Cloud?
  3. Test if a local backup can be created in the tmp folder:
    1. Log into the affected system via SSH or Console
    2. Access the root shell: shell sudo su -
    3. Run manual backup:  save_settings --local /tmp/backup.tar.gz
      1. Note any errors, expected result is: Configuration saved.
    4. Check if backup was created: ls -al /tmp/backup.tar.gz
      1. Expected result example: -rwx------ 1 daemon daemon 2116555 Oct 31 18:58 /tmp/backup.tar.gz
  4. Check if the ZPE Cloud agent process is running:
    1. Log into the affected system via SSH or Console
    2. Access the root shell: shell sudo su -
    3. See if the process is running: ps -ef | grep zpe_cloud_agent
      1. Expected result example: root     19027     1  0 18:10 ?        00:00:00 /usr/bin/zpe_cloud_agent
  5. Check for errors in the ZPE Cloud logs around time of scheduled backup:
    1. Log into the affected system via SSH or Console
    2. Access the root shell: shell sudo su -
    3. Review the log: less /var/zpe-cloud/logs/zpe_cloud.log