Always backup your database..OK!
Posted on December 14, 2007 - Filed Under Personal Encounter |
I have already deployed two ASP.NET content management systems, the PSU Eastern Cluster Community Server (http://202.91.163.10/cs) and the Pangasinan State University Official Website (http://www.psu.edu.ph). Both websites uses Microsoft SQL Server, version 2000 for the Eastern Cluster Site and 2005 Express for the PSU Official Site. The Eastern Cluster Site’s database is working well since November 2006 and have not encountered any errors as of now. With the number of postings in the site, its database actually is a large one now.
Two days ago, the PSU Official Website’s database suddenly was marked SUSPECT by the SQL Server 2005 Express. I have not figured out as of now what exactly is the cause but the database was actually corrupted. I tried to recover it but unfortunately only the table structures were fine but most of the data were lost. I have no other choice but to setup one again and encode all the contents of the website. This all happened because I forgot to do a very important thing when you depend on CMS, I did not back-up my database!
Anyway, there is always something good that you can pick out from a bad experience. Because of what happened, I installed the latest release of the DotNetNuke CMS which is obviously far more better than the first one. And of course, I learned my lesson, I immediately created backups for my databases including the one used by the Eastern Cluster site. I am still thankful it is not the Eastern Cluster Site’s database that was corrupted or else, I can’t actually imagine how tragic it would be.
Comments
Leave a Reply