Hi,

My first suggestion is to follow the steps described in this KB, which are pretty well defined, and it's pretty much a step-by-step configuration:

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

Now, did you install NMM in all the Exchange nodes of the DAG?

Did you create a client entry for all the physical nodes and for the DAG itself?

Are you backing up the physical nodes or the DAG? DAG cannot be backed up, so remove it from any group you may have it included.

What is the output of the command:

nsrsnap_vss_save -v -?

Have you ran the NMM Config Checker? that is my second suggestion always, as that will provide you with a report on the status of the Exchange server, DB's, permissions, VSS patches, etc.

By the way, the nmm.raw you provided is useless, as there is no information about the command.

Thank you.

Carlos.

ok i did everything as below ,

but still can not backup exchange and i did not reach any log that say something about going wrong.the only thing that i know i can't disable ipv6 on servers because they are in production . But i try it before in my company without disabling ipv6 from registry and i can get backups.

Scenario2

To backup all DB's against a single node. You need to create client resource for each physical member (node) and the DAG. 
These would be the settings for the physical_node1.  Similar settings for physical_node1 but it is not scheduled.

1. Client name:physical_node1.domain.com(The physical 2 nodes should be included in the same group, but only one of the being scheduled for backup, in this case physical_node1 will be the chosen one).
2. Backup command:nsrsnap_vss_save
3. Save set:APPLICATIONS:\Microsoft Exchange 2010
4. Application Information:NSR_SNAP_TYPE=vssNSR_ALT_PATH=C:\folder_name (This path has to be a local/not shared disk, doesn't matter which drive you use and what name you assign to the folder where you want to mount the snapshot)NSR_EXCH2010_BACKUP=allNSR_EXCH2010_DAG=dag1.domain.com
5. Aliases: 
   physical_node1
   physical_node1.domain.com
   
6. Note: If you want to configure the physical nodes to act as storage node please note that for DAG environments Dedicated Storage node IS NOT SUPPORTED.
   

These would be the settings for the Dag client resource.

1. Client Name:
   dag1.domain.com
2. Backup Command:
   nsrsnap_vss_save.exe
3. Save set:
   APPLICATIONS:\Microsoft Exchange 2010   ---  remember this client resource is not scheduled.
4. Aliases:
   dag1
   dag1.domain.com
5. Do not associate this client with any group.  Do not schedule this client.

here is the nsrsnap output,

List of valid saveset entries for APPLICATIONS on client 34ISTDAG01 ...

Initializing data to display...

NMM ... Using client name 34ISTDAG01, the version of the Exchange server is Exch

ange 2010.

"APPLICATIONS:\Microsoft Exchange 2010"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase500MB"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase2000MB"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase1000MB"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase8000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase250MB07"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase750MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase500MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase750MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase1000MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase2000MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase8000MB"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase1000MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase250MB05"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase2000MB05"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase2000MB06"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase750MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase500MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase250MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase500MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase750MB"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB06"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase250MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB07"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB750MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB11"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase1000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase500MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDatabase2000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB09"

79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an

instance of an object.

"APPLICATIONS:\Microsoft Exchange 2010\PublicFolder"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB5000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB08"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDatabase2000MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB04"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase250MB"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase750MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB500MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB1000MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB12"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB08"

"APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase250MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase2000MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB1000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB06"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB10"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB500MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB750MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB750MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB01"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB09"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB05"

"APPLICATIONS:\Microsoft Exchange 2010\MailBoxDataBase250MB06"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB250MB07"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB02"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB500MB03"

"APPLICATIONS:\Microsoft Exchange 2010\MBXDB2000MB05"

68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.

Hi,

Can you please paste in here the nmm.raw of the Exchange server you are backing up?

Are you backing up the 2 DAG nodes at the same time?

What is the value of NSR_EXCH2010_BACKUP=xxx?

What is the group completion error message? Anyway having the nmm.raw will help to identify the root cause of the issue.

Did you run NMM Config Checker? If so, what is the output?

If not, why not? It is really handy and helpful

Thank you.

Carlos.

Hi ,

Here is the raw and answer for your question.

NSR_EXCH2010_BACKUP=passive

63315 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save NMM.. Exception caught: Failed to commit replica.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Progress in RunActivityExecute phase is 100 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Overall progress is 85 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Progress in RunActivityRelease phase is 100 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Overall progress is 85 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:The user's application can now resume normal operation.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Completing replication of  for anywriter agent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Progress in RunActivityRelease phase is 0 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Overall progress is 85 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM .. 027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE.  The code is: 0x800423f3. Check the application event log for more information.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM .. 024168 ERROR:The VSS shadow copy for Exchange Replication Service was not successful because of an error that occurred earlier.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM .. 024119 WARNING:Transaction logs were not truncated because of an error that occurred earlier in the job. Review the job history for errors.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Progress in RunActivityRelease phase is 0 percent.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM ..  INFO:Overall progress is 85 percent.

83394 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save NMM .. cluster failover or application role change after a replica created may have caused snapshot creation failure, try to restart the backup. 

63335 16.05.2012 13:41:17  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save NMM backup failed to complete successfully.

50404 16.05.2012 13:41:17  0 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save nsrsnap_vss_save: createInstanceBackup() failed

0 16.05.2012 13:41:17  2 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010\MailboxDataBase750MB: failed 

63309 16.05.2012 13:41:17  1 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save NMM .. bye bye.

68151 16.05.2012 13:41:17  2 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save nsrsnap_vss_save: Exiting with failure.

Hi,

I'm still missing the most important information, which is the command issued,

Can you please attach the file itself? nmm.raw

If you use the advanced editor mode you will be able to attach files, with that output you attached I cannot check nothing.

Anyway, based on the error messages I have the following suggestions:

027114 ERROR:Exchange Replication Service is stable. The error is VSS_E_WRITERERROR_RETRYABLE.  The code is: 0x800423f3. Check the application event log for more information.

49931 16.05.2012 13:41:15  5 0 0 13176 12472 0 34istdag01 nsrsnap_vss_save RM .. 024168 ERROR:The VSS shadow copy for Exchange Replication Service was not successful because of an error that occurred earlier.

Try to run a full backup of all DB's, because when there is a failover of one DB NMM will have that in consideration and will request a full backup.

Specify the general saveset instead of specific DB name:

APPLICATIONS:\Microsoft Exchange 2010

instead of for example:

APPLICATIONS:\Microsoft Exchange 2010MDB

Also, what are the values in the Application Information field?

Thank you.

Carlos.

ok i will collect and send the files as soon as possible.

Here is the nmm.raw files attached.

Hi,

This is the problem:

82296 5/18/2012 5:16:35 PM  5 0 0 13628 7432 0 34istdag01 nsrsnap_vss_save NMM .. Operation unit failed with error 'Please make sure you have configured at least one NetWorker Device and client resources are configured for the application host[exchangedag.arkas.com] and the proxy client[34istdag01] on NetWorker Server [34istemcnwbck.arkas.com]'.Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc or 4)Drive not found

This usually indicates:

1.- Configuration issue.

2.- Name resolution issue.

3.- Duplicated client ID in the Media DB (Need to open a case with Support).

Checking the first entries in the nmm.raw file I found out that you created at first the client with FQDN:

-c 34istdag01.arkas.com -g Exchange

But the last entry suggests that you deleted the client and recreated it:

-c 34istdag01 -g Exchange

Did you use the same client ID when you recreated the client? If not I think that could be the problem, however I think you are missing one variable in the Application Information field.

This is Data Domain backup, and you have correctly set the variable:

NSR_DEVICE_INTERFACE=Data_Domain

But have you set this one?:

NSR_DIRECT_ACCESS=yes/no/default

This is recquired to let NetWorker/NMM that:

yes= disk only, so data travels directly to Data Domain device (client is storage node)

no= is for storage node )no storage node in use) so data travels to NetWorker server

default= is for undefined, which means that NMM ignores this parameter and NetWorker decides about the media type based on client configuration.

Also check the pool configuration, and ensure that the pool option in the client is blank, otherwise you can face problems. Pool is always defined at group level for NMM backups, as this is snapshot group.

Please check these points and if you check name resolution, configuration etc and still same issue then I'm afraid you have duplicated client Id, so you will need to engage EMC support so they can clean your MDB to get rid of old entries of that client with FQDN.

Anyway always create clients with FQDN and not short name.

Thank you.

Carlos.

ok i tried everything but i am still getting the error " no matching devices for save of client "exchangedag.xxx.com check storage nodes devices or pools"

Hi,

Are you backing up the DAG client or the physical node? I understand that you are backing up the physical node, but error message points to a wrong configuration on the DAG client:

exchangedag.arkas.com

Have you created a client entry for the DAG client, and leave it with no group assigned?

Is the name resolution working fine?

Have you added all aliases (including FQDN, and shortname in upper case and lower case?

If everything is fine I'm afraid that you need to engage EMC so they can clean out your Media DB, as that is the problem then.

You can check /nsr/index folder. You will have nested indexes for the physical client and also for the DAG, or at least for the physical client. So please engage EMC support for that.

Thank you.

Carlos.

Hi,

The problem solved . I delete all object in dag and recreate them with fresh media pool fresh backup device with ddboost. Now backup started . Now i am trying to understand ddboost works or not. Is there any way to understand this ?

Glad to see backup is now working. So turned out to be a condiguraiton issue, right?

About the DDBOOST I don't really understand your question, what do you want to check? If you have DDBOOST enabled and licensed on the DD itself, and everything is correctly configured, including ifgroup/routing, if you have that in place, then there is nothing really to check, DDBOOST is a mechanism that should be transparent, you won't see anything related to it, what you should see is a good performance. For example, 10 GBe LAN should provide between 50 and 150 MB/s aprox, but again, that depends on the infrastructure of your LAN.

Is the backup working? If so, what is the average speed you are getting?

Thank you.

Carlos.

Is this harmful message?

79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell Object reference not set to an

instance of an object.

Hi Carlos

Thanks...after the server reboot it's not there anymore...

Hi Thierry,

If backup/restore works fine you can ignore it. It should not be there, but it could be just some temporary issue with no impact in backup/restore.

Thank you,

Carlos.