Troubleshooting Veeam Issues

Restored VM can't access LAN and the Internet

Veeam client error: file does not exist or locked

Veeam: Error: su: incorrect password

Veeam: Failed to login by SSH, port 22, , elevateToRoot Fals

Restored VM can't access LAN and the Internet

Situation: After using Veeam FastSCP to copy a VM on ESX 4.0 and then restore it on ESX 4.1 running on a different hardware, the client can't access the LAN and the Internet.

Case 1: IPCONFIG doesn't show any NIC. The Device Manager shows NIC with yellow !.

Resolution: Re-install NIC drive.

Case 2: The Device Manager shows NIC fine. IPCONFIG doesn't show any NIC.

Resolution: The VM hasn't been assigned vSwitch. Login vCenter Client and select the VM. Click Edit Settings. Check the Network adapter status. If it is empty, highlight Network adapter. Select the vSwitch in Network label as shown below.

Case 3: after restoring a VM from backup using Veeam Backup, the client can't logon Guest OS running windows because the original VM is running in the same subnet with same hostname and iP address.

Resolution: Shutdown the original VM and disjoin the restored VM from the domain. then rejoin it to the domain.

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics