Unfortunately (to my knowledge),
wildcards are not supported with NDMP backups. You’ll have to explicitly
supply the paths. What we do is:
1)
Have a policy where
you’ve explicitly listed paths, ie:
a.
/vol/vol1/first
b.
/vol/vol1/second
2)
Have a second policy
checking to see if new paths have been added. For us, that means:
a.
we’ve mounted via
NFS the root of the volume, (ie: vol1) on the backup master server,
b.
and it’s backed up
using a “Standard” backup policy for that mountpoint (cross mount points
required).
c.
You exclude each in
individual paths you are backing up in #1,
d.
and if the #2 backup
policy ever grows larger than a set amount (32kB for example), we get an email
saying something along the lines “a new vol1 path has been added” so,
e.
We have new paths to
add to policy #1
Elegant eh? (read sarcastically
of course)
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Baumann,
Kevin
Sent: April 6, 2010 12:47 PM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] NDMP backups
All,
I am trying to run NDMP backups with
certain paths and I am getting error 99 in the GUI, and the error
ndmp_data_start_backup failed, status = 9 (NDMP_ILLEGAL_ARGS_ERR).
The policy is setup as follows:
Backup Selections:
NEW_STREAM
/vol/vol2/data/[A-M]*
NEW_STREAM
/vol/vol2/data/[a-m]*
If I setup the policy to just backup
/vol/vol2/data it works.
This is on Netbackup 6.5.3 and is
connecting to a Netapp via IP (can’t connect it via fibre). And the OS of
the master/media servers are SuSE linux.
Thanks.
-Kevin