An update, as I've sorted it for now - it is kinda buried away, but
searching on 'transparent encryption' in the TSM 5.3 API manual reaps
dividends:

http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp?topic=/com.i
bm.itsmc.doc/ansa000077.htm

I've got this working for TDPSQL on Win32 now (although the only simple
way I could think of verifying it was working was to enable tracing on
traceflags encrypt and encryptdetail and checking for AES128 comms), and
will take a look at the Solaris TDPO as soon as I can.

The storage of the encryption key within the TSM server database (i.e.
not on the client itself as with the 'traditional' TSM encryption) is
interesting, and does make me think about the possibility of managing
offsite TSM DB backups separately (i.e. different physical location)
from our offsite data tapes... At least, that's what I think security
might pick up on when we run this past them...

Rgds,

David McClelland
Reuters
-----Original Message-----
From: David McClelland 
Sent: 22 April 2005 14:38
To: 'ADSM: Dist Stor Manager'
Subject: TSM 5.3, AES-128 encryption and API/TDP backups

 Hi Guys,

Just a quicky - is anyone out here using the 128-bit AES encryption
capabilities of the 5.3 API to encrypt TDPOracle on Solaris or TDPSQL
backup? I believed this was possible in 5.3, but I'm not having many (or
in fact any) hits in the online docs (or IBM.com or ADSM.org) trying to
find out how to get this working, only how to get the BA client to
encrypt via encryptiontype, include.encrypt etc.

As ever, any help or pointers gratefully received.

Many thanks,

David McClelland
IBM Certified Deployment Professional TSM 5.2 Tivoli Storage Manager
Certified Consultant Infrastructure Backup and Recovery Development
Shared Infrastructure Development Reuters
85 Fleet Street
London EC4P 4AJ


-----------------------------------------------------------------
        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.