Results 1 to 6 of 6
Thread: Application Level Encryption
-
05-15-2009, 12:52 PM #1Newcomer
- Join Date
- Sep 2008
- Posts
- 9
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Application Level Encryption
Hello,
We are attempting to implement application level encryption in the following environment...
IBM TS3500 Tape Library, Firmware level 8750; with ALMS installed.
LTO4 Ultrium drives, Firmware level 89B2
AIX 5.3.2 server, TSM server 5.4.1
After encryption is enabled, we continually get the following pair of errors when attempting a restore (backup works fine): The errors occur with different volumes, and all 12 drives.
ANR8302E I/O error on drive DRIVE01 (/dev/rmt3) with
volume SS3145 (OP=READ, Error Number=47, CC=0, KEY=07,
ASC=74, ASCQ=01, SENSE=F0.00.07.00.00.00.50.58.00.00.00.-
00.74.01.30.00.11.88.A1.00.00.01.53.43.33.31.36.37 .4C.00-
.00.00.07.CA.32.00.00.00.00.00.80.08.60.00.00.00.0 0.00.0-
0.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00. 00.00.-
00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00 .00.00-
.38.39.42.32.00.00.00.00.00.00, Description=An
undetermined error has occurred). Refer to Appendix C in
the 'Messages' manual for recommended action. (SESSION:
8714)
ANR8355E I/O error reading label for volume SS3145 in
drive DRIVE01 (/dev/rmt3). (SESSION: 8714)
If you have implemented application level encryption in a similar environment, and you overcame the above errors, please let me know.
Did or did you not have to install Feature Code 1604?
Thanks
-
05-15-2009, 12:56 PM #2Moderator
- Join Date
- Sep 2002
- Location
- Indiana
- Posts
- 2,560
- Thanks
- 0
- Thanked 1 Time in 1 Post
Have you tried to relabel a tape after enabling encryption?
-AaronThree things are certain:
Death, taxes, and lost data.
Guess which has occurred.
-
05-15-2009, 10:06 PM #3Member
- Join Date
- Feb 2007
- Location
- Pacific NW...USA
- Posts
- 206
- Thanks
- 0
- Thanked 2 Times in 2 Posts
You do not need the 1604 feature code to use application-based encryption with TSM.
You shouldn't need to relabel tapes either.
It also looks like you are running a version of TSM Server that supports LTO4 encryption.
Does the device class for your encrypted library/drives have the drive encryption flag set to yes?
The switch --> drivee=yes
-
05-20-2009, 12:56 PM #4Newcomer
- Join Date
- Sep 2008
- Posts
- 9
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Aaron, yes we did try to relabel a tape. If it had been encrypted, you cannot relable it. If it is new tape, no problem.
Thanks
-
05-20-2009, 12:59 PM #5Newcomer
- Join Date
- Sep 2008
- Posts
- 9
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Yes, the parameter drive encryption is set to on.
-
06-30-2009, 12:46 PM #6Newcomer
- Join Date
- Sep 2008
- Posts
- 9
- Thanks
- 0
- Thanked 0 Times in 0 Posts
application level encryption fixed
We were finally able to get this up and running. Tests showed that you could read the tape thaty was encrypted, as long as the tape went to the same drive that you used when it was written to.
IBM researched this problem, and we upgraded to TSM server Version 5, Release 4, Level 5.0. After this, the encryption has worked with no problem
Thanks
Similar Threads
-
%1 is not a valid win32 application
By efclem in forum Administrative ClientReplies: 2Last Post: 10-26-2006, 09:39 AM -
Any conflict with Clearcase application......
By sujith in forum Performance TuningReplies: 0Last Post: 09-13-2006, 12:52 AM -
TDP Domino Application Errors
By gavsta in forum DominoReplies: 4Last Post: 06-28-2005, 08:18 AM -
ANR4740W Either the high level address, low level address,
By jaycsimon in forum Backup / Archive DiscussionReplies: 1Last Post: 04-21-2005, 05:27 AM -
Reporting in NT Application Log
By nl33855 in forum TDP/Application Layer BackupReplies: 2Last Post: 08-27-2003, 01:05 PM


Reply With Quote
