NetBackup™ Deduplication Guide

To create a universal share in the NetBackup web UI

1. If necessary, configure an MSDP storage server.

   See Create a Media Server Deduplication Pool storage server in the NetBackup web UI.

2. On the left, click Storage > Disk storage.
3. Click on the Universal shares tab. Then click Add.

4. Provide the following required information:

   • Enter a Display name. This name is used in the universal share path.

   • Select a Type. If you want to set up Cloud cache properties, you must select Regular. If Accelerator type is selected, you must specify the Disk volume.

   • Select the Storage server.

   • Select the Disk volume.

     When Accelerator is selected in Type, you can only select a cloud disk volume that is configured on the MSDP storage server.

     Click the search icon to get the volume list, and select the disk volume. PureDiskVolume is selected by default.

     This option is available only if universal share with object storage in cloud feature is enabled.

   • In Cloud cache properties, specify the size of the local disk cache in the Request cloud cache disk space.

     The Request cloud cache disk space can only be set here on initial setup. Any subsequent changes must be made on the storage server properties page.

     Note:

     When you update the Cloud cache properties setting in storage server properties page, there is an interruption of the current shared mounts. When you click Save, the vpfsd process restarts to apply the new value.

     In addition, new universal shares cannot be created if the available size is less than 128GB.

   • Select the Protocol: NFS or SMB (CIFS)

     Select the Direct NFS check box to improve the performance of Network Attached Storage (NAS) over standard NFS for Oracle Databases. With direct NFS, the insecure export option is added to the export path on the NFS server.

     For example, /mnt/vpfs_shares/dnfs/dnfs client-abcd(rw,insecure,mp,fsid=4161bb04-f62f-40f3-af09-0d9a8713694b)

     See Use Direct Network File System to improve the performance of Network Attached Storage.

   • Specify a Host that is allowed to mount the share and then click Add to list. You can use the host name, IP address or range, short name, or the FQDN to specify the Host. You can enter multiple hosts for each share.

     NetBackup uses a set of rules to validate any wildcard characters that are used for the Host that you specify. More information about Host validation is available:

     See About Host wildcard validation for universal share creation.

     When Accelerator is selected in Type, the Host can only be FQDN.

5. At this point, continue to enter values in the remaining fields or click Save to save the universal share. You can update the remaining fields later from the universal share's details page:

   • Select a Quota type: Unlimited or Custom. If you select Custom, also specify the quota in MB, GB, or TB units.

     The Custom quota value limits the amount of data that is ingested into the share. Quotas are enforced using the front-end terabyte (FETB) calculation method. They are Implemented per share and can be modified at any time. You do not need to remount the share for the change to a take effect.

     To update the quote type or value from the universal share's details page, click Edit in the Quota section.

   • Specify the User names (Local or Active Directory) and the Group names (Active Directory only). Only the specified users or groups can access the share. You can add and update the User names and the Group Names later from the details page of an existing universal share.

     Note:

     Currently, the User names and the Group names are supported only for the SMB (CIFS) protocol.

   • Specify Kerberos security methods if the selected protocol is NFS and the Kerberos service is supported on the selected Storage server.

     If you select more than one Kerberos security methods, you can specify any method as mount command option to the share from client host.

     • Kerberos 5

       Uses Kerberos V5 instead of local UNIX UIDs and GIDs to authenticate the users.

     • Kerberos 5i

       Uses Kerberos V5 for user authentication and performs integrity checking of NFS operations using the secure checksums to prevent tampering of the data.

     • Kerberos 5p

       Uses Kerberos V5 for user authentication and integrity checking. It encrypts NFS traffic to prevent traffic sniffing. This option is the most secure setting but it also involves the most performance overhead.