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.