Symantec Backup Exec - Job Selection Failures & Notifications

Hi, I have a job defined in Backup Exec where the job fails to backup a specified folder but yet the job reports success.  For the particular folder the job does report 'This backup set may not contain any data'.  Can anyone please help on the following:
1) How I diagnose this issue?  Are there any logs that may be of use?
2) Why are these types of situations not reported as errors?  I would like to know when a top level selection fails to get backed up or for that matter when a sub-folder fails to get backed up.

Thanks in advance,
Terry
wahlsterAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

hunartCommented:
I have the following questions for you then:

1) What are you backing up?  Flat files, database files or Exchange database files?
2) Do you add Verify after each backup?
3) What are the error code from the logs?

0
wahlsterAuthor Commented:
Hi hunart,
Thanks for the reply.

I am backing up flat files.  The only thing is that the directory is also a DFS (Replicated Directory File Share) but I don't think that is the problem...I think.

I do Verify.

Here is the log results below.  I'm not really seeing an error code.
################################################################################
AOFO: Started for resource: "\\MSP-SQL\D:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 10.49.128.59:3866 <--> 10.49.128.56:10000
Network data connection is established between    10.49.128.59:3878 <--> 10.49.128.56:3249

Set Information - \\MSP-SQL\D:
Backup Set Information
Family Name: "Media created 3/9/2011 2:00:04 PM"
Backup of "\\MSP-SQL\D:"
Backup set #183 on storage media #9
Backup set description: "MS Daily Backup"
Backup Method: Full - Back Up Files - Reset Archive Bit

Backup started on 3/30/2011 at 8:51:19 PM.
Backup completed on 3/30/2011 at 8:51:29 PM.

Backup Set Summary
Backed up 0 files in 10 directories.
Processed 5,768 bytes in  10 seconds.
Throughput rate: 0.033 MB/min
Compression Type: Hardware

This backup set may not contain any data.
################################################################################
0
Lee_YCPCommented:
Are you doing a full/copy backup or a incremental/differential?  The latter will be zero if the file has not changed.  That seems obvious, but easily overlooked.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

wahlsterAuthor Commented:
Hi Lee_YCP,  Backup method is set Full/reset archive bit.  You did have me second guessing though.
Thanks,
Terry
0
Lee_YCPCommented:
Well, I have witnessed the condition you mention when I do differential backups in BExec 2010 SP1.  What version BExec are you using?

To further try and eliminate other possible "obvious" culprits:
It looks like it is able to "list" the directories, does the account you are using to backup in BExec have "Read/Write" permissions on the files or is the BExec account in the Admin group to access the D$?

Are the flat files still in the process of being created by SQL when the BExec backup job runs?  Check the date/time on the flat files and ensure completing before the job runs.

Are there files in the DFS (if it is on D$)?  Are they backing up?

Ultimately, do not execute the job, but start the wizard to restore the files on D$ and see what information is in the BExec repository that you could restore.  If files exist that you could possibly restore for D$, how many days ago where they backed up?
0
Lee_YCPCommented:
Also, If using 2010, manually change your VSS to Symantec or one of the others and see if that corrects your issue.
0
wahlsterAuthor Commented:
Thanks again for your replies.  I ended up contacting Symantec and the issue was in fact that the folder that I was trying to backup is a DFSR (Repliated Distributed File Share).  If this is the case then you need to select the desired folder under the 'Shadow Copy Compents'.  Please see screen shot.  The appears to have solved the backup proble.
Thanks,
Terry

 Shadow Copy Components Selection
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
wahlsterAuthor Commented:
Contacted Symantec Support for the solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.