FBBR – Troubleshooting – SFTP Retention
November 30, 2023
FBBR – Troubleshooting – SMB Backup
December 2, 2023
FBBR – Troubleshooting – SFTP Retention
November 30, 2023
FBBR – Troubleshooting – SMB Backup
December 2, 2023

FBBR – Troubleshooting – NFS Backup

6.7

2049/tcp

7.0 / 8.0

111/tcp/udp – rpc-bind: Core storage NFSv3 – RPC portmapper
2049/tcp/udp – NFS Transport

The below ports are dynamic and need to check with storage vendor for correct setting.

635/tcp/udp – mountd
1110/tcp/udp – statd
4045/tcp/udp – lockd

Mount Failure

During backup operation, vCenter mounts the NFS Path temporarily to /storage/remote/backup/nfs//
Post the Backup transfer, it would be unmount.

You can use any Linux Machine or VCSA Appliance to validate NFS Mount and File upload.

You can try mount the NFS Share and do a file copy

/usr/bin/mount -t nfs <NFS_SERVER_IP>:/<NFS_PATH> /<LOCAL_PATH> -o hard,intr

Post the mount you can test file operations like mkdir, touch, rmdir, rm

You can validate the mount by the command “mount”. It provides information of the nfs version.

Alternatively, you can also use

nfsstat -m

To unmount,

umount <LOCAL_PATH>

You can use -v to provide more detailed information

If you want to mount using a particular protocol version, you can specify -o

mount -t nfs 192.168.7.101:/backup /var/core/tmp -o vers=4.1

If you see the expected snippets of Mount Operation in backup.log, you can see the below snippets.

2021-06-24T22:35:48.408 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::run_timed_cmd:MountedFSStorageIOLib.py:130] ERROR: Cmd ['/usr/bin/mount', '-t', 'nfs', '192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local/M_7.0.2.00200_20210624-223437/', '/storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3', '-o', 'hard,intr'] failed. rc: 32, stdout: , stderr: mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local/M_7.0.2.00200_20210624-223437_/ failed, reason given by server: No such file or directory
2021-06-24T22:35:48.409 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::mount:MountedFSStorageIOLib.py:229] INFO: Failed to mount the nfs share 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local/M_7.0.2.00200_20210624-223437_/ at /storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3. Err- rc: 32, out=, err=mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local/M_7.0.2.00200_20210624-223437_/ failed, reason given by server: No such file or directory
2021-06-24T22:35:48.547 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::_run_timed_cmd:MountedFSStorageIOLib.py:130] ERROR: Cmd ['/usr/bin/mount', '-t', 'nfs', '192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local', '/storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3', '-o', 'hard,intr'] failed. rc: 32, stdout: , stderr: mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local failed, reason given by server: No such file or directory
2021-06-24T22:35:48.548 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::mount:MountedFSStorageIOLib.py:229] INFO: Failed to mount the nfs share 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local at /storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3. Err- rc: 32, out=, err=mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local failed, reason given by server: No such file or directory
2021-06-24T22:35:48.683 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::_run_timed_cmd:MountedFSStorageIOLib.py:130] ERROR: Cmd ['/usr/bin/mount', '-t', 'nfs', '192.168.7.54:/srv/nfs/vCenter', '/storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3', '-o', 'hard,intr'] failed. rc: 32, stdout: , stderr: mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter failed, reason given by server: No such file or directory
2021-06-24T22:35:48.684 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::mount:MountedFSStorageIOLib.py:229] INFO: Failed to mount the nfs share 192.168.7.54:/srv/nfs/vCenter at /storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3. Err- rc: 32, out=, err=mount.nfs: mounting 192.168.7.54:/srv/nfs/vCenter failed, reason given by server: No such file or directory
2021-06-24T22:35:48.759 [20210624-223437-17958471] [MainProcess:PID-40134] [MountedFSStorageIOLib::mount:MountedFSStorageIOLib.py:224] INFO: Successfully mounted the nfs share 192.168.7.54:/srv/nfs at /storage/remote/backup/nfs/192.168.7.54/8D4LiVIo/meGJBKe3

Even though, we receive the No such file or directory error still it’s an successful mount. The reason being, vCenter tries to mount the complete path

192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local/M_7.0.2.00200_20210624-223437_/

Since the path does not exist, it tries to mount the parent directory which is

192.168.7.54:/srv/nfs/vCenter/sn_vc70d.vmware.local

If that also, is not successful it mounts its parent directory.

192.168.7.54:/srv/nfs/vCenter

If unsuccessful, then its parent directory.

192.168.7.54:/srv/nfs

If any of the path is valid and the mount is successful, you would receive the Success message and the backup gets initiated.
Hence, it is expected to get an No such file or directory message from the backup server.

Instead if it receives any other response, the backup operation fails. So if any of the folders in path is valid, the backup succeeds.

For example,

nfs://192.168.7.54:/srv/nfs/wrong_directory

So the mount would be done on the fs folder and the folder named wrong_directory would be created.

In the Series:

Related posts

January 8, 2024

Exporting and viewing LDIF from vCenter using SSH / JXplorer

Read more
December 9, 2023

SSH Key based authentication for vCenter using Putty

Read more
December 8, 2023

SSH Key based authentication for vCenter using Openssh

Read more

Leave a Reply

Your email address will not be published. Required fields are marked *