Case Project 4-1: Dealing with a Disk Crash Last week, a disk containing CSM Tec
ID: 3786972 • Letter: C
Question
Case Project 4-1: Dealing with a Disk Crash Last week, a disk containing CSM Tech Publishing’s current project manuscripts crashed. Fortunately, there was a backup, but all les that had been added or changed that day were lost. A new disk had to be purchased for overnight delivery, and the data had to be restored. Several days of work time were lost. The owner of CSM Tech wants to know what can be done to prevent the loss of data and time if a disk crashes in the future. The server currently has two disks installed: one for the Windows boot and system volumes and one for manuscript les. The disk used for manuscript les is about one-third full. There’s enough money in the budget to purchase up to two new drives if needed. What solution do you recommend, and why?
*Need to know what drives to buy and why. Also would I use the manuscript file disk that is one-third full.*
MCSA Guide to Installing and Configuring Microsoft Windows Server 2012 /R2, Exam 70-410 | Edition 1
Explanation / Answer
As asked in the case above to prevent the data loss in future the way out is to create a clone of the primary disk on a regular basis. For example if the manuscript is of high importance the interval for automatic backup can be of less than a minute so that minimum loss is occured during primary disk faliure. This time interval can me more than a minute or wath ever depending upon the sensitivity, priority and cost assosiated with data.
I would recomment to purchase one disk and make it as a replica of the primary disk containing the manuscripts. As discussed above this will be the best and cheap option to go with and avoid any data loss in future. We should not use the same disk to create bacup even it is empty because if the disk gets corrupted the whole chunk of data gets lost ractically making the disk unusable/unrecoverable. Hence, a seperate disk should always be prefferd for creating backup.