We are considering purchasing a CDL 4100 and EMC is telling us we will get
1200MBps performance. Can anyone provide feedback on how their VTL --
specifically EMC DL 4100 is performing? I have spoken to some friends who have
implemented one and are getting much lower performance #s... they say
hello goran,
you need an dsm.opt (which is no link to an existing dsm.opt !!!) in:
/usr/tivoli/tsm/client/api/bin64/
it should contain the following entry:
SERVERNAME ASMPSR_tdpo
then your tdp is able to find the right stanza in the global dsm.sys file.
regards
lemmy
Hi Sunanda,
Have you configured your devclass like this (taken from my devconfig file):
DEFINE DEVCLASS 3592_CLASS DEVTYPE=3592 FORMAT=DRIVE MOUNTLIMIT=DRIVES
MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=3584LIB WORM
=NO DRIVEENCRYPTION=ALLOW SCALECAPACITY=100
I think you have to specify
In my case 10TB of type=file will store 10TB of data. 10TB of VTL will
store nearly 20TB of data. That is my only reason.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
caldwem01
Sent: Tuesday, June 12, 2007 5:21 PM
To:
In my world I am limited to 800MB to the VTL because I only have four
2GB fiber connections to the VTL. Migrations are limited to 400MB
because I have only two 2GB connections to the disk pools. When the Ins
are going to the right Outs I get close to the above speeds.
Andy Huebner
Validate with EMC that the the 1200MBps is Native or compressed, we had
the same discussion with our CDL 740 and the actual max was 469MBS. I'm
not sure if the newer 4100 is clustering the VTL Heads to get an actual
1200MBS.
Charles Hart
lowneil [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor
Hi,
We are currently running TSM version 5.3.2 and using a 3584 library.
We have a script that runs daily to eject our offsite volumes to the IO
Station, however at times it fails to run correctly because all drives are
busy. However when performing a q mount we can see that some of the
On Jun 15, 2007, at 9:19 AM, William Kyndt wrote:
Hi,
We are currently running TSM version 5.3.2 and using a 3584 library.
We have a script that runs daily to eject our offsite volumes to
the IO Station, however at times it fails to run correctly because
all drives are busy. However when
Hi William!
UPDate DEVclass deviceclassname MOUNTRetention=amount of minutes
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
William Kyndt
Sent: vrijdag 15 juni 2007 15:20
To:
Upd devclass ? mountretention=?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
William Kyndt
Sent: Friday, June 15, 2007 9:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: How to change the default idle timeout for dismounting volumes
Hi,
We are
From: ADSM: Dist Stor Manager on behalf of Justin Miller
Not to rain on your parade or anything but in talking to my IBM rep she
told me that the licensing strategy is indeed changing with the 5.4
release but not for the better in my opinion. Now instead of basing it on
the number of CPU's that
On Fri, Jun 15, 2007 at 11:12:57AM -0500, Mark Stapleton wrote:
From: ADSM: Dist Stor Manager on behalf of Justin Miller
Not to rain on your parade or anything but in talking to my IBM rep she
told me that the licensing strategy is indeed changing with the 5.4
release but not for the better in
On Fri, 15 Jun 2007 11:12:57 -0500, Mark Stapleton [EMAIL PROTECTED] said:
Counting CPUs is a snap for windows: from a DOS prompt, type
set n
for the number of CPUs. (The type of processor can be easily deduced
by the make/model of server.) Use your existing Windows domain admin
tools
On Fri, 15 Jun 2007 11:41:17 -0500, Bob Booth [EMAIL PROTECTED] said:
IBM.. please listen to your customers, we have been giving you plenty of
warning. You can save yourself and us money and time, if you change your
ways.
...
Not to toot my own horn (but deliberately tooting Bob's), but
Why a VTL vs FILE devclass volumes on local drives?
1) With a VTL you can do LAN free backups.
2) Data Compression:
2A) TSM Client does compression: Big performance hit on the client,
slower backups/restores
2B) TSM server does compression (FILE devclass volumes on compressed
file systems): Big
I've got a client who's failing to restore an Exchange store, and he's
not really getting any suggestive errors; this kind of surprises me,
I'm used to the problem being pretty nicely pointed to, one way or
another.
Windows Server 2003 R2 SP1
Exchange agent Version 5, Release 4, Level 0.2
My TSM
Hello TSMers,
I have been asked to report the number of tapes that we have used in 2006 and
the same for 2006.
Has anyone done something like that?
I am looking at the LAST_WRITE_DATE on the volumes but I am not sure if that
is the right place to look.
TSM version 5.2
Hi Allen,
RC=425 is Exchange API error. This normally means that
the Exchange Server found something that it did not like.
Are you doing the FULL restore separate from the INCR restores?
If so, are you turning off the Run Recovery option?
If you use the GUI and do them all together (FULL + INCR),
... On z/OS the tape library is manage by other mainframe
products. TSM on z/OS has no knowledge about the tape library on z/OS
other than the number of drives and the device types. SMS rules decides
on the tape media is correct and the system assign the tape
I think you hit every nail right on the head, Milton. I would emphasize
#5, as people tend to minimize how big of a deal it is to provision and
administer large amounts of disk. A GOOD VTL (not all are good) will
make that provisioning issue go away.
As to de-dupe, it's considered by many to be
John Schneider said:
I can't speak for everybody's product out there, but the EMC CDL (EDL)
releases the used pages from the virtual volume as soon as you begin to
overwrite the virtual volume from the beginning. One thing that does
this is a Label Libvolume.
This is the way they all work. And
It's been politely pointed out to me that grousing at folks who take
time off to come to Oxford isn't likely to make them feel happy about
coming to Oxford. Good point.
- Allen S. Rout
It really is all over the board as to the details...
Think of it as a custom filesystem with a really large block size. (As
in 64 or 256 MB instead of the typical 8K you see in a normal
filesystem.)
As to how the whole deduplication thing works, you can read an article I
wrote on the subject
On Fri, Jun 15, 2007 at 05:19:34PM -0400, Allen S. Rout wrote:
It's been politely pointed out to me that grousing at folks who take
time off to come to Oxford isn't likely to make them feel happy about
coming to Oxford. Good point.
Agreed.
That said,
Talk to your BP's, SE's and anyone else
Good info in the article - clears up a lot of things about VTL's and
de-dupe. There are a few things it doesn't mention, which I still have
questions on, though. Anyone have any insight on these questions?
What is the sample size for determining duplication of data? If it's
64MB or 256MB
What is the sample size for determining duplication of data? If it's
64MB or 256MB blocks, am I going to get many hits, as the same data may
not
be blocked the same way each time?
The sample size is much smaller than that, as small as 16K-256K. It's
all over the board, though.
If I de-dupe,
You cannot encrypt the data before it goes to the VTL and expect it to
de-dupe it. But you can encrypt when copying from the VTL to tape, or
you can put an encryption box behind the VTL head but in front of the
disk and you're OK (although I don't see the point).
You obviously don't live in a
Although I don't work in such a world now, I did for several years, and
I also consult in such environments quite regularly. I'm also HUGE
proponent of encryption in general.
What I am saying is I don't see the point in encrypting data behind the
VTL. Since the encryption is invisible to the
28 matches
Mail list logo
