I just got a situation that requires yet another storage pool hierarchy, and I am starting to run into the problem described in [1]; basically I have more than enough disk in aggregate to handle nigh
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Wed, 25 Oct 2006 13:38:14 -0400
Um. I don't really see what the issue is. TSM is elegantly designed to automatically compensate for a disk pool being too small on occasion by kicking in the migration to tape automatically for you,
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Wed, 25 Oct 2006 13:43:28 -0400
-- Daniel Clark wrote: -- We are using this kind of setup with TSM 5.2. We have run into two types of problems. The first problem is that things get really ugly if the storage pools collectively get
TSM is elegantly designed to automatically compensate for a disk pool being too small on occasion by kicking in the migration to tape automatically for you, based on the thresholds you set. So it's w
The first problem is that things get really ugly if the storage pools collectively get larger than the shared disk space. Ugly in what kind of way? Clients don't just block until one of the FILE clas
You probably want to avoid RAID5 for disk storage pools, whether sequential or random. That can really slow client backups, because RAID5 is quite slow for writing. RAID5 is really only good for read
On 10/26/06, Roger Deschner <rogerd AT uic DOT edu> wrote: You probably want to avoid RAID5 for disk storage pools, whether sequential or random. That can really slow client backups, because RAID5 is
Author: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
Date: Thu, 26 Oct 2006 14:35:32 +0200
Hi, Reading the threat and missing something. Why another stg? For normal backup data I like to use JBOD config. No read protection at all and maximum usable GB per disk. In order to minimize the num
Author: Mark Stapleton <mark.s AT EVOLVINGSOL DOT COM>
Date: Thu, 26 Oct 2006 08:22:57 -0500
There's a certain amount of sense there. What is the purpose of fault tolerance in a TSM disk storage pool? At the end of a process cycle, all customer data exists in at least three or four places: 1
we are using RAID5 in last 6 years as diskpools with no problems whatsoever we used SSA, now we are using SATA on DS4100 goran From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Be
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Thu, 26 Oct 2006 10:15:26 -0400
--Daniel Clark wrote: -- No, the clients keep trying to send data, and transaction failures occur until some disk space is made available. In addition, when a write to a file volume fails for lack of
You may have missed it, as the reason that prompted my question was buried in one of the later replies - basically I need to have a "special" storage pool for a limited set of machines that has a pri
There's a certain amount of sense there. What is the purpose of fault tolerance in a TSM disk storage pool? At the end of a process cycle, all customer data exists in at least three or four places: I
No, the clients keep trying to send data, and transaction failures occur until some disk space is made available. In addition, when a write to a file volume fails for lack of disk space, TSM will all
And now for the counterpoint. I've got ~3-4 TB in 6 15-disk SSA RADI5s, between them I fill a Gb pipe coming in, if the clients on the other side ever get organized. 30MB/s peak per RAID is seldom t
I do not agree. New SAN boxes with write cache (with battery's) are smart. Very smart. New boxes are even better and need less ram to have the same performance. I did some tests on raw devices and I