Error ndmpagent (pid=8176) st07caddvnx: The backup path is configured: \bkup. This is not an absolute root dir path.

[danhatt]

I was just handed a new EMC VNX to backup. There are two other EMC devices being backed by NBU without any problems.

Environment:

NBU 7.5 running on Windows 2008 R2 with disks on EMC Clariion and an HP StorageWorks MSL 4048 Tape library for data storage.

There is a VNXe and a VNX 5300 that are working just fine with the already in place policies.

The new EMC is another VNX 5300, st07caddvnx. I do not have any administrative access to it

The st07caddvnx errors out with "This is not an absolute root dir path." I cannot locate any information on determining what the absolute root dir path is.

Am I missing something? Or is the absolute root dir path just a red herring?

Thanks.

DAN

08/28/2013 11:27:45 - Info nbjm (pid=4076) starting backup job (jobid=18680) for client st07caddvnx, policy sv07caddvnx_test, schedule Differential-Inc
08/28/2013 11:27:45 - Info nbjm (pid=4076) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=18680, request id:{F39858EE-6904-4B45-AB22-76CF49A462E9})
08/28/2013 11:27:45 - requesting resource Disk_Group_1
08/28/2013 11:27:45 - requesting resource sv07nbumaster.ct.dot.ca.gov.NBU_CLIENT.MAXJOBS.st07caddvnx
08/28/2013 11:27:45 - requesting resource sv07nbumaster.ct.dot.ca.gov.NBU_POLICY.MAXJOBS.sv07caddvnx_test
08/28/2013 11:27:45 - granted resource  sv07nbumaster.ct.dot.ca.gov.NBU_CLIENT.MAXJOBS.st07caddvnx
08/28/2013 11:27:45 - granted resource  sv07nbumaster.ct.dot.ca.gov.NBU_POLICY.MAXJOBS.sv07caddvnx_test
08/28/2013 11:27:45 - granted resource  MediaID=@aaaaS;Path=w:\;MediaServer=sv07nbumaster
08/28/2013 11:27:45 - granted resource  SU_W
08/28/2013 11:27:45 - estimated 0 kbytes needed
08/28/2013 11:27:45 - Info nbjm (pid=4076) started backup (backupid=st07caddvnx_1377714465) job for client st07caddvnx, policy sv07caddvnx_test, schedule Differential-Inc on storage unit SU_W
08/28/2013 11:27:45 - Info bpbrm (pid=8576) st07caddvnx is the host to backup data from
08/28/2013 11:27:45 - Info bpbrm (pid=8576) reading file list from client
08/28/2013 11:27:45 - Info bpbrm (pid=8576) starting ndmpagent on client
08/28/2013 11:27:45 - Info ndmpagent (pid=8176) Backup started
08/28/2013 11:27:45 - Info bptm (pid=5612) start
08/28/2013 11:27:45 - Info bptm (pid=5612) using 30 data buffers
08/28/2013 11:27:45 - Info bptm (pid=5612) using 262144 data buffer size
08/28/2013 11:27:45 - started process bpbrm (pid=8576)
08/28/2013 11:27:45 - connecting
08/28/2013 11:27:45 - connected; connect time: 0:00:00
08/28/2013 11:27:46 - Info bptm (pid=5612) start backup
08/28/2013 11:27:47 - Error ndmpagent (pid=8176) st07caddvnx: The backup path is configured: \bkup. This is not an absolute root dir path.
08/28/2013 11:27:47 - Error ndmpagent (pid=8176) NDMP backup failed, path = \bkup
08/28/2013 11:27:47 - Error bptm (pid=5612) none of the NDMP backups for client st07caddvnx completed successfully
08/28/2013 11:27:47 - begin writing
08/28/2013 11:27:49 - Info bptm (pid=5612) EXITING with status 99 <----------
08/28/2013 11:27:49 - Info ndmpagent (pid=0) done. status: 99: NDMP backup failure
08/28/2013 11:27:49 - end writing; write time: 0:00:02
NDMP backup failure  (99)

[Marianne]

Please show us the policy config?

bppllist <policy-name> -U

[Will_Restore · Accepted solution]

Ask your SAN administrator.  The path would be something like

  /root_vdm_1/bkup 

[danhatt]

Hi Marianne:

Here is the information you requested.

Thanks.

DAN

Policy Name:       sv07caddvnx_test

  Policy Type:         NDMP
  Active:              yes
  Effective date:      08/28/2013 12:30:51
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  NDMP          NDMP          st07caddvnx

  Include:  \bkup

  Schedule:              Full
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

  Schedule:              Differential-Inc
    Type:                Differential Incremental Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    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)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

[danhatt]

wr:

Correct, /root_vdm_1/bkup is exactly right.

Thank you very much.

DAN

[danhatt]

Spoke too soon. There was a major difference this time. Before the job failed this time, it actually mounted a tape and started to back up befpore the "This is not an absolute root dir path." I think Will Restore has put me on the right path. May need a little more work. But this is progress.

Thanks.

DAN

[Marianne]

Include:  \bkup

This is not a valid NDMP path.

Please speak to NAS admin.

[quebek]

Exaclty as Marainne stated.

Ask the storage admins to logon to control station of this VNX and run such command:

server_df server_2

server_df server_3

If your datamovers are configured in primary/standby you need to only ask to run first command. Ask them to proive you outputs, here are examples from mine:

[nasadmin@xxx ~]$ server_df server_2
server_2 :
Filesystem          kbytes         used        avail capacity Mounted on
fs-XXXarchive 7576304104   3053932928   4522371176   40%    /root_vdm_3/fs-XXXarchive
fs-XXX054     1868394032   1651384264    217009768   88%    /root_vdm_5/fs-XXX054
fs-051_comm     1035033496   1023112648     11920848   99%    /root_vdm_2/fs-051_comm
fs-XXX052a    1662447344      1073712   1661373632    0%    /root_vdm_3/fs-XXX052a
fs-XXX051     3277217984   3144984936    132233048   96%    /root_vdm_2/fs-XXX051
root_fs_vdm_vdm_XXX053
                    114592         8520       106072    7%    /root_vdm_4/.etc
fs-XXX052     3327636984   2454218880    873418104   74%    /root_vdm_3/fs-XXX052
root_fs_vdm_vdm_XXX052
                    114592        10576       104016    9%    /root_vdm_3/.etc
root_fs_vdm_vdm_XXX051
                    114592         9368       105224    8%    /root_vdm_2/.etc
fs-XXX050     3477510056   3332383424    145126632   96%    /root_vdm_1/fs-XXX050
root_fs_vdm_vdm_XXX050
                    114592         9624       104968    8%    /root_vdm_1/.etc
root_fs_vdm_vdm_XXX054
                    114592         9104       105488    8%    /root_vdm_5/.etc
root_fs_common       15368         5280        10088   34%    /.etc_common
root_fs_2           258128        16872       241256    7%    /


 

Also I think you have too less information in the backup selection list. In my env I have such directives in backup selection list:

SET HIST = Y
SET UPDATE = Y
SET OPTIONS = NT
SET SNAPSURE = Y
SET DIRECT = Y
/root_vdm_1/fs-xxxx050

[Mark_Solutions]

Take a look at your other policies that are working correctly to see what is in those and the replicate that other than the path itself

[danhatt]

This was the first policy in a new VNX. The path that wr suggested was exactly right. However, when I tried it yesterday, it failed.

I contacted the NAS admin. He said the root was /root_vdm_1/. When I tried it today, it worked.

My training has consisted of "Good luck", what I have discoverd in  the various manuals and (most helpful) this forum.

quebek:

Could you give a brief idea of what the following are for?

SET HIST = Y
SET UPDATE = Y
SET OPTIONS = NT
SET SNAPSURE = Y
SET DIRECT = Y

Thanks.

DAN

[Will_Restore]

Dan, SET variables are descibed in this EMC VNX guide, starting page 58

http://corpusweb130.emc.com/upd_prod_VNX/UPDFinalPDF/jp/NDMP_Backups.pdf