Hi team, here's a new case.
Symptom
The backup fails, and the failure cause is "The lun can not be found" displayed on eBackup.
Possible Cause
Due to network problems, volumes cannot be attached to the initiator of eBackup on the production storage.
As a result, disks cannot be scanned and timed out.
Solution
1. On the eBackup page, find a failed task and obtain the details (including Backup Proxy and RequestID), as shown in the following figure. Backup Proxy is 172.18. 138.13, and RequestId is 0bd4d05b.
2. Use SSH to log in to the 172.18 and 138.13 nodes, switch to the (cd /opt/huawei-data-protection/ebackup/microservice/ebk_backup/logs) directory of the ebk_backup microservice, and run the following command:
zgrep 0bd4d05b ebk_backup.log* (The current request ID is 0bd4d05b. In other scenarios, adjust the parameter based on the request ID.)
As shown in the following figure, the logs show that multiple disk scanning attempts fail, and the production storage is https://172.18.XXX.XXX:8088.
3. Run the cat /sys/class/fc_host/host*/port_name command to obtain the WWN information of fc_host on the current node.
As shown in the following figure, the FC WWNs of the current eBackup node are 100000109b3afd22 and 100000109b3afd23, respectively.
(If the production storage is accessed in IP SAN mode, run the command to obtain the iqn:cat /etc/iscsi/initiatorname.iscsi of the local node.)
4. Log in to DeviceManager of the production storage and choose https://172.18.126.154:8088.Host > Initiator. Locate the host whose name is prefixed with eBackup and click to view the initiator information, as shown in the following figure. The initiator is offline. In this case, volumes cannot be attached to the production storage. Ask the customer to check the network. After the initiator recovers, retry the backup.
Applicable Version
All versions
