Forum Discussion

sandeepk's avatar
sandeepk
Level 5
7 years ago

MSDP volume down issue (Wonder still they don’t identify, why this issue still occurs)

Dear Team,

This is very worst case i am facing on my customer side. from last 4 months but still i am not getting any work around and solution

customer having 7.7.3 NeT backup application install windows System

master media and MSDP configured on the same server.

MSDP Volume size is 30 TB data backup size is 20 TB

We have open so many case for the same but VERITAS Technical Team don’t have solution and workaround for this issue.

Wonder still they don’t identify, why this issue still occurs

  • You still have not provided any information as previously requested, therefore we cannot assist you further.

    You need to provide info for us to help, if not please close this request.

  • There is no reason to vent in this forum at your unhappiness, this is a support forum where we can assist you with relevant information being provided of the problem. 

    If you have an issue with the level of support, request an escalation!!!

    If you would like to provide the logs and error outputs of the problem we can assist you, there are a number of ex employees, expert users etc here who have numerous years and decades of experience to assist.

    Provide accurate details of your problem, status code errors of the job (20TB is a large single instance backup), logs from the following will assist us (spad logs; nbjm; bptm; bpstsinfo; bpbrm; pdde-config.log; nbemm; spoold; pd.conf file and any event logs (application and system) when the job fails and we will do our best to assist.

    Cheers,

    JM

    • J_MCCOLL's avatar
      J_MCCOLL
      Level 4

      Additionally I would also recommending that you upgrade to NBU 8.1 as there were a large number of updates around the MSPD area between your current version and the latest version which could solve your problem.

      • sandeepk's avatar
        sandeepk
        Level 5

        We coordinate with VERITAS team from the last one month but still they are not identify the issue. Not also given workaround.

         

        I am surprising advance team also not  putting  any comment and output on this issue