03-17-2015 02:47 AM
vmd failed to come up after initiating restart node (Windows 2012 R2 Standard) from Azure portal. What can be the reason ?
Also, I would like to know the difference between vmd and nbemm.
Solved! Go to Solution.
03-17-2015 03:21 AM
Check if Symantec Private Branch Exchance Service is running.
Start if this is not running.
If it is running, open cmd (Run as Administrator if UAC is not disabled), cd to <install-path>\veritas\netbackup\bin.
Run:
bpps
copy the text in the output and paste here.
NBU processes are covered in Appendix A of NetBackup Troubleshooting Guide
You will find a process flow diagram and explanation of what each process does.
In short: nbemm is the process controlling the NBU relational database.
vmd is the Volume Manager service that is necessary to configure devices.
03-17-2015 03:21 AM
Check if Symantec Private Branch Exchance Service is running.
Start if this is not running.
If it is running, open cmd (Run as Administrator if UAC is not disabled), cd to <install-path>\veritas\netbackup\bin.
Run:
bpps
copy the text in the output and paste here.
NBU processes are covered in Appendix A of NetBackup Troubleshooting Guide
You will find a process flow diagram and explanation of what each process does.
In short: nbemm is the process controlling the NBU relational database.
vmd is the Volume Manager service that is necessary to configure devices.