NBU 7.6.0.3, Exchange 2013 cu4
normally i would just restart the server in order to reset VSS writer whenever i get some VSS errors, but in this case, a snapshot frozen error how should it be handled?
12/01/2015 18:00:47 - Info bpfis (pid=21524) Backup started
12/01/2015 18:01:50 - Info bpbrm (pid=30943) from client MB01: TRV - snapshot preparation successful, with the following information: Need to gather mailbox information for database <MB-03>
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL -
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL -
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL - snapshot processing failed, status 156
12/01/2015 18:01:52 - Critical bpbrm (pid=30943) from client MB01: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::SnapshotPrepare failed., status 130
12/01/2015 18:01:52 - Info bpbrm (pid=30943) DB_BACKUP_STATUS is 156
12/01/2015 18:01:53 - Info bpbrm (pid=30943) DB_BACKUP_STATUS is 156
12/01/2015 18:01:53 - Info bpbrm (pid=30943) DB_BACKUP_STATUS is 156
12/01/2015 18:01:53 - Warning bpbrm (pid=30943) from client MB01: WRN - NEW_STREAM0 is not frozen
12/01/2015 18:01:53 - Warning bpbrm (pid=30943) from client MB01: WRN - Microsoft Information Store:\MB-03 is not frozen
12/01/2015 18:01:53 - Warning bpbrm (pid=30943) from client MB01: WRN - Microsoft Information Store:\MB-01 is not frozen
12/01/2015 18:01:53 - Warning bpbrm (pid=30943) from client MB01: WRN - Microsoft Information Store:\MB-02 is not frozen
regards,
Rino