NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 2064

NetBackup status code : 2064
HOWTO104893 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: Event ID 2064 is reported by the NetBackup Volume Manager in the Windows Application event log stating that a media has expired, when it hasn't.

Event Category:None Event ID: 2064 Date:5/13/2005
TECH38986 | 2013-10-23
Technical Solutions | CMS-XML

Issue during the duplication with the Media Server Deduplication storage unit . It is giving the status 83.

15/10/2010 13:38:10 - Critical bpdm(pid=1704) image open failed: error 2060018: file not found 15/10/2010 13:38:15 - Error bpduplicate(pid= 2064 ) host dedup-media-server backup id client-server_1286913865 read failed, media open error (83). In the bpdm log:
TECH142484 | 2011-08-15
Technical Solutions | CMS-XML

Status Code Chart

2063 2064 2065
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

job history indicates that no media is available See NetBackup status code : 2064 job type is invalid
HOWTO103773 | 2014-11-20
How To | CMS-XML

Robotic cannot access media | Symantec Connect

7/20/2012 8:50:14 AM - mounting 000006 7/20/2012 9:06:36 AM - Error bptm(pid= 2064 ) error requesting media, TpErrno = Robot operation failed 7/20/2012 9:06:36 AM - Warning bptm(pid=2064) media id 000006 load operation reported an error
Connect Forums | HTML

Problem with Media and Device Management in 6.5.6 | Symantec Connect

nbproxy 6632 0.000% 0.250 11M 10/06/10 10:06:33.280 nbproxy 2064 0.000% 0.390 11M 10/06/10 10:10:48.725 bpps 7024 1.539% 0.234 2.4M 10/06/10 10:11:47.785
Connect Forums | HTML

failed to backup sql server | Symantec Connect

failed to backup sql server 13:29:50.359 [3572. 2064 ] <4> KillAllThreads: INF - Killing group #0
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?