ADSM-L

Re: Exchange Restore/Expiration Question

2003-02-13 22:06:03
Subject: Re: Exchange Restore/Expiration Question
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 13 Feb 2003 22:05:54 -0500
Bruce,

Are both log backups and full backups going to this same
management class? If so, that explains it.

Since logs are uniquely named, once DP for Exchange
marks them "inactive", they abide by the
"Retain Only Version" rule... which you show below as 120 days.
So that means they will stay around for 120 days once they
have been inactivated (when the next full is run.)

Full backups replace each other... and so.. in your setup,
if you take a full backup once per week... the 4th backup will drop
off the end and be deleted at the next server expiration task.
And that will be before the associated log backups for that
full are deleted. That probably explains what you are seeing.


Some customers don't use VEREXISTS or VERDELETED... they
simply use RETONLY and RETEXTRA so that they can keep
their backups based on time, not number of versions.
That makes it so you can run manual full backups
as often as you need to and you will still be able to
go back to earlier backups based on time, not versions.

For example... say you want to be to be able to
restore any backup for 120 days. Your settings would be:

VERDELETED   NOLIMIT
VEREXISTS    NOLIMIT
RETEXTRA     120
RETONLY      120

You may have some logs that stay around for a while,
but they will stay around a max of 120 days after they
are inactivated. Granted, it may require more storage, but it
guarantees restorability back to a certain point in time.
If you had a perfect world and only had to take full backups
once per week...and never for any other reason, you could
do it with the version settings.

In your setup, if you had to run 4 full backups in
one week, for example, that is as far as you would
be able to restore back to.

Hope that helps.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Remember that the best job security is
doing a job well and doing it cheerfully.
==============================================
> Policy Domain Name EXCHANGE_AGENT
> Policy Set Name STANDARD
> Mgmt Class Name EXCMGMTCLASS
> Copy Group Name STANDARD
> Versions Data Exists 3
> Versions Data Deleted 1
> Retain Extra Versions 60
> Retain Only Version 120
> Copy Mode MODIFIED
> Copy Serialization SHRSTATIC
> Copy Frequency 0

<Prev in Thread] Current Thread [Next in Thread>