I got a 500 error (effectively a request timeout) after switching from database storage to file system storage for pictures. The site seems to be working, but images are broken. Did it fail to write all of the images to the file system or is it a background thread that just needs to be left alone to finish.
I'm half wondering if I should restore a DB backup.
Got a 500 error switching back to DB as well, but at least the images came back. Is there another way? DB-stored images is causing performance issues on Azure.
So, I did lose some images. I had to go to a backup and update ones that were missing. I can tell you that I have about 17K images stored in the database and whatever happened to have the site timeout and give a 500 error while it was switching from DB to file system for the image storage does not work well enough to support this many images.
For now, I must keep them in the DB, but really want to move them to the file system to help with Azure DB performance and potentially to be able to use a CDN instead.
If there are any options out there for addressing this (even if it's a matter of extracting the images to the file system myself and uploading them), it'd be greatly appreciated.