Forum Discussion

J_H_Is_gone's avatar
17 years ago

exclude list - include list.

trying to wrap my head around this and just getting lost.

 

serverA

 

policyB that backs up all local drives

 

policyC that backs up one directory.

 

if I do an exclude for "all policies" and exclude that one directory that policyC wants to back up.

 

and policyC states ONLY that directory...

 

will policyC backup the contents of the dir or not?

 

does it depend on how it state it?

 

if my exclude says E:\mydir

 

if policyC says E:\mydir\*

  • The directory in your exclude_list (for all policies) would mean that the directory in question would not get backed up in policyB or policyC.

     

    You could get around this by creating an include list for policyC or an exclude list for policyB only. e.g. exclude_list.policyB containing the directory you want to exclude.

     

    E:\mydir in the exclude would exclude the directory AND contents, so the fact that policyC states E:\mydir\* would have no effect.

     

    IMHO the exclude_list.policyB would be the way to go. (I think!)

  • The directory in your exclude_list (for all policies) would mean that the directory in question would not get backed up in policyB or policyC.

     

    You could get around this by creating an include list for policyC or an exclude list for policyB only. e.g. exclude_list.policyB containing the directory you want to exclude.

     

    E:\mydir in the exclude would exclude the directory AND contents, so the fact that policyC states E:\mydir\* would have no effect.

     

    IMHO the exclude_list.policyB would be the way to go. (I think!)

  • thanks for the reply.... just not enough coffee this morning... just could not get my head around it.

  • @J.Hinchcliffe wrote:
    .... just not enough coffee this morning...

    To quote a certain Hall of Famer "Ain't it the truth?" :smileyvery-happy:

     

  • Andy,

     

    There can be dire consequences when using both Exclude List and Include List.  Here is my story.

     

    In our situation, we had a policy which backed up all local drives.  In the exclude list, which stated "All Policies" -> "All Schedules", we excluded our E:\ drive (which has 5+ million files).  However, we created an "Include List" of the E:\ if running the Flashbackup policy.

     

    When trying to run the Flashbackup policy, we kept timing out.  After putting in a call to Symantec, the reason for the problem is that our "Exclude List" was for "All Policies".  The Flashbackup policy must create an exceptions list - consuming vast amounts of storage and time.  By creating the "Exclude List" pertaining the the All Local Drives policy, this took care of our problem.

     

     

  • the big policy ( all local drives) has a large exclude list ( well large to my enviroment) about 10 entries

    the small policy is backing up 1 directory with about 50 files in it.

    so in any of your opinoins would this cause a lot of overhead or is it the best way to go.

    an exclude list for All Policies - exclude this one little dir.

    an include list just for the small policy that has just that one little dir in it.

  • For what you are trying to do, there should be no issues.  In my case, it was trying to build an exclusion table with 5+ million entries.

  • Ron Cohn wrote:

    Andy,

     

    There can be dire consequences when using both Exclude List and Include List. Here is my story.

     

    In our situation, we had a policy which backed up all local drives. In the exclude list, which stated "All Policies" -> "All Schedules", we excluded our E:\ drive (which has 5+ million files). However, we created an "Include List" of the E:\ if running the Flashbackup policy.

     

    When trying to run the Flashbackup policy, we kept timing out. After putting in a call to Symantec, the reason for the problem is that our "Exclude List" was for "All Policies". The Flashbackup policy must create an exceptions list - consuming vast amounts of storage and time. By creating the "Exclude List" pertaining the the All Local Drives policy, this took care of our problem.

     

     


    That's certainly something to be aware of :smileysurprised: - thanks Ron.