Shortly after midnight on Tuesday, February 24th the myDailyPhoto server in Dallas bit the dust. We've been struggling with numerous issues at our Dallas co-location facility and they finally came to a head. Unfortunately the problem wasn't noticed until later on that morning. We immediately put together an action plan that involved moving up the date of the server switch; it was a hard decision to make, but it seemed to have the best long-term outlook.

At noon that day our Database Administrator and all-around computer genius Sean started backing up the most current files and data from the server in Dallas while I switched the nameservers to point to our new Fremont, CA location. An interruption-of-service notice was sent out around 1:30PM EST to all of our users.

Throughout the day back-ups were continuously being downloaded onto local machines and uploaded to the new server (for which a great deal of thanks goes to Sean). All-in-all we transferred over 800MB of photos and another 10MB in files (up-and-down) over the course of three hours. We also implemented our new photo directory structure during this time to avoid having another service interruption in the near future.

There are still some remaining problems due to the unexpected and quick-paced server switch; a few avatar files were lost due to permissions problems, we're slowly coming across permissions problems on the new server, and occasionally we're finding incorrect directory structure usage. We'll be working as quickly and efficiently as possible to resolve these issues. As always, if you come across a problem, please let us know; you can e-mail me directly at any time by sending a note to mattcongrove@gmail.com.

Please note that the mobile sites and all myDailyPhoto e-mail addresses are also down at this time and will continue to be until further notice.

Thank you all very much for your patience during this unfortunate situation; we're sure the speed, efficiency, and reliability of our new California server will more than make up for the inconvenience over time. And, again, Sean deserves a tremendous amount of praise for his hard work in this effort; everyone make sure to personally thank him.