MS Exchange Backup hangs in some folders

[Lotfi_BOUCHERIT]

Hello,

Our Netbackup 7.1 infra. backs up all our servers with full BMR backup schedules. We discovered lately that one of these servers (an Exchange 2010 server) is not backin up correctly.

The backup job in the Activity Monitor shows as active but it remains not changed for a long time as if it is stuck with some folder.

When I see the folder named in task details, in the Exchange Server, I find that it is with a PadLock.

Here is the job log which doesn't show any information regarding an error or something :

20/11/2014 06:00:16 - Info nbjm(pid=2356) starting backup job (jobid=8888) for client srvXXX-xch-1, policy SrvXXX-xch-1, schedule Incremental  
20/11/2014 06:00:16 - estimated 14194735 Kbytes needed
20/11/2014 06:00:16 - Info nbjm(pid=2356) started backup job for client srvXXX-xch-1, policy SrvXXX-xch-1, schedule Incremental on storage unit srvXXX-nbu-1-hcart-robot-tld-0
20/11/2014 06:00:16 - started process bpbrm (3556)
20/11/2014 06:00:16 - started
20/11/2014 06:00:17 - Info bpbrm(pid=3556) srvXXX-xch-1 is the host to backup data from     
20/11/2014 06:00:21 - Info bpbrm(pid=3556) reading file list from client        
20/11/2014 06:00:21 - connecting
20/11/2014 06:00:23 - Info bpbrm(pid=3556) starting bpbkar32 on client         
20/11/2014 06:00:23 - connected; connect time: 00:00:02
20/11/2014 06:00:34 - Info bpbkar32(pid=61936) Backup started           
20/11/2014 06:00:34 - Info bptm(pid=6044) start            
20/11/2014 06:00:34 - Info bptm(pid=6044) using 65536 data buffer size        
20/11/2014 06:00:34 - Info bptm(pid=6044) setting receive network buffer to 263168 bytes      
20/11/2014 06:00:34 - Info bptm(pid=6044) using 30 data buffers         
20/11/2014 06:00:34 - Info bptm(pid=6044) start backup           
20/11/2014 06:00:34 - Info bptm(pid=6044) backup child process is pid 524.4404       
20/11/2014 06:00:34 - Info bptm(pid=6044) Waiting for mount of media id X561L4 (copy 1) on server srvXXX-nbu-1.
20/11/2014 06:00:34 - Info bptm(pid=524) start            
20/11/2014 06:00:34 - mounting X561L4
20/11/2014 06:01:29 - Info bptm(pid=6044) media id X561L4 mounted on drive index 1, drivepath {5,0,0,0}, drivename HP.ULTRIUM4-SCSI.001, copy 1
20/11/2014 06:01:29 - mounted; mount time: 00:00:55
20/11/2014 06:01:32 - positioning X561L4 to file 314
20/11/2014 06:02:55 - positioned X561L4; position time: 00:01:23
20/11/2014 06:02:55 - begin writing

here too, the name of the file that blocks the backup job:

/C/hp/hpsmh/namazu/pltests/kakasi-3.pl

[Nicolai · Accepted solution]

Pls see : http://www.symantec.com/docs/TECH31513

It may be the next file in the list that block operation - I think what you are seeing is the written file. A .pl is usually a text file (Perl Script).

For debugging you can try to exclude file areas under suspicion as well

[Marianne]

We need to see what happens AFTER  begin writing 

We need to see details of the exact issue on the client.
The piece of job details in your opening post is not showing any error/problem.

Is this a MS-Windows policy type?
If so, problematic files/folder should be displayed as Windows path (C:\...), not unix/linux path.

Exchange data files/folders should be excluded from filesystem policy.

[Lotfi_BOUCHERIT]

Hello, sorry for the late answer...

@Marianne , it just stucks in begin writing, it says nothing,

For the policy type it is MS-Windows, about client backup details, where can i find them??

Thanks in advance

[Marianne]

So, if it just says 'begin writing', how do you know that the backup is getting stuck on a specific file?

Client backup details can be seen on the client in bpbkar log.
This log folder does not exist by default and must be created under ...netbackup\logs.

The other logs that will help are these 2 on the media server:
bptm and bpbrm. Log folders must be created.

[Nicolai]

You can't solve this issue by looking at the GUI, please look at the link I provided in my first post.

[watsons]

what is padlock? 

Like Nicolai said, .pl is most likely a perl script (and maybe it's running)

If it always stuck at that file, and you can't predict when that file is busy, just exclude it. Create a similar file with different name if you really need to back it up.