[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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal Sent: 26 May 2010 04:37 PM To: veritas-bu@mailman.eng.auburn.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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
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:mvdb...@stortech.co.za] Sent: 26 May 2010 15:44 To: Shekel Tal; veritas-bu@mailman.eng.auburn.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-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Shekel Tal Sent: 26 May 2010 04:37 PM To: veritas-bu@mailman.eng.auburn.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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
On Wed, May 26, 2010 at 9:37 AM, Shekel Tal tal.she...@uk.fujitsu.comwrote: 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. What I think you're running into is the frequency of the pre-discovery process. man bpgetconfig and look at the -prep settings. -prep hours The preprocessing interval. This interval is the minimum time in hours between client queries to discover new paths when NetBackup uses auto- discover-streaming mode. For additional informa- tion, see Setting the Preprocess Interval for Auto Discovery in the File-List Directives for Multiple Data Streams intheNetBackup Administrator's Guide. The default Preprocess Interval value is 4 hours. If the preprocessing interval changes, change it back to the default by specifying -prep -1. The preprocessing interval can be set to prepro- cess immediately by specifying 0 as the preprocess interval for auto discovery on the bpconfig com- mand line. The maximum Preprocessing Interval is 48 hours. This has existed for many releases - I found a reference to it in the NBU 5 Windows guide. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org Linkedin http://www.linkedin.com/in/ewilts ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Incorrect File List being Built
Try removing the pempersist file. Tech note http://support.veritas.com/docs/295532 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Wednesday, May 26, 2010 11:01 AM To: Shekel Tal Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Incorrect File List being Built On Wed, May 26, 2010 at 9:37 AM, Shekel Tal tal.she...@uk.fujitsu.commailto:tal.she...@uk.fujitsu.com wrote: 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. What I think you're running into is the frequency of the pre-discovery process. man bpgetconfig and look at the -prep settings. -prep hours The preprocessing interval. This interval is the minimum time in hours between client queries to discover new paths when NetBackup uses auto- discover-streaming mode. For additional informa- tion, see Setting the Preprocess Interval for Auto Discovery in the File-List Directives for Multiple Data Streams intheNetBackup Administrator's Guide. The default Preprocess Interval value is 4 hours. If the preprocessing interval changes, change it back to the default by specifying -prep -1. The preprocessing interval can be set to prepro- cess immediately by specifying 0 as the preprocess interval for auto discovery on the bpconfig com- mand line. The maximum Preprocessing Interval is 48 hours. This has existed for many releases - I found a reference to it in the NBU 5 Windows guide. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.orgmailto:ewi...@ewilts.org [cid:image001.jpg@01CAFCE4.64F548A0]Linkedinhttp://www.linkedin.com/in/ewilts CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error; please notify Cranel Incorporated immediately by telephone at 614-431-8000 or 800-288-3475 and destroy all copies of this communication and any attachments. inline: image001.jpg___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
