Using hardware encryption, managed by TSM. Are you saying I can have two device classes sharing the same devices? For some reason, I was always under the impression that you couldn't. But after scanning the help, I don't know where I came up with that notion. That would definitely make things simple for me.
Thanks. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Tuesday, January 12, 2010 10:20 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Turning Encryption Off/On Is your encryption application-managed (controlled by TSM) or library-managed (controlled by EKM/TKLM)? If application managed, IBM is correct, you just need a different devclass that specifies drive encryption OFF, pointing to the same library, and a new storage pool that specifies the non-encrypted devclass. . I've got 4 LTO drives, onsite pool is NOT encrypted (long story there), COPY pool IS encrypted. No biggie. W On Tue, Jan 12, 2010 at 9:10 AM, Druckenmiller, David <druc...@mail.amc.edu>wrote: > We currently encrypt all our offsite tapes. Mgmt wants to me create a > single unencrypted archive tape to be stored offsite long term for > litigation reasons. > > My question is: If I turn off encryption long enough to get some data > written to this one tape, then turn encryption back on, could I then > continue to write uncrypted data to this one tape while all other tapes > would be encrypted? > > IBM is being non-committal saying we should really use new device class, > but I'd then have to move one tape drive over to new class each time I want > to write unencrypted. > > TSM 5.5.3 > AIX 6.1 > Tapes are LTO4 > > Thanks > Dave > > ----------------------------------------- > CONFIDENTIALITY NOTICE: This email and any attachments may contain > confidential information that is protected by law and is for the > sole use of the individuals or entities to which it is addressed. > If you are not the intended recipient, please notify the sender by > replying to this email and destroying all copies of the > communication and attachments. Further use, disclosure, copying, > distribution of, or reliance upon the contents of this email and > attachments is strictly prohibited. To contact Albany Medical > Center, or for a copy of our privacy practices, please visit us on > the Internet at www.amc.edu. >
