Are the NetBackup services on each cluster node part of the same cluster resource group as the file server service and the DSSU volume? If not, it's possible that the file server services and the DSSU volume for node #1 came online on node #2, but the NetBackup services for node #1 are still running on node #1. Since NetBackup doesn't see the path to the DSSU, it marks the DSSU as being down. If this is the case, you will need to stop the NetBackup services on node #1, manually fail over the file server resource group so that it is running on node #1 (along with the DSSU volume), and then restart the NetBackup services on node #1.
Ideally, the NetBackup services would be running in the same cluster resource group as the file server service and the DSSU volume to ensure that they fail over and fail back as a single group.
Have a look at the
NetBackup 6.5 High Availability Administrator's Guide for information on running a clustered media server in this fashion.