] Two different
retention policies for the same
node
25/03/2009 08:55
To
> Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
> Dist Stor cc
> Manager"
> .EDU> Re: [ADSM-L] Two different
>
.COM> To
> Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
> Dist Stor cc
> Manager"
> .EDU>
Re: [ADSM-L] Two different
retention policies for the same
node
19/03/2009 12:27
On Tue, Mar 17, 2009 at 11:18 PM, Conway, Timothy
wrote:
> Is this to avoid having two copypools? That's a reasonable goal. I
> have only one copypool, which is my DR offsite pool. Just make your
> onsite copypool an offsite pool, and you can give them 25 times better
> than they're asking for
On Tue, Mar 17, 2009 at 11:33 PM, Kelly Lipp wrote:
Where are the people that use the data going to be? How will
customers interact with them?
This is very valid point! Luckily I'm not the one who needs to think
about it ;-)
>
> If you worry DR application by application and think about all
@VM.MARIST.EDU
Subject: Re: [ADSM-L] Two different retention policies for the same node
There could be some serious issues with this. If you have an onsite
volume that has 170 day old data, with 5 day old data and 80 day old
data (due to reclamation), and the volume goes bad, all you'll be able
to res
aded.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Michael Green
Sent: Tuesday, March 17, 2009 1:57 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Two different retention policies for the same node
I've been asked to provide a DR/BAck
ads...@vm.marist.edu] On Behalf
> Of Michael Green
> Sent: Tuesday, March 17, 2009 2:57 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Two different retention policies for the same node
>
> I've been asked to provide a DR/BAckup solution that seems to
> contradict TSM
I've been asked to provide a DR/BAckup solution that seems to
contradict TSM methodology, but I've decided I'll throw this in here
anyway.
Given the following retention policy:
RETE=180
RETO=180
VERE=NOL
VERD=NOL
(180 days, no version limit)
I've been asked to find a way to keep offsite only 7 da
versions data exists - no limit
versions data deleted - no limit
retain extra versions - 30
retain only version - 30
cc:
Sent by: Subject: retention policies
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>
04/09/02 04:05
PROTECTED]>
To:[EMAIL PROTECTED]
cc:
Subject:Re: retention policies
The standard management class we use for most servers is
Ver data exists 3
Ver data deleted1
Retain extra ver30
Retain only ver 60
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECT
policies
Ours is various, whatever the business requires related to the data.
-Original Message-
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 4:05 PM
To: [EMAIL PROTECTED]
Subject: retention policies
Can I take a poll of what people are using for:
versions
Ours is various, whatever the business requires related to the data.
-Original Message-
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 4:05 PM
To: [EMAIL PROTECTED]
Subject: retention policies
Can I take a poll of what people are using for:
versions data
Mine env:
versions data exists 30
versions data deleted 1
retain extra versions 30
retain only version60
Jason Liang
- Original Message -
From: "Marc Levitan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 4:05
ginal Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Marc Levitan
Sent: Tuesday, April 09, 2002 1:05 PM
To: [EMAIL PROTECTED]
Subject: retention policies
Can I take a poll of what people are using for:
versions data exists
versions data deleted
retain extra versions
r
Can I take a poll of what people are using for:
versions data exists
versions data deleted
retain extra versions
retain only version
Thanks in advance!
Marc Levitan
Storage Manager
PFPC Global Fund Services
18 matches
Mail list logo
