Facebook
TwitterHi,
Yesterday we scheduled backups trough Plesk 12 to store, trough FTP, on our cloudserver. This morning we got allerted that Plesk was unavailable and gave the error (simular):
1030 Got error 28 from storage engine
So, we checked the space usages on the mounted /tmp drives and this was full. Full with a partial backup (repo_transport_tmp files). The /tmp is mounted on the default installation at 500MB. Is this sufficient for your backup tool to handle? Or should it be increased? And if so, to what? I can't imagine that we have to increase the /tmp mount to the max filesize the backup can be? That should be weird?
After deleted the backup from the /tmp, Plesk was able to start again.
Yesterday we scheduled backups trough Plesk 12 to store, trough FTP, on our cloudserver. This morning we got allerted that Plesk was unavailable and gave the error (simular):
1030 Got error 28 from storage engine
So, we checked the space usages on the mounted /tmp drives and this was full. Full with a partial backup (repo_transport_tmp files). The /tmp is mounted on the default installation at 500MB. Is this sufficient for your backup tool to handle? Or should it be increased? And if so, to what? I can't imagine that we have to increase the /tmp mount to the max filesize the backup can be? That should be weird?
After deleted the backup from the /tmp, Plesk was able to start again.
