Re: [ADSM-L] How to check encryption
2009-03-27 07:27:54
While physically verifying encryption can be done, it is time-
consuming (client tracing, inspecting files on TSM volumes, attempting
recall without key). A wise thing to do at the administrative level
is to employ a management class whose name includes indication of
encryption, and to set up client Include specs which use this class
name. Then, once stored on the TSM server, querying for the
management class name from the client or server will clearly indicate
that encryption was at least intended, if not actually realized.
Richard Sims
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [ADSM-L] define path problems, (continued)
- Re: [ADSM-L] define path problems, Dennis, Melburn (IT Solutions US)
- Re: [ADSM-L] define path problems, Alexander Lazarevich
- Re: [ADSM-L] define path problems, Alexander Lazarevich
- Re: [ADSM-L] define path problems, Richard Sims
- Re: [ADSM-L] define path problems, Dennis, Melburn (IT Solutions US)
- Re: [ADSM-L] define path problems, Alexander Lazarevich
- Re: [ADSM-L] define path problems, Kelly Lipp
- Re: [ADSM-L] define path problems, Kelly Lipp
- [ADSM-L] How to check encryption, Steven Harris
- Re: [ADSM-L] How to check encryption, David McClelland
- Re: [ADSM-L] How to check encryption,
Richard Sims <=
- Re: [ADSM-L] How to check encryption, Andrew Raibeck
- Re: [ADSM-L] How to check encryption, Richard Sims
- Re: [ADSM-L] How to check encryption, Francisco Molero
- Re: [ADSM-L] define path problems, Alexander Lazarevich
- Re: [ADSM-L] define path problems, Richard Sims
|
|
|