Hi ,

Can you run the backup for each database ? Please run one database at a time active and then see the result and if the active works then try passive for each database and see the result . This should reveal you something

Saveset should be something like "APPLICATIONS:\Microsoft Exchange 2013\DBname" and replace DBname with the actual database name which is seen in nsrsnap_vss_save -? output .

hi schema

You would need to check again the IIS settings.

Please take a look at these settings:

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.

Also check the bindings:

1. Start IIS Manager
2. Navigate to ->  Sites ->  Default Web Site
3. Select 'Bindings' under Actions - Edit Site or right click 'Default Web Site'  and do properties -> Bindings.
4. Under Site Bindings, look for 'https'  entry, select it and do  'Edit'
5. In Edit site Bindings Ensure 'SSL certificate' shows Microsoft Exchange (The certificate name may be different)
6. If the https binding does not exists for Exchange, create a new binding. (One for all 'all assigned' IP address and one for the local host (127.0.0.1))
7. Restart IIS.
8. Rerun the backup.

Let us know if that helps.

Thank you,

Carlos

Hello Carlos,

thanks for your answer,  I did your recommendations, bindings was good , but windows authenfication desable.

I 'm gonna try karthiks's recommendation in plus of yours and launch a new backup.

Backups still failed with the same errors :-(

Hi ,

It's good I 've followed your steps and of course enable windows authentification, and yes i checked that Kernel auth is disabled on each nodes.

thanks,

schema

you will need to enable it, making sure Kernel auth is disabled.

If you don't change that backup won't work.

you need to follow all my steps in order to have successful backups. Even if you run a backup for one single DB, you will still get the same error:

COM error occurred while validating the version of Exchange. The error code is 0x80010105

Thank you,

Carlos

Backups are still failed for now, but i found this error in the event viewer :

Processing data from remote server exdvdrartot003.eq1tot.lan failed with the following error message: [ClientAccessServer=EXDVDRARTOT003,BackEndServer=exdvdrartot003.eq1tot.lan,RequestId=088f80f1-e947-4524-9768-425802aa726c,TimeStamp=12/14/2016 3:37:39 PM] [AuthZRequestId=f0161098-ff87-42ce-a71c-d83bc6d4bee4][FailureCategory=AuthZ-CmdletAccessDeniedException] The user "eq1tot.lan/Servers/Exchange 2013/EXDVDRARTOT003" isn't assigned to any management roles. For more information, see the about_Remote_Troubleshooting Help topic.

So i'm checking Active directory rights for this computer, and i have this :

Domain Computers

Exchange install Domain Servers

Exchange servers

Exchange trusted subsystem

Managed availability Servers

So 'im checking if everything is ok on the Active directory side, i will rerun the backup and keep you posted for the result.

Regards

Hi schema

So did the backup work after the changes made?

I didn't quite get whether you said that windows authentication was disabled and you enabled it or not.

Please let us know if backups are now successful.

Thank you,

Carlos

Good Morning ,

Here the result of my last try yesterday evening, as you can see it's better, near 7Go was backuped :-)

Still got error of course, i found this o,ne in nmm.raw :

NSR critical NMM.. Exception caught: Could not connect to "RMAgentPS"(Replication Manager Client for RMAgentPS) service on port 6728 of host EXDVDRDATOT007.eq1tot.lan. Please stop and start the service and try again. Make sure to remove any stale entries for the host EXDVDRDATOT007.eq1tot.lan in etc\hosts file.

NSR critical The group or resource is not in the correct state to perform the requested operation.

NSR critical nsrsnap_vss_save: Exchange federated .. BakerJobInstantBackUpStart failed with error 0x8007139f  Fatal error and cannot continue.

The RMA service is currently running, so i will try to start and stop it, but there is one thing i don't understand about this error, the dag name is EXDVDRDATOT007 but it's a logical name, so i don't understand how can it be possible to start /stop a service on a logical device, someone can explain it to me ?

I gonna check on every nodes the RMA services and do start & stop + rerun the backup

keep you in touch

thanks,

Hi schema

Please follow the steps described under the following KB:

https://support.emc.com/kb/365455

Perform the steps outlined in the first two bullets below, or alternatively perform the step in the third bullet:

• On Exchange 2010 stand-alone servers: Domain user account with the Databases role.
  
  New-ManagementRoleAssignment -Role "Databases" -User
  
• On Exchange 2010 DAG servers: Domain user account with the Database, Database Copies, and Database Availability Group roles.
  
  New-ManagementRoleAssignment -Role "Databases" -User
  New-ManagementRoleAssignment -Role "Database Copies" -User
  New-ManagementRoleAssignment -Role "Database Availability Groups" -User

OR

• the customer can add the user to the Server Manager group instead of adding the Roles.
  

Note: On Exchange 2010 mount hosts, provide a Domain user account that is a member of the local Administrators group.

The user it refers to, is the user you have specified under the "log in" information for the service "Replication Manager Exchange Interface".

Thank you,

Carlos

Hello,

Backup still failed but with a new error :

92347:nsrsnap:***************** Snapshot Management operation has started, logging to "C:\Program Files\EMC NetWorker\nsr\logs\nwsnap.raw" *****************12/15/16 16:06:29.777251 [nsr/save/nsrsnap.c 609] Calling nsrrm_host

12/15/16 16:06:29.839544 [nsr/save/nsrsnap.c 884] Calling get_pool_name..

52051:nsrsnap:Printing savecmd=nsrsnap_vss_save.exe after parsing

12/15/16 16:06:31.227948 [nsr/save/nsrsnap.c 1691] Calling snap_wait..

APPLICATIONS:\Microsoft Exchange 2013

12/15/16 16:08:36.434911 [nsr/save/nsrsnap.c 1712] Calling parse_fs_logs_and_prefix..

82867:nsrsnap_vss_save:Stopping an instance of NMM save with process Id=22072 on host: exdvdrartot005.eq1tot.lan. There is another instance of NMM save program is already running.

102333:nsrsnap_vss_save:Exiting with failure.

I've already kill all the process tree concerning nsr_save and rerun the backup but still get this error.

Also i've tried to stop & star networker services.

Found no error in the nmm.raw , no error also in the event viewer

Hi schema

How is the group configured? Are you runnig more than one group at the same time?

I guess you are running the group only for the virtual node (DAG) and not against the physical nodes, correct?

Please try this:

1.- Stop NetWorker Remote Client (this one will also stop PowerSnap)

2.- Stop Replication Manager Exchange Interface service (if running)

3.- Stop Replication Manager AgentPS

4.- Rename on C:\Program Files\EMC NetWorker\nsr\tmp

5,. Start NetWorker Remote client

6.- Stat NetWorker PowerSnap service

7.- Start ONLY Replication Manager Agent PS, as Exchange Interface is manual and should be stopped-.

Then try a new a backup and let us know the results.

Thank you,

Carlos

Hi Carlos,

I 've done what your explained in your previous command, backup is running, i will keep you posted whan it will be finished.

For the configuration , it was done with EMC help few months ago, but maybe there is somes mistakes, so please find below screenshot about the config.

thanks,

Hello all,

This morning i had a regression on my backup , only few MB backuped ( in fact just the index ) , i found this error in the event viewer on Exchange tasks :

"source identity  does not have token serialization permission" , so i applied this : token serialization | Troubleshooting Exchange

and add an other roles : New-ManagementRoleAssignment -Role "Mailbox Import Export" -User svc_master ( found this inside EMC® NetWorker® Module forMicrosoft for Exchange ServerVSS page 34 )

All nodes had reboot after i rerun my backup, backup still running, finger crossed :-(

Hello,

This morning backup still failed, i begin to be desperate ^^

This error came back in NMM.raw : NSR critical RM .. 026671 ERROR:A COM error occurred while validating the version of Exchange. The error code is 0x80010105. The error message is: The server threw an exception..

As i already looked at IIS the last time, i will check again but i didn't change anything ..