-------------------------------------------------
Initial Call
Reported: Date: 4/18/2012 Time: 10:30am
Tech’s Name: Arcell M. Mitchell Jr.
Name of Requestor:
Department:
Phone of Requestor:
-------------------------------------------------
IT Reporting Information
Date and Time of Response to Requestor: 4/19/2012 10:15am
Date and Time Incident Occurred: 4/18/2012- unknown
Type (Hardware, Software, Phone): Exchange (outlook) due to hardware and damage file issue.
-------------------------------------------------
Incident Description: In the morning, outlook stopped working on mobile devices and workstations. Associates, VP’s, and managers were not able to send or receive emails. Steven D. Brown with Nothing But NET discover that the old exchange server had two corrupted databases. We ran eseutil.exe and Isinteg.exe to repair the corrupted databases. Due to lack of disk space and speed of external NAS drives the process took 29 hours to complete. Once the database repair was completed the server was operational and people were able to access email, but we still had three problems to address: We had no backups, the server configuration was not optimal and the SSL certificate was expired.
-------------------------------------------------
-------------------------------------------------
Systems Affected: Exchange server 10.1.1.13
-------------------------------------------------
Impact on Business: Loss of ability to use company email.
-------------------------------------------------
What is the current status of the incident? The new server for exchange is built with plenty of storage space and the whole company email is up and running.
-------------------------------------------------
What steps still need to be taken? I had Steven D. Brown with Nothing But NET load Symantec Backup Exec System Recovery on the old Exchange server and backed it up to the Iomega NAS that was connected to the