Rackspace Cloud Backup
Your backup was missed. Please check your backup agent is running.
Required Software:
- KeePass
- PuTTY
Before you start this guide, make sure that you have access to the KeePass database file as it contains the login credentials for Rackspace and the .ppk files to do remote server access via SSH. Follow this guide on how to set this up.
Check Cloud Backup system status
When the cloud backup agent is not running on your server, you'll get an email from Rackspace monitoring indicating which backup script failed. Use the following steps to check the status.
- Login to the Cloud Control Panel.
- On the top left navigation bar, click Select Product > Rackspace Cloud.
- Select Backups > Systems.
- From the list of Cloud Backup systems, click on the backup server name.
- To the right of the system name, review the status of the backup agent. The backup agent status is either connected or disconnected.
- Wait 10 seconds to ensure that the status is accurate as it can change after a few seconds.
- After 10 seconds, perform the following actions:
- connected - try running the backup again. If it fails, contact Rackspace Support.
- disconnected - restart the DriveClient service as shown in the next section.
Restart DriveClient service
Use the follow steps to restart the DriveClient service:
- Login to the server with SSH.
- Execute the command
service driveclient restart
- Return to the Cloud Backup System Details Status in the Cloud Control Panel to check that the agent status is now connected.
- Follow steps below based on the status:
- connected - try to run the backup again, contact Rackspace support if it fails.
- disconnected - download the server log located in /var/log/driveclient.log
- Attach the downloaded file to a rackspace support ticket to expedite the issue response.
Issues encountered in Safety Training server
When the service driveclient restart
command executed, it returned a permission access error. The problem was that DriveClient is trying to access cacert.pem file in /root/.driveclient/ directory which does not exist.
Not sure why DriveClient is using /root/.driveclient/ directory for cacert.pem file since it exists in /etc/driveclient/ directory. To resolve this issue, create the .driveclient directory in /root/ and create a symbolic link of cacert.pem file in it.
- Create .driveclient directory by using this command
mkdir /root/.driveclient
- Change the permission to the directory
sudo chmod u=r, o=r /root/.driveclient
- Create symbolic link
sudo ln -s /etc/driveclient/cacert.pem /root/.driveclient/cacert.pem
- Start the DriveClient with
sudo service driveclient start