Managing Mount Targets

A mount target is an NFS endpoint that lives in a chosen VCN subnet and provides network access for file systems. The mount target provides the IP address or DNS name that's used together with a unique export path to mount the file system. When you use the Console to create your first file system, the workflow also creates a mount target and export for it.

You can reuse the same mount target to make as many file systems available on the network as you need. To reuse the same mount target for multiple file systems, create an export in the mount target for each file system.

You can perform the following mount target management tasks:

• Creating a Mount Target
• Listing Mount Targets
• Getting a Mount Target's Details
• Editing a Mount Target
• Moving a Mount Target Between Compartments
• Getting Mount Command Samples
• Creating an Export
• Editing an Export and Export Options
• Setting a File System's Reported Size
• Updating Mount Target Performance
• Locking a Mount Target
• Deleting a Mount Target

When changing a mount target's performance level, you can select a level that corresponds to maximum throughput. You don't need to re-create the mount target if requirements change. The performance level of a mount target can be either a Standard type or a High Performance type.

Performance level maximum throughput is measured for reads where the block size is 1 MiB or greater with sufficient concurrency and queue depth. Maximum throughput isn't available to hydrating clones until hydration is complete.

Standard mount targets have a maximum throughput, but no storage capacity entitlement. File systems exported through a standard mount target are billed based on usage. For more information, see File System Usage and Metering.

High Performance mount targets have a maximum throughput and a storage capacity entitlement. If the storage usage in the availability domain is equal to or greater than the total entitlement, there's no additional charge for high performance mount targets. To calculate the total billable storage usage, compare the total capacity entitlement for all high performance mount targets to the actual storage used in the availability domain. Whichever amount is larger is the billable usage.

A high performance mount target requires a 30-day billing commitment. After upgrading a mount target, the billing cycle begins. Because of this commitment, when you change a high performance mount target to a lower performance level, the mount target performance is downgraded when the billing cycle ends. To find mount target throughput and billing cycle, see Getting a Mount Target's Details.

For specific pricing details, see Oracle Storage Cloud Pricing.

The mount target details page provides the following information about a mount target:

MOUNT TARGET OCID

Every Oracle Cloud Infrastructure resource has an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). You need your mount target's OCID to use the Command Line Interface (CLI) or the API. You also need the OCID when contacting support.

CREATED

The date and time that the mount target was created.

Availability Domain

When you create a mount target, you specify the availability domain that it resides in. An availability domain is one or more data centers located within a region. You need your mount target's availability domain to use the Command Line Interface (CLI) or the API. For more information, see Regions and Availability Domains.

COMPARTMENT

When you create a mount target, you specify the compartment that it resides in. A compartment is a collection of related resources (such as cloud networks, compute instances, or file systems) that are accessible only to those groups that have been given permission by an administrator in your organization. You need your mount target's compartment to use the Command Line Interface (CLI) or the API. For more information, see Managing Compartments.

REPORTED SIZE (GIB)

The maximum capacity in gibibytes reported by the file systems exported through this mount target. The File Storage service currently reports 8589934592 gibibytes (GiB) of available capacity by default. If you are installing an application that requires a specific reported size, you can change the reported size. Typically, setting the size to 1024 GiB is sufficient for most applications. This value is updated hourly. See Setting a File System's Reported Size for more information.

REPORTED INODES (GII)

The maximum capacity in gibiinodes reported by the file systems exported through this mount target. The File Storage service currently reports gibiinodes (GiI) of available inodes by default. If you are installing an application that requires specific reported inodes, you can change the reported inodes. Typically, setting the inodes to 1024 GiI is sufficient for most applications. This value is updated hourly. See Setting a File System's Reported Size for more information.

NETWORK SECURITY GROUPS

The network security groups that the mount target belongs to. Each mount target can belong to up to five (5) NSGs. See Adding a Mount Target to a Network Security Group for more information.

MOUNT TARGET THROUGHPUT

The requested read throughput for the mount target in gigabits per second (Gbps). This value only differs from Billed Throughput if there's been a request to downgrade the mount target's performance. This throughput will be available after the current billing cycle ends, unless the request is canceled or the mount target is deleted. The API calls this requestedThroughput. For more information, see Mount Target Performance.

BILLED THROUGHPUT

Current read throughput for the mount target in gigabits per second (Gbps). The API calls this observedThroughput. For more information, see Mount Target Performance.

CAPACITY ENTITLEMENT

The capacity entitlement for the mount target, if the mount target uses a high performance shape. For more information, see Mount Target Performance.

BILLING CYCLE ENDS

The date and time that the current billing cycle ends and the next billing cycle begins. High performance mount targets have a 30-day billing cycle. For more information, see Mount Target Performance.

VIRTUAL CLOUD NETWORK

The VCN that contains the subnet where the mount target VNIC resides.

SUBNET

The subnet within the VCN where the mount target VNIC resides. Subnets can be either AD-specific or regional (regional ones have "regional" after the name). For more information, see VCN and Subnet Management.

IP ADDRESS

The IP address that was assigned to the mount target when it was created. You need your mount target's IP address to mount associated file systems.

HOSTNAME

The hostname that was assigned to the mount target, if any. For more information about hostnames, see DNS in Your Virtual Cloud Network.

FULLY QUALIFIED DOMAIN NAME

The hostname together with the subnet domain name. For more information, see DNS in Your Virtual Cloud Network. If you specify a hostname, you can use the FQDN to mount the file system.

EXPORT SET OCID

The OCID of the mount target's export set resource. Each mount target has one export set, which contains all of the exports for the mount target. You need your mount target's export set OCID when you perform export-related tasks in the Command Line Interface (CLI) or the API.

EXPORTS

All of the mount target's exports are listed here. The export path and name of each file system is also listed. You need the export path to mount a file system.

• Each availability domain is limited to two Standard mount targets, two 20 Gbps High Performance mount targets, one 40 Gbps High Performance mount target, and zero 80 Gbps High Performance mount targets by default.

  See Service Limits for a list of applicable limits and instructions for requesting a limit increase.

• Each mount target can accept up to 100,000 NFS client connections. If you use in-transit encryption, each mount target can accept up to 4096 NFS/SSL client connections. See Using In-transit TLS Encryption for more information.
• Each tenancy in a region can have one CreateMountTarget or ChangeMountTargetCompartment operation in progress at a time. See 409 error occurs when creating or moving a file system or mount target for more information.
• A mount target that's scheduled for a performance downgrade can't be edited, moved, or have logging enabled until the downgrade is completed or canceled by a user.
• High performance mount targets can't be directly created or deleted. A standard mount target must be created and upgraded for high performance. A high performance mount target must be downgraded to a standard performance level before it can be deleted.

• Each mount target, during creation, requires three IP addresses in the subnet. Only the first IP address is for customer use. The second two addresses are used for an internal failover process. During a File Storage maintenance event, the failover process releases one of the two reserved addresses and uses a new IP address that's available in the subnet. The customer-facing IP address is unaffected.

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

  You can use the CLI to search for used IP addresses, including those used by mount targets. To find the IP addresses in a subnet that are used by mount targets, use the following command:

  oci network private-ip list --subnet-id <subnet_OCID> --query 'data[?contains("display-name",`fss-mnt`)]."ip-address"'

For administrators: The policy in Let users create, manage, and delete file systems allows users to manage mount targets. Because mount targets are network endpoints, users must also have "use" permissions for VNICs, private IPs, private DNS zones, and subnets to create or delete a mount target.

If you're new to policies, see Getting Started with Policies and Details for the File Storage Service.