Certifique-se de que o pacote rpcbind ou portmapper está instalado no anfitrião Linux. Execute:
# rpm -qa | grep rpcbind
Isto deve devolver algo como: rpcbind-0.1.6+git20080930-6.15
Se não vir nada, tem de instalar os pacotes através do YaST ou do zypper:
Usar o YaST: # yast2 --install rpcbind
Usar o Zypper: # zypper install rpcbind
Saiba mais sobre as informações do cliente NFS no anfitrião Linux
Tem de instalar um pacote e uma versão de cliente NFS aprovados pelo Backup and DR no anfitrião.
Verifique se o serviço portmapper ou rpcbind está em execução. Corrida:
# sudo service rpcbind status
Um anfitrião do Red Hat RHEL 6 ou CentOS Linux deve devolver algo como:
rpcbind (pid 1591) is running...
Um anfitrião Linux SLES deve devolver algo semelhante a:
Checking for service rpcbind running
Se o serviço rpcbind não estiver em execução no anfitrião Linux, inicie-o com:
# sudo service rpcbind start
Use rpcinfo para listar os programas ou serviços RPC registados. O Portmapper tem de estar registado e em execução.
# sudo rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
Verifique se o anfitrião Linux pode fazer uma chamada RPC para programas rpcbind e NFS no dispositivo de cópia de segurança/recuperação através do seguinte.
# sudo rpcinfo -T tcp <#vm internal IP> rpcbind
program 100000 version 2 ready and waiting
program 100000 version 3 ready and waiting
program 100000 version 4 ready and waiting
# sudo rpcinfo -T tcp <#vm internal IP> nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
Se os comandos anteriores devolverem a saída apresentada, significa que a conetividade NFS do anfitrião Linux para o dispositivo de cópia de segurança/recuperação é boa.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-21 UTC."],[[["\u003cp\u003eThis page details how to verify and ensure NFS client connectivity for Backup and DR on Red Hat RHEL 6, CentOS, and SLES Linux hosts.\u003c/p\u003e\n"],["\u003cp\u003eYou can check for the presence of the NFS client packages on your Linux host by using the command \u003ccode\u003e# rpm -qa | grep nfs\u003c/code\u003e, and install them with yum or YaST/zypper if they are absent.\u003c/p\u003e\n"],["\u003cp\u003eThe rpcbind/portmapper package must also be installed, verifiable via \u003ccode\u003e# rpm -qa | grep rpcbind\u003c/code\u003e, and installable via yum or YaST/zypper.\u003c/p\u003e\n"],["\u003cp\u003eYou can confirm the rpcbind service is active by running \u003ccode\u003e# sudo service rpcbind status\u003c/code\u003e, and if not running, initiate it with \u003ccode\u003e# sudo service rpcbind start\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eNFS connectivity is validated by checking for registered RPC programs with \u003ccode\u003e# sudo rpcinfo -p\u003c/code\u003e and confirming RPC calls to rpcbind and NFS on the backup/recovery appliance using \u003ccode\u003e# sudo rpcinfo -T tcp <#vm internal IP> rpcbind\u003c/code\u003e and \u003ccode\u003e# sudo rpcinfo -T tcp <#vm internal IP> nfs\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Ensure NFS connectivity for Backup and DR\n\nThis page includes information on how to ensure there is NFS connectivity for\nBackup and DR.\n\nInstall the NFS client on a Red Hat RHEL 6 or CentOS Linux host\n---------------------------------------------------------------\n\nSee if the client is installed by running: `# rpm -qa | grep nfs`\n\nThis should return something like: \n\n nfs-utils-lib-1.1.5-9.el6.x86_64\n nfs-utils-1.2.3-54.el6.x86_64\n\n- If you see nothing, then use yum to install the NFS client packages. Run: `# yum install nfs-utils nfs-utils-lib`\n- Make sure rpcbind /portmapper package is installed on the Linux host. Run:`# rpm -qa | grep rpcbind`\n\nThis should return something like: `rpcbind-0.2.0-11.el6.x86_64`\n\n- If you see nothing, then use yum to install the rpcbind. Run: `# yum install rpcbind`\n\nInstall the NFS client on a SLES Linux host\n-------------------------------------------\n\n1. To see if the client is installed, run: `# rpm -qa | grep nfs`\n\n This should return something similar to: \n\n nfs-client-1.2.1-2.6.6\n yast2-nfs-common-2.17.7-1.1.2\n yast2-nfs-client-2.17.12-0.1.81\n\n2. If you don't see either nfs-client or yast2-nfs-xxxx packages, then use\n either YaST or zypper to install the NFS client packages.\n\n - Using YaST:\n\n # yast2 --install yast2-nfs-client\n # yast2 --install yast2-nfs-common\n\n - Using Zypper:`# zypper install nfs-client`\n3. Make sure rpcbind or portmapper package is installed on the Linux host. Run:\n `# rpm -qa | grep rpcbind`\n This should return something like: rpcbind-0.1.6+git20080930-6.15\n\n4. If you see nothing, then you must install the packages using either YaST or\n zypper:\n\n - Using YaST: `# yast2 --install rpcbind`\n - Using Zypper: `# zypper install rpcbind`\n\nLearn NFS client information from the Linux host\n------------------------------------------------\n\nA Backup and DR-approved NFS client package and version must be installed on\nthe host.\n\n1. Check if the portmapper or rpcbind service is running. Run:\n `# sudo service rpcbind status`\n\n - A Red Hat RHEL 6 or CentOS Linux host should return something like: `rpcbind (pid 1591) is running...`\n - An SLES Linux host should return something like: `Checking for service rpcbind running`\n2. If rpcbind service is not running on Linux host, start it with:\n `# sudo service rpcbind start`\n\n3. Use rpcinfo to list the registered RPC programs or services. Portmapper\n must be registered and running.\n\n # sudo rpcinfo -p\n program vers proto port service\n 100000 4 tcp 111 portmapper\n 100000 3 tcp 111 portmapper\n 100000 2 tcp 111 portmapper\n 100000 4 udp 111 portmapper\n 100000 3 udp 111 portmapper\n 100000 2 udp 111 portmapper\n\n4. Check if the Linux host can make an RPC call to rpcbind and NFS programs on\n the backup/recovery appliance using the following.\n\n # sudo rpcinfo -T tcp \u003c#vm internal IP\u003e rpcbind\n program 100000 version 2 ready and waiting\n program 100000 version 3 ready and waiting\n program 100000 version 4 ready and waiting\n # sudo rpcinfo -T tcp \u003c#vm internal IP\u003e nfs\n program 100003 version 2 ready and waiting\n program 100003 version 3 ready and waiting\n\nIf the preceding commands return the output shown, then NFS connectivity from\nLinux host to the backup/recovery appliance is good."]]
