Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Summary of relocation methods after server data recovery

2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

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

In the server data recovery work, there is a case worth sharing with you. There are two hard drives in the client server in this data recovery. Because the hard disk physical failure caused the server to be unavailable, the data recovery in our company was successful. The following is not the data recovery process, but the data migration method after successful data recovery.

As the customer's server was originally practical 2 hard disk group raid led to a hard disk offline immediately after the server paralysis, so the customer in the re-establishment of the raid array using three hard drives to form a raid5 array, so that even if a single hard disk offline will not cause the server to crash immediately, the administrator can take timely remedial measures to ensure the normal operation of the server.

But then a new problem arises, how to quickly and effectively migrate the recovered data to the new raid array? The front panel of the client's server is managed by the raid card. It is unrecognizable to insert a new hard disk directly into the server, but due to the capacity limitation of a single disk, the raid cannot be created through the raid card.

Another method is to use the SATA interface above to connect a SATA hard disk to move back through the server cover, but this method also has some limitations (that is, the situation encountered by our customer). The SATA interface used by the server is not the standard size, but mini SATA and there is no adapter card, and the second solution does not work.

Note: if the amount of data is small, it can be transmitted in USB mode, but the USB interface of most servers is still USB2.0, which is only used in the case of small amount of data, which is not applicable in the case of data recovery.

Finally, the server data recovery engineer of our brain circuit proposed that we can take the network to move the data back! The specific process is as follows:

First of all, we need to start a linux live cd. We use linux system rescue cd in this case. After the linux is started, we configure the ip of the server under ifconfig. Then we put the data in the recovered original server on a win 2008 R2 machine and open the nfs service (off by default) in the win environment. "Service Manager-role-add role-check File Service-check Network File system Service for installation You need to restart the computer after the first installation. "

After the restart, we operate on the folder where the mirrored data is stored. Select share this folder in the right-click-NFS sharing tab, and then select allow root directory access in the permissions, and select read and write access type.

After the settings on the Win side are completed, let's take a look at the settings on the Linux side, and ifconfig to view the current network configuration

Because we need to assign an ip to him, here we assign the network card "enp4s0", and the ip address is assigned to 10.3.12.3 with a subnet mask of 255.0.0.0, using the following command: ifconfig enp4s0 10.3.12.3 255.0.0.0 and then use ifconfig to view the ip address

After configuring ip, check to see if the network comes with, command: ping 10.1.1.1

Then check whether the directory of the NFS share on the 10.1.1.1 machine is accessible, command: showmount-e 10.1.1.1

The source and destination machines are now connected, create a directory mkdir / mnt/bysjhf in linux

Once created, we mount the mirrored data to mount 10.1.1.1:/data / mnt/bysjhf-o nolock under the newly created folder under linux

After mounting, check the mount point information df-k

After confirming that it has been mounted, go to this folder and check the image file in the folder: root@sysresccd / mnt/bysjhf% ls

And check the hard disk and partition information: fdisk-l

After confirming the source and target devices, mirror operation: dd if=/mnt/bysjhf/data.img of=/dev/sda bs=10M

In the gigabit network environment, the speed of NFS can run to 70M/S, which is already a very ideal speed. After waiting for the completion of dd, we restart the ibm X3650 server and choose raid to boot. The expected windows startup page finally appears, the previous hard work has not been wasted, and the complete data migration 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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report