Restore Fails with Status INVALID When Using NFS Backup Provider

Environment

• Product: YugabyteDB Anywhere
• Applies to: All Versions
• Backup Provider Type: NFS

Issue

Restoring a backup using the Advanced Restore method fails when the backup provider is set to NFS. You may encounter the following error in the YBA task UI or application logs:

Task id a7212de1-57e9-413a-aacf-78b6f09b3186_PGSQL_TABLE_TYPE_demo_20250718-0 status: Failed with status INVALID. Please check YB-Controller logs for more details.

Cause

When using NFS as the backup provider, the designated NFS directory must exist on every DB node in the universe, including nodes in both the Primary and Read Replica universes.

Resolution

Step 1: Identify the Error from Logs

The YBA logs may show the following:

status: Failed with status INVALID. Please check YB-Controller logs for more details.

To investigate further:

1. SSH into any DB node.

2. Open the YB-Controller logs located at:

   /home/yugabyte/controller/logs/yb-controller-server.<server-name>.log

3. Look for entries like the following:

   E20250723 02:34:30.143187 85933 backup_service_task.cc:220] Task a7212de1-57e9-413a-aacf-78b6f09b3186_PGSQL_TABLE_TYPE_demo_20250718-0:yb-demo-n1 Failed with status INVALID

The :yb-demo-n1 suffix points to the specific node name or can be an IP address of the node where the failure occurred.

4. Review the logs on that specific node using cat or any log viewer. Example:

   cat yb-dev-Adquirente-readonly1-n1/controller/logs/yb-controller-server.yb-demo-n1.log.WARNING.20250722-224552.126585

You may find an error like this:

E20250722 22:45:53.020673 126606 cloud_store_aggregate_task_info.cc:88] ... INVALID
E20250722 22:45:53.020709 126607 cloud_store_nfs.cc:93] Got filesystem_error exception: 2
  ex.code().category().name() is generic
  ex.what() is boost::filesystem::canonical: No such file or directory [generic:2]: "/backupdb"

This indicates that the directory /backupdb is missing on that node.

Step 2: Resolve the Issue

1. SSH into all DB nodes (Primary and Read Replica).

2. Ensure the NFS mount directory (e.g., /backupdb) exists.

3. If missing, mount the NFS share correctly using the naming convention and procedure outlined in the official documentation.

   Refer to: Configure Backup Storage - NFS

Additional Resources

• YugabyteDB - Backup and Restore Overview