Installation and deployment Questions on installation, system configuration and deployment to the live server.
Version 5.x > Installation and deployment > Server Crash : Duplicate from the Thread in version 6.x (Posted by Mistake - Sorry) View modes: 
User avatar
Member
Member
stuart-holdenjones - 3/19/2012 6:01:59 AM
   
Server Crash : Duplicate from the Thread in version 6.x (Posted by Mistake - Sorry)
We have been using free edition of Kentico 5.5 on our server to serve our Intranet, however 2 weeks ago, we suffered from a Fatal .Net error. This effected every program that uses the .net framework. It could not be repaired.

I purchased a new hard drive, and done a fresh installation of Server 2003 Std Edition, and reinstalled the Kentico CMS 5.5R2 which i still had the install files for.

The old hard drive is 100% Intact, and is once again connected to the server, and is serving as a live backup so that we can copy data from the old drive to the new one.

Because of the .NET terminal error, we could not gain access to the CMSadmin section, and perform a backup using the built in tools.

Question.
How can we get our data back and get the intranet site backup and running? Do we simply copy over the iNETPUB folder which the KenticoCMS directory is located, or is there a set procedure in order to rescue this?

Any help would be appreciated.

many Thanks

Stuart.

User avatar
Kentico Support
Kentico Support
kentico_radekm - 3/19/2012 9:22:01 PM
   
RE:Server Crash : Duplicate from the Thread in version 6.x (Posted by Mistake - Sorry)
Hello.

If you are not able to access Site Manager and export your site using standard Export functionality, you can use “manual” approach instead.

Basically, you need just a two things. Project folder (which is usually located in inetpub/wwwroot folder) and database backup, which should be still installed on your SQL Server. If the SQL Server is still running, you just need to modify connectionString in your web.config file to point to proper SQL Server and DB name. Otherwise you need to back-up your DB from old SQL Server, restore it on new SQL Server and update your connectionString.

Best Regards,
Radek Macalik