Hello,
I try to secure the TSM web client (CAD) by implementing SSL. It seems that
it's not available in 5.5.1 client version and more.
Does anyone have success running the web client GUI through "stunnel" or
another software?
I managed to run the admin server GUI without any worries, but the we
Hi Mathieu,
The web client is using 3 TCP ports, and 2 of these port are random ones
by default.
In order to have it running through a TCP tunnel, you need to define
fixed TCP ports in the client options file. See the HTTPPORT and the
WEBPORTS client options.
Best regards / Cordialement /
I would look into the option of renting a library or buying a refurbished
on.
I have no idea what kind of capacity we are talking about but you could also
migrate to disk (maybe with dedupe) and then migrate back to tape if you
happen to have (or be able to rent/borrow) the disk capacity you need.
*Matt Anglin's words during the TSM Symposium last week don't give me much
hope for a quick fix, i'm losely quoting here "we develop towards things
getting bigger all the time".*
He was talking about making logs smaller if I am not mistaking.
On Fri, Sep 30, 2011 at 5:06 PM, Zoltan Forray/AC/VCU w
My understanding is that each core in a TSM server can identify around 60GB
of undeduped data per hour.
This puts a quad core at about 3-4TB per day of newly undeduped data per day
(not running at night).
Of course there are differences in CPU architecture and memory/storage as
well but IBM say's t
Good Morning/Afternoon/Evening fellow TSM Adminers,
I have a question to pose to the group about the Reuse Delay parameter and what
is the best way to utilize or not utilize it on your storage pools. I have
come across two different schools of thought on this subject and before I do
something
Hi Chad,
If you have enough scratch tapes to use reuse delay on Primary Pool it will
save you time if a DB corruption happened.
But maybe you should have different reuse delay values on Copypool and primary
pool?
Let's say you only have 1-2 days on Primary Pool in case of the DB need to be
reco
We are buying some 3592-E06 drives to replace the 3592-E05 drives in our 3584
tape libraries. The goal is to store more TB on the cartridges we already have.
The 3592-E06 drives can read the E05 format, but they will write in E05 format
too unless the tapes are re-formatted in the E06 format. So
update the device class . see help update devclass
On Tue, Oct 4, 2011 at 10:50 AM, Keith Arbogast wrote:
> We are buying some 3592-E06 drives to replace the 3592-E05 drives in our
> 3584 tape libraries. The goal is to store more TB on the cartridges we
> already have. The 3592-E06 drives can rea
Hi all
I run q libv I2000lib on my library here some of the output:
tsm: ADSM>q libv i2000lib
Library Name Volume Name Status Owner Last Use
HomeDevice
Element Typ
Hi Robert,
TSM can and will mark a volume as private when a write error is encountered on
a scratch volume to prevent reuse. It's worth investigating if that could have
been the case. You may find recent cases in the actlog.
If you had a defective drive that (possibly) cause this, you could upd
Robert et al;
Will updating the device class make the new drives write files to tapes in E06
format which have previously been formatted and written to in E05 format?
Filling volumes would then have a mixture of E05 and E06 formats. Will TSM do
that? Are the device drivers, or what not, smart e
The other side of this is that with 3rd party deduplicated replication, my
offsite copy is rarely more than one hour behind the source copy. Before
I moved to this, we would schedule our backup-stg pools to run once a day,
and they would have to run several hours before it was in sync. If the
A non-zero reuse delay on your primary pool protects you from a situation
where you need to restore your database, but your primary pool tapes are
not lost. (Not a full DR situation).
If you have a reuse delay of 0, you will still have the data available in
the copypool, but if you wanted to get
Yes.
But to be sure open up a ticket with TSM support to verify this. We did this
using TSM v 6.2.x and it worked fine.
On Tue, Oct 4, 2011 at 2:05 PM, Keith Arbogast wrote:
> Robert et al;
> Will updating the device class make the new drives write files to tapes in
> E06 format which have prev
Robert,
Thank you, I just did. We're on 6.2.2 also. I'll update the thread when they
respond.
Best wishes,
Keith
Not entirely true since you dont have todo backup stgpool as a only resort with
TSM 6.2. Since the simultaneous copy feature is now not only available for
client, but for server processes, there is nothing saying you have to copy all
the data by using backup stgpool.
And it's not a matter if it
We were using the copystg feature of the storage pools before, and even
then our TSM cycle was growing, growing and eventually passed 24 hours.
For us, it wasn't 4 hours vs 1 hour. It was 24+hours+finger crossing vs
one hour. We reached the point where we had to kill the backup-stg's and
try
Not really sure why you would need +24 hours to handle copying data to your
secondary site.
With features like:
- Copy storage pool feature for client backups
- Copy storage pool feature on migration
- Normal backup storage pool
With the first 2, there shouldnt really be much data left to copy
19 matches
Mail list logo
