WRN - can't open file: C:\WINDOWS\system32\rqvxre.u (WIN32 5: Access is denied. ) -- WRN - can't open directory: Q: (WIN32 21: The device is not ready. )

[Zahid_Haseeb]

Environment

Veritas Netbackup Server = 7.1

OS of Veritas Netbackup Server = Win2008 SP2 (32bit)

Single Machine working as Master/Media Server

Client Machine OS = Win2003 SP2 (32bit)

Netbackup Client version = 7.1

Problem

BMR backup failing while taking backup

Activity Monitor Detail Status

=========
Child Process
=========


2/1/2012 8:39:41 PM - Info nbjm(pid=2148) starting backup job (jobid=147410) for client ClusterNode1, policy Exchange2003BMRpolicy, schedule Exchange_2003  
2/1/2012 8:39:41 PM - estimated 69083474 Kbytes needed
2/1/2012 8:39:41 PM - Info nbjm(pid=2148) started backup job for client ClusterNode1, policy Exchange2003BMRpolicy, schedule Exchange_2003 on storage unit Veritas_BMR_Backup
2/1/2012 8:39:41 PM - started process bpbrm (5212)
2/1/2012 8:39:41 PM - started
2/1/2012 8:39:42 PM - Info bpbrm(pid=5212) ClusterNode1 is the host to backup data from     
2/1/2012 8:39:46 PM - Info bpbrm(pid=5212) reading file list from client        
2/1/2012 8:39:46 PM - connecting
2/1/2012 8:39:48 PM - Info bpbrm(pid=5212) starting bpbkar32 on client         
2/1/2012 8:39:48 PM - connected; connect time: 00:00:02
2/1/2012 8:39:51 PM - Info bpbkar32(pid=76920) Backup started           
2/1/2012 8:39:51 PM - Info bptm(pid=4968) start            
2/1/2012 8:39:51 PM - Info bptm(pid=4968) using 262144 data buffer size        
2/1/2012 8:39:51 PM - Info bptm(pid=4968) setting receive network buffer to 1049600 bytes      
2/1/2012 8:39:51 PM - Info bptm(pid=4968) using 30 data buffers         
2/1/2012 8:39:52 PM - Info bptm(pid=4968) start backup           
2/1/2012 8:39:52 PM - Info bptm(pid=4968) backup child process is pid 2812.3340       
2/1/2012 8:39:52 PM - Info bptm(pid=2812) start            
2/1/2012 8:39:52 PM - begin writing
2/1/2012 8:54:44 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open file: C:\WINDOWS\system32\rqvxre.u (WIN32 5: Access is denied. )
2/1/2012 8:56:04 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open file: C:\WINDOWS\system32\zzsgg.q (WIN32 5: Access is denied. )
2/1/2012 9:27:09 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open directory: Q: (WIN32 21: The device is not ready. )
2/1/2012 9:30:17 PM - Info bptm(pid=4968) waited for full buffer 79029 times, delayed 185985 times    
2/1/2012 9:30:28 PM - Info bptm(pid=4968) EXITING with status 0 <----------        
2/1/2012 9:30:28 PM - Info bpbrm(pid=5212) validating image for client ClusterNode1        
2/1/2012 9:30:31 PM - end writing; write time: 00:50:39
2/1/2012 9:30:36 PM - Info bpbkar32(pid=76920) done. status: 1: the requested operation was partially successful    
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.


-------
Master Process
--------

2/1/2012 8:39:41 PM - Info nbjm(pid=2148) starting backup job (jobid=147410) for client ClusterNode1, policy Exchange2003BMRpolicy, schedule Exchange_2003  
2/1/2012 8:39:41 PM - estimated 69083474 Kbytes needed
2/1/2012 8:39:41 PM - Info nbjm(pid=2148) started backup job for client ClusterNode1, policy Exchange2003BMRpolicy, schedule Exchange_2003 on storage unit Veritas_BMR_Backup
2/1/2012 8:39:41 PM - started process bpbrm (5212)
2/1/2012 8:39:41 PM - started
2/1/2012 8:39:42 PM - Info bpbrm(pid=5212) ClusterNode1 is the host to backup data from     
2/1/2012 8:39:46 PM - Info bpbrm(pid=5212) reading file list from client        
2/1/2012 8:39:46 PM - connecting
2/1/2012 8:39:48 PM - Info bpbrm(pid=5212) starting bpbkar32 on client         
2/1/2012 8:39:48 PM - connected; connect time: 00:00:02
2/1/2012 8:39:51 PM - Info bpbkar32(pid=76920) Backup started           
2/1/2012 8:39:51 PM - Info bptm(pid=4968) start            
2/1/2012 8:39:51 PM - Info bptm(pid=4968) using 262144 data buffer size        
2/1/2012 8:39:51 PM - Info bptm(pid=4968) setting receive network buffer to 1049600 bytes      
2/1/2012 8:39:51 PM - Info bptm(pid=4968) using 30 data buffers         
2/1/2012 8:39:52 PM - Info bptm(pid=4968) start backup           
2/1/2012 8:39:52 PM - Info bptm(pid=4968) backup child process is pid 2812.3340       
2/1/2012 8:39:52 PM - Info bptm(pid=2812) start            
2/1/2012 8:39:52 PM - begin writing
2/1/2012 8:54:44 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open file: C:\WINDOWS\system32\rqvxre.u (WIN32 5: Access is denied. )
2/1/2012 8:56:04 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open file: C:\WINDOWS\system32\zzsgg.q (WIN32 5: Access is denied. )
2/1/2012 9:27:09 PM - Warning bpbrm(pid=5212) from client ClusterNode1: WRN - can't open directory: Q: (WIN32 21: The device is not ready. )
2/1/2012 9:30:17 PM - Info bptm(pid=4968) waited for full buffer 79029 times, delayed 185985 times    
2/1/2012 9:30:28 PM - Info bptm(pid=4968) EXITING with status 0 <----------        
2/1/2012 9:30:28 PM - Info bpbrm(pid=5212) validating image for client ClusterNode1        
2/1/2012 9:30:31 PM - end writing; write time: 00:50:39
2/1/2012 9:30:36 PM - Info bpbkar32(pid=76920) done. status: 1: the requested operation was partially successful    
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.

Client ""vssadmin list writer"" command result  (This is also 100% fine)

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\User.One>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {455ea4b8-4c46-4775-b2df-b2ae92a8d76f}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {f13a81f4-2dd1-4d4c-a841-f3c234ef87c2}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {a5e2df69-3ed6-448f-9786-4ce4e7c55cb2}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {bc65bcd5-fba5-4636-9ee2-b4cb15e6cd63}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {1ec2fcc5-54b3-483b-b4c2-c726844fca68}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Service Writer'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {c95d78cb-e828-4e60-9817-249400f3725e}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {e953c760-3ed3-49f1-b52b-57abc9108f93}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {997934e8-e426-41c9-ac96-34b22d48cc10}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {3b1bfe9b-6646-4079-8efb-6fd4e98f8134}
   State: [1] Stable
   Last error: No error


C:\Documents and Settings\User.One>

[Mark_Solutions]

Those files may just be totally locked so that even VSS cannot access them.

Have you renakmed them in th elogs or is that their real names - if real then what on earth are they?

If they are not needed for a restore then just exclude them

[Zahid_Haseeb]

Thanks for your kind reply Mark.

I dont know what are these files. We may exclude them but there may be other files appear in future and we have to excluded them again and again. Any other way ?

[Marianne]

Send the output to the server owners. They need to tell you what these file are and why access is denied and if files can be excluded.

NBU is merely reporting the WIN error.  WINDOWS is preventing NBU Client service account from accessing these files.

Access Denied is normally a Windows permission problem.

Q:\ is the cluster Quorum disk and cannot be backed up.

Any other way ?

Server owners need to grant access to NBU Client service account on everything they need backed up.

[Will_Restore]

WRN - can't open directory: Q: (WIN32 21: The device is not ready. )
 

Looks like inactive node in a cluster cannot backup quorum drive, generally not a problem.

WRN - can't open file: C:\WINDOWS\system32\zzsgg.q (WIN32 5: Access is denied. )
 

I've never seen system files like that. Hope it's not a virus.

[Mark_Solutions]

As the others have said - they are very strange files and do look virus like

Q is usually a Quorum disk so it may be that you need to set up your polcies differently if this is a cluster

One policy for local drives and Shadow Copy Components with each node in it and one policy for shared drives with virtual host name in it