Forum Discussion

Riadh_R17's avatar
Riadh_R17
Level 4
5 years ago

Active directory backup partially sucessfull - can't open an object

Good Day,

when trying to backup the AD server, i get that the requested operation was partially successfull (status 1)

in the details i found 2 warnings below

tar_base::V_vTarMsgW: WRN - can't open object: System State:\SYSVOL\SYSVOL\f5f381ef-4a6f-4919-83b572a088ab66f5 (WIN32 3758161630: Unknown error)

tar_base::V_vTarMsgW: WRN - can't open object: System State:\Active Directory\e:_Windows_NTDS\ntds (WIN32 3758161630: Unknown error)

Attached the bpbkr.log file 

Please, any help to uderstand and resolve the issue. 

Thank you in advance

  • Hi Hamza_H 

    Thank you for your answer,

    it never worked before but now after restarting the server, it worked fine.

    i'm happy that it is solved.

    Thank you a lot for your support :)

     

8 Replies

  • Hi Riadh_R17 ,

    Could you please give more information about this:

    - Netbackup & Os version

    - is this ever worked before?

    -  have you looked into prerequisites for such backup (AD)?

    - Th problem is at this level :

    13:06:30.251 [6956.10524] <2> ov_log::V_GlobalLogEx: INF - object_access::V_CheckForNFS_Service(): Unable to get name for Client for NFS service - 0x424
    13:10:42.707 [6956.10524] <2> ov_log::V_GlobalLogEx: ERR - beds_ss_access::V_OpenForRead(): FS_OpenObj() Failed! (0xE000FEDE:A failure occurred opening an object. )
    13:10:42.707 [6956.10524] <2> tar_base::V_vTarMsgW: WRN - can't open object: System State:\SYSVOL\SYSVOL\f5f381ef-4a6f-4919-83b572a088ab66f5 (WIN32 3758161630: Unknown error)
    13:10:42.707 [6956.10524] <4> dos_backup::tfs_findfirst: INF - unable to find first file: 'System State:\Background Intelligent Transfer Service\'
    13:10:43.924 [6956.10524] <2> ov_log::V_GlobalLogEx: ERR - beds_ss_access::V_OpenForRead(): FS_OpenObj() Failed! (0xE000FEDE:A failure occurred opening an object. )
    13:10:43.924 [6956.10524] <2> tar_base::V_vTarMsgW: WRN - can't open object: System State:\Active Directory\e:_Windows_NTDS\ntds (WIN32 3758161630: Unknown error)

    - I looked into the error 3758161630, but no luck

    -Please provide bpbkar log with higher verbose (3 should be fine).

    BR

    • Hamza_H's avatar
      Hamza_H
      Moderator

      Here's a snip from the NetBackup™ Administrator's Guide, Volume I: UNIX, Windows, and Linux

      System requirements for Active Directory granular NetBackup
      backups and recovery

      backups and recoverybackups and recovery
      See the Operating System Compatibility List for a list of operating system versions
      that support Active Directory granular restore:
      http://www.symantec.com/docs/TECH76648
      To perform Active Directory granular backups and restores, ensure that you meet
      the following requirements:
      ■ The Network File System (NFS) must be installed on the media server and all
      Active Directory domain controllers or ADAM/LDS hosts.
      See “About installing and configuring Network File System (NFS) for Active
      Directory Granular Recovery” on page 1163.
      See “About configuring Services for Network File System (NFS) on Windows
      2012” on page 1164.
      See “About configuring Services for Network File System (NFS) on Windows
      2008 and Windows 2008 R2” on page 1170.
      ■ The NetBackup Client Service must be configured to log on as an account with
      domain privileges.
      To perform granular backups and restores of the Active Directory, the NetBackup
      Legacy Client Service (bpinetd) must run under the domain administrator
      account on the Active Directory domain controller or ADAM server. By default,
      bpinetd runs under the Local System account.
      See “Configuring the NetBackup Client Service” on page 1086.
      For information on the media server platforms that support Granular Recovery
      Technology see the NetBackup compatibility lists on the NetBackup landing page
      on the Symantec Support website.

    • Riadh_R17's avatar
      Riadh_R17
      Level 4

      Hi Hamza_H 

      Thank you for your answer.

      Netbackup version : 7.7.3

      OS version : master on solaris 10,  clients on windows 2012 (VMs)

      all prerequisites were respected.

      FI:  the same configuration on the AD ROOT server and the backup is successfull done at the same time without any issue.

      these issues comes only on the AD CHILD server which has the same configuration.

      i have attached the bpkar log

      Thank you a lot for your help.

  • WIN32 means that the error code has come from Windows...

    ...and 3758161630 is a decimal representation of hex number E000FEDE...

    ...which is sometimes written as   0xE000FEDE...

    ...but if I search for this I don't find much either.    :(

    All I can offer is that maybe you might need to check VSS:

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

    • Riadh_R17's avatar
      Riadh_R17
      Level 4

      Hi sdo,

      Thank you for your reply,

      For VSS providers, Veritas Software VSS Provider doesn't exit on both AD servers (root and child)

      For VSS writers, all are stable without errors.

      knowing that, the backup on the AD ROOT server is done succesfully without any issue. i think that absence of Veritas Software VSS Provider is not a cause.

      thank you for your help.

      • Hamza_H's avatar
        Hamza_H
        Moderator

        Hi Riadh_R17 ,

        Please take note of both technotes :

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

        (this concerns only WS2016 but couldn't find anything for 2012, it worth a try actually ,same nbu version 7.7.3)

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

        (this second technote, is just to do a backup test of the system state without nbu..)

        unless mistaken, you didn't reply if this worked before or not? have you rebooted the server? is there any system/vss/sysvolerrors in event logs on the server?

        also verify free space on all drivers, better to have more than 15% of free space on each drive.

        Good luck, 

        BR