ADSM-L

Re: [ADSM-L] IBM3592-E06 resp. TS1130

2010-11-05 10:12:49
Subject: Re: [ADSM-L] IBM3592-E06 resp. TS1130
From: Matthias Feyerabend <M.Feyerabend AT GSI DOT DE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 5 Nov 2010 15:12:10 +0100
There is backward compatibility to E05 from E06. The new drives can read and write the old tapes.
No problem using the old tapes.
I am only trying to write as much as possible on my tapes.

Yours

Matthias

Am 11/5/10 2:23 PM, schrieb Huebschman, George J.:
There is no backward compatibility from E05 to E06?
If that is the case you might want to create a new library for the E06 media.  
You could also limit the tape volser ranges available to the new drives.

I'd expect that if a drive loaded a tape with an incompatible format, it would 
recognize that.  Is that not the case?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Matthias Feyerabend
Sent: Friday, November 05, 2010 9:15 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] IBM3592-E06 resp. TS1130


   Hello,

we replaced our IBM3592-E05 with new IBM3592-E06. On long media (JB)
they store 1 TB instead 700 GB which is almost 50 % more.

My question is
"How to distinguish E05 written media from E06 written ?"

First approach is to look when the first file was written. If it is
after our replacement of the drives, it has to be in E06 format.
TSM only provides me of the last written date, but if some files are
already written in E05 format I suspect that for the rest of the tape
the format will not be changed and written in E05-Format, too.

Is there some way to recognize if a given tape is written in E05 or E06
format ?

My second question relates to the first one.
My plan is to set E05 written tapes to READONLY and do a move data for
each volume in E05-format  to get all data newly written in E06 format.

Something more clever than that ?


Matthias

--
--
Matthias Feyerabend                                | M.Feyerabend AT gsi DOT de
GSI Helmholtzzentrum für Schwerionenforschung GmbH | phone +49-6159-71-2519
Planckstr. 1                                       | privat +49-6151-718781
D-64291 Darmstadt                                  | fax   +49-6159-71-2519
www.gsi.de
Gesellschaft mit beschränkter Haftung
Sitz der Gesellschaft: Darmstadt
Handelsregister: Amtsgericht Darmstadt, HRB 1528

Geschäftsführung: Professor Dr. Dr. h.c. Horst Stöcker,
Dr. Hartmut Eickhoff

Vorsitzende des Aufsichtsrates: Dr. Beatrix Vierkorn-Rudolph
Stellvertreter: Ministerialdirigent Dr. Rolf Bernhardt

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.


--
--
Matthias Feyerabend                                | M.Feyerabend AT gsi DOT de
GSI Helmholtzzentrum für Schwerionenforschung GmbH | phone +49-6159-71-2519
Planckstr. 1                                       | privat +49-6151-718781
D-64291 Darmstadt                                  | fax   +49-6159-71-2519
www.gsi.de
Gesellschaft mit beschränkter Haftung
Sitz der Gesellschaft: Darmstadt
Handelsregister: Amtsgericht Darmstadt, HRB 1528

Geschäftsführung: Professor Dr. Dr. h.c. Horst Stöcker,
Dr. Hartmut Eickhoff

Vorsitzende des Aufsichtsrates: Dr. Beatrix Vierkorn-Rudolph
Stellvertreter: Ministerialdirigent Dr. Rolf Bernhardt

<Prev in Thread] Current Thread [Next in Thread>