Shulou(Shulou.com)06/03 Report--

I. introduction of vsan distributed storage failure

Recently, we have handled a data recovery case of vsan distributed storage, and the server that needs data recovery is a set of VSan super-converged infrastructure. Due to the abnormal shutdown caused by the abnormal power supply of the customer's server, the server administrator restarted the server and found that the logical architecture of vsan storage failed, the virtual disk files were lost and the virtual components were abnormal.

There are a total of 16 hard drives in the customer's vsan storage server, including 8 solid state drives and 8 mechanical hard drives. Solid state drives are mainly used as cache disks.

II. Vsan distributed storage server data recovery mirror backup

A large amount of important data is stored in the customer's server, and the data recovery operation needs to be carried out on the storage, so the data recovery center in Beijing is contacted by phone. After a simple communication about the failure, the data recovery engineer determines that the data recovery operation can be carried out, and goes to the customer site for data recovery.

The server data recovery engineer first numbered all the hard drives on the vsan node server in the customer's vsan distributed storage and took out the server, connected to the dedicated data recovery storage server, and mirrored the underlying data of all the hard drives in the client server byte by byte.

After the mirror is completed, the server data recovery engineer scans and analyzes the server data and finds that the customer's virtual machine component information is not seriously damaged, and the information needed for data recovery is still intact. It is estimated that the success rate of data recovery is more than 90%.

III. Server data recovery process

The server data recovery engineer began to write a scanning program suitable for this data recovery to scan and reorganize all the server components according to the client's server data, so as to get the necessary information such as the ID information and the object ID in all the component information.

Then use this information to trace back to the logical position of each data block in the component to which it belongs, and extract the data in the server completely with the help of data recovery tools.

After extracting all the available data in the server, the engineer reassembles the data according to the logical location information of the components recorded in the description information, thus piecing together a complete vmdk file.

Continue to analyze the vmdk files, merge the snapshots of the vmdk files extracted from the server with the parent disk, and extract the data files after parsing.

After successfully extracting all the data files in the client server, the server data recovery engineer sets up the same verification environment on the data recovery server as the customer database environment to verify the integrity and availability of the recovered data. After verification, the recovered data can be used normally, the database does not report errors, and the data is complete.

4. Server data recovery results

After verifying the data recovery result, the data recovery engineer notifies the client and server administrator to verify the recovery result. After the verification by the customer administrator, it is confirmed that the integrity of the data recovery result is 100%, and the server data recovery is successful.

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.