NetBackup™ Web UI Cloud Administrator's Guide

Target: AWS

1. Perform the following steps to resolve the issue of restored AWS instance check fail and the instance is not reachable:

   • Connect to EC2 Serial Console, check if the network interface is up, and VM has started with all mount points.

     If you get the following failure message while accessing EC2 Serial Console, change the instance type of VM to the one which supports EC2 Serial Console:

     This instance type is not supported for the EC2 serial console.

   • You might be logged into rescue mode if some critical mount points fail:

     • Check if the following articles are applicable:

       • XFS reports "Log inconsistent (didn't find previous header)" when trying to mount filesystem

       • Unable to mount or check XFS filesystem

     • Check if all partitions are mountable, if not, further troubleshooting might be required to find out why they are failing.

     • Drives with mount failures can be detached from the impaired VM and attached to a healthy instance in the same availability zone for further troubleshooting.

   • If mounting succeeds and there are no failures, try restarting before the next steps, till you can boot into user space.

2. If the VM is configured with PasswordAuthentication password check entry in /etc/ssh/sshd_config file, then set the value to Yes.
3. If it is configured with PubkeyAuthentication ssh key, then set the value of the entry in /etc/ssh/sshd_config file to Yes.
4. Update the device names in /etc/fstab file if they were not replaced with UUID during pre-backup.

   For example, change /dev/sdc1 → /dev/nvme1n1p1. This allows to establish the network connection.

5. Now you can troubleshoot any mount failures and logon by ssh from any non-CSP Serial Console.

Target: AWS

Perform the following steps to resolve the issue of restored AWS instance check fail and the instance is not reachable:

1. Connect to EC2 Serial Console, check if the network interface is up, and VM has started with all mount points.

   If you get the following failure message while accessing EC2 Serial Console, change the instance type of VM to the one which supports EC2 Serial Console:

   This instance type is not supported for the EC2 serial console.

2. If the VM has booted into emergency mode further troubleshooting might be required.
3. Try mounting all partitions with mount -a command. If f it fails, check if the following article is applicable:

   How to perform filesystem check (fsck) in the rescue mode?

4. While restarting, the cloud-init service might cause the VM to get stuck in network configuration. Reconfigure or stop, disable, and uninstall/remove cloud-init service using the following respective commands:

   systemctl stop cloud-init

   systemctl disable cloud-init

   zypper remove cloud-init

   If required, reinstall cloud-init service after a restart.

5. Restart the VM.
6. During restart select AWS kernel from the GRUB menu.
7. Check the mount points.
8. Check the status of the network interface with ip addr command. If it is up you should be able to log on by SSH externally, else try SSH troubleshooting.

Target: AWS

Perform the following steps to resolve the issue of restored AWS instance check fail and the instance is not reachable.

1. Stop and Start the VM.
2. Log on using EC2 Serial Console and switch to superuser.
3. Disable Azure-specific services if any:

   systemctl disable hv-kvp-daemon.service
   systemctl disable walinuxagent.service
   systemctl disable walinux-agent

4. Reconfigure the data source for cloud-init service to point it to EC2 data source, and disable any Azure cloud-specific configurations:

   • dpkg-reconfigure cloud-init

   • Few configuration files can be moved or renamed.

     For example,

     mv /etc/cloud/cloud.cfg.d/10-azure-kvp.cfg /etc/cloud/cloud.cfg.d/10-azure-kvp.cfg.disabled

     mv /etc/cloud/cloud.cfg.d/90-azure.cfg /etc/cloud/cloud.cfg.d/90-azure.cfg.disabled

   • cloud-init clean --logs

5. Set the default kernel to AWS by changing the value of GRUB_DEFAULT entry in /etc/default/grub file:

   By default we have GRUB_DEFAULT=0 in /etc/default/grub file. Change it to: GRUB_DEFAULT='1>KERNEL_INDEX' where the value of KERNEL_INDEX can be found with update-grub command.

6. Restart the VM.
7. If there is any issue after restart, enter the recovery mode for AWS kernel and drop to root shell prompt to perform any troubleshooting steps.