09-10-2014 09:11 AM
Hi Guys,
NDMP Log Message: DUMP: Dumping /vol/PROD_FILE1_DATA_02_CIFS to NDMP connection NDMP Log Message: DUMP: mapping (Pass I)[regular files] NDMP Log Message: DUMP: Reading file names from NDMP. NDMP Log Message: DUMP: Q_userhome/A*: No such file or directory NDMP Log Message: DUMP: DUMP IS ABORTED
09-11-2014 12:48 AM
The format of exclusions is specified by NetApp's NDMP implemenation and is not something designed by us. I have not looked at this for a while but last time I tested this (with an older Ontap version and older BE version) I found that you could not specify paths as the Exclusion standard did not allow the \ or / characters. If I remerber correctly the * wildcard was not functional either. EDIT it's possible such characters are not allowed in the include statement either.
What you could do was specify a string - for instance the word HOME and then any folder or file containing the word HOME in the name, wherever it was found in the file system would be excluded. To me this means you would have to be very very careful with exclusion strings in order to avoid something important not being backed up. It is possible that newer ONtap versions handle things slightly different from my original test experiences.
Unfortunately as all we are doing is passing the string as an NDMP exclude statement to the OnTap implementation of NDMP, the exact behaviour and format of the strings in the exclude statement is outside of Symantec's control and you may need to look at NetApp's own documentation to try to understand what is possible.
09-12-2014 05:00 AM
Hi Colin,
09-12-2014 05:24 AM
Sorry but due to limitations outside of Symantec's control because it is how the programming interface from the harwdare vendor works, how the NDMP option selections/exclusions/inclusions work is cumbersome. As such I am not aware of a setting which will help you. You may have to play around a bit.
What you could do is create a subfolder with a very unique name and move the stuff you don't want into that and then exlude that unique name. - however this might affect how applications that use the data are configured.