Netbackup Error Code 71
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research "none of the files mentioned in the file list exist or may not be accessible(71)" Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch
Trv - Object Not Found For File System Backup
Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 71: A Status 71 error "none of error 71 rocket league the files in the file list exist" occurs. Article:000030696 Publish: Article URL:http://www.veritas.com/docs/000030696 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 71: A Status 71 error "none of the files in the file list exist" occurs. Error Message none of the files in the file list exist Solution Overview: A Status 71 error "none of the files in the file list exist" occurs. However, it is known for certain that the backup selections specified in the policy exist on the clients in question.Troubleshooting: This can happen if the correct path is seemingly specified, but there is a "trailing space" (an extra space on the end of an entry). In the Activity Monitor of the NetBackup Administration Console, click "Jobs". Identify a Job ID that has failed with a Status 71 and note the policy associated with it. Then proceed with the following: 1. Expand Policies in the left pane 2. Double click the name of the policy that has failed with Status 71 3. In the Change Policy window, click the Files or Backup Selections tab (the tab name varies depending upon version) 4. Highlight an entry in the file list and click Rename. Then highlight the entire entry with the mouse. See if there is a space at the end of the listing. Figure 1 shows a file list entry that has a trailing space. Figure 1.
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist) Article:000027625 Publish: Article URL:http://www.veritas.com/docs/000027625 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please https://www.veritas.com/support/en_US/article.000030696 sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist) Error Message Status 71 backup of client server_name exited with status 71 (none of the files in the file list exist) Solution This issue may https://www.veritas.com/support/en_US/article.TECH33594 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 completedTo 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 STAT
and the file cannot be backed up due to an I/O error. Recommended Action: Do the following, as appropriate: Verify that the correct file list is specified http://systemmanager.ru/nbadmin.en/nbu_71.htm for this client. On Windows clients, verify that the account used to start the NetBackup Client service has read access to the files. If you back up a network drive or a UNC (universal naming convention) https://exchangeengine.wordpress.com/2010/11/22/status-code-71-in-veritas-netbackup-server-for-exchange-mail-box-backup/ path, do the following: use the Services application in the Windows Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives. To netbackup error back up network drives or UNC paths: change the NetBackup Client service startup to log in as a user that has permission to access network drives. Check the All Log Entries report for clues. To set up debug logging, do one of the following: On UNIX, Linux, and Windows clients, create a debug log directory for bpbkar. On other PC clients except Macintosh, create a debug log directory for bpcd (the bpcd netbackup error code log is created automatically on Macintosh). Increase the amount of information that appears in the logs. See "How to set logging levels on UNIX clients" in the Troubleshooting Guide. See "How to set logging levels on PC clients" in the Troubleshooting Guide. Retry the operation and check the resulting debug logs. On Novell systems, do one of the following: For the nontarget version of NetBackup for NetWare, the backup policy type must be "NetWare," and the files list should include a forward slash (/) only. There should be nothing else in the files list. To check the policy type and files list, start Backup Policy Management and right-click the name of a policy. Click the Attributes tab to check the policy type; click the Files tab to check the contents of the files list. For the target version, the backup policy type must be "Standard," and the policy files list must be formatted as follows: /target_name where a forward slash precedes the variable target_name. To check the policy type and files list, start Backup Policy Management and right-click the name of a policy. Click the Attributes tab to check the policy type; click the Files tab to check the contents of the files list. For the target version, the following NetWare mess
to say in Veritas terminology) through Symantec Veritas Netbackup. Error code was showing 71 in Activity monitor. Error was below 11/22/2010 3:23:46 PM - mounting Tp0066 11/22/2010 3:23:48 PM - Warning bpbrm(pid=2140) from client Exchange-cluster: WRN - unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\ 11/22/2010 3:23:48 PM - Warning bpbrm(pid=2140) from client Exchange-cluster: WRN - unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\ 11/22/2010 3:23:48 PM - Error bptm(pid=4636) socket operation failed - 10054 (at child.c.1294) 11/22/2010 3:23:48 PM - Warning bpbrm(pid=2140) from client Exchange-cluster: WRN - unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\ 11/22/2010 3:23:48 PM - Error bptm(pid=4636) unable to perform read from client socket, connection may have been broken 11/22/2010 3:23:48 PM - Error bpbrm(pid=2140) could not send server status message 11/22/2010 3:23:50 PM - end writing none of the files in the file list exist(71) SOLUTION/WORKAROUND: 1. Checked and found that we cannot browse and enumerate the mailboxes from the Exchnage policy \ Selections 2. Went to Exchange active node and configured the exchange backup account. ( Services-> Netbackup client->logon tab->give exchange admin account and password there). Then restart the netbackup service 3) Updated the changes using bprdreq command C:\program files\veritas\netbackup\bin\admincmd >bprdreq -readconfig 4) ran the Mailbox backup manually. And it works fine. Thanks Akther Share this:TwitterEmailFacebookMorePrintRedditLike this:Like Loading... Related Leave a Comment Leave a Comment » No comments yet. RSS feed for comments on this post. TrackBack URI Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commentin