Forum Discussion

Pierre_J's avatar
Pierre_J
Level 4
8 years ago

Off-host backup failing with status 4213

Hi, we run off-host backups for a while without problems but now we encounter status 4213.
We use W2008R2 as Master, W2012R2 as Media server and V7.7.3 for NBU.
Snapshot is being made on HP 3Par.
Error says:

02/19/2017 12:04:18 - Critical bpbrm (pid=9812) from client client.domain: FTL - In case of snapshot creation using vendor VSS hardware provider, snapshot devices may get leaked due to incomplete import operation. VSS framework does not allow to delete un-imported snapshot. The leaked snapshot devices can be recovered using Microsoft Vshadow utility. Please use the xml file [C:\Program Files\Veritas\NetBackup\temp\bpfis.fim.client.domain_1487501850.1.0.xml] created on client [clustermember.domain] to import and delete the snapshot manually using Vshadow utility from alternate client [mediaserver.domain]. Please refer event viewer and Hardware VSS provider logs for more details. Delete the file manually after cleanup.
02/19/2017 12:04:18 - Critical bpbrm (pid=9812) from client client.domain: FTL - snapshot processing failed, status 4213
02/19/2017 12:04:18 - Critical bpbrm (pid=9812) from client client.domain: FTL - snapshot creation failed, status 4213

I see diskdevices presented at the Media server which seems to be not fully cleaned up, maybe due to this error.

7.7
Windows Server 2008 R2
  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    8 years ago

    I would start with looking at the HP 3Par disk system, as it here the snapshots created and deleted.

    You can probably also see a failed writer in vssadmin list writers, some times a restart of the relevant service(s) is enough to clear the error.

    Have you tried to use the vshadow util as described in the log ?

    Have had to remove ghost/nonpresent devices manually through the device manager in windows.

    If not anything else works, deleting the snapshots on the disk system and the bpfis.fim file and the rebooting the media server is a good bet.

    • Pierre_J's avatar
      Pierre_J
      Level 4
      8 years ago

      3Par is working fine, when we reroute the snapshots to another media server the backups run fine.
      When we reroute another snapshotbackup to the erroneous media server it runs in error, so somethng is wrong with the media server.

      To be continued.

      • Michael_G_Ander's avatar
        Michael_G_Ander
        Level 6
        8 years ago

        That could be because of ghost devices on the original media server.

        If the snapshots is deleted in the HP 3 Par disk system you will have to look at the integration between HP 3 Par snapshot and the VSS system on the problematic media server.