Hi all,
As FC connection is shared by both data path and control path in TS3310
(comparing with 3494 that needs IP for library manager), I would like to
know whether any initial configuration required for 3310 to work with TSM? I
mean is it possible just to add the library to TSM server zone, insta
Yes, Mehdi
It is that easy.
You might like to configure an additional control path on the library in
case there is a problem with the drive with the control path that you
normally use.
Bring the library microcode up to date using the gui. Also install the
ITDT tool, and use it to bring the dri
Snapshots/image backups?
Don't think about the backup, think about the restore RTO/RPO.
What kind of restore scenarios do you have, how much data (in time) can you
afford to lose and what is your acceptable restore time?
Will you ever need to restore individual files? I'm not familiar with
Black
I've done some test regarding this but it was a pretty long time ago so I
don't have any results to share, sorry, just an opinion.
The default in RHEL is the CFQ scheduler which should be optimized for
throughput which is what we want.
Your other choices would be:
deadlineif you need lo
Hi all,
from where can I check what TSM server versions the TSM Administration
Center versions 6.1.3.0 and 6.2.0.0 are supporting?
I'm having TSM servers 5.3.6.0 and 5.5.3.0 running on AIX 5.3 and RHEL
5.
Thank you ands best regards,
Rainer
RHo-Consultin
I'm wondering if a Fastback type (block level incremental image) backup might
be the answer. Backing up changed blocks might be faster than trawling the
filesystem, and the ability to mount a point in time image would provide you
with file level restore as well as DR image recovery.
Just a thou
Folks, I'd truly appreciate if somebody with a moment to spare and
appropriate equipment at hand would run a couple of tests as shown
below and report back to the list.
--
Warm regards,
Michael Green
On Sat, Apr 10, 2010 at 1:47 AM, Michael Green wrote:
> I've been playing with ITDT v4 for quit
Another benefit of the image/snapshot is that it would eliminate the
huge burden that the file-level backup has on you TSM DB. For example;
if that filespace has 1 million files that results in 1 million entries
in the DB, since the image or snapshot is a single object there is only
a single entry
Robert,
Thanks for your email.
For TSM, the IBMtape driver should be installed in Exclusive mode.
And I double checked with the guy who recently installed the drivers,
and assured me they were installed in Exclusive mode.
But your email did help me solve the problem. From the Windows
se
I have :
- one server windows 2008 SP2 as a domain controller (DC)
- Two nodes as a cluster server active/passive running sqlserver 2008.
- IBM SAN ds4700 with the Fiber tape connected to SAN via fiber cable.
every node is connected to SAN using two HBA, and all disks in SAN are
dedicated to sql s
The TSM Administration Center versions 6.1 and 6.2 can connect to version
5.4, 5.5 and 6.1 TSM servers. The TSM Administration Center version 6.2
can also connect to version 6.2 TSM servers.
The TSM Administration Center version 5.5 and 5.4 can connect to a 5.3 TSM
Server, but the 5.3 server is n
Don't need the ATLDD, Just the Atape drivers.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Steven Harris
Sent: Wednesday, April 28, 2010 4:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TS3310 rapid config for TSM
Yes, Mehdi
It is that easy.
LTO2 writes to tape at maximum of 40MB/sec. If the data compresses 3.5:1 then
your server will need to feed the tape drive at 140MB/sec to keep up with the
write speed. If the data compresses 1:1 then you only need to send data at
40MB/sec.
This kind of thing used to drive me nuts until I figu
So, what is atldd for? 3494 only?
Thanks
14 matches
Mail list logo
