Creating a Mount Target

On Compute Cloud@Customer, A mount target is an NFS endpoint assigned to a subnet of your choice. The mount target provides the IP address or DNS name that's used in the mount command when connecting NFS clients to a file system.

You can create at most two mount targets per VCN: at most one mount target per pool type. Pool type refers to the backing store pool for the file system, which can be either the default pool of the attached ZFS Storage Appliance or a high performance pool. See the Backing store pool in Creating a File System. Two mount targets in a VCN are counted as one with regard to resource limits.

You can reuse a mount target to make many file systems available on the network. To reuse the same mount target for multiple file systems, create an export in the mount target for each file system. The file system and mount target must be in the same compartment and the same backing store pool when you create an export.

Caution

Don't use /30 or smaller subnets for mount target creation because they might not have enough available IP addresses.

Important

When exporting file systems to overlapping CIDRs in a VCN, exports to the longest CIDR (smallest network) must be done first. For more information and an example, see My Oracle Support article PCA File system as a Service Exports (Doc ID 2823994.1).

Before you can create a mount target, ensure that these items are configured:

  • At least one Virtual Cloud Network (VCN) and subnet is configured. See Managing VCNs and Subnets

  • (Required for Mounting File Systems Across Compute Cloud@Customer Infrastructures) A Dynamic Routing Gateway (DRG) with a route rule in the VCN. See Dynamic Routing Gateways (DRGs).
  • (Optional) Security rules for the file system mount target. Security rules can be created in the security list for the mount target subnet, or in a Network Security Group (NSG) that you add the mount target to. See Controlling Access to File Storage.

    You don't need security rules to create a mount target, but you do need security rules to eventually mount file systems that are associated with this mount target.

  • To ensure that the mount target is created using high performance storage, first configure the OraclePCA tag namespace and backing store pool (poolName) attribute in your OCI tenancy. See Creating OraclePCA Tags. Then when you create the mount target, assign the OraclePCA tag namesapce and poolName attribute to the mount target. The poolName property can be set only when the mount target is created. You cannot set or change this property value after the mount target is created.

Avoid entering confidential information in names and tags.

Was this article helpful?