![]() ![]() I am most interested in how disk managment handles this mirroring. There is a backup in place for this server but it is not our backup and we are unsure of its functionality. We are hoping to just get this server functioning normally for the time being. We absolutely will be recommending a reinstall and with a proper raid setup at some point. If you want to familiarise with this backup and restore method, use any other windows machine as a trial of the process before attempting the server Restore the machine image from USB hdd.īoot machine and any further reconfiguration and testing of services online. ![]() Create new logical volume(s) as desired.īoot recovery disk. For this I would use Veeam Endpoint FREEĭestroy the current data and disk layout. (2nd level emergency)įull volume level backup to USB hdd. ![]() If the hardware storage meets the predicted requirements then you can redesign it, or purchase upgrade disks and proceed with a reinstallationįile backup of data. You need to evaluate a clean/fresh install Vs what I suggest below.Ģ logical volumes of equal size, in device manager for the Windows software mirror? If the OS environment is unmaintained or 'corrupted' then a backup and restore will overcome the storage design issues but not software problems. If operating any significant functions - eg Domain Controller, you should specify to receive better answers. It sounds like the machine is barely online and just providing file shares. We are currently playing the wait and see game, but will have to take action soon if things do not improve as the client has limited to no access to their network shares. How does this type of mirror work, does the data move only one way? Would deactivating the mirror cause issue? Would physically removing the mirror disk cause issue? We are at the point where we are anticipating next steps. On top of that the entire system is crawling, slower than I would expect from a normal raid sync. That being said, it does not show a percentage of the resync and it has been running for multiple days. Once we discovered it was reyncing the software raid the slowness made sense. The server is extremely slow but shows low CPU and RAM usage. This also appears to not have been setup correctly as it is only mirroring the C: partition and not System Reserved. We just took over a client from another IT company. Their 2012R2 server appears to be using Microsofts built in software disk mirroring in diskmgmt.msc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |