Forum Discussion

brice1's avatar
brice1
Level 4
8 years ago
Solved

Netbackup error 130 and 4207 by backup Exchange 2013

hi all , please i can't backup exchange 2013 on nbu 8 bellow errors pls help ...

Critical bpbrm (pid=10100) from client exchangeserver.ekardist.local: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130

Could not fetch snapshot metadata or state files  (4207)

  • You are missing permissions:

    11:12:08.115 [1552.6616] <2> onlfi_vfms_logf: INF - ERR - AdjustPrivilege: AdjustTokenPrivileges failed to update privilege for SeAssignPrimaryTokenPrivilege: status 0x514.
    11:12:08.115 [1552.6616] <2> onlfi_vfms_logf: INF - ERR - Set_Exchange_Impersonation: "Replace a process level token" must be set in the Security Policy for this user.

    On each Exchange Nodes - Under Local Security Policy 
    Add the Permission - <Replace a process level token> in Local Security Policy

    Also check if this is the issue you are experiencing in addition:

    http://www.veritas.com/docs/000019349

     

  • This seems to be a local admin, not a domain admin, right?

    EseProcess::Init: WhoAmI - EKARDIST\Administrator

    Credential requirements are explained in NetBackup for Microsoft Exchange Server Administrator's Guide 

     e.g. 

    Provide the credentials for the account for NetBackup Exchange operations. This
    account must have the necessary permissions to perform Exchange restores.
    The permissions that are required depend on the Exchange version that you have.
    The account also needs the right to “Replace a process level token.”
    See “About the Exchange credentials in the client host properties” .
    See “About configuring the account for NetBackup Exchange operations”.
    See “About configuring the account for NetBackup Exchange operations with the
    right to Replace a process level token”.

10 Replies

  • In my experience status 130/4207 has to be solved by the Exchange administrator, as the problem is usually on the Exchange side of things. 

    • brice1's avatar
      brice1
      Level 4

      thks for your replay yes i made it , it's a new installation 

      • In that case you best bet is to run vssadmin list writers in an elavated prompt and check for failed writers.

        And of course checking the event logs on exchange server.

        A new installation might require a reboot to get all writers properly registered.

  • Is this a DAG or Standalone Exchange server?

    Steps to configure DAG backup involves more steps than standalone Exch server.

    • brice1's avatar
      brice1
      Level 4

      Hi Marianne it's Standalone Exchange server

      • Marianne's avatar
        Marianne
        Level 6

        Have you provided Exch credentials in Host Properties and started NBU services on Exch server with correct admin-level permissions?

        If all of that is in place, please create bpfis log folder on Exch server before next backup attempt.

        Check bpfis log for possible reason for snapshot failure and also check Event Viewer logs.