Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

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

Created: 17 Jul 2014 | 44 comments

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 

Operating Systems:

Comments 44 CommentsJump to latest comment

Riaan.Badenhorst's picture

Hello, have you started the netbackup clients services with a domain user account with access to AD?

http://www.symantec.com/business/support/index?pag...

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/cc73289...

And start the nfs redirector too.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

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

Riaan.Badenhorst's picture

Hello,

 

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

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

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

Hi Riaan,

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

Riaan.Badenhorst's picture

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

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mark_Solutions's picture

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

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Alex de Souza's picture

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

Riaan.Badenhorst's picture

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

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mark_Solutions's picture

One thing we didn't ask about is firewalls - do you have any on your system - on the client or between the client and the media server?

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

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Alex de Souza's picture

Mark,

 

Yes there firewall, did a telnet on ports 111/739 Media> client and client> media, both doors are not communicating, I will ask for the security team to release them. 

Maybe that's the problem!

Riaan.Badenhorst's picture

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

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

Riaan,

my media server is linux, what is the command that I use to replace this documentation? Sorry for the lack of skill.

On the NetBackup media server.

1. Increase the logging verbosity and enable logs for nbfsd. <install_path>\Veritas\netbackup\logs\nbfsd

2. Open command prompt and execute the command:

<install_path>\Veritas\netbackup\bin\nbfsd -d -v 5 -j <job_id> -B <backup_id>

## You can specify any number for job id. It is not mandatory to have that job id present in activity monitor or the job id of the GRT backup job.
## You can specify any backup id. (Must be clientname_9 digit number e.g. client_123456789)
 

Alex de Souza's picture

Guys,

ports released in relation to the test of NFS mount, displays the following error message on exit code = 43 prompt the client

Mark_Solutions's picture

Could you explain / show us more of that last error please - not sure exactly what you are saying so could we see the job details and log please

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Riaan.Badenhorst's picture

Hi

Dont worry about the logging. Just run this on the media server

netcat -zv localhost 111 (netcat or nc depending on your system. it checks if ports are open)

netcat -zv localhost 7394

/usr/openv/netbackup/bin/nbfsd -d -v 5 -j <job_id> -B <backup_id>

netcat -zv localhost 7394

then look at the CRED1 and CRED2 ids

 

Then run this on the client

<install_path>\Veritas\netbackup\bin\nbfs mount -server <Media_server_name> -cred <CRED1> *

 

Then run this on the client

<install_path>\Veritas\netbackup\bin\nbfs umount -server <servername> -cred <CRED2> <mount_pt>

 

Capture the output

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

#MEDIA SERVER 

[tr_alesilva@netbackup-media-4.adm.infra ~]$ nc -zv localhost 111

Connection to localhost 111 port [tcp/sunrpc] succeeded!

[tr_alesilva@netbackup-media-4.adm.infra ~]$ nc -zv localhost 7394

nc: connect to localhost port 7394 (tcp) failed: Connection refused

[tr_alesilva@netbackup-media-4.adm.infra ~]$ cd /usr/openv/netbackup/bin/

 [tr_alesilva@netbackup-media-4.adm.infra bin]$ sudo su

[root@netbackup-media-4.adm.infra bin]# /usr/openv/netbackup/bin/nbfsd -d -v 5 -j 3197709 -B sdb-win-dc-1.oi.infra_1406223293

PORT=7394

CRED1=84B16F11359B6D700DA4E629ADC1BBA53511751012ADC30735D505174768F16E264BEEEBCEF9CBEF185F7AB43A04D381ECAFD45ADFA7A506BCB0957F7DDA04D1

CRED2=F128039B5ECE452DEC968F4D6F7F4318E0DE8FC1093A54F1813BF46DDF29865DEACD85AC990C12C9BD28F705B224B6BD4BD0C53F959B52872DA9AC697FE74EB2

NBFSD STARTED 0

[root@netbackup-media-4.adm.infra bin]# nc -zv localhost 7394

nc: connect to localhost port 7394 (tcp) failed: Connection refused

#CLIENT

C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server netbackup-media-4.adm.

infra -cred 84B16F11359B6D700DA4E629ADC1BBA53511751012ADC30735D505174768F16E264B

EEEBCEF9CBEF185F7AB43A04D381ECAFD45ADFA7A506BCB0957F7DDA04D1 *

connect to netbackup-media-4.adm.infra failed

EXIT_STATUS=25

obviously not given the command of umont because it gave error on mount. Telnet only terminates successfully when I mount the test and that only the client on the media not.

Riaan.Badenhorst's picture

Thanks for the output. I find it odd that you cannot connect to 7394 after running the nbfsd mount.

 

[tr_alesilva@netbackup-media-4.adm.infra ~]$ nc -zv localhost 7394 <<<This i expect to happen as the process isn't started.

nc: connect to localhost port 7394 (tcp) failed: Connection refused

[tr_alesilva@netbackup-media-4.adm.infra ~]$ cd /usr/openv/netbackup/bin/

 [tr_alesilva@netbackup-media-4.adm.infra bin]$ sudo su

[root@netbackup-media-4.adm.infra bin]# /usr/openv/netbackup/bin/nbfsd -d -v 5 -j 3197709 -B sdb-win-dc-1.oi.infra_1406223293

PORT=7394

CRED1=84B16F11359B6D700DA4E629ADC1BBA53511751012ADC30735D505174768F16E264BEEEBCEF9CBEF185F7AB43A04D381ECAFD45ADFA7A506BCB0957F7DDA04D1

CRED2=F128039B5ECE452DEC968F4D6F7F4318E0DE8FC1093A54F1813BF46DDF29865DEACD85AC990C12C9BD28F705B224B6BD4BD0C53F959B52872DA9AC697FE74EB2

NBFSD STARTED 0

[root@netbackup-media-4.adm.infra bin]# nc -zv localhost 7394 <<But here it should connect. Did you press control C after the nbfsd command? Try the netcat from a different terminal window and don't cancel the NBFSD

nc: connect to localhost port 7394 (tcp) failed: Connection refused

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

I did as suggested and the result was this:

 

[tr_alesilva@netbackup-media-4.adm.infra ~]$ nc -zv localhost 7394

Connection to localhost 7394 port [tcp/*] succeeded!

 

Riaan.Badenhorst's picture

Ok, ports are open on the server.

 

And then the nbfs from the client? All seems ok on the server, need to look at the path getting to it from the client. If you have another linux server/client you can also test with netcat from there.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

#MEDIA

[root@netbackup-media-5.adm.infra tr_alesilva]# /usr/openv/netbackup/bin/nbfsd -d -v 5 -j 11 -B sdb-win-dc-1.oi.infra_123456789

PORT=7394
CRED1=7FC472598EEAED0A1067C342400A07AAF766630C1FF2258AEF3EAEC7024F02309D345CE20F937956AFAA7BAE4A95DE0BB                                                                 F396109F70DB70CCFC0EF07932108BF
CRED2=EEEDC99A92729290496403E12646726282ACDD24CB2B459D6E5B6BC4D3B55A6408D53437908B7977E37CC1A918D463F94                                                                 7B21C667D6EA6764222A6B5477E6DE8
NBFSD STARTED 0

#CLIENT

C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server netbackup-media-5.adm.infra -cred 7FC472598EEAED0A1067C342400A07AAF766630C1FF2258AEF3EAEC7024F02309D345CE20F937956AFAA7BAE4A95DE0BBF396109F70DB70CCFC0EF07932108BF

connect to netbackup-media-5.adm.infra failed

EXIT_STATUS=25

Riaan.Badenhorst's picture

I'm sure it will work if you run the nbfs command from the media server not the client. That means something is blocking the comms, either a firewall on the media server (can try run iptables -F) or in the network.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Riaan.Badenhorst's picture

Any updates or progress made?

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

iptables is disabled on all master and media server, including the puppet is not set to run on all servers of the NBU environment. A note, I configured a windows machine for GRT backup media server and it worked. But I have no interest in using it as a windows media server.

Riaan.Badenhorst's picture

Can you telnet to media server from the windows client on port 7394 when you've run the nbfsd mount? Basically the same test as netcat, but from windows.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

Yes,

I've done this test before and closes successfully. 

Just to remind you, the customer domain is new including the servers that are in it.

Riaan.Badenhorst's picture

Hi Alex,

 

Only thing left I can think of is to test NFS on the client. You know the nbfsd mount works, you know you the port is open from the server>server, you know the port is open from client>server, so the only thing left to look at here is  NFS on the client.

 

Maybe share a folder on the linux and try and access via the client.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

captain jack sparrow's picture

as connection looks good enough.. can you simply change your backup selection from system state to shadow copy components and try... 

have seen cases where shadow copy components works perfectly as opposed to system state only.

let us know if this helps

 Cheers !!!

CJS

 

Alex de Souza's picture

We performed two procedures previously quoted by you in the case have changed the shadow copy backup of the system state and the reverse also. In the case of test NFS posted the above test results, the NFS mounts on the client does not.

Pangal's picture

kindly let us know netbackup version .   Kindly check whether current netbackup version supports granaular level backup of windows 2012

Alex de Souza's picture

Master/Media/Client NBU version 7.6.0.2.

I will check this issue of compatibility

Alex de Souza's picture

Staff, 

who were asked today released the following ports 1039/1047/1048 http://technet.microsoft.com/en-us/library/cc753302(v=ws.10).aspx now I have another error message. But, I still can not mount the NFS client.

-------------------------------------------------------------------------------------------------------------------------------------

Job Master/Father

08/11/2014 14:40:17 - Info nbjm (pid=6936) starting backup job (jobid=3263510) for client sdb-win-dc-1.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2
08/11/2014 14:40:17 - Info nbjm (pid=6936) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3263510, request id:{8F31B888-217E-11E4-B60B-92A1F70073C1})
08/11/2014 14:40:17 - requesting resource MDSP_MEDIA_3_DISK
08/11/2014 14:40:17 - requesting resource netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-1.oi.infra
08/11/2014 14:40:17 - requesting resource netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
08/11/2014 14:40:18 - granted resource  netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-1.oi.infra
08/11/2014 14:40:18 - granted resource  netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
08/11/2014 14:40:18 - granted resource  MediaID=@aaaa9;DiskVolume=PureDiskVolume;DiskPool=MDSP_MEDIA_3_BKP_POOL;Path=PureDiskVolume;StorageServer=netbackup-media-3.adm.infra;MediaServer=netbackup-media-3.adm.infra
08/11/2014 14:40:18 - granted resource  MDSP_MEDIA_3_DISK
08/11/2014 14:40:18 - estimated 9721687 kbytes needed
08/11/2014 14:40:18 - begin Parent Job
08/11/2014 14:40:18 - begin Snapshot: Start Notify Script
08/11/2014 14:40:18 - Info RUNCMD (pid=9935) started
08/11/2014 14:40:18 - Info RUNCMD (pid=9935) exiting with status: 0
Operation Status: 0
08/11/2014 14:40:18 - end Snapshot: Start Notify Script; elapsed time 0:00:00
08/11/2014 14:40:18 - begin Snapshot: Step By Condition
Operation Status: 0
08/11/2014 14:40:18 - end Snapshot: Step By Condition; elapsed time 0:00:00
08/11/2014 14:40:18 - begin Snapshot: Stream Discovery
Operation Status: 0
08/11/2014 14:40:18 - end Snapshot: Stream Discovery; elapsed time 0:00:00
08/11/2014 14:40:18 - begin Snapshot: Read File List
Operation Status: 0
08/11/2014 14:40:18 - end Snapshot: Read File List; elapsed time 0:00:00
08/11/2014 14:40:18 - begin Snapshot: Create Snapshot
08/11/2014 14:40:18 - started process bpbrm (pid=14047)
08/11/2014 14:40:19 - Info bpbrm (pid=14047) sdb-win-dc-1.oi.infra is the host to backup data from
08/11/2014 14:40:19 - Info bpbrm (pid=14047) reading file list for client
08/11/2014 14:40:19 - Info bpbrm (pid=14047) start bpfis on client
08/11/2014 14:40:19 - Info bpbrm (pid=14047) Starting create snapshot processing
08/11/2014 14:40:19 - Info bpfis (pid=5516) Backup started
08/11/2014 14:40:20 - Critical bpbrm (pid=14047) from client sdb-win-dc-1.oi.infra: FTL - process_fs_list() failed, status 71
08/11/2014 14:40:20 - Info bpbrm (pid=14047) INF - BPFIS MESSAGE Routing to stream based backup for windows open file backup case, generating remap directive
08/11/2014 14:40:20 - Info bpfis (pid=5516) done. status: 0
08/11/2014 14:40:20 - end Snapshot: Create Snapshot; elapsed time 0:00:02
08/11/2014 14:40:20 - Info bpfis (pid=5516) done. status: 0: the requested operation was successfully completed
08/11/2014 14:40:20 - end writing
Operation Status: 0
08/11/2014 14:40:20 - end Parent Job; elapsed time 0:00:02
08/11/2014 14:40:20 - Info nbjm (pid=6936) snapshotid=sdb-win-dc-1.oi.infra_1407778818
08/11/2014 14:40:20 - begin Snapshot: Policy Execution Manager Preprocessed
08/11/2014 14:46:04 - end Snapshot: Policy Execution Manager Preprocessed; elapsed time 0:05:44
08/11/2014 14:46:04 - begin Snapshot: Validate Image
Operation Status: 0
08/11/2014 14:46:04 - end Snapshot: Validate Image; elapsed time 0:00:00
08/11/2014 14:46:04 - begin Snapshot: Delete Snapshot
08/11/2014 14:46:05 - Info bpbrm (pid=14232) Starting delete snapshot processing
Operation Status: 1
08/11/2014 14:46:05 - started process bpbrm (pid=14232)
08/11/2014 14:46:06 - Info bpfis (pid=4896) Backup started
08/11/2014 14:46:06 - Critical bpbrm (pid=14232) from client sdb-win-dc-1.oi.infra: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.sdb-win-dc-1.oi.infra_1407778818.1.0
08/11/2014 14:46:06 - Info bpfis (pid=4896) done. status: 4207
08/11/2014 14:46:06 - end Snapshot: Delete Snapshot; elapsed time 0:00:02
08/11/2014 14:46:06 - Info bpfis (pid=4896) done. status: 4207: Could not fetch snapshot metadata or state files
08/11/2014 14:46:06 - end writing
Operation Status: 4207
08/11/2014 14:46:06 - begin Snapshot: End Notify Script
08/11/2014 14:46:06 - Info RUNCMD (pid=12979) started
08/11/2014 14:46:06 - Info RUNCMD (pid=12979) exiting with status: 0
Operation Status: 0
08/11/2014 14:46:06 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 1
the requested operation was partially successful  (1)

-------------------------------------------------------------------------------------------------------------------------------------

Job secondary/son

08/11/2014 14:40:20 - Info nbjm (pid=6936) starting backup job (jobid=3263512) for client sdb-win-dc-1.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2
08/11/2014 14:40:20 - Info nbjm (pid=6936) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3263512, request id:{907D7894-217E-11E4-8208-D1D425765B2E})
08/11/2014 14:40:20 - requesting resource MDSP_MEDIA_3_DISK
08/11/2014 14:40:20 - requesting resource netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-1.oi.infra
08/11/2014 14:40:20 - requesting resource netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
08/11/2014 14:40:20 - granted resource  netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-1.oi.infra
08/11/2014 14:40:20 - granted resource  netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
08/11/2014 14:40:20 - granted resource  MediaID=@aaaa9;DiskVolume=PureDiskVolume;DiskPool=MDSP_MEDIA_3_BKP_POOL;Path=PureDiskVolume;StorageServer=netbackup-media-3.adm.infra;MediaServer=netbackup-media-3.adm.infra
08/11/2014 14:40:20 - granted resource  MDSP_MEDIA_3_DISK
08/11/2014 14:40:21 - estimated 9721646 kbytes needed
08/11/2014 14:40:21 - Info nbjm (pid=6936) started backup (backupid=sdb-win-dc-1.oi.infra_1407778821) job for client sdb-win-dc-1.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2 on storage unit MDSP_MEDIA_3_DISK
08/11/2014 14:40:21 - started process bpbrm (pid=14053)
08/11/2014 14:40:21 - Info bpbrm (pid=14053) sdb-win-dc-1.oi.infra is the host to backup data from
08/11/2014 14:40:21 - Info bpbrm (pid=14053) reading file list for client
08/11/2014 14:40:22 - Info bpbrm (pid=14053) starting bpbkar on client
08/11/2014 14:40:22 - connecting
08/11/2014 14:40:22 - connected; connect time: 0:00:00
08/11/2014 14:40:23 - Info bpbkar (pid=3964) Backup started
08/11/2014 14:40:23 - Info bpbrm (pid=14053) bptm pid: 14062
08/11/2014 14:40:23 - Error bpbrm (pid=14053) cannot start nbfsd on netbackup-media-3.adm.infra
08/11/2014 14:40:23 - Info bpbkar (pid=3964) change time comparison:<disabled>
08/11/2014 14:40:23 - Info bpbkar (pid=3964) archive bit processing:<enabled>
08/11/2014 14:40:23 - Warning bpbrm (pid=14053) from client sdb-win-dc-1.oi.infra: WRN - unable to setup NBFSD credentials, disabling granular backups
08/11/2014 14:40:23 - Info bptm (pid=14062) start
08/11/2014 14:40:23 - Info bptm (pid=14062) using 262144 data buffer size
08/11/2014 14:40:23 - Info bptm (pid=14062) using 30 data buffers
08/11/2014 14:40:23 - Info bptm (pid=14062) start backup
08/11/2014 14:40:27 - Info bptm (pid=14062) backup child process is pid 14078
08/11/2014 14:40:27 - begin writing
08/11/2014 14:46:02 - Info bptm (pid=14062) waited for full buffer 9341 times, delayed 21991 times
08/11/2014 14:46:04 - Info bptm (pid=14062) EXITING with status 0 <----------
08/11/2014 14:46:04 - Info netbackup-media-3.adm.infra (pid=14062) StorageServer=PureDisk:netbackup-media-3.adm.infra; Report=PDDO Stats (multi-threaded stream used) for (netbackup-media-3.adm.infra): scanned: 7988609 KB, CR sent: 46809 KB, CR sent over FC: 0 KB, dedup: 99.4%, cache hits: 117967 (97.5%), rebased: 826 (0.7%)
08/11/2014 14:46:04 - Info bpbrm (pid=14053) validating image for client sdb-win-dc-1.oi.infra
08/11/2014 14:46:04 - Info bpbkar (pid=3964) done. status: 1: the requested operation was partially successful
08/11/2014 14:46:04 - end writing; write time: 0:05:37
the requested operation was partially successful  (1)

Riaan.Badenhorst's picture

08/11/2014 14:40:23 - Warning bpbrm (pid=14053) from client sdb-win-dc-1.oi.infra: WRN - unable to setup NBFSD credentials, disabling granular backups

 

Test with this again http://www.symantec.com/docs/TECH124810

and make sure to stop / start nfs on client using

nfsadmin client stop

nfsadmin client start

And test telnet to the nbfsd port on the media server

 

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

#Media Server:

[root@netbackup-media-4.adm.infra ~]# /usr/openv/netbackup/bin/nbfsd -d -v 5 -j 100 -B sdb-win-dc-1.oi.infra_123456789

PORT=7394
CRED1=E1496150A61895EA24E1DFDC2D634961E2707268EBDB34EB8B64615C25725570462983D1443CC4B167C8487608B72546FA9460EA10BC4B7171684FF58507604A
CRED2=5AB22321341981492C2CA24C858020D09B57A8F74D79C778C986D7097A719F16DEF22A5F4A65C41BBBF3B2E4534B4726703B715A98F658CDB3008FD3CC62CCCC
NBFSD STARTED 0

[root@netbackup-media-4.adm.infra ~]# telnet localhost 7394
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.

[root@netbackup-media-4.adm.infra ~]# nc -zv localhost 7394
Connection to localhost 7394 port [tcp/*] succeeded!

[root@netbackup-media-4.adm.infra ~]# telnet sdb-win-dc-1.oi.infra 7394
Trying 10.12.207.49...
telnet: connect to address 10.12.207.49: Connection refused
telnet: Unable to connect to remote host: Connection refused

 

 

 

#Client:

C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server netbackup-media-4.adm.
infra -cred E1496150A61895EA24E1DFDC2D634961E2707268EBDB34EB8B64615C257255704629
83D1443CC4B167C8487608B72546FA9460EA10BC4B7171684FF58507604A *
BASEDIR=
MNTPATH=/NBUFS_A_C91FFE56D18B8055_000
MOUNTPOINT=

telnet netbackup-media-4.adm.infra 7394 succeeded!

STOP/START

nfsadmin client stop

nfsadmin client start

aborting connection, timeout period exceeded

EXIT_STATUS=41

---------------------------------------------------------------------------------------------------------------------------------

This is the correct order, you asked?

 

Riaan.Badenhorst's picture

Hi Alex,

I meant stop/start NFS before starting the test http://www.symantec.com/docs/TECH124810

 

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

#Client

1º C:\Windows\system32>nfsadmin client stop

The service was stopped successfully.

C:\Windows\system32>nfsadmin client start

The service was started successfully.

--------------------------------------------------------------------------------------------------------

6º C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server netbackup-media-4.adm.
infra -cred B708A31BBE254A231879C011EDA8D676F549F31BBBA6A36B233DE295D6EB2F5CE304
2B863207EF2D6E20EECB3511D2B85591BB4FA3914D688954005924CA8FD9 *
nbfs: -cred is required
usage: nbfs { mount | umount [-f] | vmmount | vmunmount} -server <server> -cred
<credential> [-port <port>] [-vmserver <vmserver>] [-esxhost <esx host>] <mnt_po
int>
usage: nbfs activate -server <server> -cred <credential> [-port <port>] <mounted
_export_name>
usage: nbfs deactivate -server <server> -cred <credential> [-port <port>]
usage: nbfs showmount -server <server> [-port <port>]
EXIT_STATUS=20

-------------------------------------------------------------------------------------------------------

7º Telnet netbackup-media-4.adm.infra 7394 sucessed!

#Media Server

2º [root@netbackup-media-4.adm.infra ~]# /usr/openv/netbackup/bin/nbfsd -d -v 5 -j 100 -B sdb-win-dc-1.oi.infra_123456789

PORT=7394
CRED1=B708A31BBE254A231879C011EDA8D676F549F31BBBA6A36B233DE295D6EB2F5CE304
2B863207EF2D6E20EECB3511D2B85591BB4FA3914D688954005924CA8FD9
CRED2=A382A953DB21CD0039CE4F916F64CBDA991519D2C1C93D49B72D2DFA7B4679AD686B64F486D59B64E6595A1F56A43CF224CD61623A39719B0E050E971026AA54
NBFSD STARTED 0

--------------------------------------------------------------------------------------------------------

3º [root@netbackup-media-4.adm.infra ~]# telnet localhost 7394
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.

--------------------------------------------------------------------------------------------------------

 

4º [root@netbackup-media-4.adm.infra ~]# nc -zv localhost 7394
Connection to localhost 7394 port [tcp/*] succeeded!

--------------------------------------------------------------------------------------------------------

5º [root@netbackup-media-4.adm.infra ~]# telnet sdb-win-dc-1.oi.infra 7394         Trying 10.12.207.49...
telnet: connect to address 10.12.207.49: Connection refused
telnet: Unable to connect to remote host: Connection refused

 

 

 

Alex de Souza's picture

additional detail: 

I configured a windows media server for testing, and the GRT backup ran successfully, including the restore has been validated. Only asked to release the ports 111/7394/816/13724/1556/13782/13783 the same thing was done with the media server linux, even more ports.

Windows Server 2008 R2 Enterprise

NBU: 7.6.0.2 Media client

Riaan.Badenhorst's picture

Step 5 is not required (or possible) as 7394 runs on the media server not the client.

Your step 6 failed with "EXIT_STATUS=20" because on syntax "nbfs: -cred is required".

Based on the fact that step 7 worked it would mean the nbfsd & comms is working as you can telnet to 7394

Just retry step 6 and pay attention to your syntax.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Alex de Souza's picture

6º C:\Program Files\Veritas\NetBackup\bin>nbfs mount -server netbackup-media-4.adm.
infra -cred 344E0B954C4D0EA2603022DD7E86CD76D49677725FEA849119A5EE3A5905CCD49188
25FF8BE9E4029C0A4320B22391D40967A52B09844656B72C74216399EB2B *
BASEDIR=
MNTPATH=/NBUFS_A_C58F29D04FCA34FF_000
MOUNTPOINT=
aborting connection, timeout period exceeded
EXIT_STATUS=41

Alex de Souza's picture

Guys, I have made no change in the environment and strangely the backup is running on a host of AD. At one point ends with success and others do not.

Job Master/Father:

09/26/2014 14:27:07 - Info nbjm (pid=15704) starting backup job (jobid=3422774) for client sdb-win-dc-2.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2
09/26/2014 14:27:07 - Info nbjm (pid=15704) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3422774, request id:{572E26D6-45A2-11E4-911F-81AAFA48FDE4})
09/26/2014 14:27:07 - requesting resource MDSP_MEDIA_4_DISK
09/26/2014 14:27:07 - requesting resource netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-2.oi.infra
09/26/2014 14:27:07 - requesting resource netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
09/26/2014 14:27:07 - granted resource  netbackup-master.adm.infra.NBU_CLIENT.MAXJOBS.sdb-win-dc-2.oi.infra
09/26/2014 14:27:07 - granted resource  netbackup-master.adm.infra.NBU_POLICY.MAXJOBS.AD-SDB-Oi-INFRA-WIN-DC_TESTE
09/26/2014 14:27:07 - granted resource  MediaID=@aaaaB;DiskVolume=PureDiskVolume;DiskPool=MDSP_MEDIA_4_BKP_POOL;Path=PureDiskVolume;StorageServer=netbackup-media-4.adm.infra;MediaServer=netbackup-media-4.adm.infra
09/26/2014 14:27:07 - granted resource  MDSP_MEDIA_4_DISK
09/26/2014 14:27:07 - estimated 0 kbytes needed
09/26/2014 14:27:07 - begin Parent Job
09/26/2014 14:27:07 - begin Snapshot: Start Notify Script
09/26/2014 14:27:08 - Info RUNCMD (pid=17352) started
09/26/2014 14:27:08 - Info RUNCMD (pid=17352) exiting with status: 0
Operation Status: 0
09/26/2014 14:27:08 - end Snapshot: Start Notify Script; elapsed time 0:00:01
09/26/2014 14:27:08 - begin Snapshot: Step By Condition
Operation Status: 0
09/26/2014 14:27:08 - end Snapshot: Step By Condition; elapsed time 0:00:00
09/26/2014 14:27:08 - begin Snapshot: Stream Discovery
Operation Status: 0
09/26/2014 14:27:08 - end Snapshot: Stream Discovery; elapsed time 0:00:00
09/26/2014 14:27:08 - begin Snapshot: Read File List
Operation Status: 0
09/26/2014 14:27:08 - end Snapshot: Read File List; elapsed time 0:00:00
09/26/2014 14:27:08 - begin Snapshot: Create Snapshot
09/26/2014 14:27:08 - started process bpbrm (pid=4528)
09/26/2014 14:28:28 - Info bpbrm (pid=4528) sdb-win-dc-2.oi.infra is the host to backup data from
09/26/2014 14:28:28 - Info bpbrm (pid=4528) reading file list for client
09/26/2014 14:28:28 - Info bpbrm (pid=4528) start bpfis on client
09/26/2014 14:29:08 - Info bpbrm (pid=4528) Starting create snapshot processing
09/26/2014 14:29:50 - Info bpfis (pid=472) Backup started
09/26/2014 14:29:50 - Critical bpbrm (pid=4528) from client sdb-win-dc-2.oi.infra: FTL - process_fs_list() failed, status 71
09/26/2014 14:29:50 - Info bpbrm (pid=4528) INF - BPFIS MESSAGE Routing to stream based backup for windows open file backup case, generating remap directive
09/26/2014 14:29:50 - Info bpfis (pid=472) done. status: 0
09/26/2014 14:29:50 - end Snapshot: Create Snapshot; elapsed time 0:02:42
09/26/2014 14:29:50 - Info bpfis (pid=472) done. status: 0: the requested operation was successfully completed
09/26/2014 14:29:50 - end writing
Operation Status: 0
09/26/2014 14:29:50 - end Parent Job; elapsed time 0:02:43
09/26/2014 14:29:50 - Info nbjm (pid=15704) snapshotid=sdb-win-dc-2.oi.infra_1411752427
09/26/2014 14:29:50 - begin Snapshot: Policy Execution Manager Preprocessed
Operation Status: 0
09/26/2014 14:39:28 - end Snapshot: Policy Execution Manager Preprocessed; elapsed time 0:09:38
09/26/2014 14:39:28 - begin Snapshot: Validate Image
Operation Status: 0
09/26/2014 14:39:28 - end Snapshot: Validate Image; elapsed time 0:00:00
09/26/2014 14:39:28 - begin Snapshot: Delete Snapshot
09/26/2014 14:39:28 - started process bpbrm (pid=4960)
09/26/2014 14:40:32 - Info bpbrm (pid=4960) Starting delete snapshot processing
09/26/2014 14:41:53 - Info bpfis (pid=5144) Backup started
09/26/2014 14:41:53 - Critical bpbrm (pid=4960) from client sdb-win-dc-2.oi.infra: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.sdb-win-dc-2.oi.infra_1411752427.1.0
09/26/2014 14:41:53 - Info bpfis (pid=5144) done. status: 4207
09/26/2014 14:41:53 - end Snapshot: Delete Snapshot; elapsed time 0:02:25
09/26/2014 14:41:53 - Info bpfis (pid=5144) done. status: 4207: Could not fetch snapshot metadata or state files
09/26/2014 14:41:53 - end writing
Operation Status: 4207
09/26/2014 14:41:53 - begin Snapshot: End Notify Script
09/26/2014 14:41:53 - Info RUNCMD (pid=29673) started
09/26/2014 14:41:53 - Info RUNCMD (pid=29673) exiting with status: 0
Operation Status: 0
09/26/2014 14:41:53 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 0
the requested operation was successfully completed  (0)

Job secondary/son

09/26/2014 14:29:50 - Info nbjm (pid=15704) starting backup job (jobid=3422776) for client sdb-win-dc-2.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2
09/26/2014 14:29:50 - estimated 0 kbytes needed
09/26/2014 14:29:50 - Info nbjm (pid=15704) started backup (backupid=sdb-win-dc-2.oi.infra_1411752590) job for client sdb-win-dc-2.oi.infra, policy AD-SDB-Oi-INFRA-WIN-DC_TESTE, schedule AD-Full-WIN-DC_1_2 on storage unit MDSP_MEDIA_4_DISK
09/26/2014 14:29:51 - started process bpbrm (pid=4608)
09/26/2014 14:30:15 - Info bpbrm (pid=4608) sdb-win-dc-2.oi.infra is the host to backup data from
09/26/2014 14:30:15 - Info bpbrm (pid=4608) reading file list for client
09/26/2014 14:30:53 - connecting
09/26/2014 14:32:10 - Info bpbrm (pid=4608) starting bpbkar on client
09/26/2014 14:32:10 - connected; connect time: 0:00:00
09/26/2014 14:32:11 - Info bpbkar (pid=4612) Backup started
09/26/2014 14:32:11 - Info bpbrm (pid=4608) bptm pid: 4741
09/26/2014 14:32:11 - Info bpbkar (pid=4612) change time comparison:<disabled>
09/26/2014 14:32:11 - Info bpbkar (pid=4612) archive bit processing:<enabled>
09/26/2014 14:32:11 - Info bptm (pid=4741) start
09/26/2014 14:32:11 - Info bptm (pid=4741) using 262144 data buffer size
09/26/2014 14:32:11 - Info bptm (pid=4741) using 30 data buffers
09/26/2014 14:32:12 - Info bptm (pid=4741) start backup
09/26/2014 14:32:14 - Info bptm (pid=4741) backup child process is pid 4754
09/26/2014 14:32:14 - begin writing
09/26/2014 14:37:02 - Info bpbrm (pid=4608) from client sdb-win-dc-2.oi.infra: TRV - Starting granular backup processing for (System State\Active Directory). This may take a while... 
09/26/2014 14:37:09 - Info bpbrm (pid=4608) from client sdb-win-dc-2.oi.infra: TRV - Successfully finished granular backup processing for (System State\Active Directory). 
09/26/2014 14:38:52 - Info bptm (pid=4741) waited for full buffer 9733 times, delayed 25945 times
09/26/2014 14:38:55 - Info bptm (pid=4741) EXITING with status 0 <----------
09/26/2014 14:38:55 - Info netbackup-media-4.adm.infra (pid=4741) StorageServer=PureDisk:netbackup-media-4.adm.infra; Report=PDDO Stats (multi-threaded stream used) for (netbackup-media-4.adm.infra): scanned: 8250437 KB, CR sent: 29250 KB, CR sent over FC: 0 KB, dedup: 99.6%, cache disabled
09/26/2014 14:38:55 - Info bpbrm (pid=4608) validating image for client sdb-win-dc-2.oi.infra
09/26/2014 14:39:28 - Info bpbkar (pid=4612) done. status: 0: the requested operation was successfully completed
09/26/2014 14:39:28 - end writing; write time: 0:07:14
the requested operation was successfully completed  (0)

Riaan.Badenhorst's picture

Hi Alex,

 

That is strange. What is in the file list?

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Riaan.Badenhorst's picture

USE ALL LOCAL DRIVES

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mark_Solutions's picture

Or at the very least Shadow Copy Components .. System State is for Windows 2000 and earlier...

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.