Video Screencast Help

Status Code 41 - dos_backup::V_PreProcessing: INF - no access token: scheduled backup

Created: 20 Aug 2012 | 6 comments

Master Server: Windows 2003 STD SP2 64bit, Netbackup 6.5.4
Media Server: Same as master for this policy.

Client: Exchange 2007 SP1 Rollup 9 Mailbox server role, Windows server 2008 Ent SP2 64bit

Policy Type: Full and Incremental both fail.

Symptoms: Policy starts anc connects to the client. The backups never starts to write. The backup job although timed out from the master server, appears still active on the clients "Job Tracker". To clear the backup queue all netbackup services need to be bounced.

Steps Takes: Time out period adjusted.

Backups fail with error code 41:

8/20/2012 3:54:59 PM - requesting resource d0001bms01-hcart-robot-tld-0
8/20/2012 3:54:59 PM - requesting resource d0001bms01.NBU_CLIENT.MAXJOBS.D0001EMB03.gov.local
8/20/2012 3:54:59 PM - requesting resource d0001bms01.NBU_POLICY.MAXJOBS.DC1-Exchange.InformationStore.EMB03
8/20/2012 3:55:00 PM - granted resource d0001bms01.NBU_CLIENT.MAXJOBS.D0001EMB03.gov.local
8/20/2012 3:55:00 PM - granted resource d0001bms01.NBU_POLICY.MAXJOBS.DC1-Exchange.InformationStore.EMB03
8/20/2012 3:55:00 PM - granted resource 000013
8/20/2012 3:55:00 PM - granted resource D0001R0TD2-LTO4
8/20/2012 3:55:00 PM - granted resource d0001bms01-hcart-robot-tld-0
8/20/2012 3:55:00 PM - estimated 2029760 kbytes needed
8/20/2012 3:55:00 PM - started process bpbrm (2972)
8/20/2012 3:55:02 PM - connecting
8/20/2012 3:55:04 PM - connected; connect time: 00:00:02
8/20/2012 4:55:04 PM - end writing
network connection timed out(41)

Client bpbkar log only shows:

4:01:11.506 PM: [16252.14916] <2> WinMain: DAT - _pgmptr = 'D:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe'
4:01:11.506 PM: [16252.14916] <2> WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 479715 -to 0 -clnt D0001EMB03.gov.local -class DC1-Exchange.InformationStore.EMB03 -sched Exch_Dy_SG_Diff -st CINC -bpstart_to 3600 -bpend_to 300 -read_to 3600 -blks_per_buffer 128 -use_otm -fso -b D0001EMB03.gov.local_1345492500 -kl 28 -ct 16 -use_ofb '
4:01:11.506 PM: [16252.14916] <2> date_debug: DAT - timezone: SA Western Standard Time, offset=14400, dst: NONE
4:01:11.506 PM: [16252.14916] <2> date_debug: DAT - current time: 1345492871, 8/20/2012 4:01:11 PM
4:01:11.506 PM: [16252.14916] <2> date_debug: DAT - 01/01/94 UCT:  757382400, 12/31/1993 8:00:00 PM
4:01:11.506 PM: [16252.14916] <2> date_debug: DAT - 07/01/94 UCT:  773020800, 6/30/1994 8:00:00 PM
4:01:11.506 PM: [16252.14916] <2> WinMain: DAT - standard input handle = 556
4:01:11.506 PM: [16252.14916] <2> WinMain: DAT - standard output handle = 144
4:01:11.506 PM: [16252.14916] <2> WinMain: DAT - standard error handle = 348
4:01:11.506 PM: [16252.14916] <4> tar_backup::V_SetupJobData: INF - dwJobData: 00000000
4:01:11.506 PM: [16252.14916] <4> tar_backup::V_SetupJobData: INF -     dwJob: 00000000
4:01:11.506 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
4:01:11.506 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
4:01:11.506 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
4:01:11.522 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
4:01:11.522 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
4:01:11.522 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - user name: root
4:01:11.522 PM: [16252.14916] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup

Comments 6 CommentsJump to latest comment

Marianne's picture

Backup stream was never even started on the client.

Do you only have this problem with Exchange backups or normal MS-Windows policy as well?

Have you checked Event Viewer logs for errors?

PLEASE disable Client Job Tracker on all Clients.

PS: I hope you are planning to upgrade your environment SOON? 
NBU 6.x support will reach End of Support Life on 3 October.

There were all sorts of bugs/issues with W2008 in older versions of NBU. 

Please upgrade your entire environment to NBU 7.5.0.3.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Kristopher.Persad's picture

Yes, this backup has worked before. I don't remember any changes in the backup policy or events that would have resulted in this problem.

This is only policy for this client. We don't backup anything on windows as this is a VCS cluster, so there really isn't the need. I actually alerted our change department of the EOSL so we should be rolling out 7.5 soon :).

Here's the funny bit though, when i fail over this service group to another node the backup works for a while and then stops working throwing this error.

I will put through a change to have the Client Tracker Disabled.

Mark_Solutions's picture

You are on 6.5.4 I see - is the client on the same level as that?

Best practice is to have them match when doing exchange backups (good that you will be upgrading soon)

There are a lot of exchange fixes included in 6.5.6 and that may be a quick fix for now to upgrade Master, Media and Exchange nodes.

Also remember to always set any client host properties you may have set up for each node and not for the virtual server name otherwise they will only get applied to the active node and a fail over would loose the settings - it may be worth just checking to see if all client host properties are the same for each node just in case something there is affecting things.

Hope this helps

Authorised Symantec Consultant

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

Kristopher.Persad's picture

Yes, the client is at the same level. Client tracker disabled, but no joy...

Mark_Solutions's picture

Worth the initial patch to 6.5.6 first whilst you want for the big upgrade

Authorised Symantec Consultant

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