Thanks All. Policy problem has been resolved currently.
-Original Message-
From: Richard Sims [mailto:r...@bu.edu]
Sent: Thursday, December 24, 2009 9:11 PM
To: William ZHANG
Subject: Re: TSM 5.3.4 Policy problem
On Dec 23, 2009, at 10:16 PM, William ZHANG wrote
OK, seems it works:
tsm: SHITSM01>q copygroup t=b
PolicyPolicyMgmt Copy Versions Versions Retain Retain
DomainSet Name Class Group Data DataExtraOnly
NameName NameExists Deleted Versions Version
- - --
On Dec 25, 2009, at 3:08 AM, William ZHANG wrote:
> Again,
> I want to add a archive copy group for archiving files to retain 3 years.
>
> So, see manual, but donot fully understand.
> If I should input:
>
>
> Tsm:> define copygroup DOM_SRV SET_SRV MC_90DAYS type=archive
> Dest=LTO3_ARCH_
d Sims [mailto:r...@bu.edu]
Sent: Thursday, December 24, 2009 9:11 PM
To: William ZHANG
Subject: Re: TSM 5.3.4 Policy problem
On Dec 23, 2009, at 10:16 PM, William ZHANG wrote:
>
> ---
> Another question how can I modidy archiving time to 3 years?
See Archive Co
iod you can restore from for instance).
Kind regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem
Kind regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem
Yes, but it is better to use 60 instead of 59.
Grigori G. S
Hi All,
The problem has been solved.
Many thanks to all of you!
Merry Christmas!
William
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: Monday, December 21, 2009 8:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3
On Dec 20, 2009, at 8:46 PM, William ZHANG wrote:
> Hi All,
> Thanks for your help.
>
> Do anyone know if I change the setting of TSM , how can I restore my setting
> back to before change?
You would change your settings back in the same way that you altered them.
Be aware when you reduce retent
Hi All,
Thanks for your help.
Do anyone know if I change the setting of TSM , how can I restore my setting
back to before change?
Thanks!
Best Regards,
william
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: Friday, December 1
On 18 dec 2009, at 07:18, William ZHANG wrote:
> Hi All,
>
> Thanks for your help!
>
> When I input:
> ACTIVATE POLICYSET DOM_SRC SET_SRV
>
> TSM give a message:
> ANR1557W The space management migration destination in management class
> MC_90DAYS does
> Not refer to a defined storage pool: SPA
copy group, they
>>
> manage
>
>> the data by date instead of versions. Managing retention time using the
>> versions parameters can give some unintended results (an extra backup of
a
>> changed file will reduce the period you can restore from for instance).
>>
>
o:ads...@vm.marist.edu] On Behalf Of
David E Ehresman
Sent: donderdag 17 december 2009 17:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem
If you REALLY want to keep data in TSM for 60 days, you need
Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=nolimit
verdeleted=no
le will reduce the period you can restore from for instance).
Kind regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy probl
;
>> I would take a look at the RETExtra/Only parm of the copy group, they
>>
> manage
>
>> the data by date instead of versions. Managing retention time using the
>> versions parameters can give some unintended results (an extra backup of
a
>> changed fi
eters can give some unintended results (an extra
> backup of a changed file will reduce the period you can restore from
for instance).
>
> Kind regards,
>
> Karel
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
&g
t;
>> the data by date instead of versions. Managing retention time using the
>> versions parameters can give some unintended results (an extra backup of a
>> changed file will reduce the period you can restore from for instance).
>>
>> Kind regards,
>>
>>
-Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Grigori Solonovitch
> Sent: woensdag 16 december 2009 10:31
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: TSM 5.3.4 Policy problem
>
> Yes, but it is better to use 60 instead of 59.
of a
> changed file will reduce the period you can restore from for instance).
>
> Kind regards,
>
> Karel
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Grigori Solonovitch
> Sent: woensdag 16 december 2
instance).
Kind regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem
Yes, but it is better to use 60 instead of
).
Kind regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem
Yes, but it is better to use 60 instead of 59
Yes, but it is better to use 60 instead of 59.
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com
Please consider the environment before p
21 matches
Mail list logo
