NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 52

Media Manager status code 52
HOWTO104433 | 2014-11-20
How To | CMS-XML

Device management status code 52

Device management status code 52
HOWTO104677 | 2014-11-20
How To | CMS-XML

Device configuration status code 52

Device configuration status code 52
HOWTO104589 | 2014-11-20
How To | CMS-XML

NetBackup status code: 52

NetBackup status code : 52
HOWTO103982 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: A NetBackup client restore fails with Status Code 52/2850: Message: timed out waiting for media manager to mount volume.

9/29/2008 9:40:30 AM - connected; connect time: 00:00:08 9/29/2008 9:45:40 AM - restored image nbu_1222442554 - (timed out waiting for media manager to mount volume( 52 )); restore time 00:05:20 9/29/2008 9:45:41 AM - Warning bprd(pid=3388) Restore must be resumed prior to first image expiration on 10/10/2008 11:22:34 AM
TECH63671 | 2014-11-06
Technical Solutions | CMS-XML

Backing up a VMWare machine fails with STATUS 52

Backing up a VMWare machine fails with STATUS 52
TECH146491 | 2011-08-15
Technical Solutions | CMS-XML

Backups fail with status 52 if Media Mount Timeout is set and Client de-duplication is used

Backups fail with status 52 if Media Mount Timeout is set and Client de-duplication is used
TECH141553 | 2010-10-23
Technical Solutions | CMS-XML

BUG REPORT: After installation of an engineering binary for nbpem (v5), policies which have schedules with 52 week retention and multistreaming enabled fail with status code 196 reported.

policies with scheds set to frequency of 52 weeks and multi-stream are failing with status 196 with nbpem v5
TECH65544 | 2009-01-26
Technical Solutions | CMS-XML

Backup fails with status 24 after the network stops delivering data to the media server.

Friday October 9 05:14:38 GMT 2009 10.43.2.62.13724 198.235.125. 52 .42317 1 0 49344 0 ESTABLISHED
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

NDMP backups fail with Status 99 and Error "connect error = -1004 (Timeout waiting for connected message from NDMP server)"

11/20/2014 6:10:45 PM - begin writing 11/20/2014 6:10:52 PM - Info bptm(pid=1116) EXITING with status 99 ---------- 11/20/2014 6:10: 52 PM - end writing; write time: 00:00:07
TECH226675 | 2015-02-19
Technical Solutions | CMS-XML

Oracle RMAN backup failing with status 48

01:16: 52 .033 [14266] 4 sendRequest: sending BACKUP request to bprd 01:16:52.034 [14266] 4 sendRequest: request = oracle dba medusa medusa medusa /usr/openv/netbackup/logs/user_ops/dbext/logs/14266.0.1292393811 mypolicy mysched 7 mySID 0 4 0 C C C C C 0 0 0 0 5
TECH146599 | 2015-02-03
Technical Solutions | CMS-XML

GENERAL ERROR: Unable to start ltid and vmd on the master server; an error message is returned, stating "another ltid daemon is already running".

-rw------- 1 root other 0 May 9 17:55 lmfcd.lock -rw-rw-rw- 1 root root 3603 Aug 22 17: 52 ltitables -rw------- 1 root bin 340 Jun 20 2000 README
TECH15895 | 2015-02-06
Technical Solutions | CMS-XML

Backups or restores fail with SQL GetConfiguration errors: 0x80770003 and 0x80770004.

Batch = C:\Program Files\VERITAS\NetBackup\dbext\MSSQL\rt-16.bch, Op# = 1. 15:38: 52 [2324,2364] 4 InitPipeInfo: INF - Using backup image image name . 15:38:52 [2324,2364] 4 Dbbackrec::Perform: INF - restore database database from virtual_device= vnbu0-2324-2364 with blocksize = 512, maxtransfersize = 65536, buffercount = 1, recovery
TECH11378 | 2015-02-02
Technical Solutions | CMS-XML

Attempts to configure client host properties from the master server fail with connection errors.

bptestbpcd -verbose -debug -client xxx 12:35: 52 .682 [3416.4680] 2 vnet_async_connect: vnet_vnetd.c.4163: getsockopt so_error returned: 10060 0x0000274c SOLUTION
TECH56944 | 2015-01-21
Technical Solutions | CMS-XML

Multiple filesystems and filesystem types show a "skipping" message under the detailed status of a job

8/19/2014 2:13: 52 PM - Info bpbrm(pid=96242) from client nbclient1: TRV - [/sys] is on file system type sysfs. Skipping
TECH144332 | 2014-12-29
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?