Netbackup Error 85
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Resotre issue - ERROR 85 from media manager VOX : Backup and Recovery : NetBackup : Resotre issue - ERROR 85 from media manager Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Resotre issue - ERROR 85 from media manager KS2 Level 5 10-11-2012 04:26 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content We are getting error code 85 for many media while performing restores(exchange and file resotres). Onchecking the media status it is showing "Frozen suspended". Tried to duplicate the images from the media but that also fails with same error. Are these bad medias? If yes is there anyway we can duplicate the images and then restores. we are facing this issues with many media from different different months. Any suggestions? Solved! Go to Solution. Labels: 7.5 Backing Up Backup and Recovery NetBackup Restore Troubleshooting 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Is this bptm log on the Marianne Moderator Partner Trusted Advisor Accredited Certified 10-16-2012 10:41 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Is this bptm log on the master or the media server? If bptm log folder exists on the media server at the time that the restore is attempted, it WILL most certainly log restore actions and errors. Symantec recommends that Vendo
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 Job fails with status 85 from the detail status of the job "read failed, media read error (85)" Article:000005262 Publish: Article URL:http://www.veritas.com/docs/000005262 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://vox.veritas.com/t5/NetBackup/Resotre-issue-ERROR-85-from-media-manager/td-p/517495 sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Job fails with status 85 from the detail status of the job "read failed, media read error (85)" Solution Environment: Open Storage Technologies (OST) direct copy to tape. This technology uses a NDMP configuration to duplicate the images from the OST device to https://www.veritas.com/support/en_US/article.000005262 tape. There are limited number of OST vendors that support this configuration please verify the support list to confirm the supportability of the configuration. Configuration: 3 Media server have been setup with credentials to have access to 2 OST Storage Servers. There are additional media servers in this NetBackup domain. NDMP credentials have been setup to utilize global NDMP credentials. Global NDMP Credentials Use global NDMP Select this option to enable all NetBackup media servers credentials for this under the master server to access this NDMP host using a NDMP host pre-defined global NDMP login. To create this login, click Host Properties > Master Server > Properties > NDMP in the NDMP Global Credentials dialog box. Issue: If global attributes are setup there can be a potential issue that the wrong media server will be selected to perform the read of the images for the duplications. If the NetBackup environment has multiple media servers in the environment there is the potential that a media server that has not been configured to use the OST will be selected to read the images for the duplications. If this occurs the duplications will not succeed. Solution: The NDMP credentials needed to be c
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn https://vox.veritas.com/t5/NetBackup/got-ERROR-85-when-try-Restore/td-p/652644 on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible http://systemmanager.ru/nbadmin.en/nbu_85.htm matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : got ERROR 85 when try Restore. VOX : Backup and Recovery : NetBackup : got ERROR 85 when try Restore. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to netbackup error the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution got ERROR 85 when try Restore. fernando_sant2 Level 3 02-27-2014 05:19 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, Below are the contents of detailed status restore job. Netbackup version is 7.5.0.5 Please help in sorting.. thank you. 26/02/2014 11:45:16 - Info netbackup error 85 bpbrm (pid=5238) brmogsdb01 is the host to restore to 26/02/2014 11:45:17 - Info bpbrm (pid=5238) telling media manager to start restore on client 26/02/2014 11:45:17 - Info bpbrm (pid=5238) spawning a brm child process 26/02/2014 11:45:17 - Info bpbrm (pid=5238) child pid: 5242 26/02/2014 11:45:17 - connecting 26/02/2014 11:45:18 - Info bpbrm (pid=5242) start tar on client 26/02/2014 11:45:18 - Info tar (pid=9080) Restore started. 26/02/2014 11:45:18 - connected; connect time: 0:00:00 26/02/2014 11:45:19 - Info bptm (pid=5240) Waiting for mount of media id 0013L5 (copy 1) on server brmogmed01. 26/02/2014 11:45:19 - started process bptm (pid=5240) 26/02/2014 11:45:19 - mounting 0013L5 26/02/2014 11:45:20 - Info bptm (pid=5240) INF - Waiting for mount of media id 0013L5 on server brmogmed01 for reading. 26/02/2014 11:46:23 - mounted 0013L5; mount time: 0:01:04 26/02/2014 11:46:23 - Info bptm (pid=5240) 0013L5 26/02/2014 11:46:24 - Info bptm (pid=5240) INF - Waiting for positioning of media id 0013L5 on server brmogmed01 for reading. 26/02/2014 11:46:24 - positioning 0013L5 to file 109 26/02/2014 11:47:26 - positioned 0013L5; position time: 0:01:02 26/02/2014 11:47:26 - begin reading 26/02/2014 11:47:27 - Error bptm (pid=5240) cannot read image from media id 0013L5, drive index 1, Device or resource busy 26/02/2014 11:47:28 - Error bptm (pid=5241) The following files/folders were not restored: 26/02/2014 1
following: NetBackup Problems report to determine the device or media that caused the error System and error logs for the system (UNIX and Linux) Event Viewer Application and System logs (Windows) Check for the following: A defective or a dirty drive. Clean it or have it repaired (see the tpclean command for cleaning). Incorrect drive configuration. Verify the Media and Device Management and system configuration for the drive. For example, on UNIX and Linux, the drive may be configured for fixed mode when it must be variable mode. More information is available. See the NetBackup Device Configuration Guide. Defective media. In this case, you may not be able to recover all the data on the media. Use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups. See "Troubleshooting frozen media" in the Troubleshooting Guide. The wrong media type. Verify that the media matches the drive type you use.