No deduplication.

However, I have the trouble of a file class pool, collocated by filespace, 
showing full and not allowing backups even though the pool shows 75% full, just 
used itx maxscratch allocation.
This causes an inordinate amount of human interfvention to keep afew volumes 
below maxscratch.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Stefan Folkerts
Sent: Monday, August 24, 2015 6:07 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] going to all random disk pool for tsm for ve

I believe a fileclass storagepool is better suited for this kind of
"permanent" storage on disk.
A diskpool should be used for things such as disk between the backup client
and tape for temporary random I/O storage that can handle an unlimited
amount of sessions.
A fileclass storagepool is better suited for long term storage.
I create a diskpool for VE metadata when using dedup on the filepool and
use fileclass storagepools for permanent storage on disk with or without
deduplication.

Are you planning on using deduplication on disk?


On Fri, Aug 21, 2015 at 10:12 PM, David Ehresman <
david.ehresman AT louisville DOT edu> wrote:

> Gary,
>
> TSMVE 7.1.2 makes file level restores a reality.  You may want to work
> with them a bit before deciding if you want to go to all random disk.
>
> David
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Lee, Gary
> Sent: Friday, August 21, 2015 3:31 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] going to all random disk pool for tsm for ve
>
> Hoping to get upgraded to tsm server 7.1.x within the next month.
> At that time, we are considering changing our storage strategy to all
> random disk pool.
>
> This because we cannot do a file level restore from a vmware backup from
> sequencial media, (be it tape or disk).
>
> Has anyone done this, or is there a better way?
>
> Looking for guideance and others' experience.
>