cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange DAG backups failing with error code 130

zmlat
Level 4

Our Exchange 2010 DAG backups stopped working about a month ago. I opened up a case with Veritas and they were no help...basically "call Microsoft". While I suspect it is an issue on the OS side, I was hoping that the NB logs might point in some direction.

The backups are failing with error 130...

04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - 
04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - 
04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - snapshot processing failed, status 156
04/21/2018 07:01:39 - Critical bpbrm (pid=21681) from client XXXX: FTL - snapshot creation failed - VSS volume was not prepared for snap., status 130

 

4/21/2018 07:01:39 - Info bpbrm (pid=21681) DB_BACKUP_STATUS is 156
04/21/2018 07:01:39 - Info bpbrm (pid=21681) DB_BACKUP_STATUS is 156
04/21/2018 07:01:39 - Info bpbrm (pid=21681) DB_BACKUP_STATUS is 156
04/21/2018 07:01:40 - Info bpbrm (pid=21681) DB_BACKUP_STATUS is 156
04/21/2018 07:01:40 - Info bpbrm (pid=21681) DB_BACKUP_STATUS is 156
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - NEW_STREAM0 is not frozen
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - Microsoft Information Store:\DAGNYC601DB001 is not frozen
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - Microsoft Information Store:\DAGNYC601DB003 is not frozen
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - Microsoft Information Store:\DAGNYC601DB005 is not frozen
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - Microsoft Information Store:\DAGNYC601DB007 is not frozen
04/21/2018 07:01:40 - Warning bpbrm (pid=21681) from client XXXX: WRN - Microsoft Information Store:\DAGNYC601DB009 is not frozen

Now we also backup using NetApp SnapManager, which uses the OnTap Hardware Provider. Those snaps run Mon-Fri, and on the weekend we use NBU backup to create a tape copy. This was working fine up until there was an issue with the snapmanager job hanging. Since then, all hosts in the cluster have been rebooted and the writers have all been stable with no errors, yet the NB backups continue to fail. Wonder if anyone might have some insight into this issue. Microsoft has suggested disabling the snapmanager writer...but then the daily snaps will fail.

Thanks 

2 REPLIES 2

sclind
Moderator
Moderator
   VIP   

When I get status 130 failures in Exchange backups I:

  1. stop the NB client
  2. end any bpfis processes
  3. clean up the Netbackup temp directory
  4. start the NB client 

This almost always fixes the problem for me.

Whenever you get a bpbrm log indicating an error "from client X" look at the logs on client X.

Critical bpbrm (pid=21681) from client XXXX

In this case, look at the bpfis log because it's a snapshot failure. Set the common logging level at 5 and the Windows Client logging level at 2.

When a VSS writer fails, you probably get entries in the Windows application event log, too.

I don't know where SnapManager fits in. In your policy, what provider type are you specifying? Type 0 means the  default. I expect this to resolve to the Microsoft system provider, but maybe that's what changed. If that's what you want, try setting the type to 1. Type 2 is the Veritas software provider. Type 3 is the hardware provider, meaning a VSS provider supplied by the disk vendor.

"vss admin list providers" may give some useful hint.