Forum Discussion

Alexis_Jeldrez's avatar
Alexis_Jeldrez
Level 6
4 years ago

Trying to reconnect to a MSDP after Master reinstall

We cannot reconnect to a MSDP whose NetBackup software was reinstalled.

We have a NetBackup Master Server which is out of support because it's still using Windows 2008 R2, it had NetBackup 8.0 and has an underscore in its hostname. Also, it has a MSDP which is not recommended. We decided that the first thing to fix was to make an upgrade from 8.0 to 8.2.

The upgrade process ended succesfully but TomCat refused to work ("java.lang.IllegalArgumentException: The character [_] is never valid in a domain name."), so the Web Management Console Server presented problems and the platform was unusable.

So we just reinstalled NetBackup 8.0 and recovered the catalog, but the MSDP refused connections: "Wed 03/24/2021 7:44:21.19 ERROR: Your PDDE storage data format is ahead of software supported version, not allowed to reuse".

Therefore, we made a clean install of NetBackup 8.2 after renaming the Windows hostname (without an underscore) and adding the old hostname as an alias in the hosts table. This gave us new errors, where when trying to recreate the MSDP we could create a Disk Storage Server but not a Disk Pool. Specifically, we got a "No Volumes Found" while "nbdevconfig -previewdv" showed nothing. Also, spad.exe and spoold.exe both show the following errors:

Error: 25017: DaemonLockSimpleTestW: pipe already exists
Error: 25001: spoold: a conflicting instance is currently active.
Error: 26016: Veritas PureDisk Content Router: Bootstrap failure.

 

Thank you for reading so far and I would appreciate any ideas you could share with us.

8.2
Windows Server 2008 R2
  • davidmoline's avatar
    davidmoline
    Level 6
    4 years ago

    Hi Alexis_Jeldrez 

    My suggestion is to log a support case and see if they can assist. The OS being out of support is a secondary issue in this case. 

    That said - the server name is embedded within the MSDP configuration in a number of configuration files. All live under <Path to MSDP>\etc\puredisk\ - such as spa.cfg, agent.cfg & contentrouter.cfg - which may be why you are unable to reattach the MSDP as you have changed the server name. 

    So I have no idea if this will work and it is not something I have tried, and definitedly not something I would recommend to try on a production system with important data. You could update the various places with the new server name and see if that allows your MSDP to come up. 

    Again, if this is important data, my first recommendation is to log a case and get support to assist.

    David