NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Disaster recovery in S3 interface for MSDP
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
Converting RHEL 8.6 VM image to VHD
Pre-requisites:
The boot options of the source VMs are BIOS or UEFI. Use the standard partitions rather than a logical volume manager (LVM), which is the default for many installations.
Use the persistent naming (file system label or UUID) in
fstab
configuration.Ensure that the operating system is installed on the first disk of the source VM. Do not configure a swap partition on the operating system disk.
We recommend that the network interface in the source VM uses DHCP and enabled on start.
See Prepare a Red Hat-based virtual machine for Azure
To convert the RHEL 8.6 VM image to VHD
- Install Hyper-V device drivers and rebuild the
initramfs
image file.Check if the Hyper-V drivers (hv_netvsc, hv_storvsc, hv_vmbus) are installed or not.
lsinitrd | grep hv
If they are not installed, perform the following steps.
Back up the previous
initramfs
image file.cd /boot cp initramfs-`uname -r`.img initramfs-`uname -r`.img.bak
Create a file
hv.conf
under the directory/etc/dracut.conf.d
. Add the following driver parameters to thehv.conf
file.add_drivers+=" hv_vmbus " add_drivers+=" hv_netvsc " add_drivers+=" hv_storvsc " add_drivers+=" nvme "
Note:
Add the spaces between the quotes and the driver name.
Create new initial ramdisk images with new modules.
dracut -f -v -N -regenerate-all
Check if the new modules exist in new initial ramdisk images.
lsinitrd | grep -i hv
- Rename the network interface to the name eth0 and enable the NIC on boot.
Azure Linux VMs use traditional NIC names by default.
In the network interface configuration file, configure ONBOOT=yes.
For example,
mv /etc/sysconfig/network-scripts/ifcfg-ens192 /etc/sysconfig/network-scripts/ifcfg-eth0 sed -i 's/ens192/eth0/g' /etc/sysconfig/network-scripts/ifcfg-eth0
- Regenerate the
grub.cfg
for the kernel boot options.To use the traditional NIC names in the file
/etc/default/grub
, change the line GRUB_CMDLINE_LINUX="xxxxxxx" to GRUB_CMDLINE_LINUX="xxxxxxx net.ifnames=0"Remove the following parameters if they exist: rhgb quiet crashkernel=auto
Regenerate the
grub.cfg
file.On a BIOS-based computer: grub2-mkconfig -o /boot/grub2/grub.cfg
On a UEFI-based computer: grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
- Perform a new full backup of the source VM.
- Prepare the image sharing server and configure the image sharing feature with azure account.
- Import the backup image and perform the conversion.
- Verify the converted VHD files.
In the Azure web portal:
Create a disk with the converted .vhd file.
Create a VM with the previous disk.
Navigate to Disks > Created disk > Create VM. With default Networking & Disks & Management settings, enable the boot diagnostics.
Log in to the converted VM through SSH.