ADSM-L

Re: [ADSM-L] Activate SKLM on existing TS3500 partition

2015-11-10 09:21:42
Subject: Re: [ADSM-L] Activate SKLM on existing TS3500 partition
From: Kevin Boatright <BoatrKe1 AT MEMORIALHEALTH DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 Nov 2015 14:18:33 +0000
We only relabel scratch on our VTL.  On the 3500 physical library, we don't 
relabel the tapes.  Once a scratch tape is mounted, it will encrypt the data on 
that tape.  When we implemented the TKLM encryption, I created another copypool 
to speed up the process just to get all of the tapes encrypted quickly.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Maurice van 't Loo
Sent: Wednesday, November 04, 2015 5:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Activate SKLM on existing TS3500 partition

Hello Kevin,

Thanks for your answer. It entered in my spambox, so it took a while before I 
noticed it :-)

So if I understand well, we can safely activate encryption on our existing 
library partition.
But do we need to use "relabel scratch" on the library definition in TSM?
Or does the robot recognise the use of normal scratch tapes without relabel as 
well?

Thanks,
Maurice

2015-10-21 22:34 GMT+02:00 Kevin Boatright <BoatrKe1 AT memorialhealth DOT com>:

> Once you enable encryption on the tape library, it will encrypt the
> data as it mounts the scratch tapes.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Plair, Ricky
> Sent: Wednesday, October 21, 2015 3:45 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Activate SKLM on existing TS3500 partition
>
> Hey Maurice,
>
> Did anyone reply to your email?
>
> We are performing about the same thing. We have the SKLM server built
> and we are migrating from EKM.
>
> Rick
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Maurice van 't Loo
> Sent: Wednesday, October 14, 2015 8:29 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Activate SKLM on existing TS3500 partition
>
> Friends,
>
> We currently have TSM 7.1.1.3 with TS3500's and LTO6 drives in use.
> SLKM server is build and tested successfully.
>
> Now we want to activate tape encryption.
>
> Can we just activate it on the library partition that is already in use?
> Will it start using encryption when a new scratch tape is used? Or
> when we relabel a volumes?  (relabel scratch)
>
> Thanks,
> Maurice van 't Loo
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ CONFIDENTIALITY NOTICE: This email message, including any
> attachments, is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information and/or Protected
> Health Information (PHI) subject to protection under the law,
> including the Health Insurance Portability and Accountability Act of
> 1996, as amended (HIPAA). If you are not the intended recipient or the
> person responsible for delivering the email to the intended recipient,
> be advised that you have received this email in error and that any
> use, disclosure, distribution, forwarding, printing, or copying of
> this email is strictly prohibited. If you have received this email in
> error, please notify the sender immediately and destroy all copies of the 
> original message.
> "This electronic mail message contains information which may be
> confidential, privileged and protected from further disclosure. Such
> information relates to and is used for all purposes outlined in the
> statutes below, including Peer Review, Performance Improvement,
> Quality Assurance and Claims Management and Handling functions and/or
> Attorney-Client Communications. It is being produced within the scope
> of all Georgia and Federal laws governing record confidentiality,
> including (but not limited to) Official Code of Georgia Annotated
> Sections 31-7-15; 31-7-130; 31-7-131; 31-7-132; 31-7-133; 31-7-140;
> 31-7-143. If you are not the intended recipient, please be aware that
> any disclosure, photocopying, distribution or use of the contents of
> the received information is prohibited. If you have received this
> e-mail in error, please reply to the sender immediately and
> permanently delete this message and all copies of it. Thank you.
> Communication of electronic protected health information
> (ePHI) is protected under the Health Insurance Portability and
> Accountability Act (HIPAA) Act of 1996. Electronic mail (e-mail)
> communication is not encrypted or secure. The HIPAA Security Rule
> allows for patients to initiate communication of personal health
> information over this medium and for providers to respond accordingly
> with the understanding that privacy of communication is not guaranteed."
>
"This electronic mail message contains information which may be confidential, 
privileged and protected from further disclosure. Such information relates to 
and is used for all purposes outlined in the statutes below, including Peer 
Review, Performance Improvement, Quality Assurance and Claims Management and 
Handling functions and/or Attorney-Client Communications. It is being produced 
within the scope of all Georgia and Federal laws governing record 
confidentiality, including (but not limited to) Official Code of Georgia 
Annotated Sections 31-7-15; 31-7-130; 31-7-131; 31-7-132; 31-7-133; 31-7-140; 
31-7-143. If you are not the intended recipient, please be aware that any 
disclosure, photocopying, distribution or use of the contents of the received 
information is prohibited. If you have received this e-mail in error, please 
reply to the sender immediately and permanently delete this message and all 
copies of it. Thank you. Communication of electronic protected health 
information (ePHI) is protected under the Health Insurance Portability and 
Accountability Act (HIPAA) Act of 1996. Electronic mail (e-mail) communication 
is not encrypted or secure. The HIPAA Security Rule allows for patients to 
initiate communication of personal health information over this medium and for 
providers to respond accordingly with the understanding that privacy of 
communication is not guaranteed."
<Prev in Thread] Current Thread [Next in Thread>