The following set of conditions, will cause NetVault service to stop on Linux:
- On the NVBU server the user creates a NetVault Virtual Client using the Exchange Server APM, without specifying a Virtual IP for the cluster
- A NetVault name is given on the 'Virtual client Name' field and its creation appears to be successful
- Once the VC (Virtual Client) is created, open Backup > Open the VC > right click the Exchange Server APM > Select 'Configure'
This will result in the NetVault service stopping after a minute or so with an hour glass on the Backup window.
The NetVault Network Manager process crashes while attempting to find the cluster referred to by the Virtual Client created, as no IP or network name was provided for it.
Since Network Manager is a Start of the Day process, its crash inevitably leads to the NetVault application to stop as well.
Bug 5114 has been created to correct this issue, further checks will be done at the GUI level to warn the user when the address or hostname are not provided.
When creating a NetVault Virtual Client it is primordial a Virtual IP or Virtual server name is provided so that the NetVault Network Manager process can find the targeted cluster.
Until checks are introduced in a future version of NetVault, perform the following to resolve this:
- In Client Management, delete the current yellow Virtual Client created (right click > remove)
- Right click each client that make up the cluster and select 'Remove Software', removing each time the 'Exchange Server APM'
- Determine the Virtual IP adresse of the cluster. If the virtual hostname resolves with the Virtual IP, it can also be used in the Virtual Client configuration.
- Finally, re-create the Virtual Client giving it a unique NetVault name and providing its Virtual IP address or hostname in the "Application IP Address" field.
This should allow you to access the APM configuration without incident.