Shadow Copy Components backup with DFSR ends with EXIT STATUS 69: invalid filelist specification

Article: 100010224
Last Published: 2020-01-10
Ratings: 1 0
Product(s): NetBackup

Problem

A Windows Client running DFSR gets a Shadow Copy Components stream failure - either when run individually or as part of ALL LOCAL DRIVES.

Errors observed in Activity Monitor:
EXIT STATUS 69: invalid filelist specification
 

Error Message

Activity Monitor Job Details:
---------------------------------
- Error bpbrm (pid=10440) from client MyClient: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
- Error bpbrm (pid=10440) from client MyClient: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.JBD - accelerator sent 0 bytes out of 0 bytes to server, optimization 0.0%
.
- Info bpbkar32 (pid=4864) done. status: 69: invalid filelist specification
- end writing; write time: 0:36:24
invalid filelist specification  (69)
 

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

Client 'bpbkar' log snip at General Level = 2:
--------------------
.
<2> ov_log::V_GlobalLog: INF - Using VSS to generate a new SnapshotSetID
<2> ov_log::V_GlobalLog: INF - VssSnapshotVolume- a previous VSS snap is in progress. Entering retry/timeout waiting for snap to complete. Timeout period: 0x7d0
.
.    ( 33 minute timeout )
.
<2> ov_log::V_GlobalLog: INF - StartSnapshotSetWaitForPreviousSnapToComplete - Error. Timed out waiting for previous snap to complete.
<2> ov_log::V_GlobalLog: INF -  EXIT VssSnapshotVolume::StartSnapshotSetWaitForPreviousSnapToComplete() return=[0x80042316 VSS_E_SNAPSHOT_SET_IN_PROGRESS]!
<2> ov_log::V_GlobalLog: INF -  EXIT VssSnapshotVolume::StartSnapshotSet() return=[0x80042316 VSS_E_SNAPSHOT_SET_IN_PROGRESS]!
<2> ov_log::V_GlobalLog: INF - StartSnapshotSet failed with error: [0x80042316][VSS_E_SNAPSHOT_SET_IN_PROGRESS]
<2> ov_log::V_GlobalLog: INF -  EXIT VssSnapshotVolume::Initialize() return=[0x80042316 VSS_E_SNAPSHOT_SET_IN_PROGRESS]!
<2> tar_base::V_vTarMsgW: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.
<2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup
<2> tar_base::V_vTarMsgW: INF - EXIT STATUS 69: invalid filelist specification

 

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

 

Client 'bpfis' Log -  may also show status 156 after timeout period
--------------------------
<2> bpfis main: receive filelist:<NEW_STREAM>
<2> bpfis main: receive filelist:<Shadow Copy Components:\>
<2> bpfis main: receive filelist:<NEW_STREAM>
<2> bpfis main: receive filelist:<C:\>
<2> bpfis main: receive filelist:<NEW_STREAM>
<2> bpfis main: receive filelist:<D:\>
<2> bpfis main: receive filelist:<CONTINUE>
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:23:52.016000 <Thread id - 8668> VSS API ERROR:- API [StartSnapshotSet] return val = 80042316 [VSS_E_SNAPSHOT_SET_IN_PROGRESS]
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:23:57.032000 <Thread id - 1212> VssNode::prepare StartSnapshotSet retry count[1]
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:23:57.063000 <Thread id - 8668> VSS API ERROR:- API [StartSnapshotSet] return val = 80042316 [VSS_E_SNAPSHOT_SET_IN_PROGRESS]
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:24:02.079000 <Thread id - 1212> VssNode::prepare StartSnapshotSet retry count[2]
.
.
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:53:58.910000 <Thread id - 1212> VssNode::prepare StartSnapshotSet retry count[359]
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:54:03.942000 <Thread id - 1212> VssNode::prepare StartSnapshotSet retry count[360]
<2> onlfi_vfms_logf: INF - snapshot services: vss:Fri Dec 20 2019 14:54:03.973000 <Thread id - 8668> VSS API ERROR:- API [StartSnapshotSet] return val = 80042316 [VSS_E_SNAPSHOT_SET_IN_PROGRESS]
<2> onlfi_vfms_logf: INF - snapshot services: vss: "IVssBackupComponents::StartSnapshotSet" failed with error "VSS_E_SNAPSHOT_SET_IN_PROGRESS:(error value=0x80042316)" while trying to start a new snapshot set
<2> onlfi_fim_split: INF - Extracting snapshot client error = 156
<2> onlfi_cleanup: INF - Snapshot client error = 156
<2> get_snc_error: INF - get_snc_error: Extracted snapshot error code 156
 

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

Microsoft Error  in Windows Event Viewer - Application Logs:
 Windows VSS Error  "E7001"

-------------------------
<Date / Time>    VSS    E7001    VssAdmin: Unable to create a shadow copy: Another shadow-copy creation is in progress, so the current shadow copy cannot be created.  
There are a number of common scenarios causing this problem:  * If Shadow Copies of Shared Folders is set up, ensure that no two volumes have schedules that lie within five minutes of each other.           
* If automatic backup of any form is scheduled, ensure that the backup schedule does not overlap with the schedule used for Shadow Copies of Shared Folders.    Generally, retrying the operation after a few minutes or changing the schedule of an automatic task should fix this problem. 
-------------------------
 

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

 
 

Cause

This error occurs because of limitations with Microsoft and VSS.

During a multistreamed backup, when VSS is engaged to perform a snapshot of DFSR content and the rest of System State, it is likely to fail in this way.

 

Solution

* The backup streams for DFSR content and the rest of System State must not run simultaneously in separate streams.  
* Multiple DFSR backup streams must not run simultaneously.


Methods to resolve the situation:
1. If using ALL LOCAL DRIVES, do not enable the "Allow Multiple Data Streams" check box in the Policy Attributes.   This will prevent multiple streams.  When running in a single stream, this error will not occur.
 

2. Create separate policies to isolate the DFSR content from the rest of the client data (System State and Volumes). Adjust the Policy Start Times so the 2 policies do not overlap.  

Using 2 policies to separate the DFSR data from the disk volume backup

EXAMPLE Policy 1  Backup List:
System_State:\
C:\
D:\
E:\
F:\

EXAMPLE Policy 2  Backup List:
Shadow Copy Components:\     (Contains all DFSR folders)

*** Run Policy 2 only at a time when Policy 1 has completed ***
 

 

3. Individual DFSR streams can not overlap.  DFSR and Microsoft and VSS are not capable of running overlapping streams.  If the DFSR VSS Writer is busy on one stream, the other requesting DFSR streams will not be able to properly engage the VSS DFSR Writer and the other streams will fail.  Adjust the start times per DFSR stream so one stream can start and finish before the next stream starts.

 

Applies To

This applies to all Windows versions currently supported by Microsoft.

Was this content helpful?