> There is a case open with Symantec about this issue, and I am told
> an EEB will be made available soon.
> 
> You are not supposed to have to keep a full around,

No.  You _must_ have a full plus subsequent TIR and diffs or cincs
to synthesize a new full, but it does not matter how the full was
generated.  (That was for clarity--I assume you meant "to keep a
traditional full around.")

> but once the
> full expires a new full is taken automagically.

I've used synthetic fulls and cincs for years, demonstrated them in
this mailing list and found the documentation to be pretty darned
clear.  IME, they always work.  

What's been missing from this discussion (apologies if I've missed
it) is detail about what setup you or the original poster have.
What release, what platform, what is the policy config, what images
and TIR are available when it doesn't work for you, what's the
bpdbjobs output (easy way to track the progress of a synth and the
components it is using)?

I've confirmed it is working properly in 6.5.3.1 Solaris:  no
natural full exists, nor is one created--just the current synthfull
+ cinc = new synthful.  Is this (your experience, and the support
case and EEB) a 6.5.4 issue?

> Quote<So it appears I need to keep the Full backup around even
> > though the Synthetic Full is suppose to be its equivalent.
> > 
> > The Full backup runs on Day 5 even though I don't have it
> > scheduled. In Fact Full are manual. Synthetics are scheduled. >


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