Forum Discussion

Alex_de_Souza's avatar
Alex_de_Souza
Level 4
11 years ago

ERR - Client for NFS service is either not installed or not running.

Hello guys, i'm trying to make a GRT backup of AD, but is bringing me the following message in job details:

07/17/2014 10:37:00 - Info nbjm (pid=12272) starting backup job (jobid=3178548) for client sdb-win-dc-1.oi.infra, policy AD-SDB-Oi-INFRA-1, schedule AD-Full

07/17/2014 10:37:00 - estimated 9684597 kbytes needed
07/17/2014 10:37:00 - Info nbjm (pid=12272) started backup (backupid=sdb-win-dc-1.oi.infra_1405604220) job for client sdb-win-dc-1.oi.infra, policy AD-SDB-Oi-INFRA-1, schedule AD-Full on storage unit MDSP_MEDIA_4_DISK
07/17/2014 10:37:00 - started process bpbrm (pid=15629)
07/17/2014 10:37:01 - Info bpbrm (pid=15629) sdb-win-dc-1.oi.infra is the host to backup data from
07/17/2014 10:37:01 - Info bpbrm (pid=15629) reading file list for client
07/17/2014 10:37:01 - Info bpbrm (pid=15629) starting bpbkar on client
07/17/2014 10:37:01 - connecting
07/17/2014 10:37:01 - connected; connect time: 0:00:00
07/17/2014 10:37:02 - Info bpbkar (pid=1856) Backup started
07/17/2014 10:37:02 - Info bpbrm (pid=15629) bptm pid: 15634
07/17/2014 10:37:02 - Info bpbkar (pid=1856) change time comparison:<disabled>
07/17/2014 10:37:02 - Info bpbkar (pid=1856) archive bit processing:<enabled>
07/17/2014 10:37:02 - Info bptm (pid=15634) start
07/17/2014 10:37:02 - Info bptm (pid=15634) using 262144 data buffer size
07/17/2014 10:37:02 - Info bptm (pid=15634) using 30 data buffers
07/17/2014 10:37:02 - Info bptm (pid=15634) start backup
07/17/2014 10:37:05 - Info bptm (pid=15634) backup child process is pid 15647
07/17/2014 10:37:05 - begin writing
07/17/2014 10:38:32 - Error bpbrm (pid=15629) from client sdb-win-dc-1.oi.infra: ERR - Client for NFS service is either not installed or not running.
07/17/2014 10:41:35 - Error bpbrm (pid=15629) from client sdb-win-dc-1.oi.infra: ERR - Error encountered while attempting to get additional files for System State:\
07/17/2014 10:42:52 - Info bptm (pid=15634) waited for full buffer 8122 times, delayed 22623 times
07/17/2014 10:42:55 - Info bptm (pid=15634) EXITING with status 0 <----------
07/17/2014 10:42:55 - Info netbackup-media-4.adm.infra (pid=15634) StorageServer=PureDisk:netbackup-media-4.adm.infra; Report=PDDO Stats (multi-threaded stream used) for (netbackup-media-4.adm.infra): scanned: 8062485 KB, CR sent: 42277 KB, CR sent over FC: 0 KB, dedup: 99.5%, cache hits: 119132 (98.2%)
07/17/2014 10:42:55 - Info bpbrm (pid=15629) validating image for client sdb-win-dc-1.oi.infra
07/17/2014 10:42:55 - Info bpbkar (pid=1856) done. status: 1: the requested operation was partially successful
07/17/2014 10:42:55 - end writing; write time: 0:05:50
the requested operation was partially successful  (1)

 

Master/Media Serve S.O: Red Hat 5.5

Client: Windows Server 2012

Faithfully follow the documentation symantec but it seems I did something wrong. This environment is new ie windows has never been backed him before 

Backup and Recovery
Configuring
Error messages
Installing
Linux
NetBackup
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    11 years ago
    Hello, have you started the netbackup clients services with a domain user account with access to AD? http://www.symantec.com/business/support/index?page=content&id=HOWTO86243 Also check and restart the nfs client. I've seen it die on windows even though the service is started. Use the following dont stop/start it from services. http://technet.microsoft.com/en-us/library/cc732891.aspx And start the nfs redirector too.

47 Replies

Sort By
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago
    Hello, have you started the netbackup clients services with a domain user account with access to AD? http://www.symantec.com/business/support/index?page=content&id=HOWTO86243 Also check and restart the nfs client. I've seen it die on windows even though the service is started. Use the following dont stop/start it from services. http://technet.microsoft.com/en-us/library/cc732891.aspx And start the nfs redirector too.
  • Alex_de_Souza's avatar
    Alex_de_Souza
    Level 4
    11 years ago

    Yes, i have disabled the service "Server for NFS" is active "Client for NFS" of client. I put the user in netbackup services, it has domain admin permission. I did all the procedures listed for you, however unsuccessfully. Still showing the same error message

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hello,

     

    As per my earlier post, please check the DNS services. you'll find details in this note

    http://www.symantec.com/docs/TECH164159

  • Alex_de_Souza's avatar
    Alex_de_Souza
    Level 4
    11 years ago

    Hi Riaan,

    had already done this check, but, did disengage again and still showing the same error message.

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    I've also seen other posts saying that the message is not relevant. What you don't see afterwards is a message that granular processing won't occur. The failure backing up the system state might however be the real relevant issue.

     

    Quite a few notes about that error

     

    http://www.symantec.com/docs/TECH77741

    http://www.symantec.com/docs/TECH144975

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    Work through this tech note and it subsequent links :

    http://www.symantec.com/docs/HOWTO86244

    Usually it is something like not setting the portmap service to auto which has to be done via a command line .. and sometimes the NFS client service will not re-start properly and again has extra things to be done via the command line:

    stop the cleint for nfs service

    run: net stop nfsrdr

    run: net start nfsrdr

    start the client for nfs service

    #edit# for the portmapper use: sc config portmap start= auto

  • Alex_de_Souza's avatar
    Alex_de_Souza
    Level 4
    11 years ago

    checked and applied procedure that all our friends have pointed out, but without success. Nbfsd follows the client log!

    10:32:50.851 [2160.4620] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\nbfs mount -server netbackup-media-4.adm.infra -port 7394 -cred 583F3AF41343D74442AF952B9A5A474CF0E0660790A39F899F3D490F9D041AB7578FFD5D5381B87773A75B972102F4CC74B5D15282ABB12F939FE0DE21DF5C6E * 
    10:32:50.851 [2160.4620] <2> rpc_connect: connecting to netbackup-media-4.adm.infra
    10:32:50.851 [2160.4620] <2> rpc_connect: connection established to netbackup-media-4.adm.infra
    10:32:50.851 [2160.4620] <2> vnet_pcache_init_table: [vnet_private.c:212] starting cache size 200 0xc8
    10:32:50.851 [2160.4620] <2> nbfsd_op: making call 3915 ( cl 128, xagrs= /12,winver=6,2,2/31,acp=1252,1252  (ANSI - Latin I)/27,host=sdb-win-dc-1.sdb.infra/4,mp=* )
    10:32:50.898 [2160.4620] <2> nbfsd_op: completed call 3915 - 0  /NBUFS_A_7F23C4EA7472398A_000  
    10:32:50.898 [2160.4620] <2> nbfs main: mount -o mtype=soft-o timeout=60 -o retry=1 netbackup-media-4.adm.infra:/NBUFS_A_7F23C4EA7472398A_000 *
    10:32:50.898 [2160.4620] <2> _nbfs_mount_info_check: last access information does not exist, setting it
    10:33:13.915 [2160.4620] <8> _nbfs_mount_info_set: unable to determine last export name
    10:33:13.915 [2160.4620] <2> _nbfs_connect: adding connection for netbackup-media-4.adm.infra:/NBUFS_A_7F23C4EA7472398A_000
    10:34:00.839 [2160.4620] <16> _nbfs_connect: WNetAddConnection2() failed, error = 53
    10:34:01.854 [2160.4620] <16> _nbfs_connect: WNetAddConnection2() failed, error = 53
    10:34:49.731 [2160.4620] <16> _nbfs_connect: WNetAddConnection2() failed, error = 53
    10:34:49.731 [2160.4620] <16> _nbfs_connect: aborting connection, timeout period exceeded
    10:34:49.731 [2160.4620] <2> nbfsd_op: making call 3916 ( cl 128, xagrs=  )
    10:34:49.731 [2160.4620] <2> nbfsd_op: completed call 3916 - 0    
    10:35:17.904 [6312.4476] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\nbfs mount -server netbackup-media-4.adm.infra -port 7394 -cred 583F3AF41343D74442AF952B9A5A474CF0E0660790A39F899F3D490F9D041AB7578FFD5D5381B87773A75B972102F4CC74B5D15282ABB12F939FE0DE21DF5C6E * 
    10:35:17.920 [6312.4476] <2> rpc_connect: connecting to netbackup-media-4.adm.infra
    10:35:17.920 [6312.4476] <2> rpc_connect: connection established to netbackup-media-4.adm.infra
    10:35:17.920 [6312.4476] <2> vnet_pcache_init_table: [vnet_private.c:212] starting cache size 200 0xc8
    10:35:17.920 [6312.4476] <2> nbfsd_op: making call 3915 ( cl 128, xagrs= /12,winver=6,2,2/31,acp=1252,1252  (ANSI - Latin I)/27,host=sdb-win-dc-1.sdb.infra/4,mp=* )
    10:35:17.920 [6312.4476] <2> nbfsd_op: completed call 3915 - 22    
    10:35:17.920 [6312.4476] <16> nbfsd_op: call 3915 to netbackup-media-4.adm.infra returned err 22

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Hi,

     

    Still a problem with NFS

     

    10:34:00.839 [2160.4620] <16> _nbfs_connect: WNetAddConnection2() failed, error = 53

     

    http://www.symantec.com/docs/TECH73703

     

    I would try and reinstall the NFS components

  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    11 years ago

    Good point Mark

     

    You can test if the client can mount the NFS using the test in this note

    http://www.symantec.com/docs/TECH124810