Emergency cpanel37 Upgrade (Hardware Failure)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • AndrewT
    Administrator
    • Mar 2004
    • 3655

    #1

    Emergency cpanel37 Upgrade (Hardware Failure)

    Earlier this evening we discovered a bad hard drive in the cpanel37 RAID-1 array. As a result, we took the machine offline to replace it. Normally this isn't even an issue at all but upon doing this we discovered that both hard drives had been corrupted. A significant amount of the system files are corrupt such that we are unable to start any services (HTTP, mail, etc.).

    We're currently transfering all data off of the server that we can and we will be restoring it to a new cpanel58 server. Those of you that are not using our gzo.com nameservers will have to update your nameservers to use new IP addresses for the new server. This information will be posted to this forum thread as soon as possible.

    I apologize for the inconvenience that this undoubtedly causes many of you. Please understand that we dislike situations such as these far more than anyone. Rest assured that we are doing everything that we can to get your accounts back up and running as quickly as possible.
    Last edited by AndrewT; 02-07-2007, 10:26 PM.
  • AndrewT
    Administrator
    • Mar 2004
    • 3655

    #2
    We're still transfering data off of the cpanel37 drives. This will take a while to complete. To provide a very rough estimate, we hope to begin restoring accounts within the next 6 hours. Keep in mind that this is just an estimate though because it is hard for us to tell how long everything will take.

    Comment

    • AndrewT
      Administrator
      • Mar 2004
      • 3655

      #3
      If you are not using our gzo.com nameservers, please change your nameservers to use these new IP addresses:

      75.126.144.66
      75.126.145.176
      Last edited by AndrewT; 02-08-2007, 09:48 AM.

      Comment

      • AndrewT
        Administrator
        • Mar 2004
        • 3655

        #4
        If you login to the customer control panel your server should now be listed as cpanel58. Additionally, you should be able to login to WHM on cpanel58 with the same login as you used for cpanel37.

        We're currently in the process of restoring accounts now. If you would like us to automatically restore the data for your accounts then please do not recreate them via WHM. This will be done for you.

        Comment

        • AndrewT
          Administrator
          • Mar 2004
          • 3655

          #5
          Accounts are still restoring and will be for a couple of hours at least.

          If you do not pay for our backup service then you will have to recreate e-mail accounts, aliases, subdomains, addon domains, parked domains, additional FTP accounts, etc. via cPanel. However, once you recreate these, the data will be there already (e-mails, subdomain files, etc.). You will also have to reset each domain's password via WHM as the old passwords will not work initially.

          Comment

          • AndrewT
            Administrator
            • Mar 2004
            • 3655

            #6
            Over half of the accounts have been restored now.

            We're having some problems with our domain registrar and have been unable to update the old cpanel37 gzo.com nameservers to the new IP addresses. At this point I cannot say when we will be able to do this. I certainly hope this morning.

            For the quickest solution I would recommend that you create your own custom nameservers using the IP addresses that were listed above (75.126.144.66 and 75.126.145.176) and use them on all of your domains.

            Comment

            • AndrewT
              Administrator
              • Mar 2004
              • 3655

              #7
              95% of the accounts have been restored. However, we just started experiencing even more disk errors at which point the server crashed entirely. We're continuing to work on this so that we can hopefully restore the few remaining accounts.

              We're still not having any luck updating our gzo.com nameservers with Stargate. Their entire system has been problematic all morning. I still highly recommend setting up your own custom nameservers and using them instead of the gzo.com nameservers due to the fact that we are unable to update them to the new IP addresses at this time.

              Comment

              • AndrewT
                Administrator
                • Mar 2004
                • 3655

                #8
                We got cpanel37 back online for the time being at least and we're continuing to transfer the remaining accounts off of it.

                We've also gotten DNS working on cpanel37 and have set it up so that it will redirect all domains to the new server IP until we can actually update the gzo.com nameservers at Stargate.

                Comment

                • AndrewT
                  Administrator
                  • Mar 2004
                  • 3655

                  #9
                  All accounts have now been restored. If you notice any problems please do not hesitate to submit a ticket.

                  Also, the gzo.com nameservers are now fully setup and will work properly from this point forward.

                  Comment

                  Working...