Linux BMR No Network After Reboot (GUI cannot connect)
This is usually seen on Linux BMR in OnAPP with CentOS v7.x VM's (onapp makes some changes when booting into ISO's on CentOS v7.x)
Select the first recover option on boot - login with root and empty password.
Run "ifconfig -a" and check device name (ens3 is result in our example)
Next, reboot and pres tab key under first or second boot option and type:
ip=IP nm=mask gw=getaway netdev=device name from ifconfig.
Example below
After boot you should now be able reach vm via network from the Clusterlogics GUI and can continue with the recovery process normally
Related Articles
Linux BMR No Network After Reboot (GUI cannot connect)
This is usually seen on Linux BMR in OnAPP with CentOS v7.x VM's (onapp makes some changes when booting into ISO's on CentOS v7.x) Select the first recover option on boot - login with root and empty password. Run "ifconfig -a" and check device name ...Linux BMR (ReaR)
Bare Metal Restore (ReaR) Bacula4 has developed a new Linux BMR tool. This is more tightly integrated with our GUI and is based on the ReaR *nix server imaging technology. To activate Bare Metal Restore (ReaR) simply enable it on the backup wizard: ...Linux BMR (ReaR)
Bacula4 has developed a new Linux BMR tool. This is more tightly integrated with our GUI and is based on the ReaR *nix server imaging technology. This new Linux BMR replaces the legacy/original Linux BMR found HERE For existing customers, using the ...New Linux (ReaR) BMR announced
Hello today we are pleased to announce the launch of our new Linux (ReaR) BMR solution. With this new Linux BMR utility, we are able to support practically every flavour of *.nix systems, and have brought the BMR process into our GUI. A much more ...Linux BMR
How to perform a Linux BMR 1. Load and boot the iso or USB image (available for download from your Bacula4Hosts Portal) *USE THE LATEST STABLE VERSION (NON BETA) AVAILABLE. USE ALTERNATE VERSIONS IF THERE ARE DRIVER ISSUES (IE OLDER HARDWARE) OR IF ...