Forum Discussion

Aurelien59's avatar
Aurelien59
Level 4
6 years ago

Error while configuring MSDP on Media Server

Hi all, According to this installation guide https://www.veritas.com/support/en_US/doc/25074086-127355784-0/v24332600-127355784, I am stuck at step 8, with this error (see attached jpg) : "Configur...
8.1.2
Windows Server 2016
  • Aurelien59's avatar
    Aurelien59
    6 years ago

    I finally managed to configure the disk-pool by doing this:
    Removed stall entry Media Server in NBU Database: nbemmcmd -deletehost -machinename <xxx> -machinetype media
    Removed STU Basic associated with Media Server

    Then I modified some bad entries in the registry, then I restarted the master, then the media, and finally I was able to finish the configuration, and finally I started a backup.

    Thanks for your help. :)

Aurelien59's avatar
Aurelien59
Level 4

My storage volume is M: (M:\NBU\) for MSDP and this is what I typed at step 5.

Would I have made a mistake by skipping a step before doing this setup?

Marianne's avatar
Marianne
Level 6
6 years ago

Have you checked if any files and folders have been created under M:\NBU during NBU installation?

See if any log folders and files have been created in M:\NBU\logs. 

 

    • Aurelien59's avatar
      Aurelien59
      Level 4
      6 years ago

      I finally managed to configure the disk-pool by doing this:
      Removed stall entry Media Server in NBU Database: nbemmcmd -deletehost -machinename <xxx> -machinetype media
      Removed STU Basic associated with Media Server

      Then I modified some bad entries in the registry, then I restarted the master, then the media, and finally I was able to finish the configuration, and finally I started a backup.

      Thanks for your help. :)

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        Okay - you never mentioned that you had Basic Disk. 

        There were also all sorts of references in the logs to parameters that already existed in  contentrouter.cfg. As if there was a previous MSDP config (or attempt).