cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.

jjimenez2
Level 5

Would like to seek assitance regarding on this error

05/25/2018 22:24:53 - Info nbjm (pid=7716) starting backup job (jobid=520665) for client BDOWDMI06, policy PROD_BDOWDMI06_WSF, schedule Monthly
05/25/2018 22:24:53 - Info nbjm (pid=7716) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=520665, request id:{5448D12A-0602-4368-9FAB-9E80D022EB20})
05/25/2018 22:24:53 - requesting resource bdowcbs16_stu
05/25/2018 22:24:53 - requesting resource bdowcbs11.NBU_CLIENT.MAXJOBS.BDOWDMI06
05/25/2018 22:24:53 - requesting resource bdowcbs11.NBU_POLICY.MAXJOBS.PROD_BDOWDMI06_WSF
05/25/2018 22:24:55 - granted resource  bdowcbs11.NBU_CLIENT.MAXJOBS.BDOWDMI06
05/25/2018 22:24:55 - granted resource  bdowcbs11.NBU_POLICY.MAXJOBS.PROD_BDOWDMI06_WSF
05/25/2018 22:24:55 - granted resource  MediaID=@aaaay;DiskVolume=PureDiskVolume;DiskPool=bdowcbs16_dp;Path=PureDiskVolume;StorageServer=BDO...
05/25/2018 22:24:55 - granted resource  bdowcbs16_stu
05/25/2018 22:24:56 - estimated 0 kbytes needed
05/25/2018 22:24:56 - Info nbjm (pid=7716) resumed backup (backupid=BDOWDMI06_1527256801) job for client BDOWDMI06, policy PROD_BDOWDMI06_WSF, schedule Monthly on storage unit bdowcbs16_stu
05/25/2018 22:24:57 - started process bpbrm (pid=7308)
05/25/2018 22:24:59 - Info bpbrm (pid=7308) BDOWDMI06 is the host to backup data from
05/25/2018 22:24:59 - Info bpbrm (pid=7308) reading file list for client
05/25/2018 22:25:00 - connecting
05/25/2018 22:25:03 - Info bpbrm (pid=7308) starting bpbkar32 on client
05/25/2018 22:25:03 - connected; connect time: 0:00:00
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) Backup started
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) change time comparison:<disabled>
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) archive bit processing:<enabled>
05/25/2018 22:25:04 - Info bptm (pid=9864) start
05/25/2018 22:25:04 - Info bptm (pid=9864) using 262144 data buffer size
05/25/2018 22:25:04 - Info bptm (pid=9864) setting receive network buffer to 1049600 bytes
05/25/2018 22:25:04 - Info bptm (pid=9864) using 30 data buffers
05/25/2018 22:25:06 - Info bpbkar32 (pid=4172) not using change journal data for <C:\>: not enabled
05/25/2018 22:25:12 - Info bptm (pid=9864) start backup
05/25/2018 22:25:24 - Error bpbrm (pid=7308) from client BDOWDMI06: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
05/25/2018 22:26:05 - Info bptm (pid=9864) backup child process is pid 11848.6564
05/25/2018 22:26:05 - begin writing
05/25/2018 22:26:05 - Info bptm (pid=11848) start
05/25/2018 22:28:51 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Bin\service.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:28:59 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\EpmpCStorage.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:00 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\EpmpCStorage.dat.log (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:01 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\BASH\SPSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:02 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\BASH\ShdSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:07 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\SBSDKEng.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:08 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\SBSDKGbl.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:11 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_CSDK_ServiceG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:12 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_RDRPluginG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:13 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_SNDPluginG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:13 - Info bpbrm (pid=7308) from client BDOWDMI06: TRV - last message being suppressed after 10 occurrences
05/25/2018 22:35:51 - Error bpbrm (pid=7308) from client BDOWDMI06: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
05/25/2018 22:35:51 - Error bptm (pid=11848) socket operation failed - 10054 (at ../child.c.1276)
05/25/2018 22:35:51 - Critical bpbrm (pid=7308) unexpected termination of client BDOWDMI06
05/25/2018 22:35:51 - Error bptm (pid=11848) unable to perform read from client socket, connection may have been broken
05/25/2018 22:37:45 - Info bdowcbs16.ho.ad.bdo (pid=9864) StorageServer=PureDisk:BDOWCBS16; Report=PDDO Stats (multi-threaded stream used) for (BDOWCBS16): scanned: 12791562 KB, CR sent: 30230 KB, CR sent over FC: 0 KB, dedup: 99.8%, cache disabled
05/25/2018 22:37:46 - Error bpbrm (pid=7308) could not send server status message
05/25/2018 22:37:48 - Info bpbkar32 (pid=4172) done. status: 50: client process aborted
05/25/2018 22:37:48 - end writing; write time: 0:11:43
05/28/2018 10:07:39 - job 520665 was restarted as job 522638
client process aborted  (50) Would like to seek assitance to create a case to isolate backup error below. Thanks

05/25/2018 22:24:53 - Info nbjm (pid=7716) starting backup job (jobid=520665) for client BDOWDMI06, policy PROD_BDOWDMI06_WSF, schedule Monthly
05/25/2018 22:24:53 - Info nbjm (pid=7716) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=520665, request id:{5448D12A-0602-4368-9FAB-9E80D022EB20})
05/25/2018 22:24:53 - requesting resource bdowcbs16_stu
05/25/2018 22:24:53 - requesting resource bdowcbs11.NBU_CLIENT.MAXJOBS.BDOWDMI06
05/25/2018 22:24:53 - requesting resource bdowcbs11.NBU_POLICY.MAXJOBS.PROD_BDOWDMI06_WSF
05/25/2018 22:24:55 - granted resource  bdowcbs11.NBU_CLIENT.MAXJOBS.BDOWDMI06
05/25/2018 22:24:55 - granted resource  bdowcbs11.NBU_POLICY.MAXJOBS.PROD_BDOWDMI06_WSF
05/25/2018 22:24:55 - granted resource  MediaID=@aaaay;DiskVolume=PureDiskVolume;DiskPool=bdowcbs16_dp;Path=PureDiskVolume;StorageServer=BDO...
05/25/2018 22:24:55 - granted resource  bdowcbs16_stu
05/25/2018 22:24:56 - estimated 0 kbytes needed
05/25/2018 22:24:56 - Info nbjm (pid=7716) resumed backup (backupid=BDOWDMI06_1527256801) job for client BDOWDMI06, policy PROD_BDOWDMI06_WSF, schedule Monthly on storage unit bdowcbs16_stu
05/25/2018 22:24:57 - started process bpbrm (pid=7308)
05/25/2018 22:24:59 - Info bpbrm (pid=7308) BDOWDMI06 is the host to backup data from
05/25/2018 22:24:59 - Info bpbrm (pid=7308) reading file list for client
05/25/2018 22:25:00 - connecting
05/25/2018 22:25:03 - Info bpbrm (pid=7308) starting bpbkar32 on client
05/25/2018 22:25:03 - connected; connect time: 0:00:00
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) Backup started
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) change time comparison:<disabled>
05/25/2018 22:25:04 - Info bpbkar32 (pid=4172) archive bit processing:<enabled>
05/25/2018 22:25:04 - Info bptm (pid=9864) start
05/25/2018 22:25:04 - Info bptm (pid=9864) using 262144 data buffer size
05/25/2018 22:25:04 - Info bptm (pid=9864) setting receive network buffer to 1049600 bytes
05/25/2018 22:25:04 - Info bptm (pid=9864) using 30 data buffers
05/25/2018 22:25:06 - Info bpbkar32 (pid=4172) not using change journal data for <C:\>: not enabled
05/25/2018 22:25:12 - Info bptm (pid=9864) start backup
05/25/2018 22:25:24 - Error bpbrm (pid=7308) from client BDOWDMI06: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
05/25/2018 22:26:05 - Info bptm (pid=9864) backup child process is pid 11848.6564
05/25/2018 22:26:05 - begin writing
05/25/2018 22:26:05 - Info bptm (pid=11848) start
05/25/2018 22:28:51 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Bin\service.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:28:59 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\EpmpCStorage.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:00 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\EpmpCStorage.dat.log (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:01 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\BASH\SPSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:02 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\BASH\ShdSettg.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:07 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\SBSDKEng.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:08 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\SBSDKGbl.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:11 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_CSDK_ServiceG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:12 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_RDRPluginG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:13 - Warning bpbrm (pid=7308) from client BDOWDMI06: WRN - can't open file: C:\ProgramData\Symantec\Symantec Endpoint Protection\14.0.2349.0100.105\Data\CmnClnt\_lck\_SNDPluginG (WIN32 32: The process cannot access the file because it is being used by another process. )
05/25/2018 22:29:13 - Info bpbrm (pid=7308) from client BDOWDMI06: TRV - last message being suppressed after 10 occurrences
05/25/2018 22:35:51 - Error bpbrm (pid=7308) from client BDOWDMI06: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification
05/25/2018 22:35:51 - Error bptm (pid=11848) socket operation failed - 10054 (at ../child.c.1276)
05/25/2018 22:35:51 - Critical bpbrm (pid=7308) unexpected termination of client BDOWDMI06
05/25/2018 22:35:51 - Error bptm (pid=11848) unable to perform read from client socket, connection may have been broken
05/25/2018 22:37:45 - Info bdowcbs16.ho.ad.bdo (pid=9864) StorageServer=PureDisk:BDOWCBS16; Report=PDDO Stats (multi-threaded stream used) for (BDOWCBS16): scanned: 12791562 KB, CR sent: 30230 KB, CR sent over FC: 0 KB, dedup: 99.8%, cache disabled
05/25/2018 22:37:46 - Error bpbrm (pid=7308) could not send server status message
05/25/2018 22:37:48 - Info bpbkar32 (pid=4172) done. status: 50: client process aborted
05/25/2018 22:37:48 - end writing; write time: 0:11:43
05/28/2018 10:07:39 - job 520665 was restarted as job 522638
client process aborted  (50)

3 ACCEPTED SOLUTIONS

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Can we please try to start from scratch where you give us all relevant info?

Which 7.7 NBU version on the client?
Which W2008 patch level?

What exactly is in Backup Selection in the policy?

Have you checked OS and NBU logs for errors?
OS: Eventviewer System and Application logs
NBU: bpfis and bpbkar (level 3 logs should be fine (unless you log a call with Veritas Support - they will ask for level 5) )

Have you tried to do an OS-level backup (to local disk) of System State and/or Shadow Copy Components?
Is that successful or giving errors as well? 

 

Have you tried any vssadmin commands on the client?
vssadmin list providers
vssadmin list writers 

View solution in original post

Actually, it resolve on reinstalling the Vss and the error found

View solution in original post

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please remember one thing about logging a call with Support: 
If you are as slow with response as in this forum, they will also not put a high priority on your call.
(We have asked back in June already for bpbkar and bpfis logs.)

We see this in bpbkar:

18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - ERROR: Disc \\?\Volume{2b5bf605-6057-4bc6-8b13-b3e9f1e03a63}\ is greater than defined threshold of 63 TB
18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - EXIT VssSnapshotVolume::CheckForUnsupportedDiscs() return=[0x8004230c VSS_E_VOLUME_NOT_SUPPORTED]!
18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - EXIT VssSnapshotVolume::Initialize() return=[0x8004230c VSS_E_VOLUME_NOT_SUPPORTED]!

See this TN: 
Windows System State backup fails if any mounted volume's capacity is greater than 63,000,000,000,000 bytes (57.3 TB)
https://www.veritas.com/support/en_US/article.TECH206217

 

View solution in original post

20 REPLIES 20

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, have you tried to " check the state of VSS and associated Writers" on this client?

Lowell_Palecek
Level 6
Employee

>05/25/2018 22:25:24 - Error bpbrm (pid=7308) from client BDOWDMI06: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.

As @Marianne suggested, it's worth following the advice in the log message.

Whenever you see, "Error bpbrm from client..." check the client log to find out more. Often you will find other trouble before the clent process returns an message to bpbrm. In this case, the client processes are bpfis and bpbkar32. In the bpfis log, you probably will find VSS errors. Likely, it will lead you back to a need to check the VSS writer state, but it will also give you an error code from Microsoft that you can google on to help you correct the problem.

We already restart the running VSS itself but still same problem persist. 

The client OS is Windows 2008

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Can we please try to start from scratch where you give us all relevant info?

Which 7.7 NBU version on the client?
Which W2008 patch level?

What exactly is in Backup Selection in the policy?

Have you checked OS and NBU logs for errors?
OS: Eventviewer System and Application logs
NBU: bpfis and bpbkar (level 3 logs should be fine (unless you log a call with Veritas Support - they will ask for level 5) )

Have you tried to do an OS-level backup (to local disk) of System State and/or Shadow Copy Components?
Is that successful or giving errors as well? 

 

Have you tried any vssadmin commands on the client?
vssadmin list providers
vssadmin list writers 

Heres the VSS result

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: {9db867a6-7a2d-43e5-89e2-280622aa940d}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {ffd37c3c-7eea-465a-a216-6d63941280ef}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {cb605fb6-cc6d-4573-b22e-daf99f5f31d0}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {646939bf-2d70-4eca-9f53-ed38133ccef1}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {42e9e1bb-219e-411d-aadf-16e6bfbcc228}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {bb3f23d0-2eed-42b6-bcba-ccc5c3fcbc85}
State: [1] Stable
Last error: No error

 

The NBU version is 7.7.3

No successful backup with this client.

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@jjimenez2

Thanks for marking my post as Solution, but could you please tell us how exactly the issue was solved? 

 

Actually, it resolve on reinstalling the Vss and the error found

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks for the feedback! This will help other community members with similar problems.

Hi Mariane,

I need your help, this not resolve

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please give us something to work with.
Do you have logs on the client?
Level 3 bpfis and bpbkar logs may help.
Please copy log files to bpfis.txt and bpbkar.txt and upload.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@jjimenez2

I just read through the previous posts again. 
You have not replied to any of these questions:

Which W2008 patch level?

What exactly is in Backup Selection in the policy?

Have you checked OS and NBU logs for errors?
OS: Eventviewer System and Application logs
NBU: bpfis and bpbkar (level 3 logs should be fine (unless you log a call with Veritas Support - they will ask for level 5) )

Have you tried to do an OS-level backup (to local disk) of System State and/or Shadow Copy Components?
Is that successful or giving errors as well? 

Hi Marianne,

 

Will upload here the logs.

We run backup now and wait for it to finish.

We terminate other running job for some troubleshooting purposes.

What exactly is in Backup Selection in the policy? = system state and c drive

Have you checked OS and NBU logs for errors?
OS: Eventviewer System and Application logs
NBU: bpfis and bpbkar (level 3 logs should be fine (unless you log a call with Veritas Support - they will ask for level 5) 

= We escalate the issue to microsoft but no error logs found.

=We enable the logging (verbose, database .. on client BAR )

Have you tried to do an OS-level backup (to local disk) of System State and/or Shadow Copy Components?
Is that successful or giving errors as well? 

=Still waiting to finish the backup

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please upload client's bpbkar and bpfis logs as .txt attachments. 

I already log case for this error.

They did was

-Exclude the antivirus

-Some changes on registry

-Reinstall the nbu client

still same problem persist.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please remember one thing about logging a call with Support: 
If you are as slow with response as in this forum, they will also not put a high priority on your call.
(We have asked back in June already for bpbkar and bpfis logs.)

We see this in bpbkar:

18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - ERROR: Disc \\?\Volume{2b5bf605-6057-4bc6-8b13-b3e9f1e03a63}\ is greater than defined threshold of 63 TB
18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - EXIT VssSnapshotVolume::CheckForUnsupportedDiscs() return=[0x8004230c VSS_E_VOLUME_NOT_SUPPORTED]!
18:21:45.144 [4936.5772] <2> ov_log::V_GlobalLog: INF - EXIT VssSnapshotVolume::Initialize() return=[0x8004230c VSS_E_VOLUME_NOT_SUPPORTED]!

See this TN: 
Windows System State backup fails if any mounted volume's capacity is greater than 63,000,000,000,000 bytes (57.3 TB)
https://www.veritas.com/support/en_US/article.TECH206217