cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Exchange backup failing with error

Hi Team,

My exchange backups are failing with error below. The backups going to this server only failing in the overall DAG other backups through are just fine.

02/09/2019 02:35:05 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM0 is not frozen
02/09/2019 02:35:05 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRCommonMbx is not frozen
02/09/2019 02:35:05 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRJournalmbx is not frozen
02/09/2019 02:35:05 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM1 is not frozen
02/09/2019 02:35:05 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRMBX01 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM2 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRMBX02 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM3 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRMBX03 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM4 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRMBX04 is not frozen
02/09/2019 02:35:06 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - NEW_STREAM5 is not frozen
02/09/2019 02:35:06 - end writing
Operation Status: 130

Operation Status: 0
02/09/2019 02:35:07 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\SINSRMBX05 is not frozen
02/09/2019 02:35:07 - Warning bpbrm (pid=2872) from client SINSR1SR0017MBX: WRN - Microsoft Information Store:\exch_migration is not frozen
02/09/2019 02:35:07 - Info bpfis (pid=16488) done. status: 130

02/09/2019 02:35:07 - Info bpfis (pid=16488) done. status: 130: system error occurred
02/09/2019 02:35:09 - started process bpbrm (pid=8364)
02/09/2019 02:35:22 - Info bpbrm (pid=8364) Starting delete snapshot procesSINSRg
02/09/2019 02:35:29 - end writing
Operation Status: 4207

Operation Status: 130

02/09/2019 02:35:30 - Info bpfis (pid=12248) Backup started
02/09/2019 02:35:30 - Warning bpbrm (pid=8364) from client SINSR1SR0017MBX: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.SINSRExchDAG_1549650661.1.0
02/09/2019 02:35:30 - Info bpfis (pid=12248) done. status: 4207

02/09/2019 02:35:30 - Info bpfis (pid=12248) done. status: 4207: Could not fetch snapshot metadata or state files

Thanks,

Nayab

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Exchange backup failing with error

@NAYABRSK

Please share details of how Exchange policy is configured? 
And Exchange version?

Do you have bpfis log on SINSR1SR0017MBX? 
Level 3 log should be good. 

View solution in original post

3 Replies
Highlighted
Accepted Solution!

Re: Exchange backup failing with error

@NAYABRSK

Please share details of how Exchange policy is configured? 
And Exchange version?

Do you have bpfis log on SINSR1SR0017MBX? 
Level 3 log should be good. 

View solution in original post

Highlighted

Re: Exchange backup failing with error

When a backup exchange fails for snapshot most of the time it is due to a corrupt snapshot, you should verify vssadmin list writers in a msdos console, if your snapshot appears here the only way to delete it according to microsoft is restarting the server ....

Highlighted

Re: Exchange backup failing with error

It's not strictly true that the the only way (or even the preferred way) to delete a snapshot is to restart the server. It is true that vssadmin in the command window may not be able to delete a snapshot that another process created. In these situations, diskshadow has been able to delete the snapshot in my tests.

However, this is getting the cart in front of the horse. We can't suggest how to solve the problem before we know what the problem is. We need the bpfis log to know where to start. The Windows application event log and "diskshadow list writers" may provide some supporting information for what you find in the bpfis log.