- VOX
- Data Protection
- NetBackup
- Exchange 2010 Dag without GRT backup failing
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Exchange 2010 Dag without GRT backup failing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 08:24 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 09:41 PM
1) does this ever worked fine or new configuration?
2) what is the backup selection for this exchange policy?
3) could you show the screenshot of Policy attributes tab?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 09:59 PM
1. This is not new configuration and was working fine in old configurationa and we have 2 DAG uner a same policy. One DAG is working fine but other throwing some error.
2. Microsoft Exchange Database Availability Groups:\
3. root@ppp ~]# bppllist Exchange2010DAG -U
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 10:19 PM
hi,
does this DAG1.qqq.com name of the Cluster or Node name?
could you provide the bpbkar , bpfis from Client
bpbrm and bptm logs from media server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 10:20 PM
Streaming backups are invalid with Exchange 2010
That means "Perform snapshot backups" is not enabled in the policy.
Starting from Exchange 2010, non-snapshot based backups are no longer supported by Microsoft.
Snapshot as in VSS based.
http://technet.microsoft.com/en-us/library/dd876874%28v=exchg.141%29.aspx
Microsoft Exchange Server 2007 and Exchange Server 2003 include two different options for data backup and recovery: Extensible Storage Engine (ESE) streaming backup APIs and support for the Volume Shadow Copy Service (VSS) backup APIs.
Exchange 2010 no longer supports the ESE streaming APIs for backup and restore of program files or data. Instead, Exchange 2010 supports only VSS-based backups.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 11:16 PM
if you are using the node name, you can not use the backup selection as
Microsoft Exchange Database Availability Groups:\
it should be "Microsoft Exchange Database Availability Groups:\<database name>"
http://www.symantec.com/business/support/index?page=content&id=HOWTO60734
imitations and conditions:
- Use a node name (physical server name) that the NetBackup servers can contact.
- The Backup Selection List (also known as the files list) in the policy must contain "Microsoft Exchange Database Availability Groups:\<database name>". The Backup Selection can contain more than entry, but each database must be explicitly specified. The use of "Microsoft Exchange Database Availability Groups:\" or "Microsoft Exchange Database Availability Groups:\*" is not permitted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 11:39 PM
This not a single node, its a Database availablity group (DAG); contains group of nodes.
I ran backup second time, getting below error now :
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 11:42 PM
As per RLeon's post - please check if Snapshot option is selected in policy attributes.
Unfortunately 'bppllist -U' does not report snapshot selection, only -L option.
Why do you have 2 client names in the policy?
Do you have 2 separate Exchange clusters?
If only one environment, specify only the virtual hostname in the policy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2013 11:50 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 12:05 AM
Try putting DAG1.qqq.com into its own policy to better isolate the problem.
Best not to use the "copy" feature to copy from the existing policy.
Create the new Exchange policy from scratch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 12:19 AM
Thanks for confirmation that Snapshot option is enabled.
The only thing that is left now is to look at logs...
As per Nagalla's post above:
could you provide the bpbkar , bpfis from Client
bpbrm and bptm logs from media server.
bpresolver log may also be helpful.
This log is written to the DAG node. To determine the active node, see the following:
Please copy files to reflect process name (e.g. bpbkar.txt) and post as File attachments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 12:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 12:45 AM
I have attached bpbrm and bptm.
bpbkar , bpfis and bpresolver from which server ?
Can it be
Any of the DAG member
or it should virtual Dag node
Nagalla,
How can i check that ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 05:16 AM
Those logs should be from the active node of the cluster..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2013 01:06 PM
How can i check that ?
See extract from manual in my previous post:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2013 08:44 AM
Yes is it pointing to Active node.
Issue got resolved since had changed acount to LSA account. Hence exchange backups witout GRT was failing.
There is an issue with exchange backup of DAG with GRT.
Issue is : once we run a full backup MICROSOFT EXCHANGE WRITER status changes to waitng for completeion sate on one of the dag memeber.
becuase of this successive backups are failig.
Is ther any way other than reboot ot restarting information store / replicetion service on affected server ?????????
- Shadow copy component backup failing with error code 13 in NetBackup
- Netbackup 10.0.0.1 client Solaris 5.10 upgrade fail in NetBackup
- Failed to Start File System Check on /dev/mapper/system-log during Boot up in NetBackup Appliance
- (VMware snapshot) failed with 25: SYM_VMC_FAILED_TO_CREATE_SNAPSHOT in NetBackup Appliance
- Appliance 5240 re-imaged as primary server failed in Appliances
