How long is a 'short time' - Homepages maintenance
OK, so now I'm
I finally got access to my F9 webspace via ftp on Thursday 17th January PM and found the data had apparently been restored from 15th January. No probs at all with that, a few minor updates later, all is back to normal and everyone's happy. Well almost everyone, because logfiles are missing for the day of the homepages disaster and the following day. Service.status then reports the data is lost but the problem is (presumably) fixed so that I thought was the end of it. A bit of downtime, a recent(ish) restore meaning not too much to sort out in the way of updates and a couple of days lost logfiles. Missing logfiles are a bit of a PITA and really shouldn't have happened due to PN having advance warning of impending doom, but hey, sometimes s**t happens and all that. All-in-all, a bit chaotic but not a bad result.
However, today I find that my entire HTDOCS directory is effectively duplicated because it looks like what existed was back-up today 19th January (renamed htdocs 20080119....) and replaced with a new htdocs containing data from god knows when but the directory is dated 29/07/07. The restored data is at least as old as that which PN restored earlier in the week but it could quite possibly be older, who knows !
And not only but also, in addition to what appears to be a bit of a mess in the recovery process, there are still no logfiles being generated several days after the initial problem. The lack of logfiles also applies to my other (PN) A/C that apparently wasn't even affected by the homepages problem, at least not in so far as no access or lost data was concerned.
Grrrrrrr
What exactly is going on here ? service.status appears to suggest all is sort of well and my ticket response the other day, as I predicted it would, says all is now well and suggests I refer to service.status.
I finally got access to my F9 webspace via ftp on Thursday 17th January PM and found the data had apparently been restored from 15th January. No probs at all with that, a few minor updates later, all is back to normal and everyone's happy. Well almost everyone, because logfiles are missing for the day of the homepages disaster and the following day. Service.status then reports the data is lost but the problem is (presumably) fixed so that I thought was the end of it. A bit of downtime, a recent(ish) restore meaning not too much to sort out in the way of updates and a couple of days lost logfiles. Missing logfiles are a bit of a PITA and really shouldn't have happened due to PN having advance warning of impending doom, but hey, sometimes s**t happens and all that. All-in-all, a bit chaotic but not a bad result.
However, today I find that my entire HTDOCS directory is effectively duplicated because it looks like what existed was back-up today 19th January (renamed htdocs 20080119....) and replaced with a new htdocs containing data from god knows when but the directory is dated 29/07/07. The restored data is at least as old as that which PN restored earlier in the week but it could quite possibly be older, who knows !
And not only but also, in addition to what appears to be a bit of a mess in the recovery process, there are still no logfiles being generated several days after the initial problem. The lack of logfiles also applies to my other (PN) A/C that apparently wasn't even affected by the homepages problem, at least not in so far as no access or lost data was concerned.
Grrrrrrr
What exactly is going on here ? service.status appears to suggest all is sort of well and my ticket response the other day, as I predicted it would, says all is now well and suggests I refer to service.status. 
Oh dear .... still no logfiles on either A/C and support are apparently in denial:
Needless to say, I did get back to him and point out that the last update was 15th on the problem A/C and 17th on the other A/C and today appears to be 20th ! I can absolutely guarantee there should be data for each and every hour of each and every day of the year.
Also, no response as to what to do about the massive duplication of data. I have 2 full copies of everything on my webspace and cannot delete the rogue directory due to permission issues. CHMODing 777 doesn't help in the slightest, still permission denied. Anyone have suggestions ?
Is anyone else finding data is still apparently being lost ?
... or are support trying to suggest that logfiles are still being regenerated and will be turning up sometime soon(ish) ? Maybe but I rather suspect not somehow.
Quote Response to Ticket 23918661
I can confirm the log files for the time when the service was down cannot be retrieved, but i can confirm since then the log files are now generating again.
If you do have any further questions please do not hesitate to get back in touch.
Needless to say, I did get back to him and point out that the last update was 15th on the problem A/C and 17th on the other A/C and today appears to be 20th ! I can absolutely guarantee there should be data for each and every hour of each and every day of the year.
Also, no response as to what to do about the massive duplication of data. I have 2 full copies of everything on my webspace and cannot delete the rogue directory due to permission issues. CHMODing 777 doesn't help in the slightest, still permission denied. Anyone have suggestions ?
Is anyone else finding data is still apparently being lost ?
... or are support trying to suggest that logfiles are still being regenerated and will be turning up sometime soon(ish) ? Maybe but I rather suspect not somehow.
Quote from: Ian Neil - I'll get onto it first thing in the AM.
Ian
Thanks for the call Ian, much appreciated
sites restored 100%
Neil
Quote from: Chris I've just updated the service status thread for this problem:-
http://usertools.plus.net/status/archive/1200914101.htm
It would have helped if that had advised users that if they had made changes to their website after it was migrated over, the version in htdocs would be out of date and that they would need to replicate the changes from the backup copy to the live copy (I had to do that).
