NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedules for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application-consistent snapshots
- Protecting AWS or Azure VMs for recovering to VMware
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Configuring storage for different deployments
- About incremental backup for PaaS workloads
- About archive redo log backup for PaaS workloads
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot cloud workload protection issues
- Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
- Backup from snapshot jobs take longer time than expected
- Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
- Error disambiguation in NetBackup UI
- Troubleshoot PaaS workload protection and recovery issues
Recovering images from Azure to VMware
Pre-requisites for the backed-up cloud images:
Change the network interface to use DHCP, enabled on boot.
To recover Windows 2022 VM images to VMware:
- Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
- For Windows 2022 Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
- Obtain the IP address to log on the converted VM through RDP.
Pre-requisites for the backed-up cloud images:
You need the VMW_PVSCSI driver in the source VM. To see if the driver already exists, run:
lsinitrd | grep -i vmw_pvscsi
To install the driver, do the following:
To backup
initramfs, run the following commands one by one:cd /boot
cp initramfs-`uname -r`.img initramfs-`uname -r`.img.bak
To open the
dracut.conffile, run:vi /etc/dracut.conf
Uncomment the line #add_drivers+="". Add the value "vmw_pvscsi" to the line, separating the existing module from the space. For example:
# additional kernel modules to the default. add_drivers+="vmw_pvscsi"To create new initial ramdisk images with new modules, run:
dracut -f -v -N
Run any of the following commands to check if the new modules exist in new initial ramdisk images:
lsinitrd | grep -i vmw_pvscsi
lsinitrd -f /boot/initramfs-`uname -r`.img | grep -i vmw_pvscsi
Create a new user to log on to the recovered VM.
Change the network interface to use DHCP, enabled on boot.
To recover RHEL 9.x VM images to VMware:
- Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
- For RHEL Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
- Obtain the IP address to log on the converted VM through SSH.
Pre-requisites for the backed-up cloud images:
Change the network interface to use DHCP, enabled on boot.
Create a new user to log on to the recovered VM.
To recover SUSE 15SP5 VM images to VMware
- Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
- If you do not have an existing vmw_pvscsi driver in the source VM, log on to the VMware server, and edit the Converted VM settings. In the Virtual Hardware page, click Hard disk, and then change the Virtual Device Node to IDE.
- For SUSE 15SP5 Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
- Obtain the IP address to log on to the converted VM through SSH.