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
MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure universal shares
The following are prerequisites for using the universal share MSDP build-your-own (BYO) server feature:
The universal share feature is supported on an MSDP BYO storage server with Red Hat Enterprise Linux 7.6 or later.
The universal share feature is not supported on SUSE Linux.
You must set up user authentication for the universal share.
NFS services must be installed and running if you want to use the share over NFS.
Samba services must be installed and running if you want to use share over CIFS/SMB.
You must configure Samba users on the corresponding storage server and enter the credentials on the client.
Ensure that the
nfs-utils
is installed:yum install nfs-utils -y
Ensure that the Linux samba and samba winbind packages are installed.
yum install samba samba-common samba-winbind samba-winbind-clients samba-winbind-modules -y
Ensure that the following commands are run to grant permissions to the SMB shares:
setsebool -P samba_export_all_rw on
setsebool -P samba_export_all_ro on
NGINX is installed and running.
Installing NGINX from Red Hat Software Collections:
Refer to https://www.softwarecollections.org/en/scls/rhscl/rh-nginx114/ for instructions.
Because the package name depends on the NGINX version, run yum search rh-nginx to check if a new version is available. (For NetBackup 8.3, an EEB is required if NGINX is installed from Red Hat Software Collections.)
Installing NGINX from the EPEL repository:
Refer to https://fedoraproject.org/wiki/EPEL for installation instructions of the repository and further information.
The EPEL repository is a volunteer-based community effort and not commercially supported by Red Hat.
Before you start the storage configuration, ensure that the new BYO NGINX configuration entry
/etc/nginx/conf.d/byo.conf
is included as part of the HTTP section of the original/etc/nginx/nginx.conf
file.If SE Linux has been configured, ensure that the
policycoreutils
andpolicycoreutils-python
packages are installed from the same RHEL yum source (RHEL server), and then run the following commands:semanage port -a -t http_port_t -p tcp 10087
setsebool -P httpd_can_network_connect 1
Enable the logrotate permission in SE Linux using the following command:
semanage permissive -a logrotate_t
After NGINX is installed, the HTTP web service at port 80 is enabled by default. Remove
/etc/nginx/conf.d/default.conf
or edit the file to disable the HTTP web service if it is not needed.Ensure that the
/mnt
folder on the storage server is not directly mounted by any mount points. Mount points should be mounted to its subfolders.If you configure the universal share feature on BYO after storage is configured or upgraded without the NGINX service installed, run the command:
/usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
Ensure that the required network ports are open.
See "NetBackup media server ports" in the NetBackup Network Ports Reference Guide.
Table: Hardware configuration requirements for universal shares on a Build Your Own (BYO) server
CPU |
Memory |
Disk |
---|---|---|
|
|
Disk size depends on the size of your backup. Refer to the hardware requirements for NetBackup and Media Server Deduplication Pool (MSDP). If a system has multiple data partitions, all the partitions must be the same size. Example: If a BYO server has a first partition at 4TB, all additional data partitions must be at 4TB in size. |