NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Planning your deployment
- Planning your MSDP deployment
- NetBackup naming conventions
- About MSDP deduplication nodes
- About the NetBackup deduplication destination
- About MSDP capacity support and hardware requirements
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About the NetBackup Deduplication Engine credentials
- About the network interface for MSDP
- About MSDP port usage
- About MSDP optimized synthetic backups
- About MSDP and SAN Client
- About MSDP optimized duplication and replication
- About MSDP stream handlers
- MSDP deployment best practices
- Use fully qualified domain names
- About scaling MSDP
- Send initial full backups to the storage server
- Increase the number of MSDP jobs gradually
- Introduce MSDP load balancing servers gradually
- Implement MSDP client deduplication gradually
- Use MSDP compression and encryption
- About the optimal number of backup streams for MSDP
- About storage unit groups for MSDP
- About protecting the MSDP data
- Save the MSDP storage server configuration
- Plan for disk write caching
- Provisioning the storage
- Configuring deduplication
- Configuring media server deduplication in NetBackup
- Configuring MSDP client-side deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- About the MSDP fingerprint cache
- Configuring the MSDP fingerprint cache behavior
- MSDP fingerprint cache behavior options
- About seeding the MSDP fingerprint cache for remote client deduplication
- Configuring MSDP fingerprint cache seeding on the client
- Configuring MSDP fingerprint cache seeding on the storage server
- NetBackup seedutil options
- About sampling and predictive cache
- Rebuilding the sampling cache
- Enabling 400 TB support for MSDP
- 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 compression
- About MSDP encryption
- About MSDP Encryption using NetBackup Key Management Server service
- About MSDP Encryption using external KMS server
- Configuring optimized synthetic backups for MSDP
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- About the media servers for MSDP optimized duplication within the same domain
- About MSDP push duplication within the same domain
- About MSDP pull duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring NetBackup optimized duplication or replication behavior
- Setting NetBackup configuration options by using the command line
- About MSDP replication to a different domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- About trusted primary servers for Auto Image Replication
- About the certificate to use to add a trusted primary server
- Add a trusted primary server
- Remove a trusted primary server
- Enable inter-node authentication for a NetBackup clustered primary server
- Configuring NetBackup CA and NetBackup host ID-based certificate for secure communication between the source and the target MSDP storage servers
- Configuring external CA for secure communication between the source MSDP storage server and the target MSDP storage server
- Configuring a target for MSDP replication to a remote domain
- About configuring MSDP optimized duplication and replication bandwidth
- About performance tuning of optimized duplication and replication for large images
- About performance tuning of optimized duplication and replication for MSDP cloud
- About storage lifecycle policies
- About MSDP backup policy configuration
- Creating a backup policy
- Resilient network properties
- Adding an MSDP load balancing server
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About the MSDP contentrouter.cfg file
- About saving the MSDP storage server configuration
- Setting the MSDP storage server configuration
- About the MSDP host configuration file
- Deleting an MSDP host configuration file
- Resetting the MSDP registry
- About protecting the MSDP catalog
- About MSDP FIPS compliance
- Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
- About MSDP multi-domain support
- About MSDP application user support
- About MSDP mutli-domain VLAN Support
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- Running MSDP commands with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- MSDP volume group requirements
- Configuring an MVG server using the web UI
- Creating an MVG volume using the web UI
- Configuring an MVG server using the command-line
- Creating an MVG volume using the command-line
- Updating an MVG volume using the command-line
- Configuring the targeted AIR with an MVG volume
- Updating an MVG volume using the web UI
- Listing the MVG volumes
- Deleting an MVG volume
- Configuring the MSDP server to be used by an MVG server having different credentials
- Migrate a backup policy from a regular MSDP disk volume to the MVG volume
- Migrate a backup policy from an MVG volume to a regular MSDP disk volume
- Assigning a client policy combination to another MSDP server
- Removing an MVG server configuration
- MSDP volume group disaster recovery
- The MSDP server maintenance
- Limitations of the MSDP volume group
- About the node failure management
- MSDP volume group best practices
- MSDP commands for MVG maintenance
- Troubleshooting the MVG errors
- MSDP cloud support
- About MSDP cloud support
- Create a Media Server Deduplication Pool storage server in the NetBackup web UI
- Managing credentials for MSDP-C
- Creating a cloud storage unit
- Updating cloud credentials for a cloud LSU
- Updating encryption configurations for a cloud LSU
- Deleting a cloud LSU
- Backup data to cloud by using cloud LSU
- Duplicate data cloud by using cloud LSU
- Configuring AIR to use cloud LSU
- About backward compatibility support
- About the configuration items in cloud.json, contentrouter.cfg, and spa.cfg
- Cloud space reclamation
- About the tool updates for cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About restore from a backup in Microsoft Azure Archive
- About Cohesity Alta Recovery Vault Azure and Amazon
- Configuring Veritas Alta Recovery Vault Azure and Azure Government
- Configuring Veritas Alta Recovery Vault Azure and Azure Government using the CLI
- Configuring Veritas Alta Recovery Vault Amazon and Amazon Government
- Configuring Cohesity Alta Recovery Vault Amazon and Amazon Government using the CLI
- Migrating from standard authentication to token-based authentication for Recovery Vault
- About MSDP cloud immutable (WORM) storage support
- Creating a cloud immutable storage unit using the web UI
- Updating a cloud immutable volume
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About object-level immutable storage support for Google Cloud Storage
- About using the cloud immutable storage in a cluster environment
- Troubleshooting the errors when disk volume creation using web UI fails
- Deleting the immutable image with the enterprise mode
- Deleting the S3 object permanently
- About MSDP cloud admin tool
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About instant access for object storage
- About NetBackup support for AWS Snowball Edge
- Upgrading to NetBackup 10.3 and cluster environment
- About the cloud direct
- About MSDP lazy delete
- S3 Interface for MSDP
- About S3 interface for MSDP
- Prerequisites for MSDP build-your-own (BYO) server
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 Object Lock In Flex WORM
- S3 APIs for S3 interface for MSDP
- Creating a protection policy for the MSDP object store
- Recovering the MSDP object store data from the backup images
- Instant access for MSDP object store
- Disaster recovery in S3 interface for MSDP
- Limitations in S3 interface for MSDP
- Logging and troubleshooting
- Best practices
- Monitoring deduplication activity
- Monitoring the MSDP deduplication and compression rates
- Viewing MSDP job details
- About MSDP storage capacity and usage reporting
- About MSDP container files
- Viewing storage usage within MSDP container files
- About monitoring MSDP processes
- Reporting on Auto Image Replication jobs
- Checking the image encryption status
- Managing deduplication
- Managing MSDP servers
- Viewing MSDP storage servers
- Determining the MSDP storage server state
- Viewing MSDP storage server attributes
- Setting MSDP storage server attributes
- Changing MSDP storage server properties
- Clearing MSDP storage server attributes
- About changing the MSDP storage server name or storage path
- Changing the MSDP storage server name or storage path
- Removing an MSDP load balancing server
- Deleting an MSDP storage server
- Deleting the MSDP storage server configuration
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Viewing Media Server Deduplication Pools
- Determining the Media Server Deduplication Pool state
- Viewing Media Server Deduplication Pool attributes
- Setting a Media Server Deduplication Pool attribute
- Changing a Media Server Deduplication Pool properties
- Clearing a Media Server Deduplication Pool attribute
- Determining the MSDP disk volume state
- Changing the MSDP disk volume state
- Deleting a Media Server Deduplication Pool
- Analyzing the disc space consumption of the backup images
- Deleting backup images
- About MSDP queue processing
- Processing the MSDP transaction queue manually
- About MSDP data integrity checking
- About managing MSDP storage read performance
- About MSDP storage rebasing
- About the MSDP data removal process
- Resizing the MSDP storage partition
- How MSDP restores work
- Configuring MSDP restores directly to a client
- About restoring files at a remote site
- About restoring from a backup at a target primary domain
- Specifying the restore server
- Enabling extra OS STIG hardening on WORM storage server instance
- Using multiple MSDP nodes for multistream backups on MSDP cluster
- Enabling the media server and MSDP engine affinity in the MSDP cluster
- 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
- Mounting a universal share
- Creating a protection point for a universal share
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Preparing NetBackup for the universal share accelerator
- Installing the universal share accelerator
- Creating a protection policy for the universal share accelerator
- Configure a universal share accelerator
- About the universal share accelerator quota
- Recovering a point in time for the universal share accelerator
- Deleting a recovered universal share accelerator
- Logging for universal share accelerator
- Load backup data to a universal share with the ingest mode
- Universal share with disabled MSDP data volumes
- Universal Share WORM capability
- Universal share scale out
- Managing universal share services
- Troubleshooting issues related to universal shares
- Configuring isolated recovery environment (IRE)
- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a NetBackup BYO media server
- Managing an isolated recovery environment on a NetBackup BYO media server
- Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment
- Configuring an isolated recovery environment on a WORM storage server
- Managing an isolated recovery environment on a WORM storage server
- Configuring data transmission between a production environment and an IRE WORM storage server
- Replicating the backup images from the IRE domain to the production domain
- Using the NetBackup Deduplication Shell
- About the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Adding and removing local users from the deduplication shell
- Adding MSDP users from the deduplication shell
- Adding MSDP admin alias users from the deduplication shell
- Connecting an Active Directory domain to a WORM or an MSDP storage server for Universal Shares and Instant Access
- Disconnecting an Active Directory domain from the deduplication shell
- Changing a user password from the deduplication shell
- Managing VLAN interfaces from the deduplication shell
- Managing the retention policy on a WORM storage server
- Managing images with a retention lock on a WORM storage server
- Auditing WORM retention changes
- Protecting the MSDP catalog from the deduplication shell
- About the external MSDP catalog backup
- Managing certificates from the deduplication shell
- Managing FIPS mode from the deduplication shell
- Managing post-quantum cryptography (PQC) mode from the deduplication shell
- Encrypting backups from the deduplication shell
- Tuning the MSDP configuration from the deduplication shell
- Setting the MSDP log level from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Managing the cyclic redundancy checking (CRC) service
- Managing the content router queue processing (CRQP) service
- Managing the online checking service
- Managing the compaction service
- Managing the deduplication (MSDP) services
- Managing the MSDP services across the cluster
- Managing the Storage Platform Web Service (SPWS)
- Managing Open Cloud Storage Daemon
- Managing the Cohesity provisioning file system (VPFS) configuration parameters
- Managing the Cohesity provisioning file system (VPFS) mounts
- Managing the NGINX service
- Managing the SMB service
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing the health monitor
- Viewing information about the system
- Viewing the deduplication (MSDP) history or configuration files
- Viewing process information in the pseudo-file system
- Viewing the deduplication rate of a Veritas provisioning file service (VPFS) share
- Viewing the log files
- Collecting and transferring troubleshooting files
- Managing S3 service from the deduplication shell
- Multi-person authorization for deduplication shell commands
- Managing cloud LSU in Flex Scale and Cloud Scale
- Managing the NFS version 3 server services for the MSDP container
- Viewing the NetBackup RBAC roles assigned to the MSDP container
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup MSDP log files
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Verify that the MSDP server has sufficient memory
- MSDP backup or duplication job fails
- MSDP client deduplication fails
- MSDP volume state changes to DOWN when volume is unmounted
- MSDP errors, delayed response, hangs
- Cannot delete an MSDP disk pool
- MSDP media open error (83)
- MSDP media write error (84)
- MSDP no images successfully processed (191)
- MSDP storage full conditions
- Troubleshooting MSDP catalog backup
- Storage Platform Web Service (spws) does not start
- Disk volume API or command line option does not work
- Viewing MSDP disk errors and events
- MSDP event codes and messages
- Unable to obtain the administrator password to use an AWS EC2 instance that has a Windows OS
- Trouble shooting multi-domain issues
- Troubleshooting the cloud compaction error messages
- Troubleshooting the msdpcmdrun issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About migration from Cloud Catalyst to MSDP direct cloud tiering
- About Cloud Catalyst migration strategies
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- About postmigration configuration and cleanup
- About the Cloud Catalyst migration -dryrun option
- About Cloud Catalyst migration cacontrol options
- Reverting back to Cloud Catalyst from a successful migration
- Reverting back to Cloud Catalyst from a failed migration
- Appendix C. Encryption Crawler
- Index
Use Direct Network File System to improve the performance of Network Attached Storage
Direct Network File System (dNFS) provides performance improvements for Network Attached Storage (NAS) over standard NFS for Oracle Databases. Direct NFS allows Oracle software to skip the operating system's NFS client when it communicates with a storage server. Direct NFS also improves High Availability (HA) and scalability by supporting up to four parallel network paths to storage and load-balancing across these paths. These improvements result in cost savings for database storage.
NFS servers must have write size values (wtmax) of 32768 or higher.
NFS mount points must be mounted both by operating system NFS client and Direct NFS client.
Set the NFS buffer size parameters rsize and wsize to at least 1048576 using the following command:
rsize and wsize
nfs_server:/vol/DATA/oradata /mnt/ nfs\ rw,bg,hard,nointr,rsize=1048576,wsize=1048576,tcp,actimeo=0,vers=3,timeo=600
Ensure that the TCP network buffer size is large enough to not hinder Direct NFS performance. The following command can verify the TCP buffer size:
sysctl -a |grep -e net.ipv4.tcp_[rw]mem
TCP buffer output
net.ipv4.tcp_rmem = 4096 87380 1056768
net.ipv4.tcp_wmem = 4096 16384 1056768
To change the buffer size, open
/etc/sysctl.confas root and modify the following values:sysctl.conf
net.ipv4.tcp_rmem = 4096 87380 4194304
net.ipv4.tcp_wmem = 4096 16384 4194304
Before running
sysctl -p, restart the network with /etc/rc.d/init.d/network restart.
To enable Direct NFS, run the following commands and restart the database instance:
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dnfs_on
To enable Direct NFS, run the following commands and remove the oranfstab file:
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dnfs_off
In the following directories of Direct NFS, search for the oranfstab file where the first matching entry (of the file) is the mount point. You can update the file to set up multipathing and handle other configuration details.
$ORACLE_HOME/dbs
/var/opt/oracle
/etc/mnttab
Use the following list of parameters to create the oranfstab file for each NFS server that you want to access using Direct NFS:
Table: Parameters to create the oranfstab file
Parameter | Usage |
|---|---|
Server | Unique identifier for the NFS server. |
Local | Network paths (up to 4) on the database host. |
Path | Network paths (up to 4) on the NFS server. |
Export | The exported volume on the NFS server. |
Mount | The local mount point for the exported volume. |
mnt_timeout | Time in seconds to wait for the first mount. |
dontroute | The operating system routing of outgoing messages is prevented. |
management | Network path for NFS server management interface. |
nfs_version | The NFS protocol version that the Direct NFS client uses. |
security_default | The default security mode that is applicable for all the exported NFS server paths for a server entry. |
security | The security level to enable security with the Kerberos authentication protocol with Direct NFS client. |
community | The community string for use in SNMP queries. |
Sample output of an oranfstab file.
server: myNFSServer1 local: 192.168.1.1 path: 192.168.1.2 local: 192.168.2.1 path: 192.168.2.2 local: 192.168.3.1 path: 192.168.3.2 local: 192.168.4.1 path: 192.168.4.2 export: /vol/oradata1 mount: /mnt/oradata1 export: /vol/oradata2 mount: /mnt/oradata2 mnt_timeout: 600
Ensure that you set up the oradism file at the following path: $ORACLE_HOME/bin/oradism. Direct NFS uses this oradism binary to issue mounts as root. The file must be local to each node and with the ownership of a root user.
To ensure that the file is local to each node, run the chown root $ORACLE_HOME/bin/oradism command. Run chmod 4755 $ORACLE_HOME/bin/oradism to ensure that the oradism file has the correct access permissions.
Refer to the contents of the following tables for client monitoring.
Table: v$ tables
Item | Description |
|---|---|
| Lists the NFS servers that the Direct NFS client has mounted. |
| Lists the files that the Direct NFS client has opened. |
| Lists the TCP connections that are established from the NFS server to Direct NFS. |
| Lists the statistics on the different NFS operations that the Oracle processes have issued. |
Ensure that Oracle 11g software or later is installed using the Oracle installer on the Windows server.
Create and configure the oranfstab file. You must add the oranfstab file in the %ORACLE_HOME%\dbs directory. Ensure that any file extension (for example, text file - txt) is added in the file name.
Configure the oranfstab as in the following way:
C:\>type %ORACLE_HOME%\dbs\oranfstab server: lnxnfs <=== NFS server Host name path: 10.171.52.54 <--- First path to NFS server ie NFS server NIC local: 10.171.52.33 <--- First client-side NIC export: /oraclenfs mount: y:\ uid:1000 gid:1000 C:\>
The Direct NFS client uses the UID or the GID value to access all NFS servers that are listed in the oranfstab file. Direct NFS ignores a UID or the GID value of 0. The UID and the GID used in the earlier example is of an Oracle user from the NFS server.
The exported path from the NFS server must be accessible for read, write, and run operations by the Oracle user with the UID and the GID specified in the oranfstab file. If neither UID nor GID is listed, the default value of 65534, is used to access all NFS servers listed in oranfstab file.