ADSM-L

Re: [ADSM-L] Determining devclass FILE values (a.k.a. New Server - Part Deux)

2010-09-22 05:30:42
Subject: Re: [ADSM-L] Determining devclass FILE values (a.k.a. New Server - Part Deux)
From: Stef Coene <stef.coene AT DOCUM DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 22 Sep 2010 11:29:29 +0200
On Friday 17 September 2010, you wrote:
> From the few responses I got about  6.1.4.x vs 6.2.1.1 for a new server,
> the responses leaned to 6.2.x.
>
> With that decision made, the next is laying out the structure of storage
> pools and such.
>
> Most discussions/directions from here/IBM say that DEVCLASS FILE is the
> way to go vs defining fixed storage volumes/pools for disk (or in this
> case SAN)
>
> So, have you migrated to devclass FILE?
>
> For folks that are using devclass FILE, what values did you use for MAXCAP
> and/or MOUNTLimit?  How do you calculate/arrive at these numbers?
> Pro/con's for just letting the system determine MAXCAP?
Also, do you have a (fast) DISK based volume in front of the FILE storage
pool?  We do this so we can allow lots of client backups coming in and use the
number of migration processes to control the data streams to the FILE storage
pool.

We also have 2 very very very busy 5.x servers with DISK storage pools.  We
are trying to migrate them to FILE based storage pools.  We started with 100GB
volumes but this was a disaster.  Total storage is 17TB and 32TB.
The server was running reclamation for the FILE based storage pools, backup to
a remote FILE based storage pool and backup to a tape based local storage pool
at the same time.  Not good.
When we changed the FILE based storage pool to 5 GB volumes, the result was
much better.  There was less reclamation needed because it is less likely that
a volume has a status Filling.


Stef

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>