Veritas 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 KMS 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
- Configuring deduplication to the cloud with NetBackup Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst storage server for deduplication to the cloud
- MSDP cloud support
- About MSDP cloud support
- 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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
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 is supported on an MSDP BYO storage server with Red Hat Enterprise Linux 7.6, 7.7, 7.8, or 7.9.
NFS services are installed and running if you want to use the share over NFS
Samba services are 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.
If the Samba service is part of a Windows domain, the Windows domain users can use the Samba share. In this scenario, credentials are not required to access the share.
If the Samba service is not part of Windows domain, perform the following steps:
For a NetBackup Appliance, local users are also Samba users. To manage local users, log in to the CLISH and select Main > Settings > Security > Authentication > LocalUser. The Samba password is the same as the local user's login password.
For an MDSP BYO server, create a Linux user (if one does not exist). Then, add the user to Samba.
For example, the following commands create a test_samba_user use for the Samba service only:
# adduser --no-create-home -s /sbin/nologin test_samba_user
# smbpasswd -a test_samba_user
To add an existing user to the samba service, run the following command:
# smbpasswd -a username
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.
The NGINX version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (epel).
Before you start the storage configuration, ensure that the new BYO NGINX configuration entry
/etc/nginx/conf.d/byo.conf
will be 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
Ensure that the
/mnt
folder on the storage server is not mounted by any mount points directly. Mount points should be mounted to its subfolders.
If you are configuring the universal share feature on BYO after storage is configured or upgraded without the NGINXx service installed, run the command:
/usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
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). |