At least you can, and don't have to do it on Sundays during a change
window. ;o\
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
> WEAVER, Simon
> Sent: December 6, 2005 8:15 AM
> To: 'Ed Wilts'
> Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
> Subject: RE: [Veritas-bu] Policies - Full & Incr
>
>
> Thanks for the confirmation Ed! Knew I should have started
> the new Policies
> on Friday night!!
>
> Simon Weaver
> Technical Support
> Windows Domain Administrator
>
> EADS Astrium
> Tel: 02392-708598
>
> Email: Simon.Weaver AT Astrium.eads DOT net
>
>
>
> -----Original Message-----
> From: Ed Wilts [mailto:ewilts AT ewilts DOT org]
> Sent: 06 December 2005 12:29
> To: WEAVER, Simon
> Cc: 'veritas-bu AT mailman.eng.auburn DOT edu'
> Subject: Re: [Veritas-bu] Policies - Full & Incr
>
>
> On Tue, Dec 06, 2005 at 08:44:28AM -0000, WEAVER, Simon wrote:
> > I performed a full backup on 2 clients over the weekend using their
> > existing policies. The backups were successful.
> >
> > Yesterday, to keep in line with procedures, I created 2 brand new
> > policies and set off the Incrementals - this morning they are still
> > running!
> >
> > Is this because they are running under the NEW policies I created?
> > Just want to clarify if this is the case, or whether there
> is another
> > issue
>
> The incremental is based off the last full in the same policy. If you
> created a new policy separate from the full, then the first
> backup will
> consist of everything.
>
> Each policy should have all the schedules in it - i.e. Full
> and Incremental
> in the same policy.
>
> If you rename a policy, the same thing happens - you trigger
> a full backup.
>
> --
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts AT ewilts DOT org
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
|
