![]() ![]() ![]() CurlEasyPerformWrapper : Could not perform an HTTP request. It also means that any previous backups wereĭeleted and cannot be used to restore. ![]() If that Cloud Files container does notĮxist, you must recreate it. VolumeURI field in the displayed JSON indicates the Cloud Files container thatĬloud Backup is attempting to access. You can check this by getting the agent details via the Cloud Backup API. The Cloud Files container used to store backup data has been deleted. For possible waysĬonserving resources with Cloud Backup. If disk space is so low that any of the preceding issues occur, move as manyĮxtraneous files as possible off of the local system drive. File restore operations might partially or completely fail.Automated log uploads made by using the Cloud Control Panel might not be.Corruption of the vault database might occur.The vault database might be unable to compress or decompress for backup,.Include but are not limited to the following issues: The server itself might be critically affected. If the local system has less than 100 MB of free disk space, the backup and even If you changed the account from PublicNet to ServiceNet, add an snet.If you changed the account from ServiceNet to PublicNet, remove the snet.To work around this issue, edit the bootstrap.json file and make the However, the bootstrap.json file doesn’t reflect If you use the API to change an account from ServiceNet to PublicNet or vice versa, For more information, seeĬloud Backup agent logging basics - Where to store saved logs.įollowing are some of the issues and some possible fixes: Missing Password for encrypted volume If the agent is not connected, attach the driveclient.log file to a Rackspace Support must review the driveclient.log file to determine theĬause. Permissions for the user who configured that agent are incorrect or the DriveClient Many issues might cause a backup status of Error to occur, such as the cloud account Check the logs on the server an indication of the issue. Backup status: FailedĪ status of Failed indicates that a serious problem occurred, and theīackup job did not run. Non-UTF-8 characters, a Path Not Found message displays.įor more information, see Back up databases with Cloud Backup. TheĬurrent version of Cloud Backup supports only UTF-8 characters. The path of the file in the operating system contained Non-UTF-8 characters. Then, you do not have to fully restore the To a flat file (such as an SQL® file) and back up that flat file.ĭoing so allows for a quicker backup and an easier restore.īreak individual databases into different flat files to more easily manipulate Instead, but dump the database’s contents This issue is common with database binary files. The file was exclusively locked (Windows) so that no other process could read It is possible and practical for you to exclude these files from the backupĭefinition, this kind of error goes away. Temporary files, such as PHP session files, and is almost always harmless. The file was deleted before the backup job could make the copy. The most common issues that cause this status are as follows: This status indicates that the backup completed, but the job could not backup Or someone manually stopped or terminated it. The agent could not reach one of the API endpoints, the agent was not running, Next, check the logs to determine why the agent was notĪn agent should never go offline by itself. Verify that the agent is running on the server. Service was likely not running at the time of the scheduled backup, and the This status indicates that the backup job didn’t run. Through Window’s Service Manager, or through the sc command line Windows Was hard-restarted (or the operating system rebooted) during a backup,įor Linux®, a possible fix is to upgrade to the latest version ofĭriveClient and restart the running agent.įor Windows, a possible fix is to restart the DriveClient Windows service On older DriveClient installations, the status might occur if the agent This is the initial job, the subsequent jobs might finish faster. The backup scheduler skips backups it cannot execute.Ĭonsider reducing the frequency of the job or reducing the amount of data. If the frequency of the backup job is set too high (for example, hourly),Īnd a single backup takes too long (longer than an hour), the system skips subsequent jobs. This status indicates that the scheduler skipped this backup job because another backup job wasĪlready queued. This section describes each of the backup statuses, why you might receive each Unable to back up or restore files (Windows® only).Recovery of your encrypted vault password.If you encounter issues when working with Cloud Backup, use the information in Previous section: Rackspace Cloud Backup - Preferences ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |