1) Label all of your tapes with a different volume id. 2) Run this to reset your figures: PRTERRLOG TYPE(*VOLSTAT) + VOLTYPE(3580) + VOLSTAT(*DLT) 3) Add the command from step 2 to the end of your backup. Does this help? Sample from our system, (3590 instead of 3580, but I think it generates the same report because both 3590's and 3580's are on the report): Title . . . . . . . . . . : Volume Statistics Report System type . . . . . . . : 9406 System model . . . . . . : 840 System release . . . . . : V5R2M0 System name . . . . . . . : GDIHQ System serial number . . : 10-3BD4M Report type . . . . . . . : Lifetime Report Removable media . . . . . : Self-configured tape and 1/4 inch cartridge tape Volume ---Temporary Errors--- --------K Bytes-------- ID Read Write Read Written 3FRI21 0 18 23 48978721 3FRI11 0 12 32 52770571 4FRI1 0 0 56 114890836 4FRI2 0 0 58 125937505 4FRI3 0 0 52 114124753 4FRI4 0 0 52 112985461 4FRI5 0 0 34 73269506 6FRI1 0 0 56 114596248 6FRI2 0 0 55 119812393 6FRI3 0 0 54 116376877 6FRI4 0 0 52 113274001 6FRI5 0 0 40 86509838 >> indicates media replacement is recommended > indicates media replacement criteria should be checked I didn't include them all. The first two are 3590's. The rest are 3580's. The 3580's are saving Tivoli Storage Manager data, which is already highly compressed as it sits on disk. The TSM data is all in a library called PCBACKUP. Summing up the size of all objects in PCBACKUP comes to 1,117,712,404kb. Summing up the 3580 save bytes above adds up to 1,091,777,418kb. A difference of 25,934,986kb or 26gb. 25,934,986/1,117,712,404 = 2% compression. Like I said, that TSM data is already pretty compressed. We use two 3580's: TAP04, TAP06. We store the names of all the objects in PCBACKUP, sorted by size descending, into a data queue and the two tape drives take turns processing that data queue for objects to save. This is why 4FRI5 and 6FRI5 have less then their previous tapes - they were the last tape in the sequence. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jones, John (US)" <John.Jones@xxxxxxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 03/08/2004 08:55 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Subject RE: UPS & Tape Drive We bought two 3580-H23s for each of systems, a our 730-2067 (4-way) & a 830-2400 (2-way) last summer. Ultrium2, 200GB native, etc. as everyone else has said. I bench-tested the backup speed on both systems and got 70GB/hour on the 730 and 203GB/hour on the 830. The machines are comparable in CPW (2000 & 1850 respective) but the PCI-type bus made a world of difference. The saves were performed on non-dedicated but fairly idle systems, so the numbers could fluctuate a little. The save was of our JDE data libraries and not the entire system. Throughput is somewhat less when saving the entire system, but it's still way faster than the drives they replaced. Also, we are currently getting the entire system save on a single tape with room to spare. H23s are all that can be attached to an SPD box like our 730. The reason we went with H23s vs. L23s on the 830 was that the LVD tape controller required V5R2 and we just weren't ready to make that jump yet as we had app issues holding us back. A quick question for other LTO2 users: How much data have you gotten on the tapes before it asks for volume 2 of a save? IOW are you getting the normal advertised 2-1 compression or something different? On our old BCC AIT drives we would always get about 3.8-1 overall and I'm wondering if I can expect the same from the LTO2s (760ish GB/tape compressed). This email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.