Mandri
2 Iron

NMM 9.1 don't backup Exchange 2013 DAG

Hi!

I have problem with configuring NW 9.1 and NMM 9.1 for backup Exchange DAG.

My configuration is: 

Networker Server & Client Version: 9.1.0.2

NMM Version 9.1.0.2

DAG environment Exchange 2013 and W2012 Server R2

 

Configuration DAG Client -  E2013DAG.local:

On sever E2013a DB12 has active state, on E2013B - passive.

Backup Objects:APPLICATIONS:\Microsoft Exchange 2013\DB12

backup command:nsrnmmsv

application information:

NSR_FEDERATED_BACKUP=yes

NSR_FEDERATED_PSOL=E2013a,E2013b

NSR_EXCH_INCL_SA=TRUE

NSR_EXCH_DAG=E2013DAG.local

NSR_EXCH_BACKUP=preferred

NSR_EXCH_CHECK=no

Group:test Exchange Backup

Priority:500

Parallelism:4

Block based backup:true

Client direct:true

Parallel save streams:false

Data Domain interface:IP

Remote AccessSmiley FrustratedYSTEM@E2013a, SYSTEM@E2013b

I received this error on E2013B in Application Windows log:

ESE BACKUP: Microsoft.Exchange.Store.Worker (13172) The surrogate backup by E2013b has stopped with error 0xFFFFFFFF.

ESE (ESE): Information Store - DB12 (13172) DB12: The backup has been stopped because it was halted by the client or the connection with the client failed.

NetWorker: The backup operation did not complete successfully.

107092:nsrnmmsv: Version information for C:\Program Files\EMC NetWorker\nsr\bin\nsrnmmsv.exe: Original file name: nsrnmmsv.exe Version: 9.1.0 (ntx64) Comments: Supporting Microsoft Volume Shadow Copy Service

127159:nsrnmmsv: Created temp path C:\Program Files\EMC NetWorker\nsr\tmp\nmm\2017-02-21_20-34-15_19636-14640\.

nsrnmmsv: multithreaded save set parallelism==4

145369:nsrnmmsv: Initialization success -- Exchange shell successfully initialized. Required for Exchange.

133296 1487702060 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 26 Starting backup operation. 0

145369 1487702060 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 89 Initialization success -- Exchange shell successfully initialized. Required for Exchange. 0

149887 1487702061 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 11 DAG IP: %s. 1 0 9 10.7.0.98

0 1487702061 1 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR notice 84 The Exchange DAG name "%s" was provided by the user.   The actual DAG name is "%s".  2 0 24 E2013DAG.local 0 24 E2013DAG.local

128717 1487702066 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 243 The federated Exchange backup state is set to PREFERRED, which selects passive, if available, on any node.  If a passive copy of a database is unavailable, the active copy is selected.  This method includes all mounted databases in the backup. 0

128723 1487702066 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 70 Exchange federated .. A preferred server order list has been provided. 0

0 1487702066 1 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR notice 57 Exchange federated .. Server order checked for databases: 0

0 1487702066 1 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR notice 7     %s  1 0 22 E2013A.local

0 1487702066 1 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR notice 7     %s  1 0 22 E2013B.local

0 1487702066 1 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR notice 116 Exchange federated .. An initial evaluation of listed database save set is being performed. This may take some time. 0

128686 1487702069 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 83 Exchange federated ..  Databases in DAG have been evaluated for backup..continuing. 0

111828 1487702070 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 45 Starting 'secondary' backup job on host : %s. 1 12 22 E2013A.local

51340 1487702070 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 45 %s(%d): Created Job ID: %d\n Save command: %s 4 23 10 jobhandler 1 3 306 1 5 64080 0 511 nsrnmmsv.exe -s jade.local -g "Backup/test Exchange Backup/backup/test Exchange Backup" -m E2013DAG.local -l incr -y "Wed Feb 22 23:59:59 GMT+0200 2017" -Z E2013DAG.local -A *NSR_BACKUP_GENERATIONID=1487702057 -A NSR_APP_TYPE= -A NSR_EXCH_CHECK=no -A NSR_EXCH_DAG=E2013DAG.local -A NSR_EXCH_INCL_SA=TRUE -A NSR_FEDERATED_BACKUP=yes -A NSR_FED_SECONDARY=yes -A NSR_SINGLE_SNAPSHOT=No -a "*POLICY ACTION JOBID=64076" -a "*POLICY ACTION NAME=backup" -a "*POLICY NAME=Backup"

116712 1487702170 0 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR info 32 Signal message received from %s. 1 12 22 E2013A.local

111830 1487702189 0 5 14 14640 19636 0 e2013b.local nsrnmmsv NSR info 54 Secondary backup with job id (%d) failed on host '%s'  2 1 5 64080 12 22 E2013A.local

111833 1487702189 5 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR critical 76 A 'secondary' job failure has been identified, stopping all 'secondary' jobs 0

139527 1487702189 3 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR error 51 The backup operation did not complete successfully. 0

102333 1487702190 3 0 0 14640 19636 0 e2013b.local nsrnmmsv NSR error 21 Exiting with failure. 0

21.02.2017 20:36:30 Removing files under temp path C:\Program Files\EMC NetWorker\nsr\tmp\nmm\2017-02-21_20-34-15_19636-14640.

Help me please!

Thanks!

0 Kudos
6 Replies
Hon2
1 Copper

Re: NMM 9.1 don't backup Exchange 2013 DAG

Hi Mandri,

Could you please use NMM Exchange Admin Configuration tool to validate the user account that is used to backup the Exchange DAG database ?

Click Configure Admin User on the NMM Exchange Admin Configuration window.

1. In the Configure Admin User page:

     a. Select the Configure Existing User option.

     b. Type the User Name and Password.

     c. Select the Skip Active Directory Authentication option.

     d. Click Configure.

2. Run the System Configuration Checker to verify that all the configurations are correctly set. Please provided any warning/failure alerts.

3. Please also confirm this is not a IP-less DAG hostname.

0 Kudos
Maliboo741
2 Bronze

Re: NMM 9.1 don't backup Exchange 2013 DAG

I had this problem with a new NetWorker install and Microsoft SharePoint.

"Secondary backup with job id (%d) failed on host '%s' "

The secondary host was my SharePoint Dummy node, the SQL server.  I added all nodes to the application administration user group in NetWorker to correct the problem.

0 Kudos
Dani_V1
1 Copper

Re: NMM 9.1 don't backup Exchange 2013 DAG

Hi, Mailboo74

Could you tell me what exactly did you add in the user group? I have the same problem with Exchange backup.

0 Kudos
Maliboo741
2 Bronze

Re: NMM 9.1 don't backup Exchange 2013 DAG

Hi,

I had to add both the SharePoint web front end server as well as the SharePoint sql server to the Application Administrators user group in NMC. 

user=administrator, host=webfrontend.domain.com

user=system, host=webfrontend.domain.com

user=administrator, host=sharepointsql.domain.com

user=system, host=sharepointsql.domain.com

0 Kudos
CloudsRester
1 Copper

Re: NMM 9.1 don't backup Exchange 2013 DAG

I had the same problem and added the NMM Exchange Admin user configured on the Networker client for the DAG.

- Open Networker Management Console

- Select client properties of Exchange DAG

- Select the Apps & Modules tab and add the NMM admin user created with NMM Exchange Admin Configuration

- Select the Globals (2 of 2) tab and add the FQDN of the same NMM admin user for your domain and the local Exchange servers (the client wizard config should have already added SYSTEM@exch1, SYSTEM@exch2, AND SYSTEM@exch3)


Maybe a bit overkill, but I was tired of messing around with it and just needed the backups to work.

Example:

SYSTEM@exch1

SYSTEM@exch2

SYSTEM@exch3

NMMExchange@exch-dag.domain.com

NMMExchange@exch1.domain.com

NMMExchange@exch2.domain.com

NMMExchange@exch3.domain.com

NMMExchange@domain.com

0 Kudos
Highlighted
Edu Febrero
1 Copper

Re: NMM 9.1 don't backup Exchange 2013 DAG

Y te funcionó?

0 Kudos