cancel
Showing results for 
Search instead for 
Did you mean: 

Nebackup can't open object system state, backup partially successful.

ArsalanAlli
Level 3

Hello everyone,

My server and client version is 7.6.0.4.

Server and client's OS is also same , Windows 2008 R2.

When i try to run the backup with BMR option enabled, i am getting these messages/error.

I have enabled the VSS option in Server's client attributes setting.

Any ideas?? waiting for your kind response.


12/14/2018 8:30:29 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State: (WIN32 3758161611: Unknown error)
12/14/2018 8:30:30 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Task Scheduler\TasksStore (WIN32 3758161629: Unknown error)
12/14/2018 8:30:30 PM - Error bpbrm(pid=4756) from client WIN-D4DTAKLPABL: ERR - Error encountered while attempting to get additional files for System State:\
12/14/2018 8:30:30 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\VSS Express Writer Store\WriterMetadataStore (WIN32 3758161629: Unknown error)
12/14/2018 8:30:31 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Performance Counter\PerformanceCounters (WIN32 3758161629: Unknown error)
12/14/2018 8:30:54 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\System Files\System Files (WIN32 3758161629: Unknown error)
12/14/2018 8:30:55 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Automated System Recovery\BCD\BCD (WIN32 3758161629: Unknown error)
12/14/2018 8:30:55 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Internet Information Services\IISMETABASE (WIN32 3758161629: Unknown error)
12/14/2018 8:30:55 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Internet Information Services\IISCONFIG (WIN32 3758161629: Unknown error)
12/14/2018 8:30:56 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\COM+ Class Registration Database\COM+ REGDB (WIN32 3758161629: Unknown error)
12/14/2018 8:30:56 PM - Warning bpbrm(pid=4756) from client WIN-D4DTAKLPABL: WRN - can't open object: System State:\Registry\Registry (WIN32 3758161629: Unknown error)
12/14/2018 8:30:56 PM - Info bpbrm(pid=4756) from client WIN-D4DTAKLPABL: TRV - last message being suppressed after 10 occurrences
12/14/2018 8:30:56 PM - Info bptm(pid=5108) waited for full buffer 597888 times, delayed 1890680 times
12/14/2018 8:31:08 PM - Info bptm(pid=5108) EXITING with status 0 <----------
12/14/2018 8:31:09 PM - Info bpbrm(pid=4756) validating image for client WIN-D4DTAKLPABL
12/14/2018 8:31:12 PM - Info bpbkar32(pid=5924) done. status: 1: the requested operation was partially successful
12/14/2018 8:31:12 PM - end writing; write time: 8:12:07
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

Looks like my clinet was not updated to 7.6.0.4 . After applying the patch it resolved the issue. System state backup has been completed. This looks like a bug with 7.6.0.1 and windows 2k8 R2 combined.

So now i am  getting a new error at the end of the BMR restore finalization process.

"Unable to make Registry modification required to boot the system"

KB100006227 suggested that i should be running 7.6.1 or later to restore on GPT/EFI based system.

Should i upgrade my server and client to 7.6.1 for this restore to succeed ? and yes this is a DSR.

 

Waiting for your kind response.

View solution in original post

7 REPLIES 7

VirgilDobos
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

There are several situations that can lead to this issue. Have you come across these articles? 

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

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

--Virgil

i have assigned a drive letter to system drive but i am still getting the errors while taking system state backup.

attached is the bpbkar log of the client.

i have taken the system state backup using windows wbadmin utility and it completed successfuly. 

Your bpbkar log shows this error. It comes from the VSS system. I've never seen it before in the 11 years i've been looking at NetBackup snapshot logs. A Web search shows multiple vendors blaming third-party VSS providers when you get this error.

Unable to add volume \\?\Volume{f86db146-da1b-11e7-9917-806e6f6e6963}\ 0x8004230f
EXIT VssSnapshotVolume::AddToSnapshotSet() return=[0x8004230f VSS_E_UNEXPECTED_PROVIDER_ERROR]!
Error (0x8004230f) from VSS -  VSS_E_UNEXPECTED_PROVIDER_ERROR

Marianne
Level 6
Partner    VIP    Accredited Certified

Google found this link that might be helpful:

KB01368 - Troubleshooting VSS_E_UNEXPECTED_PROVIDER_ERROR
https://techsupport.osisoft.com/Troubleshooting/KB/KB01368

 

sorry for the late reply as i was busy in another project...i'll do the steps mentioned in KB and get back with the results.

Thanks

Looks like my clinet was not updated to 7.6.0.4 . After applying the patch it resolved the issue. System state backup has been completed. This looks like a bug with 7.6.0.1 and windows 2k8 R2 combined.

So now i am  getting a new error at the end of the BMR restore finalization process.

"Unable to make Registry modification required to boot the system"

KB100006227 suggested that i should be running 7.6.1 or later to restore on GPT/EFI based system.

Should i upgrade my server and client to 7.6.1 for this restore to succeed ? and yes this is a DSR.

 

Waiting for your kind response.

Marianne
Level 6
Partner    VIP    Accredited Certified

@ArsalanAlli

If you want an honest answer:

You should upgrade to a supported NBU version. NBU 7.7.3 as a minimum.
Current latest version is 8.1.2. 

All support for NBU 7.6.x ended early 2016. 
I would not even attempt BMR on unsupported NBU version.