Shulou(Shulou.com)05/31 Report--

This article mainly introduces the relevant knowledge of virtual disk data recovery case analysis of virtual machine, the content is detailed and easy to understand, the operation is simple and fast, and has a certain reference value. I believe you will gain something after reading this virtual disk data recovery example analysis article. Let's take a look.

In the information management platform of a provincial branch of Sinopec, several VMware virtual machines-ESX SERVER share one IBM DS4100 storage, and about 40,50 virtual machines occupy 1.8TB space. in normal work, virtual disk loss is reported in vc, and ssh executes fdisk-l to ESX to check the disk, and it is found that storage no longer has a partition table. After rebooting all devices, ESX SERVER cannot connect to the STORAGE where the DS4100 is located.

After receiving the case, we carefully asked the administrator at that time but there was not much information available, but they inadvertently mentioned that they had connected to a windows 2003 server on this storage network, the details are unknown. It is natural to think that the windows 2003 may have corrupted the entire vmfs volume due to its exclusive operation on storage.

According to the analysis of the whole storage, it is found that the partition table is clear 0, there is a 55aa valid end flag, and there is a hard disk ID flag. Simply looking from front to back, I found a NTFS volume, but it did not seem to write data into it, like a volume that had just been formatted. By analyzing the BITMAP of this NTFS volume, we found that the size was about 1.8T (all space), the front part occupied part of the space, the 3G around position occupied part of the space, and the 0.9T area occupied part of the space, but the total space was no more than 100m. Based on the analysis of the VMFS volume, it is found that there are two groups of VMFS partitions in the original 1.8TB disk, the second group is about the first group of extend, the first group is about 1.5T, the second group is about 300GB, because the NTFS partition does not write data to the second VMFS partition (the DBR backup of the last sector does not cover the useful data), so the focus is on the first VMFS partition. According to the analysis of the first group of VMFS, the header structure is lost, the first-level index and the second-level index exist, and the data area covered by NTFS happens to be the temporary memory mirror of a group of virtual machines.

Through the above analysis, we can recover the data.

Step 1: mirror backup the entire STORAGE.

Step 2: after analysis, connect two VMFS partitions and extract all VMDK and configuration files directly according to the organization of VMFS analysis.

Step 3: migrate back to ESX SERVER directly through nfs.

In addition: in this example, because the fault storage has been securely backed up, the first set of VMFS volume headers, index lists, partition tables and other information are directly rebuilt during the repair, which is directly attached to the ESX SERVER environment, which is the second solution.

This is the end of the article on "instance Analysis of Virtual disk data recovery". Thank you for your reading. I believe you all have a certain understanding of the knowledge of "virtual disk data recovery instance analysis". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.