Sorry - I should have mentioned this is Redhat Linux
On Tue, Sep 3, 2013 at 11:42 AM, Billaudeau, Pierre <[email protected]>wrote: > Hi Zoltan, > Is the drive encryption enabled at the OS level. On E05 drives, I > had to update our AIX server drive definition: > chdev -l 'rmt6' -a wrt_encryption='on' > I did not have to change anything to our new E07 drive, I guess > they were set OK. > > Pierre Billaudeau > SAQ > Montreal > > -----Message d'origine----- > De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de > Zoltan Forray > Envoyé : 3 septembre 2013 11:15 > À : [email protected] > Objet : Re: [ADSM-L] Enabling Encryption in TS3500/E06 Drives > > Well, contrary to the response I received about this being as simple as > changing the devclass value, I can not get encryption to work. > > I changed the devclass to DRIVEENCRYPTION=ON and the first attempt to > write a new tape fails with: > > 9/3/2013 9:59:03 AM ANR8985E The drive 7876475 > (/dev/lin_tape/by-serial/000007876475) in library TS3500-COPY is using an > encryption method that is incompatible with the current server settings. > > So, I figured I would check the hardware settings of the TS1130 -E06 > drives. They were all set to NO ENCRYPTION. I changed this to APPLICATION > and figured that would take care of it. No such luck. Same errors. > > Tried resetting/cycling the drives - still nothing. > > Tried taking all drives and paths offline, figuring this might > reset/retrieve the new drive setting - still nothing - same errors. > > Is there some library (TS3500) setting that may be blocking this? > > So, what I am missing? > > > > > On Tue, Aug 20, 2013 at 12:34 PM, Zoltan Forray <[email protected]> wrote: > > > Well, the saga is coming to a conclusion and I am going to active > > encryption of offsite tapes, via AME/TSM. > > > > Is there anything more I need to do besides update the DEVCLASS to > > DRIVEENCRYPTION=ALLOW on all of my TSM servers? > > > > When I check the drive details via the TS3500 interface, is says > > encryption is disabled? Do I need to go to each drive and enable it? > > > > -- > > *Zoltan Forray* > > TSM Software & Hardware Administrator > > Virginia Commonwealth University > > UCC/Office of Technology Services > > [email protected] - 804-828-4807 > > Don't be a phishing victim - VCU and other reputable organizations > > will never use email to request that you reply with your password, > > social security number or confidential personal information. For more > > details visit http://infosecurity.vcu.edu/phishing.html > > > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [email protected] - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html > > ------------------ > > > Information confidentielle : Le présent message, ainsi que tout fichier > qui y est joint, est envoyé à l'intention exclusive de son ou de ses > destinataires; il est de nature confidentielle et peut constituer une > information privilégiée. Nous avertissons toute personne autre que le > destinataire prévu que tout examen, réacheminement, impression, copie, > distribution ou autre utilisation de ce message et de tout fichier qui y > est joint est strictement interdit. Si vous n'êtes pas le destinataire > prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel > et supprimer ce message et tout document joint de votre système. Merci. > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
