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
ADSM-L] TSM 5.3.4 Policy problem
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_S
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
sider the environment before printing this Email
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
William ZHANG
Sent: Thursday, December 24, 2009 6:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
Hi All,
I hav
est Regards,
william
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
David E Ehresman
Sent: Friday, December 18, 2009 12:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
If you REALLY want to keep data in TSM for 60 days, you ne
5.3.4 Policy problem
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
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
18, 2009 4:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
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
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
Regards,
william
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Carol Trible
Sent: Thursday, December 17, 2009 11:25 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
Activate makes the activated policy set the active one by copying
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
SM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
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
30 60
> STANDARD STANDARD STANDARD STANDARD 2
> 1 30 60
>
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Skylar Thompson
> Sent: Thursday, December
-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
William ZHANG
Sent: Thursday, December 17, 2009 12:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
Hello Skylar,
Do you mean,
> update copygroup DOM_SRV SET_SRV MC_90DAYS STANDARD verexists
60
>
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Skylar Thompson
> Sent: Thursday, December 17, 2009 12:44 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
.marist.edu] On Behalf Of
Skylar Thompson
Sent: Thursday, December 17, 2009 12:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem
You actually want to modify the copy group from your inactive policy
set. In most cases this should be STANDARD rather than ACTIVE. You the
and copygroup
> so that I can get what I want?
>
>
> Many thanks!
>
> William
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
> Bos, Karel
> Sent: Wednesday, December 16, 2009 6:27 PM
> To: ADSM-L@VM
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
printing this Email
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
William ZHANG
Sent: Wednesday, December 16, 2009 12:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM 5.3.4 Policy problem
Hello All,
I meet a problem,
If I want to
Hello All,
I meet a problem,
If I want to retain deleted data 60days in TSM, what commands should I input
to modified policy in TSM?
should the "versions data exists" and "versions data deleted" be modified
from 2 to 59 , right?
These are my configuration:
--
22 matches
Mail list logo