Forum Discussion

tbailey1's avatar
tbailey1
Level 2
7 months ago
Solved

"failed, status 6" error after increasing datastore (LUN) capacity

We seem to consistently have this issue where when we increase the capacity of a LUN on the SAN storage side and expand the datastore in vCenter with this capacity increase, NetBackup will throw back a "failed, status 6" error when attempting to use the san transport mode.  There are no backup issues until this capacity increase takes place.  Example of the log we see:

- begin writing
- Error bpbrm (pid=39403) from client vm_name: ERR - Error opening the snapshot disks using given transport mode: san Status 23
- Critical bpbrm (pid=39403) from client vm_name: FTL - cleanup() failed, status 6
- Error bptm (pid=39602) media manager terminated by parent process

All zoning is correct so there's nothing on the fabric side preventing connectivity.  For vCenter and ESXi we are running a later version of 7 update 3.  On the SAN side we are running IBM FlashSystem storage.  Our NetBackup version is a flavor of 10.3.0.  Does anyone have thoughts as to why this happens and how we can prevent it from happening in the future?

  • Hey

    Did you rescan the LUNs after resize on the backup host? I think in vxms logs you would see some logs indicating that the LUN expected size is and actually it is the other - thus NBU gets confused.

    If you did run rescan - try with rebooting the media server/backup host which sees the expanded LUNs. This should solve your issues.

  • Hey

    Did you rescan the LUNs after resize on the backup host? I think in vxms logs you would see some logs indicating that the LUN expected size is and actually it is the other - thus NBU gets confused.

    If you did run rescan - try with rebooting the media server/backup host which sees the expanded LUNs. This should solve your issues.