1- Last week a disk on a Windows Server 2012 system that contained CSM Tech Publishing’s current project manuscripts crashed. Fortunately, there was a backup, but all files that had been added on changed that day were lost. No RAID configurations were in use. A new disk had to be purchased for overnight delivery , and the data had to be restored. A couple days of work 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 files. The disk used for manuscript files in 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?

 

2- It’s been six months since the disk crash at CSM Tech Publishing, and the owner is breathing a little easier because the solution that you implemented in Case Project 7-1. Business is good, and the current solution is starting to run low on disk space- less than 20 percent of free space remains. In addition, the owner has some other needs that might require more disk space, and he wants to keep the data on separate volumes (what he calls drives). He wants a flexible solution in which drives and volumes aren’t restricted in their configuration. He also wants to be able to add storage space to existing volumes easily without having to reconfigure existing drives. He has the budget to add a disk storage system that can contain up to 10 HDDs. Which Windows feature can accommodate these needs, and how does it work?