Update at 18:22:39(BST): Update at 18:22:19(BST): The server was rebooted and has been returned to service. All databases have been checked and are working fine. If you continue to have issues with Queeg, please contact support via support@34sp.com
19th August 2010, at 5:50PM
19th August 2010, at 5:22PM
Update at 16:21:10(BST): The issue has now been resolved with this server.We are presently looking into faults on both of these systems.
19th August 2010, at 5:34AM
19th August 2010, at 3:21PM
Update at 05:33:46(BST): The issue has now been resolved with this server.Our support department will be closing at 5.30pm on Wednesday 18th August, to allow for system maintenance. Please ensure you contact us before this time for any urgent cases. All other cases will be dealt with first thing Thursday morning.
Apologies for any inconvenience this may cause.
16th August 2010, at 10:54AM
19th August 2010, at 4:33AM
Update at 12:25:29(BST): The issue has now been resolved with this server.
13th August 2010, at 12:15PM
13th August 2010, at 11:25AM
Update at 05:33:52(BST): The issue has now been resolved with this server.Update at 10:27:05(BST): All email and files that can be restored have now been restored. We are currently working to try and retrieve any databases that we can from the failed server, but advise customers to restore these from their own backups where available.
--
Update at 01:11:28(BST): Most sites should now be restored and active. Email should be live, and www data (that we could recover) restored.
Databases have not been restored. A full update email will go out to all affected clients first thing in the morning on 13/08/10.
--
Update at 23:00:16(BST): Throughout the evening we have been moving the recovered data from business3 to new accounts on business7. All users now have accounts recreated on this server, plus any data we could recover has been moved too.
The final stages are now underway which requires some DNS updates.
--
Update at 16:12:47(BST) :We have now restored all the email that could be retrieved from the failed server to the mailboxes on our atmail system. Work to restore sites is still under way.
--
Update at 12:09:56(BST) :An email has been sent this morning to all account holders on this server. Email has been reactivated on our atmail system and should work with your existing details. We are working to import mail held on the failed server to this.
Web sites are being transferred to a different server and we will attempt to restore these as fully as we can as soon as we can.
--
Update at 23:29:02(BST) :Attempts to restore the server have failed. We are now in the process of recovering as much data from the server disks as possible. Due to the amount of data and the nature of the failure, this is expected to take a significant amount of time, at least into 12/08/10.
Once we have recovered as much data as possible we will be beginning further restoration efforts. We will also be emailing all affected clients with a detailed update during Thursday.
--
Update at 21:49:16(BST) :Work has been continuing throughout the evening in an attempt to restore the system and save as much data as possible. Updates to follow as soon as further progress is made.
--
Update at 17:44:49(BST) :Server3 has experienced a severe fault, which we believe to be disk related at this time. We are now in the process of trying to recover as much data from the server as possible. We presently have no ETA on when services will be restored.
--
Update at 17:05:19(BST): As an emergency measure we have had to reboot the ASP Business Server.
Apologies for any inconvenience caused.
11th August 2010, at 5:04PM
19th August 2010, at 4:33AM
Update at 18:09:35(BST) :The issue has now been resolved with this server.We are presently looking at issues affecting this server, primarily www problems.
9th August 2010, at 5:44PM
9th August 2010, at 5:09PM
Update at 21:56:24(BST) :The issue has now been resolved with this server.We are presently investigating a fault affecting services on this server.
5th August 2010, at 9:43PM
5th August 2010, at 8:56PM
Update at 09:43:50( BST )
5th August 2010, at 9:17AM
5th August 2010, at 8:43AM
Update at 14:17:44( BST )
4th August 2010, at 1:55PM
4th August 2010, at 1:17PM
Update at 21:41:41( BST ) : The issue has now been resolved with this server.
3rd August 2010, at 9:36PM
3rd August 2010, at 8:41PM