How many TB of data is common in this configuration? In a large environment,
where databases are 5-10TB each and you have a demand to backup 5-10-15-20TB of
data each night, this would require you to have 10Gbs for every host, something
that would also cost a penny. Especially since the DD
In this mail, it really sounds like you're using your DD as both primary
storage and for TSM storage.
If the DD box fails, what are your losses?
Sorry for all the questions, I'm just trying to get an idea how you're using
this box. It's sounds alot like you're using it both as a filer and as
Like I said in my previous mail, it all depends on the size of you're TSM
server. Transfering (and storing) smaller amounts of data across the network is
one thing, but when u sit there with your 10TB DB2 server that needs to have a
full backup at least 2-3 days a week, transfering it across
This 6 TB supported limit for deduplicated FILEPOOL does this limit
apply when one does client side deduplication only?
Just wondering since I have just set up a 30 TB FILEPOOL for this purpose.
Regards
Hans Chr.
On Tue, Sep 27, 2011 at 8:44 PM, Daniel Sparrman
daniel.sparr...@exist.se wrote:
To be honest, it doesnt really say. The information is from the Tivoli Storage
Manager Technical Guide:
Note: In terms of sizing Tivoli Storage Manager V6.1 deduplication, we currently
recommend using Tivoli Storage Manager to deduplicate up to 6 TB total of
storage pool
space for the
I guess it just goes to show 'that your mileage may vary'. We've been happily
backing up 3-5 TB a night to VTL as primary storage with no random disk
frontend for four years now.
David
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel
It's not so much the amount of data as the amount of clients though Dave. I
dont mind having a few nodes backing up straightly to the VTL (my database
servers are doing just that), but having 1000 nodes mounting 1000 virtual tapes
in the VTL is what I'm trying to avoid with having a small
Really appreciate everyone's feedback.
In an attempt to clear up a few points and questions that Daniel (and others)
brought up and something that has surprisingly been left out of the
conversation is DD's replication capabilities.
Since TSM uses the infamous incremental forever approach,
The 6TB limit (or recommendation as described) is when you're using TSM's dedup
capabilities on the filepool, not when using the DD dedup.
Setup sounds great as long as your TSM system doesnt suffer from a logical
error (since logical errors will be deduplicated from your primary DD to your
Two DD's here at our main data center one for TSM and one for the mainframe,
both replicate to a DD880 at our DR site.
As far as the logical error risk, I am already in discussion with the
over-lords about the risk. I understand it but at times it can be trying to say
the least convincing them
OK. I only have about 600 clients going to 125 virtual drives.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Daniel
Sparrman
Sent: Wednesday, September 28, 2011 8:13 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Ang: Re: [ADSM-L] Ang: Re:
Thanks Wanda, that's a great hack
I verified this morning everything looks as expected
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: September-27-11 10:22 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Merging nodedata
Hi Daniel,
I remember hearing about a 6 TB limit for dedup in a webinar or conference call,
but what I recall is that that was a daily thruput limit. In the same section
of the
redbook as you quote is this paragraph -
Experienced administrators already know that Tivoli Storage Manager
We average between 15-20TB/day at our main site, and that goes directly to
a single DD890 (no random pool) . single-pool, file devclass, NFS mounted
on 2x10GB crossover connections. Replicates over a 1gb WAN link to another
DD890. (I spent all the money on the DD boxes, I didn't have enough
14 matches
Mail list logo
