Logo Mark

Support

Troubleshooting

Here are some common issues other users have faced in the past. Before getting in touch, have a look here to see if your problem is mentioned.


Reading the Logs

The Craft logs will usually include details of any errors. You can see them in the following locations within your site:

  • storage/logs/web.log if you are running backups via the web interface
  • storage/logs/queue.log if you are running backups via the web interface and using the queue
  • storage/logs/cli.log if you are running backups via the command line

These will hopefully give you an indication of the problem.

Connection Errors

If you are seeing errors on the Remote Backup utilities page, it's likely that the connection to your remote provider is broken or misconfigured.

First go to the settings section and make sure that "Test Connection" is working. If not, it's likely an issue with your configuration variables for your provider.

Filenames

Another reason for seeing the above error, is an issue with the backup filenames.

Remote Backup encodes information within the filenames of the backups you create. If you look in your remote destination, you'll see that backup files look like:

craft-develop__dev__231021_131208__tmepvdiqat__v4.5.5.sql

The format is:

[site name]__[environment]__[date]_[time]__[random suffix]__[version],sql

Very occastionally, an unusual site name or environment may break the regex that the plugin uses to decode this information, causing the plugin to crash.

If this is happening, get in touch and I'll try to help diagnose and update the underlying regex to accomodate the filename.

Large Backups

If you have a lot of volume files or a large database to back up, there are a number of potential issues you may face.

Storage Issues

If you are backing up large volume folders you might run into issues with server storage space. Something like:

Error (time: 77.245s): stream_copy_to_stream(): write of 8192 bytes failed with errno=28 No space left on device

This is because we have to create a copy of all data first, then zip it up before sending it to the remote location.

For example if you have 5Gb of files in your volumes, you will need an extra 10Gb of space on the server:

  • 5Gb to hold a copy of the volume data
  • Another 5Gb for the zip file created from the above data

These files will be deleted after a successful backup.

Queue Issues

If you are backing up via the web interface and using the queue, you might notice backup operations failing (sometimes silently)

TTR (Time to Reserve)

TTR ("Time To Reserve") is the max time (in seconds) that a queue operation can take. This is a Craft setting and not a PHP setting, so it's not affected by the max_execution time.

Remote Backup offers an easy way to adjust this value via the settings page, so if you are noticing issues backing-up then increase this value from the default 300 (5 minutes).

Data Costs

If you have large volumes make sure you are aware of any data caps on inbound or outbound data. For example if you are hosting 5Gb of files on S3 and then backing them up to a different bucket you will have read 5Gb of files and sent another 5Gb when performing a single backup.


🪲 Search Github Issues

Also ave a quick search through the Github Issues page to see if somebody else has faced your issue in the past. If so, feel free to drop a comment there too to get help.

Previous
Usage