Forum Discussion

manol4ik's avatar
manol4ik
Level 5
13 years ago
Solved

error: pipe close failed

Dear Friends 

 

I have an issue, maybe someone can help me, i have Symantec Netbackup 7.1 Windows X64, and everytime i want to access to the Backup. Archive and Restore i got the same message, so i cant restore any of my data

ERROR: PIPE CLOSE FAILED

 

thanks for the help

 

 

Regards,

 

 

Alejandro

7.1.x and Earlier
Agents
Backup and Recovery
Best Practice
Compatibility
Configuring
Managing Backup Devices
Monitoring
NetBackup
Restore
  • I_like_3_14's avatar
    I_like_3_14
    13 years ago

    I'm a bit late to the game, but this may help someone who runs into this string (like I did).  I was getting this error, then realized that the restore type was wrong.  In the "Select for Restore" drop down box in the BAR, you have several options.  I forgot I was previously performing a VMWare restore, and that setting sticks until you change it.  Once I changed it back to "Restore from normal backup...", all was well. 

    Sometimes, it's the simple things that eat up your troubleshooting time.  ;)

15 Replies

Sort By
Show More
  • mph999's avatar
    mph999
    Level 6
    13 years ago

    We seem to b emissing the bpjava-susvc log ...

    We'll need that log that covers the same time period as the other logs, which means you may need to recollect all of them.

    martin

  • raji14's avatar
    raji14
    Level 3
    13 years ago

    I'm having the same issue here. Did you figure anything out on how to resolve this? Thanks

  • raji14's avatar
    raji14
    Level 3
    13 years ago

    This may sound silly, but my issue turned out to be that I didn't have the right server/clients specified in the the BAR settings. I just didn't think to even verify that because of the pipeline error. After looking that up, it threw me way off track.  Anyways, thanks

  • I_like_3_14's avatar
    I_like_3_14
    Level 3
    13 years ago

    I'm a bit late to the game, but this may help someone who runs into this string (like I did).  I was getting this error, then realized that the restore type was wrong.  In the "Select for Restore" drop down box in the BAR, you have several options.  I forgot I was previously performing a VMWare restore, and that setting sticks until you change it.  Once I changed it back to "Restore from normal backup...", all was well. 

    Sometimes, it's the simple things that eat up your troubleshooting time.  ;)