Solved!
Go to SolutionExchange 2010 - Another instance is already running.
Hi there,
I'm currently trying to backup a Exchange 2010 server, but the job fails with this error in the NMM.RAW log:
"There is another instance of NMM save program is already running."
I can't see any other jobs in the system for this server running. Anyone have any idea why this might be happening? Any assistance would be greatly appreciated.
5593
1
Posted March 11th, 2012 18:00
Dear Alan,
may be you can refer to http://solutions.emc.com/emcsolutionview.asp?id=esg126922 for detail on diagnosis the issue.
5593
1
Posted March 11th, 2012 19:00
Hi AlanJH,
Additionally, Make sure that the nmm saving process has been killed from the Exchange 2010 server ( From the Task Manager of that server). As you cannot run two nmm processes at the same time , Make sure the old NMM process has been killed or kill it manually and then try the backup again.
Thanks,
Ahmed Bahaa
5593
0
Posted March 12th, 2012 22:00
Thanks Carlos,
I stopped the services and renamed the TMP file and the Exchange server was able to complete the backup job.
Many thanks to all who replied!
Regards,
AH
5593
0
Posted March 13th, 2012 00:00
Hi Alan,
Just to clarify, and to let you know that there is a reason behind removing /nsr/tmp, it's not only as in Windows OS issues when restarting fix 99,9% of the problems
Basically NetWorker will use that folder to keep local tracking of the backup process, and specially in NMM, Replication Manager and PowerSnap embedded modules place in that folder the temporary files and locks for the backup.
Cleaning out that folder will erase any information related with the last or current backup session.
Thank you.
Carlos.
5593
0
Posted December 4th, 2012 04:00
For others reading this, I saw it on NW 7.6.4 caused by the group not being snapshot enabled after nsrsnap_vss_save was entered as save command for the client. Creating new groups that were snapshot enabled and moving the filesystems backups of the exchange servers into these new groups solved the issue.
5589
0
Posted July 9th, 2015 10:00
Hi! Carlos I have the Same issue with Exchange and I do it that you refer but I still getting the same error.
I kill the process nsrsnap_vss_save, clean the tmp dir on Exchange Server and NW Server, but the problem persist.
any Suggestions?
5589
0
Posted July 9th, 2015 10:00
Hi Oscar,
What NMM version are you running?
If 2.x then most likely there is overlapping of File System and Exchange backup.
Also is not good to kill nsrsnap_vss_save as that could leave the writer being used in bad status.
You have to have in mind that in DAG environments there are "slave jobs" running in other nodes, so check that there is nothing running in any of the nodes.
Thank you,
Carlos
777
0
Posted July 9th, 2015 12:00
I suppose you are aware that 7.6.x is no longer supported, right?
Once again, if it's a DAG environment check there is nothing running in any other node, otherwise the error message is a red hearing and there is something else going on.
Thank you,
Carlos
777
0
Posted July 9th, 2015 12:00
Sorry Carlos, I make a mistake NMM is 2.4.1 Build 92
NW version is 7.6.5.7 build 1231
CarlosRojas
1 Rookie
•
1693 Posts
5593
1
Posted March 12th, 2012 03:00
Hi Alan,
Besides the previous recommendation I would suggest you to check the following:
1.- Is there nsrsnap_vss_save.exe currently running on the client you have NMM installed on? If so manually terminate the process tree
2.- I would suggest you to stop NetWorker services including Replication Manager service/s, rename or delete /nsr/tmp folder and start NetWorker services and RM services again, to get ride of any pending session or operation.
3.- Also ensure that, if you are backing up Exchange 2010, check the status of the DB's, as maybe a previous backup attempt left the DB in status "Backup Running", so NMM understand that there is a concurrent backup operation taking place and will fail with that message:
http://technet.microsoft.com/en-us/library/bb124924.aspx
Thank you.
Carlos.