exchange 2010 DAG backup problem

redliquid · ‎01-27-2016

hi:

my environment as below:
windows 2008 R2 SP1 + exchange 2010 SP3 + NBU 7.5

my exchange backup policy as below:

# bppllist exchange2010_dag0 -L

Policy Name: exchange2010_dag0
Options: 0x0
template: FALSE
audit_reason: ?
Names: (none)
Policy Type: MS-Exchange-Server (16)
Active: yes
Effective date: 01/27/2016 20:46:12
Mult. Data Stream: no
Perform Snapshot Backup: yes
Snapshot Method: VSS
Snapshot Method Arguments: prov_type=0,max_snapshots=1,snap_attr=0
Perform Offhost Backup: no
Backup Copy: 0
Use Data Mover: no
Data Mover Type: -1
Use Alternate Client: no
Alternate Client Name: (none)
Use Virtual Machine: 0
Hyper-V Server Name: (none)
Enable Instant Recovery: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR Info: no
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Client Encrypt: no
Checkpoint: no
Residence: stu1
Volume Pool: NetBackup
Server Group: *ANY*
Granular Restore Info: yes
Exchange Source passive db: yes
Exchange 2010 Preferred Server: nodea.mydomain.com nodeb.mydomain.com
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Generation: 28
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
Client/HW/OS/Pri/DMI: dag0.mydomain.com Windows-x64 Windows2008 0 0 0 0 ?
Include: /Microsoft Exchange Database Availability Groups:\exchange_bak_test1
Include: /Microsoft Exchange Database Availability Groups:\exchange_bak_test2
Include: /Microsoft Exchange Database Availability Groups:\staff
Include: /Microsoft Exchange Database Availability Groups:\branch
Schedule: Full
Type: FULL SExchange (0)
Frequency: 7 day(s) (604800 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 024:00:00 000:00:00 024:00:00
Monday 000:00:00 024:00:00 024:00:00 048:00:00
Tuesday 000:00:00 024:00:00 048:00:00 072:00:00
Wednesday 000:00:00 024:00:00 072:00:00 096:00:00
Thursday 000:00:00 024:00:00 096:00:00 120:00:00
Friday 000:00:00 024:00:00 120:00:00 144:00:00
Saturday 000:00:00 024:00:00 144:00:00 168:00:00
Schedule: Differential-Inc
Type: INCR (1)
Frequency: 1 day(s) (86400 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 024:00:00 000:00:00 024:00:00
Monday 000:00:00 024:00:00 024:00:00 048:00:00
Tuesday 000:00:00 024:00:00 048:00:00 072:00:00
Wednesday 000:00:00 024:00:00 072:00:00 096:00:00
Thursday 000:00:00 024:00:00 096:00:00 120:00:00
Friday 000:00:00 024:00:00 120:00:00 144:00:00
Saturday 000:00:00 024:00:00 144:00:00 168:00:00
Schedule: User
Type: UBAK Exchange (2)
Frequency: 7 day(s) (604800 seconds)
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 024:00:00 000:00:00 024:00:00
Monday 000:00:00 024:00:00 024:00:00 048:00:00
Tuesday 000:00:00 024:00:00 048:00:00 072:00:00
Wednesday 000:00:00 024:00:00 072:00:00 096:00:00
Thursday 000:00:00 024:00:00 096:00:00 120:00:00
Friday 000:00:00 024:00:00 120:00:00 144:00:00
Saturday 000:00:00 024:00:00 144:00:00 168:00:00

my selection in policy:

/Microsoft Exchange Database Availability Groups:\exchange_bak_test1
/Microsoft Exchange Database Availability Groups:\exchange_bak_test2
/Microsoft Exchange Database Availability Groups:\staff
/Microsoft Exchange Database Availability Groups:\branch

the backup log:

01/27/2016 21:48:59 - Info nbjm (pid=2612) starting backup job (jobid=1492) for client dag0.mydomain.com, policy exchange2010_dag0, schedule Full
01/27/2016 21:48:59 - Info nbjm (pid=2612) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1492, request id:{B7B3869C-C4FC-11E5-9A86-85E4175CE783})
01/27/2016 21:48:59 - requesting resource stu1
01/27/2016 21:48:59 - requesting resource nbu75.NBU_CLIENT.MAXJOBS.dag0.mydomain.com
01/27/2016 21:48:59 - requesting resource nbu75.NBU_POLICY.MAXJOBS.exchange2010_dag0
01/27/2016 21:48:59 - granted resource  nbu75.NBU_CLIENT.MAXJOBS.dag0.mydomain.com
01/27/2016 21:48:59 - granted resource  nbu75.NBU_POLICY.MAXJOBS.exchange2010_dag0
01/27/2016 21:48:59 - granted resource  MediaID=@aaaac;Path=/v_storage/stu1;MediaServer=nbu75
01/27/2016 21:48:59 - granted resource  stu1
01/27/2016 21:48:59 - estimated 0 kbytes needed
01/27/2016 21:48:59 - begin Parent Job
01/27/2016 21:48:59 - begin Snapshot: Start Notify Script
01/27/2016 21:48:59 - Info RUNCMD (pid=5855) started
01/27/2016 21:48:59 - Info RUNCMD (pid=5855) exiting with status: 0
Operation Status: 0
01/27/2016 21:48:59 - end Snapshot: Start Notify Script; elapsed time 0:00:00
01/27/2016 21:48:59 - begin Snapshot: Step By Condition
Operation Status: 0
01/27/2016 21:48:59 - end Snapshot: Step By Condition; elapsed time 0:00:00
01/27/2016 21:48:59 - begin Snapshot: Read File List
Operation Status: 0
01/27/2016 21:48:59 - end Snapshot: Read File List; elapsed time 0:00:00
01/27/2016 21:48:59 - begin Snapshot: Create Snapshot
01/27/2016 21:49:00 - started process bpbrm (pid=5861)
01/27/2016 21:50:22 - Info bpbrm (pid=5861) client_pid=6196
01/27/2016 21:50:22 - Info bpbrm (pid=5861) from client dag0.mydomain.com: BPRESOLVER has executed on server (NODEA)
01/27/2016 21:50:44 - Info bpresolver (pid=6196) done.  status: 2
01/27/2016 21:50:44 - Error bpbrm (pid=5861) You must use the backup directive for Database Availability Groups for an Exchange DAG backup
01/27/2016 21:50:44 - Info bpresolver (pid=0) done. status: 72: the client type is incorrect in the configuration database
01/27/2016 21:50:44 - end writing
Operation Status: 72
01/27/2016 21:50:44 - end Snapshot: Create Snapshot; elapsed time 0:01:45
01/27/2016 21:50:44 - begin Snapshot: Stop On Error
Operation Status: 0
01/27/2016 21:50:44 - end Snapshot: Stop On Error; elapsed time 0:00:00
01/27/2016 21:50:44 - begin Snapshot: End Notify Script
01/27/2016 21:50:44 - Info RUNCMD (pid=5908) started
01/27/2016 21:50:44 - Info RUNCMD (pid=5908) exiting with status: 0
Operation Status: 0
01/27/2016 21:50:44 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 72
01/27/2016 21:50:44 - end Parent Job; elapsed time 0:01:45
the client type is incorrect in the configuration database  (72)

01/27/2016 21:50:44 - Error bpbrm (pid=5861) You must use the backup directive for Database Availability Groups for an Exchange DAG backup

01/27/2016 21:50:44 - Info bpresolver (pid=0) done. status: 72: the client type is incorrect in the configuration database

i search in community, almost is You cannot use the backup directive for Database Availability Groups for an Exchange DAG backup，so can anybody give me some advice?

sdo · ‎01-27-2016

Your directives look malformed:

/Microsoft Exchange Database Availability Groups:\exchange_bak_test1
/Microsoft Exchange Database Availability Groups:\exchange_bak_test2
/Microsoft Exchange Database Availability Groups:\staff
/Microsoft Exchange Database Availability Groups:\branch

...with leading "/". Why do you have leading "/" ?

.

Perhaps we could try to first get a backup of this working:

Microsoft Exchange Database Availability Groups:\

...i..e change your policy, if you can, to use just the one directive. If this works, then you can begin to experiment/try seperating them out, maybe.

sdo · ‎01-27-2016

Looks like you need a minimum of NetBackup Client v7.5.0.5:

Exchange

2010 SP3

64

Windows Server 2008 R2

x86-64

64

7.5.0.5

Go to Top of "Microsoft Exchange"

...from:

https://download.veritas.com/resources/content/live/SFDC/6000/000006088/en_US/nbu_76_db_scl.html?__gda__=1454006052_8137b39615862d276a27cc06d2de9d9b#database_agents-microsoft_exchange-microsoft_exchange_-_supported_configurations

...from:

https://www.veritas.com/support/en_US/article.000006088

redliquid · ‎01-27-2016

ok, i'm trying your recommend

feedback later

redliquid · ‎01-27-2016

thanks sdo

but i was successfully in my environment, the problem was appeared after i pofweroff my machine and power on,

redliquid · ‎01-27-2016

if i use Microsoft Exchange Database Availability Groups:\ in backup selection, that can be backup successfully. the log information:

01/28/2016 13:28:41 - Info nbjm (pid=2691) starting backup job (jobid=1522) for client NODEB.MYDOMAIN.COM, policy exchange2010_dag0, schedule Full
01/28/2016 13:28:41 - Info nbjm (pid=2691) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1522, request id:{FDB762CA-C57F-11E5-BE50-681A5622EA13})
01/28/2016 13:28:41 - requesting resource stu1
01/28/2016 13:28:41 - requesting resource nbu75.NBU_CLIENT.MAXJOBS.NODEB.MYDOMAIN.COM
01/28/2016 13:28:41 - requesting resource nbu75.NBU_POLICY.MAXJOBS.exchange2010_dag0
01/28/2016 13:28:41 - granted resource nbu75.NBU_CLIENT.MAXJOBS.NODEB.MYDOMAIN.COM
01/28/2016 13:28:41 - granted resource nbu75.NBU_POLICY.MAXJOBS.exchange2010_dag0
01/28/2016 13:28:41 - granted resource MediaID=@aaaac;Path=/v_storage/stu1;MediaServer=nbu75
01/28/2016 13:28:41 - granted resource stu1
01/28/2016 13:28:41 - estimated 0 kbytes needed
01/28/2016 13:28:41 - begin Parent Job
Operation Status: 0
01/28/2016 13:28:41 - end Parent Job; elapsed time 0:00:00
Operation Status: 0
01/28/2016 13:28:41 - started process bpbrm (pid=6209)
01/28/2016 13:29:42 - Info bpbrm (pid=6209) NODEB.MYDOMAIN.COM is the host to backup data from
01/28/2016 13:29:42 - Info bpbrm (pid=6209) reading file list from client
01/28/2016 13:29:42 - Info bpbrm (pid=6209) start bpfis on client
01/28/2016 13:29:42 - begin Create Snapshot
01/28/2016 13:29:43 - Info bpfis (pid=4004) Backup started
01/28/2016 13:30:52 - Warning bpbrm (pid=6209) from client NODEB.MYDOMAIN.COM: WRN - Database <Mailbox Database 0803020244> is not mounted and cannot be backed up.
01/28/2016 13:30:52 - Warning bpbrm (pid=6209) from client NODEB.MYDOMAIN.COM: WRN - Database <Public Folder Database 1661219227> is not mounted and cannot be backed up.
01/28/2016 13:31:14 - Info bpfis (pid=4004) done. status: 1
01/28/2016 13:31:14 - end Create Snapshot; elapsed time 0:01:32
01/28/2016 13:31:14 - Info bpfis (pid=0) done. status: 1: the requested operation was partially successful
01/28/2016 13:31:14 - end writing
Operation Status: 1
Operation Status: 69
Operation Status: 0
01/28/2016 13:33:23 - started process bpbrm (pid=6632)
01/28/2016 13:34:04 - begin Delete Snapshot
01/28/2016 13:34:04 - Info bpfis (pid=0) Snapshot will not be deleted
01/28/2016 13:34:25 - Info bpfis (pid=5648) Backup started
01/28/2016 13:34:28 - Info bpfis (pid=5648) done. status: 0
01/28/2016 13:34:29 - end Delete Snapshot; elapsed time 0:00:25
01/28/2016 13:34:29 - Info bpfis (pid=0) done. status: 0: the requested operation was successfully completed
01/28/2016 13:34:29 - end writing
Operation Status: 0
Operation Status: 69
invalid filelist specification (69)

01/28/2016 13:31:14 - Info nbjm (pid=2691) starting backup job (jobid=1524) for client NODEB.MYDOMAIN.COM, policy exchange2010_dag0, schedule Full
01/28/2016 13:31:14 - estimated 0 kbytes needed
01/28/2016 13:31:14 - Info nbjm (pid=2691) started backup (backupid=dag0.mydomain.com_1453959074) job for client NODEB.MYDOMAIN.COM, policy exchange2010_dag0, schedule Full on storage unit stu1
01/28/2016 13:31:14 - started process bpbrm (pid=6348)
01/28/2016 13:32:14 - Info bpbrm (pid=6348) NODEB.MYDOMAIN.COM is the host to backup data from
01/28/2016 13:32:14 - Info bpbrm (pid=6348) reading file list from client
01/28/2016 13:32:35 - connecting
01/28/2016 13:32:55 - Info bpbrm (pid=6348) starting bpbkar on client
01/28/2016 13:32:55 - connected; connect time: 0:00:00
01/28/2016 13:33:20 - Info bpbkar (pid=5036) Backup started
01/28/2016 13:33:20 - Info bpbrm (pid=6348) bptm pid: 6605
01/28/2016 13:33:20 - Info bptm (pid=6605) start
01/28/2016 13:33:21 - Error bpbrm (pid=6348) from client dag0.mydomain.com: ERR - Streaming backups are invalid with Exchange 2010.
01/28/2016 13:33:23 - Error bptm (pid=6605) media manager terminated by parent process
01/28/2016 13:33:23 - Error bpbrm (pid=6348) could not send server status message
01/28/2016 13:33:23 - Info bpbkar (pid=5036) done. status: 69: invalid filelist specification
01/28/2016 13:33:23 - end writing
invalid filelist specification (69)

if i just want backup the specified database, how can i do ? example i just want backup XXXXX

Marianne · ‎01-27-2016

It may very well not be possible. Have you had a look at the Backup Selection examples in NBU for Exch manual? I do not have access to manuals right now, but this is the 1st place I would look. Links to manuals in Handy NBU Links in my signature.

Handy NetBackup Links

Marianne · ‎01-27-2016

Looking in the manual at the Policy config for DAG, I see this in Examples table:

Example policy that backs up a database for an Exchange DAG

Backup selections
- Microsoft Exchange Database Availability Groups:\Mailbox Database
- Microsoft Exchange Database Availability Groups:\forest or domain name\Microsoft Information Store\Mailbox Database

Handy NetBackup Links

VOX

exchange 2010 DAG backup problem