UNSOLVED

castro_flavio

updated

15 years ago

0

5136

June 7th, 2011 12:00

Nmm 2.3 with Exchange 2010

Hi people,

I'm needing to configure my Networker to back up Exchange 2010, but I'm having trouble, below is the scenario:

Exchange 2010 SP1 with DAG
Networker 7.6 SP1
NMM 2.3

Can someone help me, please.

Thanks,

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    416

    1

    Posted June 8th, 2011 02:00

    There has been some recent discussion on this subject in technical forum area for NW:

    https://community.emc.com/community/support/networker?view=discussions

    You may wish to check it out.  If it does not work please open a thread there with as much as specific your question can be.

  • 416

    0

    Posted June 9th, 2011 06:00

    Is experiencing the following error when running the backup?

    savegrp: suppressed 6 lines of verbose output

    80634:nsrsnap_vss_save:NMM .. Warning: The specified snapshot policy allows snapshots to be stored locally on the client for a period of time before expiration. Locally stored snapshots present a risk of data loss if there is a failure of the local media containing the snapshot, or if a snapshot rollover fails and the corresponding locally retained snapshot expires before a manual rollover can be performed. Group: "db_IS_exchange_diario_2010" Snapshot Policy: "Policies Exchange" Snapshots Per Day: "1" Retain: "2" Backup Snapshots: "All" Level: "full".

    79946:nsrsnap_vss_save:NMM .. Exchange2010 Shell

    79598:nsrsnap_vss_save:NMM .. Exchange2010 Shell 

    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.

    68151 1307585107 2 0 0 13836 12424 0 aluminio.bancoschahin.com.br nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0

  • joka2

    1 Rookie

    •

    144 Posts

    416

    0

    Posted July 1st, 2011 03:00

    I'm also trying to configure a Exchange 2010 DAG backup with NMM 2.3

    We get this error:

    DAG name entered for client not in a DAG

    and also

    "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."

    When is NMM configuration going to be easy!

    Regards,

    Johannes

  • 416

    0

    Posted July 1st, 2011 13:00

    I'm having the same problem as you, Joka

  • cfowler2

    14 Posts

    416

    0

    Posted January 6th, 2012 10:00

    Anyone ever receive a response to this?  We're having the same issue - DAG name entered for client not in a DAG.  We've followed the configuration instructions so we're certain this is a permissions issue but would like verification.  If smoeone actually got anywhere with this it would be great to know.

    Cheers,

    C

  • cfowler2

    14 Posts

    416

    0

    Posted January 6th, 2012 12:00

    Thanks for the response.  I've followed your suggestions and everything checks out.  I do see some issues in the nmm.raw file that indicate something may be wrong with how we specified the application information.  "unknown application information parameter: %s..."  have to do some more reading.

  • ZennaroNicola

    1 Rookie

    •

    88 Posts

    416

    0

    Posted January 11th, 2012 06:00

    try defining client resource with capital letters..i had a similiar problem solved with this workaround

  • cfowler2

    14 Posts

    416

    0

    Posted January 11th, 2012 07:00

    Thank you for the suggestion.  As it turns out our issues were resolved by Rebooting the Exchange Servers, Replication Manager was in a poor state that apparently only a reboot could resolve and the other issue, which we suspected, was a credentials issue.  We're green across the board now.  Thanks for the help everyone!