NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 5020

NetBackup status code : 5020
HOWTO91650 | 2013-10-02
How To | CMS-XML

NetBackup status code: 5020

NetBackup status code : 5020
HOWTO72975 | 2012-11-19
How To | CMS-XML

BUG REPORT: Incremental NDMP backups of EMC Celerra to dedupe storage units fail with status 84

Problem only happens with incremental NDMP backups of EMC Celerra to dedupe storage units, for example to PureDisk, MSDP, NetBackup 5020 Appliance, DataDomain. Backups fail with status 84, bptm log on the media server showing that its not finding a valid tar
TECH177405 | 2013-10-25
Technical Solutions | CMS-XML

BUG REPORT: Oracle backups fail intermittently with ora-27028 error and Veritas NetBackup (tm) Status Code 150 (termination requested by administrator) even though the backup is not terminated by the administrator.

00:38:52.717 [484.5376] 2 bpbrm signal_media_manager: Sending SIGHUP to media manager 4740 00:38:52.717 [484.5376] 2 bpbrm kill_bpbrm_child: killing bpbrm child 5020 . 00:38:52.717 [484.5376] 2 bpbrm signal_bpbrm_child: sending Terminate to bpbrm child 5020
TECH45851 | 2013-10-23
Technical Solutions | CMS-XML

Backup Windows exchange pop error:1542

11/13/2012 15:35:09 - Info bpfis(pid=0) Snapshot will not be deleted 11/13/2012 15:35:13 - Info bpfis(pid= 5020 ) Backup started 11/13/2012 15:35:13 - Critical bpbrm(pid=2684) from client win-mbox01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.win-mbox01_1352792034.1.0
TECH200009 | 2013-09-04
Technical Solutions | CMS-XML

Restores started by Master Server are successful, but attempts to restore through a specific machine (not a Master or Media Server) fail with status 46, 59 and 25

03/04/2009 11:17:17 - connecting 03/04/2009 11:17:19 - Warning bptm(pid=4224) failure logging message to client ueipa0164 in log /C/Arquivos de programas/Veritas/NetBackup/logs/user_ops/UI22244A/logs/nbwin003: server not allowed access (46) 03/04/2009 11:17:20 - Error bpbrm(pid= 5020 ) bpcd on ueipa0164 exited with status 59: access to the client was not allowed
TECH69399 | 2011-08-16
Technical Solutions | CMS-XML

GENERAL ERROR: Corba exception on getDiskVolumeInfo during inventory of a NetBackup deduplication disk pool. Dedup backup/optimized duplications fail status 83/84.

Issue occurred shortly after upgrading the NetBackup PureDisk Appliance 5000/ 5020 systems from 1.2 to 1.3.0.1. The aformentioned error indicates the master cannot connect to the nbrmms service on the remote media servers.
TECH162602 | 2011-06-17
Technical Solutions | CMS-XML

Displaying NetBackup 5020 appliance Fibre Channel port information

**** Ports **** Bus ID Port WWN Dev Num Status Mode Speed Remote Ports 06:00.0 21:00:00:24:FF:xx:xx:xx 3 Online Target (NBU) 8 gbit/s 06:00.1 21:00:00:24:FF:xx:xx:xx 4 Online Initiator 8 gbit
HOWTO89144 | 2013-10-01
How To | CMS-XML

Displaying NetBackup 5020 appliance Fibre Channel port information

**** Ports **** Bus ID Port WWN Dev Num Status Mode Speed Remote Ports 06:00.0 21:00:00:24:FF:xx:xx:xx 3 Online Target (NBU) 8 gbit/s 06:00.1 21:00:00:24:FF:xx:xx:xx 4 Online Initiator 8 gbit
HOWTO70650 | 2012-02-07
How To | CMS-XML

Duplications fail with media open error(83) | Symantec Connect

Duplications fail with media open error(83) - NetBackup 7.1.0.3 on master, all media servers, and most clients - NetBackup Disk Appliance 5020 , set at production site and set at DR site, all running v1.4.1.1, and 6.6.3.49048
Connect Forums | HTML

Exchange GRT restore from a 5020 NBU appliance | Symantec Connect

Exchange GRT restore from a 5020 NBU appliance ERROR : Database System Error.
Connect Forums | HTML

Status Code Chart

5019 5020 5021
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Exit Status: 48 (client hostname could not be found) | Symantec Connect

Exit Status: 48 (client hostname could not be found) I have an environment consist of cluster master server windows 2008 and 5 media servers and 2 5020 appliances.I installed agent on the linux redhat client and and i added all server list to bp.conf and etc/hosts in the client and i added the client name in the master server host file.when i'm trying to ping from the client every thing working fine,but i couldnot do this from the master to client.then when i configured the policy the jobs failed with status
Connect Forums | HTML

7.1 Late Breaking News

http://www.symantec.com/docs/tech158909 (ET2372545) NBU7.1 MSDP optimized duplication to 5020 NetBackup PureDisk Appliance fails w/ status 84, error 2060017 system call failed http://www.symantec.com/docs/TECH162248
TECH153422 | 2012-03-28
Technical Solutions | CMS-XML

Disk Pool down on 5020 appliance

The disk pool went down for a newly configured 5020 appliance. Also, customer unable to login via PureDisk GUI. Otherwise, all services are up and responsive on appliance.
TECH212095 | 2013-10-31
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?