SaaS
I receive the following error when attempting a workspace export:
“The export_applications job took too long and was timed out.”
I’ve tried this multiple times and keep getting same result.
My workspace is 47GB including data.
There are 11 tables, the largest of which contains 11,000 rows.
It is important that data is preserved during export.
Hi @quassify,
47GB is a lot of data. Could you try exporting one application at a time to see if that works?
Data will be preserved, and you’ll be able to re-create the workspace as if all the applications were exported in the same archive.
Thank you for the reply. I have no applications. It’s just one database containing 11 tables.
The data is mostly image files. I’m not aware of any option to compress within Baserow. Manually replacing each image file with a compressed version is not feasible because of the huge volume of images. Is there any way to extend the export timer so it doesn’t timeout so quickly? Or is there some other export option I’m not considering?
Hey @quassify, I’m sorry to hear that you’re running into problems exporting your workspace. The export is prepared in zip format, so it should automatically already be compressed. It looks like the export job is indeed timing out. Do you happen to remember at which percentage it times out?
I tried removing lots of media. The database is now 16GB yet export still consistently fails
It times out at 90%.
Hey @quassify, we have just increase the timeout of the export job from 60 minutes to 90 minutes. That should give the system enough time to make the full export if it stopped at 90%. Would you mind trying again?
Thank you. The exports still stick at 90% and then fail shortly after 90 minutes with the following error:
“Action not completed. Something went wrong during the job execution.”
I’ve just checked the logs, and it seems that your job running into a `Timeout error`. We can’t really increase the time of the jobs any further. It’s a bit of a tricky situation because there are so many individual files to be exported.
Would it be an option for you to use the “Export files“ feature? If you click on the three dots next to a table or view, you can choose the “Export files“ feature. This will generate a zip file with just the files. You can create a view only shows row 1 through 1000, for example, export the files to zip with the “Group files by row id“ enabled, and save the files on your computer. Repeat with the row 1001 through 2000, etc until you’ve downloaded all your files.
I’m not sure what the reason is why you’re looking to export, but if you just need the files, then that could help.
I simply wish to migrate to self-hosted, preserving all data including files.
Considering the volume of files involved, it is not practical to transfer them manually to self hosted.
It seems that the export tool can’t handle the amount of files because it keeps timing out. Because you’re moving to self-hosted, I suggest doing a direct database backup instead of using the export function. This way, you won’t have to worry about running out of time because you’ll keep all your data, including attachments. You could also see if you can back up files through an API or direct access, and then re-link them after the move. If not, you could also try exporting in smaller groups.
Thank you Susan. Can you please advise on how to do a direct database backup? I’ve been unable to find any guides for this procedure.