10-20-2011 03:58 AM
Hi All,
On a new solution backing up Exchange 2010 DAG on NBU 7.1 for the first time. My backups are fine, however the exchange logs are not being truncated by NetBackup.
Please see below my policy output:
Policy Type: MS-Exchange-Server
Active: yes
Effective date: 09/14/2011 17:18:01
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: xxxxxxxx-hcart2-robot-tld-0
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Exchange Source passive db if available: yes
Exchange 2010 Preferred Server: xxxxxxxxxx Application Discovery: no
Discovery Lifetime: 28800 seconds
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: Windows-x64 Windows2008 xxxxxxxxxx
Include: Microsoft Exchange Database Availability Groups:\
Schedule: Weekly_Full
Type: Automatic Backup
Maximum MPX: 4
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: xxxxxxxxxx-hcart2-robot-tld-0
Volume Pool: Weekly
Server Group: (same as specified for policy)
Calendar sched: Enabled
Sunday, Week 1
Sunday, Week 2
Sunday, Week 3
Sunday, Week 4
Sunday, Week 5
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 06:00:00 --> Sunday 08:00:00
I also run a daily full schedule. Its a pretty standard policy.
Ive checked through the logs and i cannot see anywhere "Exchange Logs Truncated" in bpbkar.log as i would in Exchange 2007. Circular logging is not enabled and im running Full's only. Also there are no errors on the application log.
I also noticed this in the bpbkar.log, i dont know what it means?
exchange_shadowcopy_access::V_Read_FI_Metadata(): INF - Not enough room in the bfr for the BEDS Stream Header, 14 bytes read
01:25:56.613: [8776.9068] <2> (I see this quite alot in cheap exchange backup)
Anyone have any idea's on this?
Many Thanks
Jay
10-20-2011 04:25 AM
I would expect an ESE entry in the application logs that the backup had completed successfully with perhaps a note about the logs?
Are you using 7.1.0.2 on both Media Server and Client?
If you environment working correctly - if replication is not ocurring correctly the logs will not get truncated.
I also see you have multiple data streams enabled - does you policy produce one job or more?
If it produces more than one job do any fail? (as this will prevent the logs from being truncated for all storage groups)
Thanks
10-20-2011 04:59 AM
NetBackup merely notifies Exchange that the backup was successful. It is then up to Exchange to truncate transaction logs.
Have a look at this section in the manual about Full backups:
This schedule type backs up the Exchange Server database and associated transaction
logs. Exchange truncates all committed transaction logs after NetBackup notifies it that
the backup succeeded. In replicated environments, the truncation is scheduled and does
not occur immediately.
10-20-2011 05:06 AM
see this pict, hope this is can help u.