and
> SPECIFY the case you will use for your throughput test.)
>
>
> My recommendations:
>
> * My personal favorite for mid-range disk is the V7000, with the
> XIV-Like DDP firmware. There is a low-end inexpensive version and
> higher-end version. The cool thing is
s that you can improve performance as you grow by adding
spindles.
* Test. If you don't have dedup now, set up a small pool and play with
it, so you get a feel for the lifecycle.
Wanda
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU
Bill,
My concern was that if the copy storage pool was tape, then with small primary
stgpool volumes there might be a lot more tape mounts required, especially if
the stgpools are collocated. Since your output pools are on disk, then the
higher mount/unmount activity wouldn't be an issue.
..P
3 3:54 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Dedup stgpool target
Bill,
Are you virtual volumes purely on tape on the target server, or are they
fronted by some sort of disk storage pool? I am trying to understand whether a
small volume size for the ingest dedup file pool will cause a lot of tape
are on virtual volumes. I have never seen any issues
>related to the primary pool volume size.
>
>- bill
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul
>Zarnowski
>Sent: Monday, November 18, 2013 9:35 AM
>To: AD
[mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul
Zarnowski
Sent: Monday, November 18, 2013 9:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Dedup stgpool target
One other question, if you don't mind Bill: Do you have Copy Storage Pools?
If so, are they on tape or file? If tape, is the small v
gt;>There is also a tape library. Really big files are excluded from dedup via
>>the stgpool MAXSIZE parameter and
>>land on a separate pool on the Nexsan storage which then migrates to tape.
>>
>>Hope this helps,
>>
>>Bill Colwell
>>Draper Lab
>>
&g
ilto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sergio
O. Fuentes
Sent: Friday, November 15, 2013 12:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Dedup stgpool target
Bill,
Thanks for info. Just curious, are you utilizing source-side dedupe or
relying on the TSM identify to identify all your dupli
Bill,
Thanks for info. Just curious, are you utilizing source-side dedupe or
relying on the TSM identify to identify all your duplicates
(post-process)? How does the maxsize parameter interact with source-side
dedup? I'll have to look that up.
Eventually you have to reclaim your copy pools and
hierarchies so
mapping out pre-allocation would be a nightmare.
thanks,
- bill
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul
Zarnowski
Sent: Thursday, November 14, 2013 2:33 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Dedup stgpool
b
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
>Sergio O. Fuentes
>Sent: Wednesday, November 13, 2013 10:32 AM
>To: ADSM-L@VM.MARIST.EDU
>Subject: TSM Dedup stgpool target
>
>In an earlier thread, I polled this group
Behalf Of Sergio
O. Fuentes
Sent: Wednesday, November 13, 2013 10:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TSM Dedup stgpool target
In an earlier thread, I polled this group on whether people recommend going
with an array-based dedup solution or doing a TSM dedup solution. Well, the
answers came
In an earlier thread, I polled this group on whether people recommend going
with an array-based dedup solution or doing a TSM dedup solution. Well, the
answers came back mixed, obviously with an 'It depends'-type clause.
So, moving on… assuming that I'm using TSM dedup, what sort of target arr
13 matches
Mail list logo
