Answering my own question,
This was resolved by turning off multistreaming for this policy. With
multistreaming, a separate stream was spawned for each drive, even if
the drive was filtered out and gave errors with the synthetic.
This problem did not occur when the policy was set to not use
multistreaming. Kudos to NBU support for solving this one.
On 12/17/2009 8:39 PM, David Stanaway wrote:
Okay,
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.
Is there something I am missing? The client exclusions are set up right
as they work for the other schedule types. Do the synthetics ignore the
exclusion lists since they are not touching the client system?
In Legato, the ALL backup selection skips volumes that are associated
with an MSCS cluster. Is there a policy specific way I can do the same
thing?
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
