The policy is multistream enabled, so each local drive and windows 
special save directives get a job stream.

Here is an EG:

clients:
CNODE1
CNODE2
CVIRT1

policies:
CVIRT_full_win
Type:   MS-Windows
Backup Selections:
  Q:
  R:
Exclusions: None
Schedules:
  Full (Full)
  Daily (Differential/Inc)
Clients:
  CVIRT1

SYS_synth_win
Type: MS-Windows
Backup Selections:
  ALL_LOCAL_DRIVES
Exclusions:
   CNODE1: Q:, R:
   CNODE2: Q:, R:
Schedules:
  Full (Full)
  Daily (Differential/Inc)
  Weekly (Full - Synthetic)
Clients:
  CNODE1
  CNODE2

Sequence of events:

Full schedule for SYS_synth_win runs and creates images for VSS 
compontents, System State, C:
Q: and R: are not backed up, no errors..

Daily inc schedule runs and creates images for VSS compontents, System 
State, C:
Q: and R: are not backed up, no errors.

Weekly schedule runs, the parent job spawns a job for each 
ALL_LOCAL_DRIVES regardless of the exclusions.
The cluster drives jobs all fail with a 671 since there are no images to 
create the synthetic with.

I could build a policy for the cluster nodes local system backups that 
doesn't use ALL_LOCAL_DRIVES, but that is going to be harder to manage, 
and I would much rather use that directive wherever I can so that I 
never see a case where we failed to backup a new local drive added some 
time in the future and being overlooked for the backup policy.


On 12/18/2009 11:56 AM, bob944 wrote:
>> so I have a problem with backing up MSCS clusters with
>> ALL_LOCAL_DRIVES backup selections.
>>
>> The cluster nodes not holding the volume attempt to backup
>> the volumes and fail. This was easy enough to fix with
>> policy specific client exclusions, and these exclusions
>> for the clustered volumes get skipped correctly when
>> backing up with Full, or Differential-Incremental
>> schedules, and images for those volumes don't get created.
>>
>> The Synthetic Full schedule however errors out with the
>> cluster volumes with an exist status 671.
>>      
> I don't know the answer but have a suggestion.
>
> If you include a known-good file with each stream (however you have
> them broken up), does the synthetic work?
>
> Example:
>
>       NEW_STREAM
>       f:\
>       c:\windows\system32\drivers\etc
>       NEW_STREAM
>       g:\
>       c:\windows\system32\drivers\etc
>
> I do this (/etc on *nix and the above on windows, with also "winnt"
> vs windows and with the likely system-drive-letters--c: and d:
> usually) anywhere that I back up an optional mount point which may
> or may not have anything mounted to it and I want to be alerted by a
> stat 71.
>
>
>    

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu