PLESK Crash Recovery
Many times the hosting server crashes with PLESK either because of a hard disk, a virus or because the server was hacked. In these cases you need to recover the last data from the hard disk. Let’s see some of the problems usually came across.
"I have a server of approximately 50 domains. Yesterday one of the clients’ applications was hacked, a troian was inserted to the server and the team from the datacenter told me I have to reinstall the operation system. They put my old hard disk in the new server, but it is my duty to recover the data. I have a backup made with PLESK one week ago, but I would like to have recovered the last data from the server. What can I do. Datacenter will reinstall Linux with PLESK."
"I have over 150 domains, yesterday I did something to the server and today it wouldn’t boot. I have reinstalled Linux with PLESK, but with the new 8.3 PLESK, not the 8.1 that I’ve had before and I also want my latest data. What can I do? I have access to the old hard disk, it is installed."
These kind of problems occur almost day-to-day, we hear them, we read them on forums and almost always the recovery of the data, especially the last ones, not the one week backup, is made manually. Why manually? The templates have to be recreated, the clients and the domains of these, the databases, the mail users (they can be hundreds of users) have to be recreated, the data from the old server have to be remade (database, web pages and not the last the unread e-mails), and this is not an easy thing to do, taking into account that the users will try to read their emails using the old passwords. If we succeed in convincing the owners of the domains that we changed their passwords, the mail users will not be easy to contact and to be convinced.
YOU NEED to have a fast solution.
Here we can intervene with recovering the data from the old HDD and remaking all the data from this database. The recovery can be successfully made in some hours, not days. The steps we follow to recover the data and the success of these. Unfortunately we cannot guarantee a 100% recovery, however we reach 80-95%, the rest can be done later, manually:
|Service||Percentage of success|
|Recreating the templates||90%|
|Recreating the clients||100%|
|Recreating the domains based on names, with FTP user on virtual hosting||98%|
|Recreating the domains based on packages (PHP, ASP etc)||80-90%|
|Recreating the subdomains based on names, with FTP user on virtual hosting||98%|
|Recreating the subdomains based on packages (PHP, ASP etc)||80-90%|
|Recreating the databases with user name and password (MySQL)||98%|
|Recreating the email addresses||95-98%|
|Recreating the email addresses with specific settings (forward, alias etc)||90%|
|Recreating the webusers||95%|
|Recreating of the old database - MyISAM (in case of InnoDB can occur problems)||99%|
|Recreating of read, unread, sent messages||100%|
|Recreating of web sites, giving back the user rights||99%|
- There has not been made tests on recovering some ColdFusion, Postgres data and some specific settings for some servers. The server administrator will have to redo these settings, usually only the administrator knows these settings.
- After the data recovery, the administrator has to verify the sites, the data in maximum 24 hours. He also has to be available on messenger during the data recovery.
- In case of failure, a 75% refund is offered. The time of the recovery is between 4-8 hours depending on the number of domains and the problems that occur on the server. Each assignment will be planned together with the server administrator.