NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device management status code 70

Device management status code 70
HOWTO104691 | 2014-11-20
How To | CMS-XML

Device configuration status code 70

Explanation: An error occurs while opening an NDMP connection to a NAS filer. Examine debug logs for more information on the error.
HOWTO104606 | 2014-11-20
How To | CMS-XML

NetBackup status code: 70

Change the wildcards in the file list to specify fewer files. Click here to view technical notes and other information in the Symantec Knowledge Base about this status code .
HOWTO103998 | 2014-11-20
How To | CMS-XML

Media Manager status code 70

If vmd is already running, examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide
HOWTO104450 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: Data appears to be missing from within the NetBackup Administration console. The message "Cannot connect to vmd (70)" may also occur when listing devices or media.

GENERAL ERROR : Data appears to be missing from within the NetBackup Administration console. The message "Cannot connect to vmd (70)" may also occur when listing devices or media.
TECH36294 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Media Manager error 70, cannot connect to vmd

GENERAL ERROR : Media Manager error 70 , cannot connect to vmd
TECH56208 | 2008-01-28
Technical Solutions | CMS-XML

GENERAL ERROR: When using Veritas NetBackup (tm) drives disappear from the Device Monitor. Attempts to manually reconfigure the drive(s) result in a "cannot connect on vmd (70)" error.

GENERAL ERROR : When using Veritas NetBackup (tm) drives disappear from the Device Monitor. Attempts to manually reconfigure the drive(s) result in a "cannot connect on vmd (70)" error.
TECH48625 | 2007-01-31
Technical Solutions | CMS-XML

STATUS CODE 70: "Cannot connect on vmd" errors occur when configuring devices for a Media Server, even though vmd (the Volume Manager daemon/service) is running on the Media Server and connectivity to the Media Server is known to be good.

Overview Cannot connect on vmd errors (Figure 1) occur when configuring devices for a Media Server, even though vmd (the Volume Manager daemon/service) is running on the Media Server and connectivity to the Media Server is known to be good.
TECH48411 | 2007-01-07
Technical Solutions | CMS-XML

How to troubleshoot NDMP Backups failures when status code 99 (or other NDMP backup failure) is reported. Includes logging instructions.

4. Enable ndmpd debug logging on the NAS device: For Network Appliance NAS, type the following to enable ndmpd debug logging: ndmpd debug 70 NOTE:
TECH56492 | 2014-10-01
Technical Solutions | CMS-XML

How to enable debug logging on a NetApp NDMP device when NDMP backup fails with Status Code 99 - DUMP: could not create "backup" snapshot : No space left on device.

ndmpd debug screen ndmpd debug 70 2. Recreate the issue by running a manual backup job.
TECH68849 | 2014-01-20
Technical Solutions | CMS-XML

Drives marked as down due to Move Medium Error

01:00:11.036 [36886] 2 roblib: 00080 0x00c03f22 14000000 00100000 00000000 (21510) 01:00:11.036 [36886] 2 roblib: CDB: 0xa5 00 00 00 10 0b 01 04 00 00 00 00 (36611) 01:00:14 sb[18]=[ 70 , 00, 05, 00, 00, 00, 00, 0a, 00, 00, 00, 00, 3b, 0e, 00,cf, 00, 04
TECH225696 | 2014-10-23
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

03:30:31.891 [Debug] 51216 137 PID:25000 TID:3 File ID:117 [No context] 3 [parseData] not enough data to parse: dataAvail = (37)64 6f 5f 79 70 63 61 6c 6c 3a 20 63 6c 6e 74 5f 63 61 6c 6c 3a 20 52 50 43 3a 20 54 69 6d 65 64 20 6f 75 74 a ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Incremental backup using client direct fail with status 14

13:48:14.163: [1556.5604] 16 dtcp_write: TCP - failure: attempted to send 70 bytes
TECH185860 | 2013-11-12
Technical Solutions | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail
TECH144245 | 2013-11-15
Technical Solutions | CMS-XML

GENERAL ERROR: The Volume Manager service (vmd) will not stay running on a Windows master or media server.

Could not connect to vmd on host ( 70 ) unable to obtain bound socket
TECH19068 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?