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
Troubleshooting universal share configuration issues
To configure a universal share, ensure that instant access is enabled on the storage server. For more information about instant access, see the following guides:
To ensure that instant access is enabled on the storage server
- Log on to the storage server and run the following command (build your own (BYO) only):
/usr/openv/pdde/vpfs/bin/ia_byo_precheck.sh
- Review the pre-condition checking results and the configuration results:
/var/log/vps/ia_byo_precheck.log
(BYO only)/usr/openv/pdde/vpfs/vpfs-config.log
(BYO and appliance configurations)In the following example, several required services are not running:
[root@rhelnbu06 ~]# /usr/openv/pdde/vpfs/bin/ia_byo_precheck.sh Mon Apr 13 12:42:14 EDT 2020 Try to get storagepath Mon Apr 13 12:42:14 EDT 2020 Storage ContentRouter config path is /msdp/etc/puredisk/contentrouter.cfg Mon Apr 13 12:42:14 EDT 2020 Storagepath is /msdp Mon Apr 13 12:42:14 EDT 2020 File system for partition /msdp is ext2/ext3 Mon Apr 13 12:42:14 EDT 2020 File system for partition /msdp/data is ext2/ext3 Mon Apr 13 12:42:14 EDT 2020 **** Hardware Virtualization not supported, Instant Access browse may be slow **** Mon Apr 13 12:42:14 EDT 2020 **** system memory support 50 vpfs livemounts **** Mon Apr 13 12:42:14 EDT 2020 **** nginx service required by Instant Access is not running **** Mon Apr 13 12:42:14 EDT 2020 **** smb service required by Instant Access is not running **** Mon Apr 13 12:42:14 EDT 2020 **** docker service required by VMware Instant Access is not running ****
- Resolve the issues that are identified in the log. For example, restart any services that are required for instant access.
To ensure that the storage server has universal share capability
- Make sure that the storage service is running NetBackup 8.3 or later.
- Log on to the storage server and run the following command:
nbdevquery -liststs -U
Make sure that the InstantAcess flag is listed in the command's output.
If the flag is not listed, see one of the guides mentioned above to enable instant access on the storage server.
- Run the following command:
nbdevconfig -getconfig -stype PureDisk -storage_server storage_server_name
Make sure that the UNIVERSAL_SHARE_STORAGE flag is listed in the command's output.
If the flag is not listed, create a universal share on the storage server:
A universal share can be started, restarted, or stopped with NetBackup services:
Use the following command to start or restart a universal share:
netbackup start
Use the following command to stop universal share:
netbackup stop
Whenever a universal share is created on the NetBackup web UI, a mount point is also created on the storage server.
For example:
[root@rsvlmvc01vm309 vpfs.mnt]# mount | grep vpfs vpfsd on /mnt/vpfs type fuse.vpfsd (rw,nosuid,nodev,relatime,user_id=0, group_id=0,default_permissions,allow_other) vpfsd on /mnt/vpfs_shares/aa7e/aa7e83e5-93e4-57ea-a4a8-81ddbf5f819e type fuse.vpfsd (rw,nosuid,nodev,relatime,user_id=0,group_id=0, default_permissions,allow_other)
In this example, aa7e83e5-93e4-57ea-a4a8-81ddbf5f819e
is the universal share's ID. This ID is found on the details page of the universal share in the NetBackup web UI: On the left, click and then select the universal share to view its details.