What type of NDMP device is it? I have found, in the past, that the mount point that failed wasn't a real mount poing. In the case of EMC Celerra for example it must be a uxfs type file system. If I do a server_mount it shows many mount points but half of them are not uxfs and therefore I get the same error you get when attempting to back them up.

Hope this helps.

I am not mounting the volume in my master server. It is a SAN backup from the filer to the tape drive directly. Also the other volumes in the policy are being backed up without any errors

What kind of NDMP device? EMC is not the same as NetApp, etc.

It's not simply a spelling mistake in the Backup Selection for the Policy is it? A trailing 'space' maybe? An extra or missing '.' (dot).

Obviously your config is correct in that all the others work, so it appears to be either the Backup Selection in the Policy or the NetApp side of things.

It is NetworkAppliance with Data ONTAP Release 7.2.3

Try this:

List Attributes

set_ndmp_attr -list

Verify access

set_ndmp_attr -verify <NDMP server>

Check deamons are up

vmps

Authenticate Access

set_ndmp_attr -auth filer root

check if everything is setup properly

all the test commands working properly. to remind you, i can backup all the volume except this volume

Are these full backups or incrementals you get the 99's on? We have gotten 99's when running an incremental and no data has changed on that volume.

The 99 error for NDMP backups tend to be a catch-all type error code, but the detail in Activity Monitor will usually lead on a good direction to look, like path does not exists, etc.  You also need to look at the logs on the NetApp to see what type of things are occurring.  I have had these on Celerra and the Celerra will say that the path does not exists on the Celerra.  Too bad NDMP backups don't ive you a 71 :)

Has this path ever backed up successfully? Create ndmp logs on the master if the NetApp logs do not show anything.

Thanks for the update razad. Nice to know there was a logical reason for this!

We actually backup our snapshots directly via our 'backup selection', as opposed to allowing the backup to create one that it then backs up from. Something else to watch out for if we ever change our methodology.