POST VCF upgradation, VC backup fails with the error message "Path not exported by the remote filesystem."

Products

• VMware vCenter Server

Issue/Introduction

This article informs the users that manual reboot is required after VC is upgraded from 7.0.1 to 7.0.2 since VCF did not reboot the servers. This has been handled in and after 7.0.3.

Symptoms:

After the VCF upgrade, VC is expected to reboot, if it undergoes any kernel update.
VC backup failed with the error message "Path not exported by the remote filesystem."
Errors similar to the following are found when trying to mount NFS:

root@vcenter-1 [ / ]# mount -t nfs 172.16.45.251:/backup/part2lab/vcenter-1 /mnt-vcenter-1_logs -v
mount.nfs: timeout set for Mon Jun 20 10:38:06 2022
mount.nfs: trying text-based options 'vers=4.2,addr=172.16.45.251,clientaddr=172.16.45.8'
mount.nfs: mount(2): No such device
mount.nfs: No such device

Environment

VMware vCenter Server 7.0.2
VMware vCenter Server 7.0.1

Cause

vCenter did not reboot after the upgrade from 7.0.1 to 7.0.2. After any linux kernel update, it has to reboot the VC.

Resolution

70u3 onwards, VC will be rebooted post patching, due to kernel FIPS.

Workaround:
User should reboot the VC after the upgrade of the VC. Please refer to : Reboot or Shut Down vCenter Server