Hot Diggety! Koen Willems was rumored to have written: Apparently, it was bad tapes. Interesting. Guess that makes sense. Nah, wasn't planning to. The backups are fast enough that we wouldn't have an
Hot Diggety! David Longo was rumored to have written: Looks like two bad tapes in the 3570 library. Thanks! Going to store them in the 'rejects pile' until I can legally have them degaussed and then
Hot Diggety! David Longo was rumored to have written: Niiice! Sounds like bulk of data must be ASCII or something easily compressible with repeatable data. Thanks, using FORMAT=ULTRIUMC and it now in
Couple unrelated questions: 1. When I query a 3570 library, there's one tape that baffles me: Library Name Volume Name Status Last Use Home Element -- -- -- -- -- 3570LIB1 133060 Private 34 I can't d
Author: "Cook, Dwight E" <DWIGHT.E.COOK AT SAIC DOT COM>
Date: Tue, 27 Aug 2002 04:30:37 -0700
Tapes like this generally become this way due to some error such as not being able to read the volume's internal label when mounted to fill a scratch request. There is some TSM message that is along
Author: Koen Willems <koen_willems AT HOTMAIL DOT COM>
Date: Tue, 27 Aug 2002 13:16:48 +0000
Dear reader, Maybe that the access state is "unavaileble" try "q vol f=d" look at the access state if it is not in a readw state use "update vol XXXX access=readwrite" Then do a move data on the volu
Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Tue, 27 Aug 2002 10:06:45 -0400
For question 2, on my 3584 drives I have the FORMAT=ULTRIUMC and it uses comperssion. I'm getting about 275GB average on my tapes (IBM tapes), have gotten nearly 400GB on some! David Longo Couple unr
Author: Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Date: Tue, 27 Aug 2002 14:09:23 +0200
This could also occur when you checkin a scratch tape, without setting the status to scratch. However, as I remember it, you only have to update the library volume using upd libvol "library_name" "vo
Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Tue, 27 Aug 2002 09:48:45 -0400
My experience with tapes in this condition is that the "write protect" tab was set on by accident. AS Dwighty check the tape out. Then check the Write Protect. If it is on, then set it off and check
Author: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
Date: Wed, 28 Aug 2002 16:52:53 +0300
Dan, David already answered to question 2 but as an additional remark - when TSM started to write a tape volume uncompressed the tape has to become back scratch to start write on it with compression.