At 12:30 PM (EST) on Monday, December 13th, 2021, ecbiz213 suffered a hardware failure associated with the hard drives on the server. Despite the best efforts of our team, the RAID array has been deemed unrecoverable.
We are working to move all affected accounts to new hardware as quickly as possible.
12/13/21 — 3:00 PM — We began moving accounts on the server to new hardware as of 1:40 PM EST on December 13th, 2021. Work is still in progress.
12/14/21 — 10:30 AM — We were able to locate more up-to-date backups on the server. We are currently in the process of checking the restorations on the server and making sure the most up-to-date backups are the ones restored.
12/14/21 — 8:30 PM — We were able to successfully restore all backups on the server. This concludes our move to new hardware.
Note: ecbiz213 is the name of a server housing hosting accounts. In order to find the name of your server, please see How to Find Your Server Name in cPanel.
Our Systems team will restore accounts from the most recent backups we had on file as soon as possible.
If you have a more recent backup that you would rather restore, you may do so as soon as your account is accessible. Here are some guides on restoring sites from backups to assist you in the restoration process:
- How to Restore a Backup File/Folder Using the Backup Manager
- How to Restore a Database With Backup Manager
- Doing a WordPress Backup and Restore for Your Databases
- The Complete Guide to cPanel Backups
If you need assistance with your restoration process, please submit a verified ticket to our Support team.
We sincerely apologize for the issues and inconvenience that this event has caused. We are confident that we will be able to regain your confidence as the best web host for your needs and thank you for the opportunity to do so.
Thoughts on “ecbiz213 Failure and Recovery”
No substantial context in this article – What is the ETA? To what point in time will data be restored? How does a RAID array fail, was it RAID-0? Ridiculous.
We apologize for any inconvenience caused by the ecbiz213 failure. Unfortunately, an ETA is difficult to provide as the resolution of the issue depends on a variety of factors. While our team works to resolve the issue we will provide additional information as it becomes available.