Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist)

Article:TECH33594  |  Created: 2004-01-02  |  Updated: 2010-09-07  |  Article URL http://www.symantec.com/docs/TECH33594
Article Type
Technical Solution


Environment

Subject

Issue



Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist)


Error



Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist)


Solution



This issue may arise if the CDROM drive path is added to the file list and multi-streaming is enabled, regardless if there is an exclusion set for the specific client and drive path (see note). If this is the case, a message similar to the one below can be found in the bpbkar log on the client:

Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist)

If multi-streaming is not enabled, the backup will continue and finish with the appropriate status code. If this is the case, a message similar to the one below can be found in the bpbkar log on the client:

5:45:24.125 PM: [3096.1988] <2> tar_base::V_vTarMsgW: TRV - Skipping path on network file system: G:
5:45:24.125 PM: [3096.1988] <2> tar_base::V_vTarMsgW: INF -  EXIT STATUS 0: the requested operation was successfully completed

To determine how VERITAS NetBackup (tm) will see the drive paths on the local computer, run bpmount at a command prompt on the client. This will show all the local drives, including CDROMs and floppy drives. Note that floppy drives will be labeled as CDROM (Figure 1).

4:16:41.591 PM: [3924.2452] <2> tar_base::V_vTarMsgW: TRV - Skipping path on network file system: G:
4:16:41.622 PM: [3924.2452] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 71: none of the files in the file list exist

Figure 1
 

Next, run bppllist -allpolices -L -U on the master server to confirm which drives were added to the file list.

If the CDROM drive path matches a drive path in the file list, there are two options to resolve this issue (if the CDROM is required to be backed up, see steps below).  

Option 1
1. Right-click on the policy, and select Change
2. Select the Backup Selections tab, select the CD-ROM drive path, then select Delete and OK (Figure 2)

Option 2
1. Right-click on the policy, and select Change
2. Select the Backup Selections tab, select all drive paths (and the system state if applicable), then select Delete and OK (Figure 2)
3. Select to add the directive All Local Drives

Figure 2
 

In order to back up a CDROM, the following steps will have to be followed:

1. Right-click on the policy and select Change
2. Select the Attributes tab
3. Select the Backup Network Drives check box and click OK (Figure 3)

Figure 3
 

Note: If multiple streams are enabled on the backup, a job will be created for each drive path. Since a separate job is created for the CDROM drive path, the job will attempt to run and subsequently fail with a status 71. This is the intended function of NetBackup.

 


Legacy ID



269969


Article URL http://www.symantec.com/docs/TECH33594


Terms of use for this information are found in Legal Notices