As per backup command you are using the application information NSR_DATA_MOVER=xxx and NSR_DM_PORT=xxx.
If you are not using proxy host I would suggest you to remove those options.
Also I saw that the NSR_ALT_PATH is set to K:\snap, is that a local drive? If not you have to specify a local drive to mount the snapshots.
Also please ensure that the Microsoft Exchange Information Store has startup type manual on the passive node, and normally that service should be stopped on the passive node. (I understand you are backing up the passive node as per log output).
Also I would suggest you to download and install NMM Config Checker (Available in Powerlink) so you can check if the Application host has the latest patches installed and if the configuration of Exchange DB's are correct as well.
And finally check that all the VSS writers are in status [1] stable, and no errors, running the command:
ble1
4 Operator
•
14.4K Posts
0
December 7th, 2010 16:00
Is this active or passive node? Also, can you check mentioned log if it contains more information? What is the version and build of NMM you use?
36115_carloscor
217 Posts
0
December 7th, 2010 23:00
Hello there,
As per backup command you are using the application information NSR_DATA_MOVER=xxx and NSR_DM_PORT=xxx.
If you are not using proxy host I would suggest you to remove those options.
Also I saw that the NSR_ALT_PATH is set to K:\snap, is that a local drive? If not you have to specify a local drive to mount the snapshots.
Also please ensure that the Microsoft Exchange Information Store has startup type manual on the passive node, and normally that service should be stopped on the passive node. (I understand you are backing up the passive node as per log output).
Also I would suggest you to download and install NMM Config Checker (Available in Powerlink) so you can check if the Application host has the latest patches installed and if the configuration of Exchange DB's are correct as well.
And finally check that all the VSS writers are in status [1] stable, and no errors, running the command:
vssadmin list writers
Please let us know if this helps.
Thank you.
Best regards,
Carlos.