Error: rename failed | tmp/encrypted_uploads.zip -> tmp/uploads.zip.crypt

Hi,

I looked at the logs and it seems that the archiving process was timing out due to your large ‘uploads’ size. I noticed backup was finally successful after you increased your max_execution_time. I checked our cloud storage and your encrypted files are waiting to be restore on the new instance. Please make sure you have enough resources and proper max_execution_time as this is definitely a restore on the larger size. Thanks for your patience and please let us know if you have any additional issues.

Thank you for looking inside! Sad enough, before I saw your answer I started restore process, and it just hanged at following.
> Latest Progress:
60%
Extracting file: “db.zip.crypt”

Now it looks like I managed to extend max_exec_tim, but *I can’t find how to restart *restore**. (= Server reboot doesn’t help at all.

A simple plugin Disable/Enable will clear all temp files and will allow you to start over. We should probably put that in the Restore notes.

It helped to restart the process, but with high execution limit time results are still the same: 60%, *extracting…*

Should I send you logs, or you see it in your server? I have no idea what to do with this issue. =(

• This reply was modified 4 years, 4 months ago by Anonymous User 15879810.

I think your server may be running out of memory. For a 3GB archive to process you need a server with good resources. I’ll close the issue here and follow up via email for more details.