Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

7582

May 8th, 2012 07:00

Exchange 2010 save with NMM2.3 (passive)

Hello

I'm trying to back up Exchange 2010 in a two-node DAG-Environment through NMM2.3. I installed and ran the config checker, everythings fine. I created a client ressource for each node and a ressource for the DAG as well. Config checker sais everything is correctly configured. But the group fails after 30 seconds after start and i'm getting following errors:

SAVEGROUP DETAILS:

"savegrp: suppressed 5 lines of verbose output

The term 'Get-DatabaseAvailabilityGroup' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

powershell.Invoke Get-MailboxServer failed.

The term 'Get-MailboxServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

80873:nsrsnap_vss_save:NMM ..DAG name entered for client not in a DAG. Cannot continue.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1336481003 2 0 0 10052 9132 0 node1.domain.local nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

, retrying to initialize Powershell session using credentials...

63430:nsrsnap_vss_save:NMM .. failed accessing reg key SOFT

"

NMM.RAW:

52701 1336485726 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 19 Command line:\n  %s 1 0 511 C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe -A optype=conventional -A NSR_SNAP_TYPE=vss -A NSR_EXCH2010_DAG=dagalias.domain.local -A NSR_EXCH2010_BACKUP=passive -A NSR_ALT_PATH=D:\NWExchSnapshots -A NSR_PARENT_JOBID=38385 -b Exch2010Pool -c node01.domain.local -g RZ_A_EXCHANGE2010_MAILBOX -LL -m node01.domain.local -s backupserver.domain.local -l full -q -W 78 -A snap_sessionid=1336485725 -A NSR_STRICT_SYNC=0 -A NSR_PS_DEBUG_ID=1336485721 -A NSRSNAP_JOBID=38388 APPLICATIONS:\Microso

52702 1336485726 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 33 System Version: %d.%d Build %d %s 4 1 1 6 1 1 1 1 4 7601 0 1 S

52705 1336485726 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 40 Computer Name: %s User Name: %s (%s) 3 0 11 NODE01 0 19 NT AUTHORITY\SYSTEM 0 6 SYSTEM

73064 1336485726 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 81 Version information for %s:\n    Original file name: %s\n         Version: %s\n Comments: %s 4 0 52 C:\Program Files\Legato\nsr\bin\nsrsnap_vss_save.exe 0 20 nsrsnap_vss_save.exe 0 8 2.3.0.87 0 49 NetWorker Module for Microsoft Applications (x64)

52681 1336485727 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 28 NetWorker Server Version: %s 1 0 71 NetWorker 7.6.3.3.Build.870 NetWorker Source Capacity Data Zone Enabler

50423 1336485727 0 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 85 nsrsnap_vss_save: Unknown Application Information parameter: %s, may not be supported 1 0 13 NSRSNAP_JOBID

50411 1336485727 0 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 77 nsrsnap_vss_save: Data mover host name not specified. Assuming local host: %s 1 12 25 node01.domain.local

50402 1336485728 0 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 46 nsrsnap_vss_save: Inserting %s in saveset list 1 0 37 APPLICATIONS:\Microsoft Exchange 2010

80271 1336485729 0 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 137 NMM .. Valid snapshot policy. Group: "%s" Snapshot Policy: "%s" Snapshots Per Day: "%s"  Retain: "%s" Backup Snapshots: "%s" Level: "%s". 6 0 25 RZ_A_EXCHANGE2010_MAILBOX 0 25 Exch2010_ServerlessBackup 0 1 1 0 1 0 0 3 All 0 4 full

63430 1336485729 5 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 41 NMM .. failed accessing reg key %s - 0x%x 2 0 35 SOFTWARE\Legato\NetWorker\VSSClient 1 1 6

80873 1336485730 5 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 65 NMM ..DAG name entered for client not in a DAG. Cannot continue.  0

63335 1336485730 5 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 43 NMM backup failed to complete successfully. 0

50404 1336485730 0 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 47 nsrsnap_vss_save: createInstanceBackup() failed 0

0 1336485730 2 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 29 nsrsnap_vss_save: %s: failed  1 0 37 APPLICATIONS:\Microsoft Exchange 2010

63309 1336485730 1 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 15 NMM .. bye bye. 0

68151 1336485730 2 0 0 11020 10392 0 node01.domain.local nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

The same time the group starts, i'm getting an application event error on the Exchange-Node with eventid 17, Source "MSExchange RBAC" :

(Process w3wp.exe, PID 2976) "RBAC authorization returns Access Denied for user domain.local/Server/EXCHSRV1. Reason: No role assignments associated with the specified user were found on Domain Controller domaincontroller.domain.local"

The Replication Manager Exchange Interface-Service runs with the service account we granted the exchange-rights:

New-ManagementRoleAssignment -Role "Databases" -User < user account>

New-ManagementRoleAssignment -Role "Database Copies"  -User

New-ManagementRoleAssignment -Role "Database Availability Groups" -User

get-ExchangeServer EXCHSRV1 | Add-AdPermission -user exadmin -AccessRights ExtendedRight -extendedrights  Receive-As, Send-As, ms-Exch-Store-Admin

- The DNS-Entry for DAG exists and i can ping it from nearly everywhere... So DNS should not be the cause of the problem...

Environment:

*************************

Networker Server & Client Version: 7.6.3.Build.870

NMM Version 2.3.0.87

OS NWServer & Exchange-Nodes: W2008 Server R2

Save to a DD630, OS Version: 5.1.1.0-291218

- Client Ressources:

Name: node1.domain.local / node2.domain.local

SaveSet: APPLICATIONS:\Microsoft Exchange 2010

Backup command: nsrsnap_vss_save.exe

Application information:

NSR_SNAP_TYPE=vss

NSR_EXCH2010_DAG=dagalias.domain.local

NSR_EXCH2010_BACKUP=passive

NSR_ALT_PATH=D:\NWExchSnapshots

NSR_IGNORE_MISSING_SYSTEM_FILES=yes

Deduplication: Data Domain backup checkbox: not set

Aliases:

Node01 / Node02

node01.domain.local / node02.domain.local

- DAG Ressource:

Name: dag.domain.local

SaveSet: APPLICATIONS:\Microsoft Exchange 2010

Backup command: nsrsnap_vss_save.exe

Application information: none

Aliases:

DAG01

dag01.domain.local

Any suggestions and ideas are highly appreciated. Thanks

1.7K Posts

May 12th, 2012 23:00

Hi Phasius,

This error message:

NMM .. failed accessing reg key SOFTWARE\Legato\NetWorker\VSSClient - 0x0

Could indicate a problem with the permissions for that particular registry key, anyway is good that now you are able to display the savesets.

Having this now fixed try this:

1.- Stop NetWorker services including Replication manager services (the 2 of them)

2.- Delete /nsr/tmp folder

3.- Start NetWorker services, including ONLY Replication Manager AgentPS (Replication Manager Exchange Interface service is manual and will be started automatically when required).

4.- Run a new backup.

If it fails please attach the file nmm.raw from that exchange server.

Thank you.

Carlos.

20 Posts

May 8th, 2012 09:00

A couple things stand out to me:

  1. I see two different names for the DAG, there should only be one name for the DAG and it should be the same in both places.

    1. NSR_EXCH2010_DAG=dagalias.domain.local  <--- Is this the DNS name of the DAG?
    2. DAG Ressource: Name: dag.domain.local          <---- Or is this the DNS nsme of the DAG?

     2. Whatever is registered in Exchange as the DAG resource is what have to use. You cant use alias, CNAME, etc.

     3. You also seem to be having permission errors. You said you ran the config checker and you used the same user name and password that will be used to execute the nsrsnap_vss_save command?


544 Posts

May 8th, 2012 21:00

Hi,

Can you please run the following command and paste here the output?:

nsrsnap_vss_save -v -?

Also please check the following Powerlink KB article:

https://solutions.emc.com/emcsolutionview.asp?id=esg127800

Thanks,

Ahmed Bahaa

1.7K Posts

May 8th, 2012 22:00

Hi Phasius,

RBAC event ID 17 means that some role has not been created or assigned to the user.

In this case user should be the one starting up Replication Manager Exchange Interface service.

Please check below the roles assignments required for that user to avoid those events:

These are the permissions you need to set.

First create the roles  (If already created there is no problem in running these commands):

New-ManagementRoleAssignment -Role "Databases" -User < user account>

New-ManagementRoleAssignment -Role "Database Copies"  -User

New-ManagementRoleAssignment -Role "Database Availability Groups" -User

Once roles have been created assign them to the user as follows:

get-ExchangeServer EXCHSRV | Add-AdPermission -user exadmin -AccessRights ExtendedRight -extendedrights  Receive-As, Send-As, ms-Exch-Store-Admin

Where EXCHSRV is the name of your Exchange server and exadmin is the user you are using to start up RM Exchange Interface service.

But anyway you will also need to check the name resolution.

Thank you.

Carlos.

9 Posts

May 9th, 2012 05:00

Thanks for your answers guys. I'm still getting the same errors...

@danag:

1) The DAG-Names for both client and DAG-ressources are the same, i made a tipo here in the posting. Sorry for that.

3) yeah this nsrsnap_vss_save.exe was run with the same user as set in the config checker and to which the exchange rights have been granted to:

C:\Windows\system32>nsrsnap_vss_save -v -?

[Output]

68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.

C:\Windows\system32>

I checked all the steps in https://solutions.emc.com/emcsolutionview.asp?id=esg127800 :

- what confuses me is, the article says the 'Replication Manager Exchange Interface'-service has to run under LOCAL SYSTEM. But by default, installer changes it to the service account you grant rights to, and Carlos mentioned it too. What is correct now? Local System or the service account?

@Carlos:

- in reran all role assignments, it should be definitly correct right now.

- name resolution for the dag, backupserver, and exchange-servers are working from and to all servers (forward- and reverse lookup).

Anything else? thanks for your help

1.7K Posts

May 9th, 2012 05:00

Hey, I cannot see any valid saveset in there, so command didn't run successfully.

You still have IP_V6 enabled.

You need to look into the Exchange Applicaiton event logs, as you will for sure fin more information in there, however I would suggest you to:

1.- Check status of writers:

vssadmin list writers

2.- Stop NetWorker servieces indluding the 2 Replicaiton Manager services

3.- Delete /nsr/tmp on the exchange client

4.- Start NW services, and second the Replicaiton Manager AgantPS, and leave RM Exchange interface stopped.

Run the same command again and check the output, if valid savesets displayed run a backup, if fails then run:

nsrsnap_vss_save -D3vvv -v -?

Thank you.

Carlos.

1.7K Posts

May 9th, 2012 22:00

Hi,

You still have IP_V6 enabled, you should disable it.

Also, this is the key message:

NMM .. writer Microsoft Exchange Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.

To speed up the troubleshooting and resolution of the problem, specially if it's a compatibility related issue, I would recommend you to install NMM Config Checker and run in on that server, check out the results and it will tell you what thep problem is, or at least will point you in the right direction.

I also saw you are using build 087, I would suggest you to upgrade to 109, which is the latest however, before doing anything please run the following command on the Exchange server:

First from command line run this command:

vssclupdate.exe

This will update in NetWorker/NMM the list of writers on that server, let's say will repopulate the writers information.

Thank you.

Carlos.

9 Posts

May 16th, 2012 04:00

Hi Carlos

It is finally working - thank you very much!

No Events found!

Top