Re: TDP for MS-SQL retention
2006-08-01 14:36:52
My error in my email:
VEREXISTS NOLIMIT
RETEXTRA 30
VERDELETED 1
RETONLY 60
Yes, this is not the default MC, but the default MC is:
VEREXISTS 8
RETEXTRA 30
VERDELETED 1
RETONLY 365
I will double check on the DSM.OPT !
Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/01/2006 01:41 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
Re: [ADSM-L] TDP for MS-SQL retention
Zoltan,
What is the RETEXTRA setting?
You should have something like this:
VEREXISTS NOLIMIT
VEREXISTS NOLIMIT
RETEXTRA 30
RETONLY 30
This will keep all inactive backups for 30 days.
Also.. if the management class is not the default,
make sure you have coded the INCLUDE statements
correctly in the DSM.OPT for DP for SQL.
For example:
INCLUDE "\...\meta\...\*" SqlDbMetaMgmtClass_diskonly_30DAYS
INCLUDE "\...\data\...\*" SqlDbDataMgmtClass_disktape_30DAYS
Del
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/01/2006
01:20:04 PM:
> Can someone explain why our M$-SQL TDP backups are not following the
> management class retention ?
>
> I am getting complaints that the backups are rolling off much too
quickly
> and we aren't keeping the proper amount of versions.
>
> The MC is setup as VERSIONS EXIST= NOLIMIT and RETAIN ONLY=30, yet we
are
> only seeing 3-versions of the backups at any given time.
>
> Any thoughts ?
>
> I believe the TDP is at the latest, 5.2(3).1 and the client is higher.
|
|
|