Eybackup Process Failing

Issue Description:

When the eybackup process fails across all instances, this document provides solutions that have been tested in both internal environments and customer deployments.

Errors:

1. The AWS Access Key Id you provided does not exist in our records.

2. AWS Authentication Error

   sudo -i eybackup -e postgresql -k 81D7EB1098362CF3 Expected(200) <=> Actual(403 Forbidden)
excon.error.response :body => "\n<code>InvalidAccessKeyId</code>The AWS Access Key Id you provided does not exist in our records."

3. Permission Denied

Permission denied: '/var/lib/eybackup/...'

Solutions

Option 1:

• Run the chef.

• The backup will automatically resume on the next scheduled run. 

Option 2:

Follow these steps to manually resolve the issue:

1. Apply Changes to All Environments

   • Hit the "Apply" button on all involved environments

2. Manually Trigger a Backup

   • Execute the following command to extract the backup command:

     sudo crontab -l | grep eybackup | awk '{$1=$2=$3=$4=$5=""; print substr($0,6)}'

   • Extract the resulting command, and run it

3. Validate Success

   • Check the backup log file to confirm successful execution:

     cat /var/log/eybackup.log