System State Components are missing from Backups
We have discovered some of the System State Components are missing from our Backups. While we are trying to restore the server's system state, the recovery is failing. System state backup along with Filesystem backups are getting completed without any issues. These components also remain unavailable while performing windows native backup. This issue is under investigation with Microsoft. At the same time, we would like to have one script created which will be used as bpstart_notify batch script which will check the following components before the backup gets triggered. If the components are missing, the backup will not get triggered. ASR - Automated system recovery Background intelligent transfer server COM + class registration database Performance counter registry system files task scheduler vss express writer store windows management instrumentation Can anyone help me with such a script? Or if there is an alternate option for this. Thanks in advance.874Views0likes2CommentsProblem 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: (C:)\\?\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?Solved3.9KViews0likes4CommentsHow unix backup works?
Hi, Can anybody please explain how unix file system backup works ? We have vss in windows filesystem backup which is needed as there are many files being used at the time of backup, what is the similar technology in unix? And for a unix incrimental backup, is netbackup using atime or mtime to backup changed files?930Views0likes2CommentsMS-Windows policy and VSS question
Hi everyone, Just a quick question regarding an MS-Windows policy and VSS. Does the policy backup from the VSS snapshot or does it only use VSS for open files? If the backup takes 7 hours, is there a chance of backing up changes files during that 7 hours? Or will the backup only run from the VSS snapshot taken when the backup starts? We need to backup a file/folder structure at a specific time on a physical machine. Any advise would be much appreciated! Thanks in advance!Solved1.5KViews0likes4Comments