Unsolved
This post is more than 5 years old
2 Posts
0
2176
September 13th, 2018 04:00
NDMP Exclude issue using Netbackup 8.1 and Isilon 8.1.0.4
Hi,
I have recently been tasked with looking after our backup environment, which is a Netbackup 8.1 using NDMP to backup Isilon via A100 backup accelerators.
What I would of assumed a trivial process is becoming a bit of a head scratcher. I need to create an NDMP policy to backup a directory which contains a number of large sized folders. I am trying to setup a policy that excludes particular folders from a stream but I am unable to get the folder excluded regardless of what syntax I try.
The policy (for testing purposes) is as follows:
SET EXCLUDE='Folder Space'
/ifs/Archive/Restore/test
Within the DIR "test" there is are two folders, one named "FolderSpace" and one named "Folder Space". I want the policy to backup "FolderSpace" but not "Folder Space" but whatever syntax I try I am unable to exclude the folder. I have tried:
SET EXCLUDE=Folder Space
SET EXCLUDE='Folder Space"
SET EXCLUDE=Folder\ Space
SET EXCLUDE='Folder\ Space'
Now I know for this test I could just point the backup at /ifs/Archive/Restore/test/FolderSpace to achieve what I want, but the actual work I need to do is made up of a lot of DIRs so the ability to exclude particular folders is definitely needed. I did raise a call with Veritas and they have advised me to speak to the Filer vendor on how NDMP is used for there products.
Please help! Thanks!
Peter_Sero
4 Operator
•
1.2K Posts
0
September 14th, 2018 09:00
SET EXCLUDE=Folder\ Space
is the correct syntax.
Maybe the directory name has more than one space character, or non-ASCII spaces:
$ ls -d1 Folder*
Folder Space
Folder Space
Folder Space
$ ls -d1 Folder* | od -c
0000000 F o l d e r S p a c e \n F o
0000020 l d e r S p a c e \n F o l d
0000040 e r ** S p a c e \n
0000052
First example has two spaces in the middle,
second example has a space at the end.
Third example has a 'non-breaking space' Unicode character in the middle.
It takes two bytes in UTF-8 encoding, where
the second byte is represented by ** in the output of od -c.
While we ar at it: One more thing, big caveat, related to NDMP and include/exclude settings on Isilon:
It is possible, but dangerous, to define multiple NDMP jobs for the same base directory (FILESYSTEM)
with different include-FILES or EXCLUDE patterns.
Be warned that this will lead to unexpected results, because OneFS NDMP only keeps
one single backup timestamp per NDMP FILESYSTEM base directory and NDMP level.
FILESYSTEM=/ifs/test
FILES=a b c
FILESYSTEM=/ifs/test
FILES=d e f
Say the a b c job runs at 1am and the d e f job at 2am, the timestamp (for the given NDMP level)
for /ifs/test will finally be set to 2am.
Next day when the a b c job is running with an incremental level (>=1),
it will backup only data changes that happened after 2am (23h ago),
and miss any changes from the hour between 1am (24h ago) and 2am.
fwiw
-- Peter