Featured Article

Windows Exchange Server Recovery

IBM X3400 SERVER RAID 5:

I am using a RAID 5 array server which does not seem to be working, and which contains a lot of data related to my business. The server will not boot up into the array, and I am getting a message which says that there is a ‘fatal error’ and that the Controller Monitor has failed, which I assume means that the RAID controller is not working. The computer then suggests that I press any key to continue, and when I do that it fails to go into the Windows loading screen, and instead just hangs there, almost as though it were frozen. I am not able to get into the desktop so that I can view the data on the servers, and while I can see a few folders in BIOS, I can’t get to the data that I need. I have tried removing all of the RAID 5 hard drives, and resetting them in order to get the boot up, but nothing has worked, and the drives are not responding to any kind of repair program.

DELL POWEREDGE 6300 SERVER RAID 5:

I need some help with a Dell PowerEdge 6300 server which is running a RAID 5 array. I tried to install an update for the RAID controller, and since then the system has not allowed me to get into the drives to remove my data. When I try to go into the server folder itself, the computer puts up a large red cross, and says that the drive is not readable. I am not able to look at any of the files in the drive, and so can’t recover the information that way. The server freezes up when I try to view the files, and eventually I am forced to shut it down by taking out the power cable. I have so much data on there that needs to be recovered that I feel overwhelmed by the task. I don’t know what I can do now to get the data back, but some of it is very important and I need to be able to view it again.

Windows Exchange Server Recovery

Developed by Microsoft and now an industry standard, Microsoft Exchange Server is something that many companies rely upon for their e-mail provision as well as providing add-ins to their CRM systems.

Available as an online system you will find that the majority of companies running Windows Exchange do so in-house on their own dedicated servers that allows for a more hands on approach.

There have been many versions of Microsoft Exchange Server since its inception and now, in 2013, we have the obligatory Microsoft Exchange Server 2013.

There are a considerable number of individuals and organisations who still run older versions of this software simply because it is what they are used to.

Windows Exchange Server is prone to a lot of the same problems as you might find on an ordinary desktop computer or small office server. For the most part it is the software that is the heart of the enterprise here whilst the hardware operates on a similar principle to the kind of machine you might find on your desk in your workplace.

Exchange servers generally have additionally memory fitted and larger hard drives to cope with the influx of information from the Internet, web servers and email servers and there are occasions when these discs run into trouble.

Common problems that are associated with hard drives installed in Microsoft Exchange Servers are listed as events and usually the most common events are documented in log files as 507, 509 and 510. More often than not the slowing down of the writing of information to the hard drives during processes carried out by Microsoft Exchange causes these events.

Some individuals might opt for the ‘switch it off and back on again’ technique but really all this succeeds in doing is prolonging the problem. The continual rebooting of a system suffering from writing to disk errors – servers in particular – can only lead ultimately to the loss of data simply because the data has not been written to the drive in the first place.

When errors such as 507, 509 and 510 begin to emerge this means that there are problems with hard drives either in their infancy or about to become major issues which could lead to the loss of data overall or indeed complete hard drive failure.