cancel
Showing results for 
Search instead for 
Did you mean: 

vmd failed to come up after initiating restart from Azure portal

sym_biosis
Level 4

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.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

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.
 

View solution in original post

1 REPLY 1

Marianne
Level 6
Partner    VIP    Accredited Certified

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.