Thanks, will try that
I can see there is a stream file for each
policy which ran with the file structure inside – makes sense
From:
Marianne Van Den Berg [mailto:mvdberg AT stortech.co DOT za]
Sent: 26 May 2010 15:44
To: Shekel Tal;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu]
Incorrect File List being Built
Delete the STREAMS
files under images\client-name
Warning: This will probably cause incremental to run as fulls until
a new full has run.
Kind regards
M.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Shekel Tal
Sent: 26 May 2010 04:37 PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Incorrect
File List being Built
Hi Guys
I have quite an interesting one here
NetBackup 6.5.5 – windows 2003 Master
NetBackup 6.5.5 Windows 2003 Media Server behind a firewall
backing itself up
All comms going through vnetd
I am using a file list such as:
E:\Folder1\*
E:\Folder2\*
I am doing this so that I can pull the data of the disk
using multiple streams so that I can keep a decent data flow to an LTO4 drive.
Else certain directories containing small file just slow the
entire backup volume down
The first backup run used the wildcard and detected each
subdirectory and ran a separate stream.
When new sub directories are added they are not detected by
the wildcard discovery – the directories which existed at the time the
first back ran are the only ones which jobs are created for.
If I create a new policy and specify E:\Folder1\* -
NetBackup will then detect all the subdirectories and kick off a job for each
one.
Its almost as if the file list is being cached somewhere and
not being rediscovered for each scheduled backup.
Any thoughts or similar experiences?
I am sure I have actually seen this will earlier versions of
NetBackup – going back to NB5
Cheers