Netbackup Error 52
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 Backups fail with status 52 if Media Mount Timeout is set and Client De-Duplication is used Article:000009288 Publish: Article URL:http://www.veritas.com/docs/000009288 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 When enabling media mount timeout, backups using Client Deduplication to either a De-Duplication Pool (MSDP) or PureDisk Storage Pool (PDDO) Storage Unit fail with Status Code 52 after reaching media mount timeout. However, that issue does not occur if the De-Duplication is done on the media server.The client is not notifying bpbrm correctly to reset the timeout. Error Message 17:35:56.089 [1092] <2> bpbrm Exit: client backup EXIT STATUS 52: timed out waiting for media manager to mount volume Cause Bpbrm Log Extracts: Backup job using Client De-Dup starts with Media Mount Timeout set to 5 minutes. 17:30:28.694 [1092] <2> logparams: -backup -S media.abc.com -c client.abc.com -ct 13 -ru root -cl ctu_c_drive_2 -sched Full -bt 1279643428 -dt 0 -st 0 -b client.abc.com_1279643428 -mediasvr media.abc.com -jobid 2827 -jobgrpid 2827 -masterversion 700000 -maxfrag 512 -reqid -1279640712 -mt 0 -to 300 -stunit pd66stu -rl 1 -rp 1209600 -p PureDiskVolume -mst 6 -flags 2 -storagesvr rdg2950-27.uklab.veritas.com -sts_type PureDisk -use_ofb -use_otm -WOFB_enabled 1 -WOFB_fim 1 -nbu -jm -secure 1 -kl 28 -rg other -fso -ckpt_time 900 -connect_options 16974338 2) Requests the client does the de-duplication 17:30:28.695 [109
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 : File backup-Recurring error 52 VOX : Backup and Recovery : NetBackup : File backup-Recurring error 52 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page File backup-Recurring https://www.veritas.com/support/en_US/article.000009288 error 52 neetu Level 3 10-23-2013 06:59 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi all, I had this stuation several times where the incremental file backup fails with error 52 however many times I try to restart or resume it. However, the same client backs up successfully if full backup is triggered. Does anyone have an explanation for this? https://vox.veritas.com/t5/NetBackup/File-backup-Recurring-error-52/td-p/582849 Labels: Backing Up Backup and Recovery Error messages NetBackup Windows Server (2003-2008) 0 Kudos Reply 7 Replies Is it the same media id used Marianne Moderator Partner Trusted Advisor Accredited Certified 10-23-2013 07:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Is it the same media id used each time for this incremental backup? What is media mount timeout set to? Have you checked bptm log on the media server for the reason why tape cannot be mounted? Handy NetBackup Links 0 Kudos Reply No. The error recurred on neetu Level 3 10-23-2013 07:17 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content No. The error recurred on different media. Also, same media was used for the full backup later. No issues found then! As of now I do not have the bptm logs handy. 0 Kudos Reply Please provide the logs as sri_vani Level 6 Partner 10-23-2013 07:19 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Please provide the logs as Marianne suggested and verify the Media Id 1)what kind of backup it is? Request you to verify similar kind of issue? http://www.syma
tape but http://systemmanager.ru/nbadmin.en/nbu_52.htm was not specified as a cleaning tape. Another possible cause: the last available drive has a mount request for a non-backup (such as a restore). Then a backup that requires the same drive is initiated before the mount completes. This netbackup error error is due to the drive not being reported as busy until the mount completes. Recommended Action: Do the following, as appropriate: Verify that the requested volume is available and an appropriate drive is ready and in the UP state. netbackup error 52 If this error occurs during a read operation (restore, duplicate, verify), the drives could be busy. Increase the timeout for the media mount that the NetBackup global attribute specifies, to allow more time to mount and position the media. Verify that the tape is not a cleaning tape that is configured as a regular volume. When an Automated Cartridge System controls the robot, verify that the ACSLS system is up. If it is an initial installation, a procedure is available. See "Resolving common configuration problems" in the Troubleshooting Guide. On Windows, check the Event Viewer Application log for the error messages that indicate why the tape mount did not complete. On UNIX and Linux, check the system log.