Case:
HP EVA4400, 5*12 blocks 1T physical disk, all storage spaces form two Storage Group, allocating Lun about LUN: 9TB 1, 8TB of about 4, LUN mapped to two Windows Server.After the device is restarted, all Lun mounted to Windows is not initialized.
Solution:
1. Back up the fault storage in a read -only way, and then no longer operate the original storage. The specific implementation rules are about: a. Divide 5 LUNs used to place mirrors on the new P6300 storage. In order to be obviously different from the source storage and prevent misunderstanding, the size of these 5 LUN is slightly greater than the fault LUN. b. The fault storage EVA4400 and mirror target storage P6300 received a HP DL380 server at the same time. c. Install Windows system on the Windows system on DL380 Winhex. d. Use Winhex to store only mirrors for source faults. Engineers with more than 2 mirror processes confirm the operation. 2. After each group of LUN is backup, the source failure can be removed to avoid misunderstanding during recovery. 3. Logic analysis in the backup carrier, and the general process of analysis is: a. Analyze whether the GPT format is abnormal, such as abnormalities, calculate the reconstruction after calculation. b. Analyze whether the FileSystem DBR is abnormal. If there is abnormalities, reconstruction is calculated. c. Analyze whether the NTFS $ MFT Filerecord structure area is abnormal. If there are abnormalities, re -generate the NTFS $ logfile or upper and lower verification. d. Analyze whether the NTFS INDX is abnormal. If there are abnormalities, re -generate it through NTFS $ logfile or context check. e. After confirming in the virtual environment, loading the file system in the backup environment, CHKDSK can see if it can be verified by the system. If the reasons are not analyzed, repeat the above process, or make a response based on the situation. 4. Data from the fixed LUN to process the next LUN. 5. After all the data is completed, verify and transfer, and complete the business process.