Showing results for 
Search instead for 
Did you mean: 

Try to backup as BMR, but return error as 156.

I create backup BMR on exchange 2003 service pack 2 (OS: windows 2003)

it return error as:

7/27/2010 1:10:32 PM - estimated 0 Kbytes needed
7/27/2010 1:10:32 PM - started process bpbrm (5240)
7/27/2010 1:10:32 PM - started
7/27/2010 1:10:37 PM - connecting
7/27/2010 1:10:39 PM - connected; connect time: 00:00:02
7/27/2010 1:10:46 PM - mounting 000031
7/27/2010 1:11:23 PM - mounted; mount time: 00:00:37
7/27/2010 1:11:23 PM - positioning 000031 to file 35
7/27/2010 1:13:02 PM - positioned 000031; position time: 00:01:39
7/27/2010 1:13:02 PM - begin writing
7/27/2010 2:43:53 PM - Error bpbrm(pid=5240) from client mailsrv-01: ERR - failure reading file: C:\Program Files\eXchange POP3 5.0\data\trace\To Exchange.2010. (WIN32 2: Unknown error)
7/27/2010 2:43:54 PM - Error bpbrm(pid=5240) from client mailsrv-01: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy64\Program Files\eXchange POP3 5.0\data\trace\To Exchange.2010.
7/27/2010 2:43:54 PM - Critical bpbrm(pid=5240) from client mailsrv-01: FTL - Backup operation aborted!     
7/27/2010 2:44:10 PM - end writing; write time: 01:31:08
snapshot error encountered(156)

I configure Volume Shadow Copy on C: drive as no limit.

Anyone has solutions?
7 Replies

Re: Try to backup as BMR, but return error as 156.

Can you check if Open file backups are not desired for the client, disable them. This will decrease the resources used by the client during backup and resolve any Status 156 errors. The default NetBackup install options are to have open file backups enabled.

To confirm if VSS or VSP open file backups are activated:
1. Within the NetBackup Administration Console, expand Host Properties in the hand pane
2. Within Host Properties, click Master Server and then the double-click the name of the Master Server in the right pane
3. Click on the Client Attributes section
4. If the client in question is listed here, click on the client name. If it is not listed, add and click on the client name.
5. Click the Windows Open File Backup tab
6. Ensure that Enable Windows Open File Backups for this client is not selected if open file backups are not required

If open file backup functionality is needed, the most common cause for snapshot errors is cache file configuration. The steps on changing this depend on whether VSP or VSS is used as the Snapshot Provider.

Re: Try to backup as BMR, but return error as 156.

Thanks varunprakash,

I understand as NetBackup use VSS as default, and I check it again on configure it OK.

I try to backup again, but it resturn partial backup. it can't read SYSTEM STATE file.

I headach about this issue.

Any idea?

Re: Try to backup as BMR, but return error as 156.

You should make sure the the Volume Shadow Copy Services are set to "manual" on the NBU client system (Services.msc).

Also make sure that this client is supported.  Is it 64 bit Windows?  NBU 7?  BMR on 64 bit is supported at 7.0.1. 

Thanks RySchFrNet

Volume Shadow Copy Sefice as "Manual" on client and my client as Windows 2003 32 bit.
When I exclude path: "C:\Program Files\eXchange POP3 5.0", it can backup successfully.

I wonder how can I backup as BMR and include path: "C:\Program Files\eXchange POP3 5.0" too.

Re: Try to backup as BMR, but return error as 156.

I hope the policy being used to take this backup has type "MS-WINDOWS" and not "STANDARD". Please confrim.
I could see some related problems with bpbrm error code 156. it looks to be a issue related to the volume thats mounted on the client system. Try rebooting client if possible and fire backup.
Which NBU version you are using?


Re: Try to backup as BMR, but return error as 156.

I use "MS-WINDOWS" and reboot server but still same.

Re: Try to backup as BMR, but return error as 156.

I recommend opening a service request with Symantec on this problem.
NOTE: Please make a note that this is not a BMR process problem. Something is going wrong in NBU backup process while taking shadow copy components backup.
This comment may help handling service request better.