roudybob

10 Posts

23897

May 4th, 2011 05:00

NMM 2.3 and Exchange 2010

Hi,

I'm struggling to get a exchange 2010 DAG cluster backed up with the new nmm2.3 i'm getting the following reported when trying to run a backup

50412:nsrsnap_vss_save:nsrsnap_vss_save: Invalid argument: -g is specified without snap_sessionID

I've added all the exchange mailbox servers in the cluster as clients and defined the DAG as a client with the relevent options as defined in the APP guide but no luck Networker is 7.61 build 467 and the clients are Windows 2008R2

Regards

Rob

Responses(20)

36115_carloscor

217 Posts

0

May 4th, 2011 06:00

Hi Rob,

Let's start from the beginning:

- Ensure that in IIS you have set the correct permissions for PowerShell, as described in the documentation:

1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell.
2. On the right-hand side pane, double-click Authentication and Enable Windows Authentication.
3. In Windows Authentication, right-click and ensure that the Kernel Mode Authentication is clear.

- Ensure that you have created one client entry for each member of the DAG

- Check the Application Information variables set for those clients. DAG members:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=C:\snapshot (That path is an example, you can set any path you want, but ensure that the value entered there is a local disk)

NSR_CHECK_JET_ERRORS=no (You can set yes or not, if you don't specify that value by default errors won't be checked)

NSR_EXCH2010_BACKUP=passive (You can select active, passive or all, check what DB's are active or passive in each node, if all passive in one node you can backup only that node setting here passive)

NSR_EXCH_CHECK=no (You can select yes or not if you want or don't want to perform Exchange DB consistency check)

NSR_EXCH2010_DAG= (Add here the name of the DAG with FQDN)

These variables have to be set in the nodes hosting DB's, but for the DAG server no need, only the following are required:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=C:\snapshot

Also please note that with NMM 2.3 in DAG environments you will not backup the DAG itself, but the nodes hosting DB's, so if selected please uncheck the box in the DAG client entry "Scheduled backup".

Apart from that check that the group has set the Serverless backup snapshot policy, that the snapshot backup box is selected as well, and choose the right pool for that backup.

Having this set correctly please check that vssadmin list writers reports all the writers in status [1] Stable, and that vssadmin list shadows doesn't display any shadow created, once you check that you can go ahead can run a backup.

Thank you.

Carlos.

36115_carloscor

217 Posts

1

May 4th, 2011 05:00

Hi Rob,

That error message looks to me as if you have selected a pool within the client configuration.

Please note that the pool will be defined in the group configuration, under "Snapshot Policy", so please remove the pool from the client configuration and run a new backup. This time should work fine.

Thank you.

Carlos.

roudybob

10 Posts

0

May 4th, 2011 06:00

Hi Carlos

well you have helped me to get further i'm now getting

80746:nsrsnap_vss_save:NMM .. unrecoverable error retrieving the Exchange Server version -- 0x5012.

68151 1304514779 2 0 0 1412 7492 0 ***-*-m*01.anglia.local nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0
***-dag-ex2010.***.local APPLICATIONS:\Microsoft Exchange 2010: Backup of [APPLICATIONS:\Microsoft Exchange 2010] failed

I fspecified the pool in the client out of habit but the documentation didn't define to leave empty, but still my bad

Regards

Rob

roudybob

10 Posts

0

May 5th, 2011 05:00

Hi Carlos,

I have configured the clients as per your instructions am getting stable on the vss writers and nsrsnap_vss_save -? displays properly I now get

82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010\DB01-C#### Primary is valid.

63781:nsrsnap_vss_save:NMM .. attempt to add component of writer Microsoft Exchange Replica Writer returned an error and can not be added. Error = -2147467259.

63783:nsrsnap_vss_save:NMM .. attempt to add components of writer Microsoft Exchange Replica Writer returned an error and were not added. Error = -2147467259.

80826:nsrsnap_vss_save:NMM .. Backup of Exchange 2010 saveset Microsoft Exchange 2010\DB01-C#### Primary failed. Error 0x80004005.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

Internal error.

68151 1304598394 2 0 0 6156 4856 0 ***-i-m**.anglia.local nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

APPLICATIONS:\Microsoft Exchange 2010\DB01-C#### Primary: Backup of [APPLICATIONS:\Microsoft Exchange 2010\DB01-C#### Primary] failed

Regards

Rob

36115_carloscor

217 Posts

1

May 5th, 2011 07:00

Hi Rob,

That looks to me yet as a permissions issue.

Please verify the permissions granted for the user starting up the following service:

Replication Manager Exchange Interface.

This user needs Exchange Organization, Domain Administrator and "send-as, Receive-as" permissions.

If the user has already those permissions, check in COM+, as described in NMM 2.3 Documentation:

Modifying the Microsoft Exchange 2007 COM+ component’s user account or password
If your user account, your password information, or both change after the COM+ component is registered, use the following procedure to change the user account or password information for the COM+ component:
1. Start component services.
2. Expand Computers > My Computer > DCOM Configuration.
3. Right-click Replication Manager Exchange Interface and select Properties from the context menu.
4. Click the Identity tab.
5. Modify the domain user account or password and click OK.

This will also modify the account information for the Replication Manager Exchange Interface Service.

Please let us know how it goes.

Thank you.

Carlos.

roudybob

10 Posts

0

May 5th, 2011 08:00

Hi Carlos,

I've tried the dcom permissions which were set as per documentation but I'm getting the same/similar error still i'm afraid

Internal error.

68151 1304606458 2 0 0 7056 1360 0 ***-i-m**01.anglia.local nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

fo - Name: LogReplayQueueIncreasing Value: False

PSPropertyInfo - Name: LogCopyQueueIncreasing Value: False

PSPropertyInfo - Name: OutstandingDumpsterRequests Value:

Regards

Rob

36115_carloscor

217 Posts

1

May 9th, 2011 02:00

Hi Rob,

I would kindly ask you to open a case so I can investigate further and request you some logs that I would need to look into.

Once case is fixed I'll post the resolution steps in here.

Thank you.

Carlos.

roudybob

10 Posts

0

May 10th, 2011 01:00

Hi Carlos,

I opened a case and suggestions were made, but in the meantime was still persevering in trying to get it to work, in the end it turns out we have 9 databases all on separate volumes with the log files on separate volume to the log log files (all in separate volumes) but configured in the same mount point. The config checker for 2.3 pointed out that they can't exist in the same volume so created a new mount point and moved the logged files to it. I then got another error which was different and looked like the snapshot stuff was working, so in desperation made a note of all the setting deleted all the exchange clients and the groups and recreated.

This then worked and was able to backup a single database to backup and restore successfully.

I did have to restart the information store in exchange as I was getting another error but this was detailed the applications guide under troubleshooting

So in short following your instructions to setup the backup for a DAG works fine but must have had some left over hidden configuration in the client (probably from the many changes I was making trying to get it to work) which deleting and recreating correctly cured

Thanks for your help in resolving this

Regards

Rob

ronald_lijs

15 Posts

0

May 22nd, 2011 10:00

Hi guys,

I am getting a slight similar error been debugging, but can't get any further...

...

RPC Authentication: Client successfully obtained AUTH_LGTO credentials

NMM .. Supported writer WMI Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.

Checking name is valid or notExecution in check_valid_name save set name APPLICATIONS:\Microsoft Exchange 2010Comparing APPLICATIONS with save set name APPLICATIONS:\Microsoft Exchange 201082624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.

NMM .. return of backup type for Exchange 2010 is -- passive.

NMM .. failed to retieve Replica Writer for passive databases.

63335:nsrsnap_vss_save:NMM backup failed to complete successfully.

nsrsnap_vss_save(275): Entering SendRecoverJobFailure().

Internal error.

nsrsnap_vss_save(287): Exiting SendBackupJobFailure().

nsrsnap_vss_save: Sending backup status to nsrsnap

nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010: failed

...

Any more ideas? I am following Carlos' recomendations.

Thanks!

Ronald

36115_carloscor

217 Posts

0

May 22nd, 2011 23:00

Hello Ronald,

Can you please run the following command on the Exchange server hosting the passive DataBases?:

vssadmin list writers

Based on the error message you are getting looks to me as if the Exchange Writer is not in the correct status:

"failed to retieve Replica Writer for passive databases"

Also please ensure that the host you are backing up is hosting at least one Passive DataBase, otherwise backup will fail as "there is nothing to backup".

What is the save set you have specified for that client?

Thank you.

Carlos.

ronald_lijs

15 Posts

0

May 23rd, 2011 00:00

Hi Carlos,

I had checked this and was looking for errors, but JUST noticed that the Replication Writer is not there!

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

Writer name: 'Task Scheduler Writer'

Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

State: [1] Stable

Last error: No error

Writer name: 'VSS Metadata Store Writer'

Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

State: [1] Stable

Last error: No error

Writer name: 'Performance Counters Writer'

Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

State: [1] Stable

Last error: No error

Writer name: 'System Writer'

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Instance Id: {3d37b61b-708f-45f7-ad5f-d605ad797e71}

State: [1] Stable

Last error: No error

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {dc24d21a-1454-4e34-b02b-62b8b2421b2e}

State: [1] Stable

Last error: No error

Writer name: 'FSCVSSWriter'

Writer Id: {68124191-7787-401a-8afa-12d9d7ccc6ee}

Writer Instance Id: {160f49d9-96e5-4acb-a3ad-29f9bb3cf606}

State: [1] Stable

Last error: No error

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {dd1e5993-17e0-412f-a724-109293cd6887}

State: [1] Stable

Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {a19a9cd6-3f8b-458d-8f07-018e85da05e4}

State: [1] Stable

Last error: No error

Writer name: 'IIS Config Writer'

Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

Writer Instance Id: {2b083e5d-aa98-404d-8a80-114ad0c01312}

State: [1] Stable

Last error: No error

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {e6957b60-2516-4fa1-a12c-f7b4a8c63837}

State: [1] Stable

Last error: No error

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {87e33888-0e04-43dc-a8f0-72bbfbc37682}

State: [1] Stable

Last error: No error

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {9c6493d5-cab6-417b-9f7a-0df874f315df}

State: [1] Stable

Last error: No error

Writer name: 'Cluster Database'

Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

Writer Instance Id: {ea5fe984-a943-4069-8c0a-05802a5ffcc3}

State: [1] Stable

Last error: No error

Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {1a37fa4c-d7d2-482f-a0e4-ece7009bbc03}

State: [1] Stable

Last error: No error

Writer name: 'Microsoft Exchange Writer'

Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

Writer Instance Id: {4bc8c772-f7a3-42cc-bc13-7106f9ba9cbf}

State: [1] Stable

Last error: No error

This essentially means that either the DAG is not configurd properly? I am not proficient in Exchange :-(

Thanks,

Ronald

36115_carloscor

217 Posts

0

May 23rd, 2011 01:00

Hello Ronald,

Indeed Exchange 2010 should be installing/registering 2 writers as you said:

Microsoft Exchange Writer

Replication Writer (will be available for use with copies of databases in a DAG).

Based on this I would say that yes, something is not correct on the DAG side, however, let me suggest you to download NMM Config Checker 1.1 from Powerlink:

Home > Support > Software Downloads and Licensing > Downloads J-O > NetWorker Module

NetWorker Module for Microsoft Applications Config Checker provides pre-installation verification of configurations for Microsoft SharePoint, Microsoft Exchange, and EMC CLARiiON® to ensure proper operation with EMC NetWorker.

The error message is pretty clear, looks like, because of the Replication Writer is not present, NMM/NetWorker doesn't detect any save set that matches the requested operations (NSR_EXCH2010_BACKUP=passive). This variable is only intended for DAG environments so, if you have this variable set, but NetWorker/NMM doesn't detect the Data Bases being replicated (Replication Writer) then backup will fail because there is nothing to be backed up.

I would engage you Exchange admin to look into this.

Thank you.

Carlos.

Holger_Inf

122 Posts

0

May 24th, 2011 01:00

please check solution esg121717

the nmm.raw in applogs on the client may contain

Error: database files and log files are on the same volume. Terminating backup. ";

This will produce the 0x80004005 error as well.

Cause

NW123619 Limitation of NMM module at this time Data and log location cannot be on the same drive

Resolution

Workaround: Do not have the Data and log files on the same physical Drive letter. Even if you using CLARiiON device with 2 lun assigned to the same windows Drive letter you will see the same issue. Data and logs location must be on 2 physical drive letter.

Note: This is currently the work around and Engineering is still working on NW123619 contact EMC support for further details on Changes for NMM 2.3 with Exchange 2007 and Exchange 2010

roudybob

10 Posts

0

June 7th, 2011 03:00

Hi,

Have had backup working in Exchange 2010 for a couple of weeks and thought I would try a restore and it doesn't work the error it responds with is

48373 1307440076 5 0 0 9836 8516 0 xxx-i-mbx01.anglia.local nsrsnap_vss_recover 42 PS CLIENT .. failed to obtain module error 0

the error above was from a system recover of 1 folder but get a similar error on a DB restore to a recovery database

Cheers

Rob

36115_carloscor

217 Posts

0

June 7th, 2011 04:00

Hello Rob,

I would say this should be a new threat, however please see below some tips:

Is this a DAG or stand-alone environment?

If DAG please note the following requirements to perform restores:

1.- In NMM GUI, you need to restore from DAG name, not from Physical node and, to do it you have to follow these steps:

a) Options->Configure options

b) On the first field, where you see the client name, please click on the double green arrow icon.

c) On the left pane you will see all the clients, please select the DAG client (with FQDN in case you see more than one) and click on add

d) Once you have added the DAG name, please click on the drop-down menu on the top right (where the physical client name appears) and select the DAG with FQDN.

e) Try to perform the restore again.

Now please go to the "Monitor" tab on the left pane, and click on "Clean" to clean out all the previous logs, then try another restore, and if it fails please attach the output of the logs shown in the Monitor tab of the NMM GUI.

Thank you.

Carlos.

1
2

View All

No Events found!