Forum Discussion

Jason_Sauer_2's avatar
Jason_Sauer_2
Level 4
19 years ago

error 71 - Backing up SAN data

Error: none of the files in the file list exist(71)

First we create a snapshot, after the split, we mount the snapshot on the NetBackup server. Tried about 20 attempts with different settings. The weird part is that we had two successful backups, but as soon as one would work, it would fail the next time without any changes being made.

First we thought it was a permissions issue, but the service account has sufficient rights, we even tried using local system account. Tried checking "Backup Network Drives". Using Windows-NT for the Policy Type, but we did try Standard just for kicks. One other odity, Windows Explorer can see the mounted drives okay, but when browsing the system through NetBackup (in Backup Selections window), the SAN drives don't show up.

I'm sure it's something simple, just don't know what I'm missing.

Environment:
NetBackup 6.0 MP2
Windows 2003 SP1
7.1.x and Earlier
Backup and Recovery
NetBackup
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    Thank you for following up and posting the solution. We all gain by using this forum.
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    STATUS CODE 71: After upgrading to Veritas NetBackup (tm) 6.0, client backups fail intermittently with Status 71 "none of the files in the file list exist".
    http://support.veritas.com/docs/280876
  • zippy's avatar
    zippy
    Level 6
    19 years ago
    jason,

    The backup $PATH is set incorrectly within the backup schedule.

    JD
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    In-depth Troubleshooting Guide for Exit Status Code 71 in NetBackup (tm) Server / Enterprise Server
    http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/277438.pdf
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    When trying to back up mapped network drives on Windows, the backup fails with status 71: none of the files in the file list exist
    http://seer.support.veritas.com/docs/279997.htm
  • Jason_Sauer_2's avatar
    Jason_Sauer_2
    Level 4
    19 years ago
    Tried everything listed in the articles mentioned. Path list is correct, NetBackup is a new installation, not an upgrade. Made sure that there are no trailing spaces in the path list. Tried it both through the GUI and through the command line (manually specified file list). The only thing we didn't try was mapping network drives as a different user. Not sure how to do that when the drives are visible to windows as local disks.

    Also, the path is fairly simple, just the U drive. Changing the selection to C:\ works fine, so I know the path syntax is correct.
  • Raghava_Chary's avatar
    Raghava_Chary
    Level 4
    19 years ago
    Jason,

    As you have tried all the posibilities not much to suggest .. but still thinking from a diff angle you can check the following.

    1. Enable the logs and see what exactly is causing the error.

    2. Some times if the connectivity is poor between the client and master it may give 71 instead of 41 or 54, is it writing at least 100KB ? If not then check whether it is resolving the master name correctly by using "bpclntcmd" command.

    3. Is it a cluster box? If yes please check whether these packages are moving to a diff node while the backup was running...

    4. Finally create a test policy and try to back it up only specific folder / folders see if that is getting successful.

    5. Did you mention ALL_LOCAL_DRIVES in the backup selections list?


    Raghava.Message was edited by:
    Raghava
  • Jason_Sauer_2's avatar
    Jason_Sauer_2
    Level 4
    19 years ago
    Thank you all for your input, but I finally found the problem, nothing to do with NetBackup. The command I was using to mount the volumes (shadowimage command: pairdisplay -x mount U: HarddiskVolume3) didn't seem to fully mount the drive. Mountvol and Windows explorer both reported correct mounting, but Disk Management and NetBackup could not see the drives. So I changed the script to use Mountvol and mount the volumes to a drive letter on the C drive... problem solved.

    I know you were all sitting on the edge of your seats waiting to see the solution :)