cancel
Showing results for 
Search instead for 
Did you mean: 

Status Code 1 - WRN - can't open file

Cunha_Julio_Ces
Level 2
Partner Accredited Certified

Hello everyone,

 

I need an assistence about the status code 1 WRN - can't open file.

Currently I have an job showing status code 1 like follow bellow.

I have checked in master server, host properties -> Master Servers - > Client attributies -> Windows Open Files Backups and Enable Windows Open File backups for this client is enable.

After that, I created a new policy on Master Server for this client, but the issue persist.

I have changed the policy storage from robot to disk or from disk to robot but no worked.

There are any other step to do to resolve this case?

************************

some informations about vssadim


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

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {13bc4dd5-9210-47b6-a67d-f38dcf2a9f57}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {99273546-552d-4797-9483-3cfb1ca090b9}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f9295536-612d-47f5-867f-7b8291562f73}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {cff0bbc7-690a-4284-a7d3-cb9d6b961557}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {6ec0af63-c2ff-4ce3-a30d-f89bc476105a}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {18e4f52f-63a3-42c7-9377-6b276abeee07}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {079147c2-423e-486a-98a0-496df34b7850}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {835419ae-183f-4eac-b6f8-fa9e0c4b671d}
   State: [1] Stable
   Last error: No error


C:\>

*************************

 

NetBackup Details

21/01/2016 14:24:05 - Info nbjm(pid=10664) starting backup job (jobid=1985306) for client srv10826, policy Server_Name, schedule Full-Weekly  
21/01/2016 14:24:05 - Info nbjm(pid=10664) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1985306, request id:{0C9FAE30-4B5B-4098-B710-9710264F4052})  
21/01/2016 14:24:05 - requesting resource srv10420-hcart-robot-acs-0
21/01/2016 14:24:05 - requesting resource bkpserver01.NBU_CLIENT.MAXJOBS.srv10826
21/01/2016 14:24:05 - requesting resource bkpserver01.NBU_POLICY.MAXJOBS.Server_Name
21/01/2016 14:24:06 - granted resource bkpserver01.NBU_CLIENT.MAXJOBS.srv10826
21/01/2016 14:24:06 - granted resource bkpserver01.NBU_POLICY.MAXJOBS.Server_Name
21/01/2016 14:24:06 - granted resource AA0708
21/01/2016 14:24:06 - granted resource Drive019
21/01/2016 14:24:06 - granted resource srv10420-hcart-robot-acs-0
21/01/2016 14:24:07 - estimated 17678049 Kbytes needed
21/01/2016 14:24:07 - Info nbjm(pid=10664) started backup (backupid=srv10826_1453393446) job for client srv10826, policy Server_Name, schedule Full-Weekly on storage unit srv10420-hcart-robot-acs-0
21/01/2016 14:24:08 - started process bpbrm (11772)
21/01/2016 14:24:12 - Info bpbrm(pid=11772) starting bptm           
21/01/2016 14:24:12 - Info bpbrm(pid=11772) Started media manager using bpcd successfully       
21/01/2016 14:24:15 - Info bpbrm(pid=11772) srv10826 is the host to backup data from     
21/01/2016 14:24:15 - Info bpbrm(pid=11772) telling media manager to start backup on client     
21/01/2016 14:24:15 - Info bptm(pid=16868) using 65536 data buffer size        
21/01/2016 14:24:15 - Info bptm(pid=16868) using 256 data buffers         
21/01/2016 14:24:16 - Info bptm(pid=16868) start backup           
21/01/2016 14:24:16 - Info bptm(pid=16868) Waiting for mount of media id AA0708 (copy 1) on server srv10420. 
21/01/2016 14:24:22 - mounting AA0708
21/01/2016 14:24:24 - Info bpbrm(pid=10972) sending bpsched msg: CONNECTING TO CLIENT FOR srv10826_1453393446     
21/01/2016 14:24:24 - connecting
21/01/2016 14:24:25 - Info bptm(pid=14476) setting receive network buffer to 263168 bytes      
21/01/2016 14:24:25 - Info bpbrm(pid=10972) start bpbkar32 on client         
21/01/2016 14:24:26 - connected; connect time: 0:00:02
21/01/2016 14:24:30 - Info bpbkar32(pid=4616) Backup started           
21/01/2016 14:24:30 - Info bpbrm(pid=10972) Sending the file list to the client      
21/01/2016 14:24:30 - Info bpbkar32(pid=4616) change time comparison:<disabled>          
21/01/2016 14:24:30 - Info bpbkar32(pid=4616) archive bit processing:<disabled>          
21/01/2016 14:24:32 - Info bpbkar32(pid=4616) not using change journal data for <C:\>: not configured for use  
21/01/2016 14:24:32 - Info bpbkar32(pid=4616) not using change journal data for <D:\>: not configured for use  
21/01/2016 14:25:11 - Info bptm(pid=16868) media id AA0708 mounted on drive index 15, drivepath {7,0,1,0}, drivename Drive019, copy 1
21/01/2016 14:25:12 - mounted; mount time: 0:00:50
21/01/2016 14:25:19 - positioning AA0708 to file 49
21/01/2016 14:27:27 - positioned AA0708; position time: 0:02:08
21/01/2016 14:27:27 - begin writing
21/01/2016 14:28:09 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\System Volume Information\Syscache.hve.LOG2 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:28:32 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\Cluster\CLUSDB.LOG1 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:28:32 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\Cluster\CLUSDB.LOG2 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:46 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive0.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:46 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\LocalService\AppData\Local\lastalive1.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:48 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG1 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:48 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\LocalService\NTUSER.DAT.LOG2 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:48 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG1 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:48 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\ServiceProfiles\NetworkService\NTUSER.DAT.LOG2 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:49 - Warning bpbrm(pid=10972) from client srv10826: WRN - can't open file: C:\Windows\System32\config\DEFAULT.LOG1 (WIN32 32: The process cannot access the file because it is being used by another process. )
21/01/2016 14:29:49 - Info bpbrm(pid=10972) from client srv10826: TRV - last message being suppressed after 10 occurrences 
21/01/2016 14:33:06 - Info bpbrm(pid=11772) media manager for backup id srv10826_1453393446 exited with status 0: the requested operation was successfully completed
21/01/2016 14:33:07 - Info bpbrm(pid=11772) child done, status 1         
21/01/2016 14:33:08 - end writing; write time: 0:05:41
the requested operation was partially successful(1)
 
The job was successfully completed, but some files may have been
busy or inaccessible. See the problems report or the client's logs for more details.

1 ACCEPTED SOLUTION

Accepted Solutions

sdo
Moderator
Moderator
Partner    VIP    Certified

I suspect that the file locks are because the volume could not be snaphot by VSS, and the client dropped to using plain file system backup.

When checking VSS, I have seen cases where "vssadmin list writers" shows no problems, but one of the other list commands fails or hangs, so I always run all five list commands to make sure that no other part of VSS has come to a sticky end.

After that, check the NetBackup Client bpbkar and bpfis logs - especially look for any odd "BEDS" error codes with a hexadecimal value, and any non-zero "Win32" error codes.

After that, it's time to dive through the Windows event logs for application and setup and system entries for anything to do with volume shadowing.

View solution in original post

1 REPLY 1

sdo
Moderator
Moderator
Partner    VIP    Certified

I suspect that the file locks are because the volume could not be snaphot by VSS, and the client dropped to using plain file system backup.

When checking VSS, I have seen cases where "vssadmin list writers" shows no problems, but one of the other list commands fails or hangs, so I always run all five list commands to make sure that no other part of VSS has come to a sticky end.

After that, check the NetBackup Client bpbkar and bpfis logs - especially look for any odd "BEDS" error codes with a hexadecimal value, and any non-zero "Win32" error codes.

After that, it's time to dive through the Windows event logs for application and setup and system entries for anything to do with volume shadowing.