Quote:
Originally Posted by cd34
From pieces of conversations, and the delays, here's my theory:
disk crash at host on sybase server, no backups
drive sent out for recovery - this is not a quick process if it is a media rather than mechanical failure
site that was transferred to new hosting company, database configs not altered, machine continues to try to contact sybase server which is offline (hence the 27 second timeout)
If it is at a drive recovery company, they give so little feedback and you have no idea where they are in the process until they are done. The sales rep will tell you things are progressing, we're at x%, should be done Friday, etc. Until you get that tracking number, you just don't know when you're going to get the drive back.
|
My webhost is suppose to make weekly backups of all my sites (adult and mainstream). I continue to make manual monthly backups in case something happens to their operation. I don't want to sued by clients or lose income streams.
It is hard to believe that this could happen to a major adult player. Just goes to show you that behind some of these seemingly professional programs are sites held together with spit and duct tape.