As I stated in a previous post.
The issue here may not be Synthetic Backups.
An unsheduled Full backup(not synthetic) runs the next day !!!after I expire
the original full!!! The original Full was run "manually". Using Calendar
based with no date to start.
Remember this was just a test to see what happened if I expired the full.
However Bob states you must have the full plus TIRs. This is a TIR policy.
All diffs exist. I expect an error if a requirement is not met, not running
a full backup, unless this is something new.
Running 6.5.4 but it may not be related to this release. Suse 10 ia64 (old
sgi)
Job is gone so I'll need to regenerate.
Jim
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of bob944
Sent: Wednesday, July 08, 2009 12:26 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: JimH AT FederalEdge DOT com; jhilton6 AT excite DOT com
Subject: Re: [Veritas-bu] Synthetic Backups
> 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
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
