Forum Discussion

felix_nguyen's avatar
felix_nguyen
Level 4
10 years ago

System state restore incomplete - programs cannot be started 0xc0000142

Hi all,

 

I am trying to restore a system to a different physical server which has the same hardware for test purposes. 

I followed this manual: https://support.symantec.com/en_US/article.TECH56473.html

Unfortunately the restore of the volumes were partially successful and the System State restore was incomplete with the following error message:

"1: (2808) Windows File System policy restore error"

The server boots normally but I can't open some programs like cmd.exe and I get this error message:

The application was unable to start correctly (0xc0000142). Click OK to close the application.

Can someone please tell me what's wrong with or how I can solve this problem?

 

More details for the System State restore:

02.07.2015 09:43:01 - begin Restore
02.07.2015 09:43:05 - restoring from image xxx_1435767073
02.07.2015 09:43:07 - Info bprd (pid=7224) Restoring from copy 1 of image created 07/01/15 18:11:13 from policy FS
02.07.2015 09:43:09 - Info bpbrm (pid=8664) servername is the host to restore to
02.07.2015 09:43:09 - Info bpbrm (pid=8664) reading file list for client
02.07.2015 09:43:10 - connecting
02.07.2015 09:43:10 - Info bpbrm (pid=8664) starting bptm
02.07.2015 09:43:12 - Info tar32 (pid=2252) Restore started
02.07.2015 09:43:12 - connected; connect time: 0:00:00
02.07.2015 09:43:12 - Info bptm (pid=7408) start
02.07.2015 09:43:12 - started process bptm (pid=7408)
02.07.2015 09:43:12 - Info bptm (pid=7408) reading backup image
02.07.2015 09:43:13 - Info bptm (pid=7408) using 512 data buffers
02.07.2015 09:43:13 - Info bptm (pid=7408) spawning a child process
02.07.2015 09:43:13 - Info bptm (pid=7408) child pid: 8500
02.07.2015 09:43:13 - Info bptm (pid=8500) start
02.07.2015 09:43:13 - started process bptm (pid=8500)
02.07.2015 09:43:13 - begin reading
02.07.2015 09:43:17 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\Task Scheduler\TasksStore
02.07.2015 09:45:54 - Warning bpbrm (pid=8664) from client servername: WRN - error writing object: System State:\System Files\System Files
02.07.2015 09:45:55 - Warning bpbrm (pid=8664) from client servername: WRN - error writing byte: 1995937280
02.07.2015 09:45:55 - Warning bpbrm (pid=8664) from client servername: WRN - desired byte count: 65536
02.07.2015 09:45:55 - Warning bpbrm (pid=8664) from client servername: WRN - actual byte count: 51208
02.07.2015 09:46:02 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\Internet Information Services\IISMETABASE
02.07.2015 09:46:06 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\Registry\Registry
02.07.2015 09:46:06 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\Automated System Recovery\BCD\BCD
02.07.2015 09:46:06 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\COM+ Class Registration Database\COM+ REGDB
02.07.2015 09:46:07 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\Windows Management Instrumentation\WMI
02.07.2015 09:46:08 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\_SharedHardlinkData_\14865af6.10000.3809
02.07.2015 09:46:10 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\_SharedHardlinkData_\14865af6.10000.3aeb
02.07.2015 09:46:10 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\_SharedHardlinkData_\14865af6.10000.3b50
02.07.2015 09:46:10 - Warning bpbrm (pid=8664) from client servername: WRN - System needs to be rebooted for restored object to take effect: System State:\_SharedHardlinkData_\14865af6.10000.3b52
02.07.2015 09:46:10 - Info bpbrm (pid=8664) from client servername: TRV - last message being suppressed after 10 occurrences
02.07.2015 09:47:03 - Error bpbrm (pid=8664) from client servername: ERR - unable to create object for restore: System State:\_SharedHardlinkData_\14865af6.10000.ed5b (WIN32 3758130365: Unknown error)
02.07.2015 09:47:03 - Error bpbrm (pid=8664) from client servername: ERR - unable to create object for restore: System State:\_SharedHardlinkData_\14865af6.10000.ee66 (WIN32 3758130365: Unknown error)
02.07.2015 09:47:03 - Error bpbrm (pid=8664) from client servername: ERR - unable to create object for restore: System State:\_SharedHardlinkData_\14865af6.10000.ee70 (WIN32 3758130365: Unknown error)
02.07.2015 09:47:08 - Info bptm (pid=7408) waited for empty buffer 8039 times, delayed 13002 times
02.07.2015 09:47:08 - end reading; read time: 0:03:55
02.07.2015 09:47:10 - Info bptm (pid=7408) completed reading backup image
02.07.2015 09:47:10 - Info bptm (pid=7408) EXITING with status 0 <----------
02.07.2015 09:47:10 - Info tar32 (pid=2252) done. status 5
02.07.2015 09:47:10 - Info tar32 (pid=2252) done. status: 185
02.07.2015 09:47:10 - Info tar32 (pid=2252) done. status: 185: tar did not find all the files to be restored
02.07.2015 09:47:10 - Error bpbrm (pid=8664) client restore EXIT STATUS 185: tar did not find all the files to be restored
02.07.2015 09:47:10 - restored from image xxx_1435767073; restore time: 0:04:05
02.07.2015 09:47:10 - Warning bprd (pid=7224) Restore must be resumed prior to first image expiration on 02/10/2015 18:11:13
02.07.2015 09:47:10 - end Restore; elapsed time 0:04:09
Windows File System policy restore error  (2808)

7.6
Backup and Recovery
NetBackup
Restore
Windows Server (2003-2008)
  • sdo's avatar
    sdo
    10 years ago

    NetBackup BMR does not have to implement DHCP, it just requires (in some confiiguration scenarios) the presence of a DHCP server - but not in all configuration scenarios.

    You can still use BMR without having to use PXE and BOOTP protocols, and instead just use a BMR SRT ISO, and you can create/follow your own BMR client recovery process/procedure (set of steps) which does not even require DHCP at any stage - and only ever requires TCP/1556 just like any normal backup client for backup/restore purposes.

    .

    See Jaime's excellent introductory procedures for BMR:

    https://www-secure.symantec.com/connect/articles/basic-setup-steps-bare-metal-restore-bmr-option-nbu

    .

    FYI - the NetBackup 7.6 Blueprint for BMR can be found by following links here:

    https://www-secure.symantec.com/connect/forums/list-netbackup-blueprints

  • sdo's avatar
    sdo
    Moderator
    10 years ago

    Is the hardware exactly the same?  I mean, same model of hardware, same motherboard revision, same BIOS version, same vendor firmware, same HBAs in same slots with same HBA BIOS and firmware, and same NIC firmware etc... Anything which is even slightly different is considered a disimilar recovery.

    I think one of the key points in that TN is this:   "Most of the time using the following steps the way it is, will result in good bootable system."

    ...which implies not always.  If you have an old and mature OS instance which has had lots of changes and upgrades and install, and uninstalls, and domain membership and GPO pushed to it, and who knows what manner of third party software installed on it, well this probably makes it more difficult.

    .

    Is there a back story as to why you are having to attempt this?

    If you are testing, then is there a reason for not using NetBackup BMR?  It's free to use.

    Oh - and the usual question of... Windows OS and SP and NetBackup Client version and patch level?

  • felix_nguyen's avatar
    felix_nguyen
    Level 4
    10 years ago

    Both servers belong to the same serie and are actually the same model. They were bought at the same time. So both of them should be very similar to each other.

    I can't use NBU BMR due to the fact that we have another OS deployment software (Altiris) in the network. They will interfere with each other if I try to use BMR which uses DHCP.

    NBU Server 7.6.0.4: Master and media server are the same system.

    OS: Windows Server 2008 R2 64 Bit

    NBU Client: 7.6.0.1

  • sdo's avatar
    sdo
    Moderator
    10 years ago

    NetBackup BMR does not have to implement DHCP, it just requires (in some confiiguration scenarios) the presence of a DHCP server - but not in all configuration scenarios.

    You can still use BMR without having to use PXE and BOOTP protocols, and instead just use a BMR SRT ISO, and you can create/follow your own BMR client recovery process/procedure (set of steps) which does not even require DHCP at any stage - and only ever requires TCP/1556 just like any normal backup client for backup/restore purposes.

    .

    See Jaime's excellent introductory procedures for BMR:

    https://www-secure.symantec.com/connect/articles/basic-setup-steps-bare-metal-restore-bmr-option-nbu

    .

    FYI - the NetBackup 7.6 Blueprint for BMR can be found by following links here:

    https://www-secure.symantec.com/connect/forums/list-netbackup-blueprints

  • felix_nguyen's avatar
    felix_nguyen
    Level 4
    10 years ago

    Thanks for your help.

    @sdo: BMR helped to get the restore done. :)

    @Michael G Andersen: I knew this technote but unfortunately that couldn'd solve the problem.