cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Problem with VSS on a physical Windows Server

Hi,

I am adding a physical Windows Server 2016machine as a first client in a new Windows Policy (This is a new NetBackup installation, version 8.1.1). The backups fail with status 69, the log says (some host names edited throughout):

[...]

07.06.2018 12:43:59 - Info bpbkar (pid=13064) will attempt to use change journal data for <C:\>
07.06.2018 12:43:59 - Info bpbkar (pid=13064) not using change journal data for <System State:\>: not supported for non-local volumes / file systems
07.06.2018 12:43:59 - Info bpbkar (pid=13064) not using change journal data for <_BACKUP_SPECIAL_OBJECTS AFTER System State:>: not supported for non-local volumes / file systems
07.06.2018 12:43:59 - Info bpbkar (pid=13064) not using change journal data for <EFI System Partition:\>: not supported for non-local volumes / file systems
07.06.2018 12:44:03 - Error bpbrm (pid=62449) from client <client>: 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
07.06.2018 12:44:09 - Info bpbkar (pid=13064) not using change journal data for <C:\>: no previous track log
07.06.2018 12:44:51 - Info bpbkar (pid=13064) 5000 entries sent to bpdbm
07.06.2018 12:45:11 - Info bpbkar (pid=13064) 10000 entries sent to bpdbm
07.06.2018 12:45:36 - Info bpbkar (pid=13064) 15000 entries sent to bpdbm
07.06.2018 12:45:54 - Info bpbkar (pid=13064) 20000 entries sent to bpdbm
07.06.2018 12:46:26 - Info bpbkar (pid=13064) 25000 entries sent to bpdbm
07.06.2018 12:46:44 - Error bpbrm (pid=62449) from client <client>: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.JBD - accelerator sent 6763415552 bytes out of 6732860928 bytes to server, optimization 0.0%
07.06.2018 12:46:46 - Error bptm (pid=62640) media manager terminated by parent process
07.06.2018 12:46:51 - Info <appliance> (pid=62640) StorageServer=PureDisk:<appliance>; Report=PDDO Stats (multi-threaded stream used) for (<appliance>): scanned: 6575591 KB, CR sent: 18475 KB, CR sent over FC: 0 KB, dedup: 99.7%, cache disabled
07.06.2018 12:46:52 - Error bpbrm (pid=62449) could not send server status message to client
07.06.2018 12:46:53 - Info bpbkar (pid=13064) done. status: 69: invalid filelist specification
07.06.2018 12:46:40 - end writing; write time: 0:02:54
invalid filelist specification  (69)
07.06.2018 12:46:55 - Info bpbrm (pid=63398) Starting delete snapshot processing
07.06.2018 12:46:56 - Info bpfis (pid=11140) Backup started
07.06.2018 12:46:56 - Warning bpbrm (pid=63398) from client <client>: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.<client>_1528368217.1.0
07.06.2018 12:46:56 - Info bpfis (pid=11140) done. status: 4207
07.06.2018 12:46:56 - Info bpfis (pid=11140) done. status: 4207: Could not fetch snapshot metadata or state files

 

- "vssadmin list writers" on the client shows "No errors" and "stable" for all writers

- The backup stores about 6GB (of about 56GB on the disk) of data, so at least something must be working

- A VSS backup using Windows Backup succeeded

- I have tried all available options for the VSS provider type, the error is always the same

- During the (NetBackup) backup, "vssadmin list shadows" shows an active shadow copy that did not exists before the backup:

C:\Windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Contents of shadow copy set ID: {306403af-d5a9-4d24-b3c2-4914a0a1a5a8}
   Contained 1 shadow copies at creation time: 6/7/2018 12:43:54 PM
      Shadow Copy ID: {e07da3a5-2dba-4544-b3f4-9893df0759d8}
         Original Volume: (CSmiley Happy\\?\Volume{aa396902-6d6d-48a3-a039-67d87383d939}\
         Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy10
         Originating Machine: <client>
         Service Machine: <client>
         Provider: 'Microsoft Software Shadow Copy provider 1.0'
         Type: ApplicationRollback
         Attributes: Persistent, No auto release, Differential

Any ideas anybody?

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Problem with VSS on a physical Windows Server

Can you provide the bpbkar and event logs (app / system) in text format immediately after performing an attempt of the backup in question?

Also check out the following article:

https://www.veritas.com/support/en_US/article.TECH206217

View solution in original post

4 Replies
Highlighted
Accepted Solution!

Re: Problem with VSS on a physical Windows Server

Can you provide the bpbkar and event logs (app / system) in text format immediately after performing an attempt of the backup in question?

Also check out the following article:

https://www.veritas.com/support/en_US/article.TECH206217

View solution in original post

Highlighted

Re: Problem with VSS on a physical Windows Server

What is the Backup Selection in your policy?

Highlighted

Re: Problem with VSS on a physical Windows Server

Spot on, @J_MCCOLL! Thank you. Even though the large disks were excluded in the backup policy, they were apparently still scanned and the backup failed. I changed the registry parameter and the backup succeeded.

Highlighted

Re: Problem with VSS on a physical Windows Server


@Marianne wrote:

What is the Backup Selection in your policy?


ALL_LOCAL_DRIVES, with some NTFS mount points excluded in the host properties. The article supplied by @J_MCCOLL had the solution, though.