Video Screencast Help

Differential Exchange backups are failing with status 130

Created: 27 Nov 2013 • Updated: 19 Feb 2014 | 7 comments
This issue has been solved. See solution.

We have Exchnage backup configured for individual information store groups earlier. Recently we have clubbed all together and made it as single Information store backup. But when we are running with complete Information Store backup , its differential is failing with status 130 whereas if there individual groups its been a success.

Operating Systems:

Comments 7 CommentsJump to latest comment

Nagalla's picture

Does it have GRT enabled?

what are the netbackup and exchage versions?

post the deatil status of the failed job?

did you see any messages in event viewer?

 

Krishna Srinivas's picture

Hi ,

 

we don't have GRT enabled .

 

11/27/2013 02:32:32 - Info nbjm (pid=8107) starting backup job (jobid=40555) for client gibsvwin240, policy Exchange_2010_GIB, schedule Daily_Differential_Incremental_2weeks
11/27/2013 02:32:32 - Info nbjm (pid=8107) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=40555, request id:{2B154F28-570C-11E3-B10E-0255B7156582})
11/27/2013 02:32:32 - requesting resource stu_disk_gi1c1xibkp001
11/27/2013 02:32:32 - requesting resource gi1m1xibkp001.NBU_CLIENT.MAXJOBS.gibsvwin240
11/27/2013 02:32:32 - requesting resource gi1m1xibkp001.NBU_POLICY.MAXJOBS.Exchange_2010_GIB
11/27/2013 02:32:32 - granted resource  gi1m1xibkp001.NBU_CLIENT.MAXJOBS.gibsvwin240
11/27/2013 02:32:32 - granted resource  gi1m1xibkp001.NBU_POLICY.MAXJOBS.Exchange_2010_GIB
11/27/2013 02:32:32 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_gi1c1xibkp001;Path=PureDiskVolume;StorageServer=gi1c1xibkp001;MediaServer=gi1c1xibkp001
11/27/2013 02:32:32 - granted resource  stu_disk_gi1c1xibkp001
11/27/2013 02:32:32 - estimated 669015 kbytes needed
11/27/2013 02:32:32 - begin Parent Job
11/27/2013 02:32:32 - begin Snapshot: Start Notify Script
11/27/2013 02:32:32 - Info RUNCMD (pid=8829) started
11/27/2013 02:32:32 - Info RUNCMD (pid=8829) exiting with status: 0
Operation Status: 0
11/27/2013 02:32:32 - end Snapshot: Start Notify Script; elapsed time 0:00:00
11/27/2013 02:32:32 - begin Snapshot: Step By Condition
Operation Status: 0
11/27/2013 02:32:32 - end Snapshot: Step By Condition; elapsed time 0:00:00
11/27/2013 02:32:32 - begin Snapshot: Stream Discovery
Operation Status: 0
11/27/2013 02:32:32 - end Snapshot: Stream Discovery; elapsed time 0:00:00
11/27/2013 02:32:32 - begin Snapshot: Read File List
Operation Status: 0
11/27/2013 02:32:32 - end Snapshot: Read File List; elapsed time 0:00:00
11/27/2013 02:32:32 - begin Snapshot: Create Snapshot
11/27/2013 02:32:33 - started process bpbrm (pid=11544)
11/27/2013 02:32:34 - Info bpbrm (pid=11544) gibsvwin240 is the host to backup data from
11/27/2013 02:32:34 - Info bpbrm (pid=11544) reading file list from client
11/27/2013 02:32:34 - Info bpbrm (pid=11544) start bpfis on client
11/27/2013 02:32:34 - Info bpbrm (pid=11544) Starting create snapshot processing
11/27/2013 02:32:34 - Info bpfis (pid=10944) Backup started
11/27/2013 02:33:16 - Critical bpbrm (pid=11544) from client gibsvwin240: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130
11/27/2013 02:33:16 - Critical bpbrm (pid=11544) from client gibsvwin240: FTL - snapshot preparation failed, status 130
11/27/2013 02:33:16 - Info bpfis (pid=10944) done. status: 130
11/27/2013 02:33:16 - end Snapshot: Create Snapshot; elapsed time 0:00:44
11/27/2013 02:33:16 - Info bpfis (pid=0) done. status: 130: system error occurred
11/27/2013 02:33:16 - end writing
Operation Status: 130
11/27/2013 02:33:16 - begin Snapshot: Stop On Error
Operation Status: 0
11/27/2013 02:33:16 - end Snapshot: Stop On Error; elapsed time 0:00:00
11/27/2013 02:33:16 - begin Snapshot: Delete Snapshot
11/27/2013 02:33:17 - started process bpbrm (pid=11660)
11/27/2013 02:33:18 - Info bpbrm (pid=11660) Starting delete snapshot processing
11/27/2013 02:33:18 - Info bpfis (pid=0) Snapshot will not be deleted
11/27/2013 02:33:18 - Info bpfis (pid=2748) Backup started
11/27/2013 02:33:18 - Critical bpbrm (pid=11660) from client gibsvwin240: FTL - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.gibsvwin240_1385519552.0
11/27/2013 02:33:19 - Info bpfis (pid=2748) done. status: 0
11/27/2013 02:33:19 - end Parent Job; elapsed time 0:00:47
11/27/2013 02:33:19 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
11/27/2013 02:33:19 - end writing
Operation Status: 0
11/27/2013 02:33:19 - end Snapshot: Delete Snapshot; elapsed time 0:00:03
11/27/2013 02:33:19 - begin Snapshot: End Notify Script
11/27/2013 02:33:19 - Info RUNCMD (pid=9347) started
11/27/2013 02:33:19 - Info RUNCMD (pid=9347) exiting with status: 0
Operation Status: 0
11/27/2013 02:33:19 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 130
11/27/2013 02:43:20 - Info bpbrm (pid=14644) gibsvwin240 is the host to backup data from
11/27/2013 02:43:20 - Info bpbrm (pid=14644) reading file list from client
11/27/2013 02:43:20 - Info bpbrm (pid=14644) start bpfis on client
11/27/2013 02:43:20 - Info bpbrm (pid=14644) Starting create snapshot processing
11/27/2013 02:43:21 - Info bpfis (pid=10676) Backup started
system error occurred  (130)
inn_kam's picture

well

 

check Netbackup Client service as admin rights on Exchange server

Krishna Srinivas's picture

Yes , It has and in my case Full backup of exchange is absolutely fine and also incr is fine when the backup is taken on group level.

Nagalla's picture

11/27/2013 02:33:16 - Critical bpbrm (pid=11544) from client gibsvwin240: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130

try disabling the Circular Logging feature in exchage and see if it helps... 

http://www.symantec.com/business/support/index?page=content&id=TECH192178

How to Disable Circular Logging in Exchange 2010 :

  • To use the Exchange Management Console to disable circular logging:
1.      In the console tree, navigate to Organization Configuration | Mailbox.
2.      In the result pane, on the Database Management tab, select the database you want to configure.
3.      In the action pane, under the database name, click Properties.
4.      Click on the Maintenance tab
5.      Clear the Enable circular logging check box.
6.      Click OK
7.   To make your changes to the circular logging settings effective, Restart the Microsoft Exchange Information Store service, or dismount and then mount all of the databases in the storage group.
  • To disable circular logging using Exchange Management Shell, run the following command:
Set-MailboxDatabase -Identity "Database Name" -CircularLoggingEnabled $false

 

SOLUTION