cancel
Showing results for 
Search instead for 
Did you mean: 

ndmp_data_start_recover failed, status = 9 (NDMP_ILLEGAL_ARGS_ERR)

kaemuaset
Level 3

Hi

I Trying to restore a file to System storage Nseries ibm N6070 and i have the next error code :

 

ndmp_data_start_recover failed, status = 9 (NDMP_ILLEGAL_ARGS_ERR)

Please i need a solution.

Thanks a lot

 

 

26 REPLIES 26

kaemuaset
Level 3

This is the log file

19-mar-2014 12:29:08 - begin Restore
19-mar-2014 12:29:10 - number of images required: 1
19-mar-2014 12:29:10 - media needed: J00491
19-mar-2014 12:29:10 - media needed: J00480
19-mar-2014 12:29:15 - restoring from image NAS500MAJA01_1357984090
19-mar-2014 12:29:16 - Info bpbrm (pid=15707) NAS500MAJA01 is the host to restore to
19-mar-2014 12:29:16 - Info bpbrm (pid=15707) telling media manager to start restore on client
19-mar-2014 12:29:16 - Info bpbrm (pid=15707) spawning a brm child process
19-mar-2014 12:29:16 - Info bpbrm (pid=15707) child pid: 15721
19-mar-2014 12:29:17 - Info bpbrm (pid=15721) start tar on client
19-mar-2014 12:29:17 - Info tar (pid=15733) Restore started.
19-mar-2014 12:29:18 - Info bptm (pid=15713) Waiting for mount of media id J00480 (copy 1) on server netbackup.
19-mar-2014 12:29:18 - started process bptm (pid=15713)
19-mar-2014 12:29:18 - mounting J00480
19-mar-2014 12:29:18 - requesting resource J00480
19-mar-2014 12:29:18 - granted resource  J00480
19-mar-2014 12:29:18 - granted resource  PTOPEN_NEW_NASMAJA01_09
19-mar-2014 12:29:19 - Info bptm (pid=15713) INF - Waiting for mount of media id J00480 on server netbackup for reading.
19-mar-2014 12:29:28 - mounted J00480; mount time: 0:00:10
19-mar-2014 12:29:28 - Info bptm (pid=15713) J00480
19-mar-2014 12:29:29 - Info bptm (pid=15713) INF - Waiting for positioning of media id J00480 on server netbackup for reading.
19-mar-2014 12:29:29 - positioning J00480 to file 113
19-mar-2014 12:29:33 - positioned J00480; position time: 0:00:04
19-mar-2014 12:29:33 - begin reading
19-mar-2014 12:29:38 - Error ndmpagent (pid=15733) ndmp_data_start_recover failed, status = 9 (NDMP_ILLEGAL_ARGS_ERR)
19-mar-2014 12:29:39 - Error ndmpagent (pid=15733) NDMP restore failed from path /vol/fs0009/RRHH_SDE
19-mar-2014 12:29:45 - Info bpbrm (pid=15707) got ERROR 5 from media manager
19-mar-2014 12:29:45 - Info bpbrm (pid=15707) terminating bpbrm child 15721 jobid=19452318
19-mar-2014 12:29:45 - restored from image NAS500MAJA01_1357984090; restore time: 0:00:30
19-mar-2014 12:29:46 - end Restore; elapsed time 0:00:38
Failed to get status code information (2826)
 

mnolan
Level 6
Employee Accredited Certified

Here is the technote with our logging instructions in the second half.

http://www.symantec.com/docs/TECH56492

In this instance, you may also want to create the ndmp log folder, not just ndmpagent.

What I think will really be key, is getting the ndmpd logging on your filer, and unforunately we do not have any instructions on how to do so.

The reason I say this is that NetBackup is receiving "NDMP_ILLEGAL_ARGS_ERR" from the filer.  The filer's log should show was argument we passed and maybe why it wasn't allowed on that system. Once this is know, there hopefully should be a way to resolve the issue.

 

A few questions I would normally ask would be, is the image being restored from the same or a similar filer?

Where is the restore going? Original path? New Path? Are either valid currently? (Just the volume section, ndmp v3 and above should create the rest of the location as needed.)

kaemuaset
Level 3

Hello mnolan

The restore is :

 from /vol/fs0009/RRHH_SDE/2011/FORMACIÓN/  to /vol/fs0009/RRHH_SDE/2011/FORMACIÓN_restore/

 

The protocol version ndmp is 4.

 

Thanks

kaemuaset
Level 3

We have storage unit with reduce fragment size to 2000 megabytes.

I would like to know the fragment size in the image. how can i know it ?

 

Thanks

mnolan
Level 6
Employee Accredited Certified

I would still suggest looking at the filer's log to determine what argument it noted as illegal.

Is /vol/fs0009 still a valid volume?

What OS and NB version is the media server performing the restore.

kaemuaset
Level 3

HI

/vol/fs0009 is a valid volum

The media is:

ues90028:/usr/openv/netbackup/db#uname -a
HP-UX ues90028 B.11.31 U ia64 2738915687 unlimited-user license

and netbackup is 7.1.0.4

This is the robot and the device. I have interest in NASMAJA01.

robot     99    -    TLD    -       -  -          -                         /dev/rchgr/autoch18
  drive    -   99 hcart2    1      UP  -          PTOPEN_NEW_NB_NDMP_01     /dev/rtape/tape156_BESTnb
  drive    -  100 hcart2    4      UP  -          PTOPEN_NEW_NB_NDMP_02     /dev/rtape/tape278_BESTnb
  drive    -  101 hcart2    2      UP  -          PTOPEN_NEW_NASMAJA01_01   nrst87h
  drive    -  102 hcart2    6      UP  -          PTOPEN_NEW_NASMAJA01_02   nrst88h
  drive    -  103 hcart2   10      UP  -          PTOPEN_NEW_NASMAJA01_03   nrst89h
  drive    -  104 hcart2   14      UP  -          PTOPEN_NEW_NASMAJA01_04   nrst90h
  drive    -  105 hcart2   18      UP  -          PTOPEN_NEW_NASMAJA01_05   nrst91h
  drive    -  106 hcart2   22      UP  -          PTOPEN_NEW_NASMAJA01_06   nrst92h
  drive    -  107 hcart2   26      UP  -          PTOPEN_NEW_NASMAJA01_07   nrst93h
  drive    -  108 hcart2   30      UP  -          PTOPEN_NEW_NASMAJA01_08   nrst94h
  drive    -  109 hcart2    3      UP  -          PTOPEN_NEW_NASMAJA01_09   nrst0h
  drive    -  110 hcart2    7      UP  -          PTOPEN_NEW_NASMAJA01_10   nrst20h
  drive    -  111 hcart2   11      UP  -          PTOPEN_NEW_NASMAJA01_11   nrst2h
  drive    -  112 hcart2   15      UP  -          PTOPEN_NEW_NASMAJA01_12   nrst16h
  drive    -  113 hcart2   19      UP  -          PTOPEN_NEW_NASMAJA01_13   nrst12h
  drive    -  114 hcart2   23      UP  -          PTOPEN_NEW_NASMAJA01_14   nrst18h
  drive    -  115 hcart2   27      UP  -          PTOPEN_NEW_NASMAJA01_15   nrst17h
  drive    -  116 hcart2   31      UP  -          PTOPEN_NEW_NASMAJA01_16   nrst5h
  drive    -  117 hcart2    5      UP  -          PTOPEN_NEW_NASMAJA02_01   nrst0h
  drive    -  118 hcart2    9      UP  -          PTOPEN_NEW_NASMAJA02_02   nrst1h
  drive    -  119 hcart2   13      UP  -          PTOPEN_NEW_NASMAJA02_03   nrst2h
  drive    -  120 hcart2   17      UP  -          PTOPEN_NEW_NASMAJA02_04   nrst6h
  drive    -  121 hcart2   21      UP  -          PTOPEN_NEW_NASMAJA02_05   nrst14h
  drive    -  122 hcart2   25      UP  -          PTOPEN_NEW_NASMAJA02_06   nrst3h
  drive    -  123 hcart2   29      UP  -          PTOPEN_NEW_NASMAJA02_07   nrst12h
  drive    -  124 hcart2   33      UP  -          PTOPEN_NEW_NASMAJA02_08   nrst4h
  drive    -  125 hcart2    8      UP  -          PTOPEN_NEW_NASMAJA02_09   nrst107h
  drive    -  126 hcart2   12      UP  -          PTOPEN_NEW_NASMAJA02_10   nrst109h
  drive    -  127 hcart2   16      UP  -          PTOPEN_NEW_NASMAJA02_11   nrst108h
  drive    -  128 hcart2   20      UP  -          PTOPEN_NEW_NASMAJA02_12   nrst110h
  drive    -  129 hcart2   24      UP  -          PTOPEN_NEW_NASMAJA02_13   nrst113h
  drive    -  130 hcart2   28      UP  -          PTOPEN_NEW_NASMAJA02_14   nrst111h
  drive    -  131 hcart2   32      UP  -          PTOPEN_NEW_NASMAJA02_15   nrst114h
  drive    -  132 hcart2   34      UP  -          PTOPEN_NEW_NASMAJA02_16   nrst112h
 

kaemuaset
Level 3

/vol/fs0009 is a  valid volume

NB-->7.1.0.4

media server --> hpUX 11.31

I  have made a backup and a restore and the operation was successfully completed but when i attempt to restore from /vol/fs0009/RRHH_SDE/2011/FORMACIÓN/ to /vol/fs0009/RRHH_SDE/2011/FORMACIÓN_restore the restore fails.

 

Trail successfully with another file.

Policy Name:       MIN_NAS500MAJA01_N_FS_TI_PRUEBA

 

  Policy Type:         NDMP

  Active:              yes

  Effective date:      01/20/2011 12:15:00

  Mult. Data Streams:  yes

  Client Encrypt:      no

  Checkpoint:          no

  Policy Priority:     80000

  Max Jobs/Policy:     1

  Disaster Recovery:   0

  Collect BMR info:    no

  Residence:           STU_NAS500MAJA01_PTOPEN_NEW_LTO3

  Volume Pool:         NDMP_IBM

  Server Group:        *ANY*

  Keyword:             NAS500MAJA01 IBM

  Data Classification:       -

  Residence is Storage Lifecycle Policy:    no

  Application Discovery:      no

  Discovery Lifetime:      0 seconds

 

  Granular Restore Info:  no

  Ignore Client Direct:  no

  HW/OS/Client:  NDMP          NDMP          NAS500MAJA01

 

  Include:  set snapsure=yes

            NEW_STREAM

            /vol/fs0009/RRHH_SDE/2011/DIRECCION ADJUNTA/RELACIONES LABORALES

 

  Schedule:          Full

    Type:            Full Backup

    Maximum MPX:     1

    Synthetic:       0

    PFI Recovery:    0

    Retention Level: 16 (1 day)

    Number Copies:   1

    Fail on Error:   0

    Residence:       (specific storage unit not required)

    Volume Pool:     (same as policy volume pool)

    Server Group:    (same as specified for policy)

    Calendar sched: Enabled

    Residence is Storage Lifecycle Policy:     0

    Daily Windows:

 

******BACKUP LOG .

25-mar-2014 16:01:03 - Info nbjm (pid=290) starting backup job (jobid=19565501) for client NAS500MAJA01, policy MIN_NAS500MAJA01_N_FS_TI_PRUEBA, schedule Full

25-mar-2014 16:01:04 - estimated 133639 kbytes needed

25-mar-2014 16:01:04 - Info nbjm (pid=290) started backup job for client NAS500MAJA01, policy MIN_NAS500MAJA01_N_FS_TI_PRUEBA, schedule Full on storage unit STU_NAS500MAJA01_PTOPEN_NEW_LTO3

25-mar-2014 16:01:05 - started process bpbrm (pid=2269)

25-mar-2014 16:01:06 - Info bpbrm (pid=2269) NAS500MAJA01 is the host to backup data from

25-mar-2014 16:01:06 - Info bpbrm (pid=2269) reading file list from client

25-mar-2014 16:01:06 - Info bpbrm (pid=2269) starting ndmpagent on client

25-mar-2014 16:01:06 - connecting

25-mar-2014 16:01:06 - connected; connect time: 0:00:00

25-mar-2014 16:01:07 - Info ndmpagent (pid=2286) Backup started

25-mar-2014 16:01:07 - Info bpbrm (pid=2269) bptm pid: 2293

25-mar-2014 16:01:08 - Info bptm (pid=2293) start

25-mar-2014 16:01:08 - Info bptm (pid=2293) using 64 data buffers

25-mar-2014 16:01:08 - Info bptm (pid=2293) using 262144 data buffer size

25-mar-2014 16:01:08 - Info bptm (pid=2293) start backup

25-mar-2014 16:01:08 - Info bptm (pid=2293) Waiting for mount of media id J00051 (copy 1) on server netbackup.

25-mar-2014 16:01:08 - mounting J00051

25-mar-2014 16:01:18 - Info bptm (pid=2293) media id J00051 mounted on drive index 113, drivepath nrst12h, drivename PTOPEN_NEW_NASMAJA01_13, copy 1

25-mar-2014 16:01:18 - mounted J00051; mount time: 0:00:10

25-mar-2014 16:01:19 - positioning J00051 to file 5

25-mar-2014 16:01:19 - positioned J00051; position time: 0:00:00

25-mar-2014 16:01:19 - begin writing

25-mar-2014 16:02:03 - Info bptm (pid=2293) EXITING with status 0 <----------

25-mar-2014 16:02:03 - Info bpbrm (pid=2269) validating image for client NAS500MAJA01

25-mar-2014 16:02:03 - Info ndmpagent (pid=2286) done. status: 0: the requested operation was successfully completed

25-mar-2014 16:02:03 - end writing; write time: 0:00:44 the requested operation was successfully completed  (0)

 

 

******RESTORE LOG

 

Restore started 03/25/2014 16:03:34

 

16:03:38 (19565523.xxx) Restore job id 19565523 will require 1 image.

16:03:38 (19565523.xxx) Media id J00051 is needed for the restore.

 

16:03:43 (19565523.001) Restoring from copy 1 of image created Tue Mar 25 16:01:04 2014

16:03:46 (19565523.001) INF - If Media id J00051 is not in a robotic library administrative interaction may be required to satisfy this mount request.

16:03:47 (19565523.001) INF - Waiting for mount of media id J00051 on server netbackup for reading.

16:03:57 (19565523.001) INF - Waiting for positioning of media id J00051 on server netbackup for reading.

16:03:57 (19565523.001) INF - Beginning restore from server netbackup to client NAS500MAJA01.

16:04:00 (19565523.001) INF - Restoring NDMP files from /vol/fs0009/RRHH_SDE/2011/DIRECCION ADJUNTA/RELACIONES LABORALES/ to [See line below]

16:04:00 (19565523.001) INF - Restoring NDMP files from [See line above] to /vol/fs0009/RRHH_SDE/2011/DIRECCION ADJUNTA/RELACIONES LABORALES_RESTORE/

16:04:01 (19565523.001) DAR disabled by host parameters

16:04:02 (19565523.001) Attempting normal restore.

16:04:15 (19565523.001) NDMP restore successful from path /vol/fs0009/RRHH_SDE/2011/DIRECCION ADJUNTA/RELACIONES LABORALES

16:04:15 (19565523.001) /vol/fs0009/RRHH_SDE/2011/DIRECCION ADJUNTA/RELACIONES LABORALES/

16:04:16 (19565523.001) Status of restore from copy 1 of image created Tue Mar 25 16:01:04 2014 = the requested operation was successfully completed

 

16:04:17 (19565523.xxx) INF - Status = the requested operation was successfully completed.

 

frank_butler1
Level 3

Try restoring it to a different directory instead of a different name.  Make sure the directory exists first.  See if you get the same error

 

kaemuaset
Level 3

I have tryied to restore to a different directory and i get the same error.

kaemuaset
Level 3

Hello ,

I am using a stu and inside settings  i have  the next parameter -->reduce fragment size to ---> and i have the valor 2000 megabytes.

I would like to know  if it´s possible to see that parameter in the image .

Thanks a lot

mnolan
Level 6
Employee Accredited Certified

I myself do not know of a way to see the fragment size.

 

However, I am still more concerned about what the illegal argument is.

Have you setup any logging from

http://www.symantec.com/business/support/index?page=content&id=TECH56492 ?

If you create a folder named ndmp as well as ndmpagent, ndmp will show the exact communication from NB to the filer and you may see what parameters were passed that were not allowed.

Perhaps the backup was done before a change to a data buffer parameter that has now been changed on both the media server and filer? The restore would attempt to set the mover window size to this old value and could no longer be in the valid range of the filer?

 

kaemuaset
Level 3

Hi

I have created jet the folder ndmp but when the restore finish this folder is empty.

In the ndmpagent folder i can´t see any parameter from filer to media.

Where can i see it ?

 

In the command vxlogcfg -a -p 51216 -o 134.. and vxlogcfg -a -p 51216 -o 151 ...

what type of services or daemons  are 134 and 151 ?

 

Thanks

 

 

mnolan
Level 6
Employee Accredited Certified

134 is ndmpagent and 151 is ndmp

http://www.symantec.com/docs/HOWTO72854

Be sure the logging folders are created in the log directory, if you are on a unix system, it will be /usr/openv/logs for these unified logs.

Also be sure the logging dirs are setup on the media server performing the restore.

kaemuaset
Level 3

The folders was create jet  in /usr/openv/logs

In the ndmpagent folder i can´t see any parameter from filer to media.

Where can i see it ?

 

Thanks

 

 

mnolan
Level 6
Employee Accredited Certified

If you've just created the ndmp folder, you'll have to re-run the attempt to log the failure.

 

You'll be looking through the log to see when the filer gives back the NDMP_ILLEGAL_ARGS_ERR and then scroll up to see what we sent to it.

 

NDMP protocol logging designates communication logging as such. (Not exact, but close)

----> SENT TO

<---- Received From

 

kaemuaset
Level 3

Hi

i have created the ndmpagent folder  and  i  have to re-run the restore

i can see the next in the fragment of the file ndmpagent attached.

I want to restore now from /vol/fs0009/RRHH_SDE/2011/FORMACIÓN/ to the original side  /vol/fs0009/RRHH_SDE/2011/FORMACIÓN/ and i can see that :

 

original_path   = 2011/FORMACIM-CM-^FN/

destination_dir = /vol/fs0009/RRHH_SDE/2011/FORMACIM-CM-^FN/

 

Any idea to fix the problem ?

 

 

mnolan
Level 6
Employee Accredited Certified

Could you provide the output of the verify command from the technote I listed?

Specicially the version of NDMP the filer lists it supports.

Thanks.


The unified log seems to not be displaying the foreign characters correctly, but don't dismay, generally at the communication level it is okay.

 

The real issue seems to be that the filer is reporting back

Destination path must end with original path.

 

Thus the illegal arguments must be the paths given for restore. The question now is, why?

Does /vol/fs0009 still exist on this filer?

 

kaemuaset
Level 3

/vol/fs0009 exit

i would like to know what  destination path i have to set to restore ok ?

kaemuaset
Level 3

Attach the ndmpagent unified log .