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
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- About MSDP Encryption using NetBackup Key Management Server service
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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
- About the cloud direct
- 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 managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Managing universal share services
- Troubleshooting issues related to universal shares
- 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
Mounting a universal share
Choose the mounting procedure that matches the type of universal share you created.
To mount an SMB universal share using Windows Explorer
- Log on to the Windows server, then navigate to the Map a Network Drive tool.
- Choose an available drive letter.
- Specify the mount path as follows:
\\<MSDP storage server>\<id>
For example, \\server.example.com\my-db-share
You can find the mount path on the NetBackup web UI: Storage > Disk storage > Universal shares.
- Click Finish.
To mount an SMB universal share using Windows command prompt
- Log on to the Windows server, then open a command prompt.
- Specify the mount path using the following command:
net use <drive_letter>:\\<MSDP storage server >\<id>
For example: net use <drive_letter>:\\<MSDP storage server >\<id>
- Specify the mount path as follows:
\\<MSDP storage server>\<id>
For example, \net use \\server.example.com\my-db-share
You can find the MSDP storage server name and the export path from the Universal share details page in the NetBackup web UI: Storage > Disk storage > Universal shares
To mount an NFS universal share
- Log on to the server as root.
- Create a directory for the mount point using the following command:
mkdir /mnt/<your_ushare_mount_point_subfolder>
- NFSv3 with krb5:
Mount the universal share using the following one of the following commands:
NFSv3:
mount -t nfs <MSDP storage server>:<export path> -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=3,timeo=600 /mnt/<your_ushare_mount_point_subfolder>
For example:
mount -t nfs server.example.com:/mnt/vpfs_shares/3cc7/3cc77559-64f8-4ceb-be90-3e242b89f5e9 -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=3,timeo=600 /mnt/<your_ushare_mount_point_subfolder>
NFSv4:
mount -t nfs <MSDP storage server> : <export path> -o vers=4.0,rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=4,timeo=600 /mnt/ <your_ushare_mount_point_subfolder>
Note:
If you use NFSv4 on a Flex Appliance application instance, the export path must be entered as a relative path. Do not include /mnt/vpfs_shares.
For example:
mount -t nfs server.example.com:/3cc7/3cc77559-64f8-4ceb-be90-3e242b89f5e9 -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=4,timeo=600 /mnt/<your_ushare_mount_point_subfolder>
For NetBackup FlexScale and AKS/EKS cloud platforms, if you use NFSv4 to mount the NFS share on NFS client, you must use the relative share path without the prefix
/mnt/vpfs_shares
.For example, if the export share path is engine1.com:/mnt/vpfs_shares/usha/ushare1, use NFSv4 to mount it on client as follows:
mount -t nfs -o 'vers=4' engine1.com:/usha/ushare1 /tmp/testdir.
To mount an NFS share with Kerberos based authentication for NFSv3 or NFSv4, use any of the three types of security options:
krb5
krb5i
krb5p
mount -t nfs <MSDP storage server>:<export path> -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=3,timeo=600,sec=krb5 /mnt/<your_ushare_mount_point_subfolder>
NFSv4 with krb5:
mount -t nfs <MSDP storage server>:<export path> -o rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=4,timeo=600,sec=krb5 /mnt/<your_ushare_mount_point_subfolder>
Use krb5 for authentication only.
krb5i computes a hash on every remote procedure (RPC) call request to the server and every response to the client. The hash is computed on an entire message: RPC header, plus NFS arguments or results.
krb5p uses encryption to provide privacy. With krb5p, NFS arguments and results are encrypted.
krb5 provides better performance and it decreases in the following order: krb5 > krb5i > krb5p.
You can find the mount path on the NetBackup web UI: Storage > Disk storage > Universal shares.