That's interesting. We are beginning to look at encryption.
If I start encrypting now with my TSM 5.2 server, what happens when I upgrade
to 5.3? Is there a "conversion" from 56 bit to 128 bit? Is it "messy"?
Or should I just upgrade to 5.3 first?
Thanks,
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax: 321.434.5509
david.longo AT health-first DOT org
>>> David.McClelland AT REUTERS DOT COM 05/25/05 4:57 AM >>>
Hi Eric,
You're in luck, as TSM offers various options for encrypting data as it
is sent from the client. Up until TSM 5.3, you were limited to 56bit DES
for BA Client backups where you do have to manage the keys yourself on
the client.
At TSM 5.3 and above, you can have up to 128bit AES backups at the API
level as well (in other words, your TDP backups can be encrypted too) -
these can be managed using 'Transparent Encryption' which means that you
no longer have to manage keys at the client side as they're stored on
the TSM server along with the data.
Hope that helps,
David McClelland
Customer Domain Expert - Transactions
Shared Infrastructure Development
Reuters
85 Fleet Street
London EC4P 4AJ
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Jones, Eric J
Sent: 25 May 2005 02:33
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [spam] Encryption
Good Evening.
Running TSM 5.2.2 on AIX 5.2
Clients are a mix of Solaris 7,8,9 AIX 4.2, AIX 5.2, Windows NT,
Windows 2000 and Windows 2003 most running TSM 5.2.2.
I've been reading the forums and was thinking I would probably not have
to worry about this until now.
I was asked to check and see what it would take to encrypt our data.
I have 2 questions.
1: Is it a problem to use an encryption device to encrypt the data
before it is sent to the TSM server? I know I would have to have the
encryption key to restore the data but I was wondering if there were any
problems that I would face.
2: Can TSM encrypt the data? I've read 1 article that indicated it was
in TSM 5.3 but I did not see much on 5.2.2 which we are running. Are
there any potential problems with using TSM to encrypt if it is
possible? I know if you loose the key your done but other than that.
Thanks for all the help,
Eric
-----------------------------------------------------------------
Visit our Internet site at http://www.reuters.com
To find out more about Reuters Products and Services visit
http://www.reuters.com/productinfo
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
##############################################################
This message is for the named person's use only. It may
contain confidential, proprietary, or legally privileged
information. No confidentiality or privilege is waived or
lost by any mistransmission. If you receive this message
in error, please immediately delete it and all copies of it
from your system, destroy any hard copies of it, and notify
the sender. You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message
if you are not the intended recipient. Health First reserves
the right to monitor all e-mail communications through its
networks. Any views or opinions expressed in this message
are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of
a particular entity; and (2) the sender is authorized by
the entity to give such views or opinions.
##############################################################
|
