Netbackup Error Code 83

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

Media Open Error 83 Netbackup

Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) media open error 83 netbackup 7 English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 83: When attempting

Plug-in Reports Error 2060001 One Or More Invalid Arguments

a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Article:000032095 Publish: Article URL:http://www.veritas.com/docs/000032095 Support / Article Sign In Remember error code 84 in netbackup 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 83: When attempting a backup which goes netbackup restore media open error 83 to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Error Message media open error Solution Overview: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error).  Troubleshooting: Please review the TechNote on Status Code 83 in the Related Documents section, and confirm that is not the issue.  Then, check the NetBackup Client Service, and see what Windows account is starting the service.  Log files:  N/A Resolution: If the backup is going to a network location on a NAS server, the NetBackup Client Service needs to start with an account that has access to the network.  The local system account does not have access to the network (see Figure 1). Figure 1   Changed the NetBackup Client Server to start with an account with network privileges, and stop and restart the service (see Figure 2).  Figure 2   Terms of use for this information are found in Legal Notices.

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

Image Open Failed: Error 2060001: One Or More Invalid Arguments

About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers image open failed: error 2060013: no more entries Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas

Sts_get_server_prop_byname Failed: Error 2060046 Plugin Error

PartnerNet STATUS CODE 83: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Article:000032095 https://www.veritas.com/support/en_US/article.000032095 Publish: Article URL:http://www.veritas.com/docs/000032095 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 Related Articles Article Languages Subscribe to this Article https://www.veritas.com/support/en_US/article.000032095 Manage your Subscriptions Problem STATUS CODE 83: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Error Message media open error Solution Overview: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error).  Troubleshooting: Please review the TechNote on Status Code 83 in the Related Documents section, and confirm that is not the issue.  Then, check the NetBackup Client Service, and see what Windows account is starting the service.  Log files:  N/A Resolution: If the backup is going to a network location on a NAS server, the NetBackup Client Service needs to start with an account that has access to the network.  The local system account does not have access to the network (see Figure 1). Figure 1   Changed the NetBackup Client Server to start with an account with network privileges, and stop and restart the service

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 https://www.veritas.com/support/en_US/article.000010656 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 CODE http://systemmanager.ru/nbadmin.en/nbu_83.htm 83: duplication jobs in NetBackup 7.x are failing with status 83 (media open error) reported. Article:000010656 Publish: Article URL:http://www.veritas.com/docs/000010656 Support / Article Sign In Remember me Forgot Password? Don't media open 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 Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Duplication jobs end with a Status 83, read side failure.   When media open error client names are specified using two different combinations of upper and lower case (for example, configurations containing both an all upper-case HOSTNAME as well as a lower-case hostname elsewhere), duplication jobs for that client may fail with status code 83 reported by bpdm.  An additional error code of 2060018 may appear in the log as well (see below).Note: This configuration can cause additional symptoms - see the related documents below.       Error Message The bpdm log may contain a message similar to the following: 04:02:58.652 [8732.5684] <32> bp_sts_open_image: sts_open_image failed: error 2060018 Cause An enhancement has been filed (Etrack 2024375) to change NetBackup to be case insenstive when dealing with the hostname part of images.  Solution Workaround:Be consistent with case sensitivity when using client hostnames in NetBackup configuraiton.If this workaround is unfeasible, please contact Symantec technical support, referencing this case and Etrack 2024362 (NetBackup 7.0) or 2149179 (NetBackup 7.0.1) to obtain an Emergency Engineering Binary (EEB) replacement library for this issue.ETA of Fix:Symantec acknowledges that the above mentioned issue (Etrack 2024375) is present in the cu

check the following: NetBackup Problems report Event Viewer Application log (Windows) System log (UNIX and Linux) Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device. On UNIX and Linux, the problem may be due one or more of the following: Two (or more) devices were configured that are the same physical device (for different densities perhaps). Verify that none of the /dev files that were used for these devices have the same major or minor numbers. Links exist in the file system that allow users access to the drives. The configuration for the drives was modified (in the administrator interface or vm.conf) and the Media Manager device daemon, ltid, was not restarted. Verify the configuration and then start ltid. On Windows, the problem may be that the Media and Device Management device configuration was modified but the NetBackup Device Manager service was not restarted. Verify the configuration and restart the NetBackup Device Manager service. On Windows, make sure the tapes are not write protected. For detailed troubleshooting information: Create a debug log directory for bpdm (if the device is disk) or bptm (if the device is tape). On UNIX and Linux, restartltid in the verbose mode by running the following: /usr/openv/volmgr/bin/ltid -v Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the vm.conf file if necessary. On Windows, enable verbose logging by adding VERBOSE on a line by itself in the install_path\Volmgr\vm.conf file. Then, stop and restart the NetBackup Device Manager service. Retry the operation and check the resulting debug log files. On Windows systems, look at the install_path\VERITAS\NetBackup\db\media\errors log for a drive that frequently produces errors. On UNIX and Linux systems, look at the /usr/openv/netbackup/db/media/errors log (which is also included in the /usr/openv/netbackup/bin/goodies/support/support script output) for a drive that frequently produces errors.