> Expert > Backup and Restore Agents > Backup Agents > Network Share > NFS Exports > Network Share Configuration for NFS Exports

Subclient Contents for NFS Exports

Subclient contents for NFS exports support two formats. In one format, the content path begins with the file server interface and the appropriate NFS export is automatically mounted. In the other format, the content path includes the mount point.

When you browse for content for a new subclient, the browse defaults to the auto-mount format (exports on file server). For a new subclient, to enter subclient contents in the mount point format, you must manually enter the content path. For existing subclients, the browse is based on the format of the existing subclient content.

Important

A subclient cannot contain a mix of content formats and cannot be changed from one format to the other format. To start using a different format, create a new subclient.

Auto-mount Format

The content path for the auto-mount format begins with the file server interface: for example, file_server_interface:/NFS_export_path.

Considerations

Before creating a content path that begins with the file server interface, consider the following information:

  • Full backup operations and data discovery operations are supported.

  • Ad-hoc backup and ad-hoc archiving operations are not supported. To perform archiving operations or ad-hoc backup operations on a single node, use the mount point format.

  • Backups of data pointed by symbolic links with registry nBackupSymLinkData is not supported. For more information, see Enabling Backup of Symbolic Link Contents on a Client.

  • Long path backups are not supported.

  • Configuring backups to prevent data duplication of hard-linked files is not supported.

  • If you enter file_server_interface:/ as the content path, all of the exports on the file server are backed up. However, the root volume associated with export / is not included in the backup operation. For example, for a NetApp filer using Cluster-Mode, file_server_interface:/ does not protect the root volume associated with junction path /.

  • Browsing for subclient contents displays the exports on the file server.

  • Backup and restore operations with user impersonation is not supported.

  • In-place restore operations are not supported at archiveset level or backupset level. To restore data in-place, restore from the subclient level.

Mount Point Format

The content path for the mount point format includes the mount point: for example, /mount/nfs.

Considerations

Before creating a content path that includes the mount point, consider the following information:

  • You must manually mount the NFS export in the same directory on all the Linux data access nodes.

  • Browsing for subclient contents displays the contents of the proxy.

  • The mount point format cannot be used for the default subclient. Use the auto-mount format for the default subclient.

  • Backups of data pointed by symbolic links with registry nBackupSymLinkData is not supported. For more information, see Enabling Backup of Symbolic Link Contents on a Client.

Loading...