tag:blogger.com,1999:blog-2458333828604973286.post-2702317573791799682008-02-28T12:15:00.008-05:002008-02-28T13:03:36.356-05:00Live Site Issue: File Names (Resolved)We are working to resolve an issue with <span class="blsp-spelling-error" id="SPELLING_ERROR_0">downloads</span> currently where the user is prompted to download an incorrect file. Our team has found the issue and is working to resolve as quickly as possible.<br /><br />Regards,<br /><br />Shannon<br />------------------------------------<br />UPDATE 12:38 PM EST - Issue Resolved<br /><br />The issue with the file names being the same has now been resolved. It was actually a bigger issue than the simple file names. A new script running on the server that we moved from the development environment to the live product server had a seemingly small bug in it that prevent it from binding the change to a single user's <span class="blsp-spelling-corrected" id="SPELLING_ERROR_0">account</span> and caused a site wide update instead. The only recourse was to remove the offending script <span class="blsp-spelling-corrected" id="SPELLING_ERROR_1">until</span> it could be looked at closely and to restore the data from a backup.<br /><br />This is where things got a little messy. Our system backs up data regularly in case something like this comes up. However, the issue arose when some of <span class="blsp-spelling-corrected" id="SPELLING_ERROR_2">the</span> backups still had the offending incorrect data in them. Luckily, one of the backups from earlier today 6:00 AM EST had <span class="blsp-spelling-corrected" id="SPELLING_ERROR_3">the</span> proper data. In a perfect world, we would be able to restore <span class="blsp-spelling-corrected" id="SPELLING_ERROR_4">the</span> single table and fields that caused the issue, but <span class="blsp-spelling-corrected" id="SPELLING_ERROR_5">unfortunately</span>, that is not the case. Databases are generally monolithic creatures with one aspect of data, like product information, intimately tied to other tables, like user information and order information. The only reliable solution is to restore the entire data set to the last known good value. This means the 6AM data backup. Meaning, there is a current data gap from 6:00AM EST today until 12:00 noon today that is unrecoverable at this time.<br /><br />Ultimately, this is a good thing. I see issues in a potential data loss recover process that will need to be improved and I am putting those at the top of our task list. Changes will include a better testing environment before scripts go out, a better QC check when the script moves to <span class="blsp-spelling-corrected" id="SPELLING_ERROR_6">the</span> live server, and a faster, automated data or site restore option. It took a few hours to restore the data when it should only have taken a few minutes. We didn't want the 6 hour data gap, but in <span class="blsp-spelling-corrected" id="SPELLING_ERROR_7">hindsight</span>, we <span class="blsp-spelling-error" id="SPELLING_ERROR_8">should have</span> just accepted it for the time being. We spent far too long looking at ways around the gap in data to no avail.<br /><br />Finally, the system should be working properly now. If it is not, we will be on it all day. For sellers, the orders placed during <span class="blsp-spelling-corrected" id="SPELLING_ERROR_9">the</span> data gap will not be recovered- this unfortunately, is unavoidable. You can still send <span class="blsp-spelling-corrected" id="SPELLING_ERROR_10">the</span> downloads to customers manually using the Add <span class="blsp-spelling-corrected" id="SPELLING_ERROR_11">Download</span> Email link found on the Product Detail page in your account.<br /><br />Thank you for bearing with us during this hectic time,<br /><br />ShannonPayLoadzhttp://www.blogger.com/profile/12957320134637151535noreply@blogger.com