Strange filesize after export/import
Hi, we are just testing the migration of a TSM 5.1.9.5 (AIX 4.3) to a TSM 5.2.7.2 (AIX 5.2). So far everything seems OK, policies and data were exported and imported just fine, but I noticed a discrepancy in the file sizes shown in a select from contents for ALL files (data are from a ContenManager)! This is an example: On the old TSM tsm: ECKWANDselect * from contents where file_name='/MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD' VOLUME_NAME: /tivoli1/stgpool/archiv_po4_1_file01 NODE_NAME: ARCHIV_PO TYPE: Bkup FILESPACE_NAME: /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1 FILE_NAME: /MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD AGGREGATED: No FILE_SIZE: 56210 SEGMENT: CACHED: No FILESPACE_ID: 6 FILESPACE_HEXNAME: FILE_HEXNAME: After the import on the new TSM: tsm: TEST-KANDELselect * from contents where file_name='/MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD' VOLUME_NAME: /usr/local/tsm/server2/data/apo4_01 NODE_NAME: ARCHIV_PO TYPE: Bkup FILESPACE_NAME: /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1 FILE_NAME: /MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD AGGREGATED: 124/256 FILE_SIZE: 11195180 SEGMENT: CACHED: No FILESPACE_ID: 1 FILESPACE_HEXNAME: FILE_HEXNAME: Note the difference in FILE_SIZE: 56210 vs. 11195180! This seems strange! And what does the difference in the field AGGREGATED mean (No vs. 124/256)? Interestingly enough, I can restore the object from the new TSM and inspect it in a viewer (it's a TIFF) just fine. The dsmc query shows it as: tsm query backup /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1//MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1AKKDBJHB.DMD Size Backup DateMgmt Class A/I File ----- --- API 55,858 B 03/25/01 00:11:12MC_ARCHIV_ A /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1AKKDBJHB.DMD Another thing is puzzeling me: the blank in the filename in the select, which is not appearing in the query backup result. Any hints? TIA Andreas
Re: inventory expiration time
Richard Hammersley schrieb: The machine is a new dual processor P520 with 4 gig of memory attached to an EMC cx300 san. We also have a p520, but with 12 GB of memory. We're running TSM 5.3.3 on AIX 5.3. Our inventory expiration runs once a week and takes more than 6 hours to complete: ANR0812I Inventory file expiration process 4218 completed: examined 7907625 objects, deleting 1416779 backup objects, 191 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
AW: inventory expiration time
4CPU, Windows2003, 4GB Ram, CX700 Disks Raid5 (shared, 10k), TSM 5.3.2 During the same time there is expiration from an other smaller instance on the same machine that lasts about an hour. Regards Stefan Holzwarth DB Speed Expiration ACTIVITY Date Examined Objects Examined Up/Hr EXPIRATION 2006-06-27 2430008 925200 EXPIRATION 2006-06-28 2404404 1083600 EXPIRATION 2006-06-29 2453121 993600 EXPIRATION 2006-06-30 2535449 928800 EXPIRATION 2006-07-01 2600885 835200 EXPIRATION 2006-07-02 2751620 1004400 EXPIRATION 2006-07-03 2913433 99 EXPIRATION 2006-07-04 2560030 946800 EXPIRATION 2006-07-05 2568634 1098000 EXPIRATION 2006-07-06 2619294 1198800 EXPIRATION 2006-07-07 2835640 1044000 EXPIRATION 2006-07-08 2922019 932400 EXPIRATION 2006-07-09 3152030 1177200 EXPIRATION 2006-07-10 3307528 1004400 EXPIRATION 2006-07-11 2942075 1036800 EXPIRATION 2006-07-12 2947009 1134000 EXPIRATION 2006-07-13 3077056 914400 EXPIRATION 2006-07-14 3003355 878400 EXPIRATION 2006-07-15 2888349 972000 EXPIRATION 2006-07-16 3059609 1245600 EXPIRATION 2006-07-17 3226511 117 EXPIRATION 2006-07-18 2994471 968400 EXPIRATION 2006-07-18 2653356 2469600 EXPIRATION 2006-07-19 2937517 1011600 EXPIRATION 2006-07-20 2874305 1137600 EXPIRATION 2006-07-20 2585014 2818800 EXPIRATION 2006-07-21 3125122 882000 EXPIRATION 2006-07-22 3130365 828000 EXPIRATION 2006-07-23 3262415 1245600 EXPIRATION 2006-07-24 3308901 1245600 EXPIRATION 2006-07-25 3038719 1227600 EXPIRATION 2006-07-26 2990903 943200 EXPIRATION 2006-07-27 2971022 1296000 -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Dirk Kastens Gesendet: Freitag, 28. Juli 2006 08:30 An: ADSM-L@VM.MARIST.EDU Betreff: Re: inventory expiration time Richard Hammersley schrieb: The machine is a new dual processor P520 with 4 gig of memory attached to an EMC cx300 san. We also have a p520, but with 12 GB of memory. We're running TSM 5.3.3 on AIX 5.3. Our inventory expiration runs once a week and takes more than 6 hours to complete: ANR0812I Inventory file expiration process 4218 completed: examined 7907625 objects, deleting 1416779 backup objects, 191 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470
Re: CAN RESTORE ACTIVITY BE TRACED?
Laura - Use the TSM Problem Determination Guide, which has been cited in numerous postings. Richard Sims On Jul 27, 2006, at 11:37 AM, Laura Mastandrea wrote: Running TSM 5.2.4 on AIX 5.3 and restoring a Windows 2000 Advanced server client. The filespace is on tape in a non-colocated storage pool. The tape library is a 3584 with LTO3 drives. It takes about 3 hours to restore 7 GB of compressed data. I can monitor by doing q se f=d, but for three hours I can't do this. The server at the time was not busy with other tape activity that I could see. Is there a trace I can run on this a restore to see what is taking so long? Is there a SQL Select that would give me where the time was spent for this restore or is my only source the activity log? Thank you for your assistance. Laura Mastandrea DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. This communication does not form any contractual obligation on behalf of the sender or, the sender's employer, or the employer's parent company, affiliates or subsidiaries.
Re: Strange filesize after export/import
On Jul 28, 2006, at 2:20 AM, Andreas Priebe wrote: ... Note the difference in FILE_SIZE: 56210 vs. 11195180! This seems strange! And what does the difference in the field AGGREGATED mean (No vs. 124/256)? ... Another thing is puzzeling me: the blank in the filename in the select, which is not appearing in the query backup result. Andreas - See CONTENTS in http://people.bu.edu/rbs/ADSM.QuickFacts for the basics on this. The FILE_SIZE has not reflected client file size since ADSMv3. FILE_SIZE is the Aggregate size, which is also known as the Physical size. If you're familiar with MVS file blocking, then this is would be a familiar concept. It's a means of gaining greater throughput by collecting and writing multiple smaller files as a larger clump. In your old system, as data expired within an Aggregate, a single enduring file may be the sole survivor in an Aggregate. Reclamation, and Move Data with Reconstruct=Yes, will compact an Aggregate such that the Aggregate size may coincidentally become equal to the client file size; but that's a relatively rare condition, seen with old data. The blank is a Select report convention for the Contents table which separates the directories nest from the ultimate file. (The syscat.columns Remark column misleadingly says that this is Client's Name for File, when in fact it is Directories + Space + Filename.) The intervening directories are known elsewhere in TSM SQL as the HL_NAME. Richard Sims
Restore in DR site is very slow
Production side: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 8 LTO3 drives DB2 database: 8.2, 1.2TB with 7 backup drives, backup time 1.2 hour offisite copy, 2 processes, with 4 drives. DR site: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 4 LTO3 drives My problem is, when I did twice restore test, the first time it used 4 drives to do restore, used 5 hours to restore. The second test, it only used 2 drives to do restore and it used 12 hours. My question is, how can I ensure the restore can constantly use 4 drives to do restore? TIA.
Fw: Restore in DR site is very slow
Increase the number of processes used for the offsite copy. With only 2 processes, you have 2 target tapes, so the data may only be on 2 tapes in the copypool. If you use more processes, you're more likely to have the data spread across more tapes. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 07/28/2006 08:31 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/28/2006 07:54:05 AM: Production side: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 8 LTO3 drives DB2 database: 8.2, 1.2TB with 7 backup drives, backup time 1.2 hour offisite copy, 2 processes, with 4 drives. DR site: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 4 LTO3 drives My problem is, when I did twice restore test, the first time it used 4 drives to do restore, used 5 hours to restore. The second test, it only used 2 drives to do restore and it used 12 hours. My question is, how can I ensure the restore can constantly use 4 drives to do restore? TIA.
Failure: return code 4 ?
I rec'd a failure last night for one of my backups. Following is the pertinent section of the act log: Date/TimeMessage -- 07/27/06 22:30:04 ANR2561I Schedule prompter contacting PROVTSM (session 11866) to start a scheduled operation. (SESSION: 47) 07/27/06 22:30:06 ANR0403I Session 11866 ended for node PROVTSM (). (SESSION: 47) 07/27/06 22:30:06 ANR0406I Session 11867 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64003)). (SESSION: 11867) 07/27/06 22:30:12 ANR0406I Session 11868 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64004)). (SESSION: 11868) 07/27/06 22:33:08 ANR0403I Session 11868 ended for node PROVTSM (AIX). (SESSION: 11868) 07/27/06 22:33:09 ANE4952I (Session: 11867, Node: PROVTSM) Total number of objects inspected: 65,454 (SESSION: 11867) 07/27/06 22:33:09 ANE4954I (Session: 11867, Node: PROVTSM) Total number of objects backed up: 228 (SESSION: 11867) 07/27/06 22:33:09 ANE4958I (Session: 11867, Node: PROVTSM) Total number of objects updated: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4960I (Session: 11867, Node: PROVTSM) Total number of objects rebound: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4957I (Session: 11867, Node: PROVTSM) Total number of objects deleted: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4970I (Session: 11867, Node: PROVTSM) Total number of objects expired: 5 (SESSION: 11867) 07/27/06 22:33:09 ANE4959I (Session: 11867, Node: PROVTSM) Total number of objects failed: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4961I (Session: 11867, Node: PROVTSM) Total number of bytes transferred:94.41 MB (SESSION: 11867) 07/27/06 22:33:09 ANE4963I (Session: 11867, Node: PROVTSM) Data transfer time:1.00 sec (SESSION: 11867) 07/27/06 22:33:09 ANE4966I (Session: 11867, Node: PROVTSM) Network data transfer rate:95,810.94 KB/sec (SESSION: 11867) 07/27/06 22:33:09 ANE4967I (Session: 11867, Node: PROVTSM) Aggregate data transfer rate:527.73 KB/sec (SESSION: 11867) 07/27/06 22:33:09 ANE4968I (Session: 11867, Node: PROVTSM) Objects compressed by:0% (SESSION: 11867) 07/27/06 22:33:09 ANE4964I (Session: 11867, Node: PROVTSM) Elapsed processing time:00:03:03 (SESSION: 11867) 07/27/06 22:33:09 ANR2579E Schedule PROVTSM in domain AIX for node PROVTSM failed (return code 4). (SESSION: 11867) 07/27/06 22:33:09 ANR0403I Session 11867 ended for node PROVTSM (AIX). (SESSION: 11867) 07/27/06 22:33:10 ANR0406I Session 11872 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64005)). (SESSION: 11872) 07/27/06 22:33:10 ANR0403I Session 11872 ended for node PROVTSM (AIX). (SESSION: 11872) I cannot see any other evidence of the failure. Could someone help? Also I tried to run dsmc i this morning but it started backiing up directories that were excluded in the inclexcl.def file. Does anyone know why this may have happened? Thanks! Dave Zarnoch [EMAIL PROTECTED] _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
Re: Failure: return code 4 ?
Look up the help information for message ANR2579E, that will give you some direction. Also would be helpful to know the full server and client versions you are using, output from Q EV F=D for this event and node name, and Q SCHED F=D for this schedule. Regarding the include/exclude question: more information is needed. Look at dsmc query inclexcl output to make sure that the directories are indeed excluded. Maybe someone changed the include-exclude file, or changed the inclexcl option to point to a different file, or changed a client option set on the server, or changed the node to use a different client option set, Or maybe your dsm.sys file has multiple stanzas, and you are using a stanza with different include-exclude settings. Or you might have EXCLUDE instead of EXCLUDE.DIR, etc. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/28/2006 06:00:09 AM: I rec'd a failure last night for one of my backups. Following is the pertinent section of the act log: Date/TimeMessage -- 07/27/06 22:30:04 ANR2561I Schedule prompter contacting PROVTSM (session 11866) to start a scheduled operation. (SESSION: 47) 07/27/06 22:30:06 ANR0403I Session 11866 ended for node PROVTSM (). (SESSION: 47) 07/27/06 22:30:06 ANR0406I Session 11867 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64003)). (SESSION: 11867) 07/27/06 22:30:12 ANR0406I Session 11868 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64004)). (SESSION: 11868) 07/27/06 22:33:08 ANR0403I Session 11868 ended for node PROVTSM (AIX). (SESSION: 11868) 07/27/06 22:33:09 ANE4952I (Session: 11867, Node: PROVTSM) Total number of objects inspected: 65,454 (SESSION: 11867) 07/27/06 22:33:09 ANE4954I (Session: 11867, Node: PROVTSM) Total number of objects backed up: 228 (SESSION: 11867) 07/27/06 22:33:09 ANE4958I (Session: 11867, Node: PROVTSM) Total number of objects updated: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4960I (Session: 11867, Node: PROVTSM) Total number of objects rebound: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4957I (Session: 11867, Node: PROVTSM) Total number of objects deleted: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4970I (Session: 11867, Node: PROVTSM) Total number of objects expired: 5 (SESSION: 11867) 07/27/06 22:33:09 ANE4959I (Session: 11867, Node: PROVTSM) Total number of objects failed: 0 (SESSION: 11867) 07/27/06 22:33:09 ANE4961I (Session: 11867, Node: PROVTSM) Total number of bytes transferred:94.41 MB (SESSION: 11867) 07/27/06 22:33:09 ANE4963I (Session: 11867, Node: PROVTSM) Data transfer time:1.00 sec (SESSION: 11867) 07/27/06 22:33:09 ANE4966I (Session: 11867, Node: PROVTSM) Network data transfer rate:95,810.94 KB/sec (SESSION: 11867) 07/27/06 22:33:09 ANE4967I (Session: 11867, Node: PROVTSM) Aggregate data transfer rate:527.73 KB/sec (SESSION: 11867) 07/27/06 22:33:09 ANE4968I (Session: 11867, Node: PROVTSM) Objects compressed by:0% (SESSION: 11867) 07/27/06 22:33:09 ANE4964I (Session: 11867, Node: PROVTSM) Elapsed processing time:00:03:03 (SESSION: 11867) 07/27/06 22:33:09 ANR2579E Schedule PROVTSM in domain AIX for node PROVTSM failed (return code 4). (SESSION: 11867) 07/27/06 22:33:09 ANR0403I Session 11867 ended for node PROVTSM (AIX). (SESSION: 11867) 07/27/06 22:33:10 ANR0406I Session 11872 started for node PROVTSM (AIX) (Tcp/Ip provtsm(64005)). (SESSION: 11872) 07/27/06 22:33:10 ANR0403I Session 11872 ended for node PROVTSM (AIX). (SESSION: 11872) I cannot see any other evidence of the failure. Could someone help? Also I tried to run dsmc i
Re: Configuring TSM on Sun Cluster
Have you received any replies ¿? Could re-send it ¿? Thanks, Iban Bernaldo De Quiros Y Marquez Technical Specialist Sun Microsystems, Inc. Serrano Galvache, 56 Madrid 28033 ES Phone +34 91 767 6233 Mobile + 34 659 01 91 12 Email [EMAIL PROTECTED] -Mensaje original- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de Paul Zarnowski Enviado el: martes, 18 de julio de 2006 21:09 Para: ADSM-L@VM.MARIST.EDU Asunto: [ADSM-L] Configuring TSM on Sun Cluster I know it's not officially supported, but has anyone figured out how to configure TSM in a Sun Cluster environment? Thanks. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Error reading label
Hi Everybody, We recently had a new rack addition installed in our 3494 library this Sunday. Since that was done, we have been getting about 75 scratch tapes since Monday being changed from scratch to a private state because of errors reading the label. I've checked about 30 of these tapes and they look fine. Has anyone run into this problem ? Could it be an alignment issue with the gripper ? Rich
Re: inventory expiration time
300 gig fibre channel attached through a brocade switch. raid5 9 spindles. topas shows between 94% and 100% busy for the hdiskpower0 device that has the database and only the database on it. 1500 to 3000 tps, 5000 to 1 KB-read Allen S. Rout wrote: On Thu, 27 Jul 2006 16:13:41 -0400, Richard Hammersley [EMAIL PROTECTED] said: The machine is a new dual processor P520 with 4 gig of memory attached to an EMC cx300 san. What's the underlying disk in the cx300? - Allen S. Rout
Re: Error reading label
On Jul 28, 2006, at 10:21 AM, Richard Mochnaczewski wrote: Hi Everybody, We recently had a new rack addition installed in our 3494 library this Sunday. Since that was done, we have been getting about 75 scratch tapes since Monday being changed from scratch to a private state because of errors reading the label. I've checked about 30 of these tapes and they look fine. Has anyone run into this problem ? Could it be an alignment issue with the gripper ? Rich Richard - I presume that this was a frame install, and is a barcode reading issue rather than success in picking, mounting, but media label reading issue. Barcode reading issues can result from failing to do a full Teach on the frame so that the accessor understands positioning therein, or (unlikely) a cell matrix has shifted since the install. The CE can inspect the 3494 logs to see what the issue is. I would verify conditions by first going to the 3494 LCD panel and checking that tapes known to be in that area are properly cataloged as such in the LM database. (Look for any anomalies in what it shows, relative to other tapes in other frames.) If the accessor will enter the new frame area, incite an attempt to mount a tape while you watch, and see if the laser scans the barcode region properly, compared with scanning barcodes in the more visible frame 1, for example. Another Richard
Integrated Solutiuons Console access problem
I just installed the Integrated Solutions Console for TSM and the Storage Manager Administration Center I entered a password during install for the icsadmin id and it won't accept it when I login via the http interface I made the password simple to start with and know that I am entering it right. How can I reset the password if I cant get in at all Tim Brown Systems Specialist Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: [EMAIL PROTECTED] Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
Audit restore storage volume tape
Hello, We were receiving the message below on a tape volume file in our primary storage pool during reclamation on 101645 processing causing it to fail. I performed a Audit Volume 101645 fix=yes on the volume in question. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 53454652 hdr version 0002 hdr length 0032 sequence number 0061 data length server id segment id 60002793965424476 48 crc 003D.(PROCESS: 187) ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0061 server id segment id 08602819.(PROCESS The following message is now reoccurring during reclamation on the same tape volume (101645) in our primary sequential pool and causing reclamation to fail. This started to occur after I performed a Audit Volume 101645 Fix=Yes on a tape. ANR1162W Space reclamation skipping damaged file on volume 100646: Node XX200, Type Backup, File space /u14, File name /oradat/archive/TSIC/ TSIC_1_88894_525973123.arc. ANR0985I Process 193 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at Reclamation of storage pool LPOOL has ended. Files reclaimed 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0. Question 1 - If I do a Restore Storage Pool volume for that tape and it will restore the damaged file (s) from the copy pool only. Is there any way to keep this volume from being marked destroyed since it's only the one file that is damaged automatically by TSM? Since there is only 1 file that is the problem. Question 2 - If the file on the copy pool volume is damaged also and causes the same message above after I do a Audit volume ## fix=? how do I get rid of the ANR1162W message that is appears for that ONE file which causes reclamation to fail? TSM 5.3.2 Thanks in Advance!
Backup DB2 with TSM
Hi, I have 2 servers connected to a DB2 server using a service IP (floating IP /virtual IP) where only one server will actively connect to the DB at one time.(When A down the Service IP will point to B, and B connect to DB.. Vice versa).These servers have their own IP. Currently I'm kind of confuses how to set the IP in the dsm.sys in the client and api folder and devconfig.out. I need to use the service IP/floating IP not the server IP itself. If I were to use the service IP for both servers then it would be conflicted. Any way, how I can set the IP using services IP so that these servers can run under the same schedule for filesystems backup? Thanks, Regards, Zareyna Salim Technical Consultant
Re: Audit restore storage volume tape
You can do a move volume and it should move all the good files. You may have to do this a couple of times. This should get all the good files off the tape. Now try the restore. If that wont work then the only thing is delete the volume with discard=yes and you have lost data. If it is current data on the system the next backup will pick it up. -- Phillip Ford Senior Software Specialist Enterprise Computing Services Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, July 28, 2006 10:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Audit restore storage volume tape Hello, We were receiving the message below on a tape volume file in our primary storage pool during reclamation on 101645 processing causing it to fail. I performed a Audit Volume 101645 fix=yes on the volume in question. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 53454652 hdr version 0002 hdr length 0032 sequence number 0061 data length server id segment id 60002793965424476 48 crc 003D.(PROCESS: 187) ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0061 server id segment id 08602819.(PROCESS The following message is now reoccurring during reclamation on the same tape volume (101645) in our primary sequential pool and causing reclamation to fail. This started to occur after I performed a Audit Volume 101645 Fix=Yes on a tape. ANR1162W Space reclamation skipping damaged file on volume 100646: Node XX200, Type Backup, File space /u14, File name /oradat/archive/TSIC/ TSIC_1_88894_525973123.arc. ANR0985I Process 193 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at Reclamation of storage pool LPOOL has ended. Files reclaimed 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0. Question 1 - If I do a Restore Storage Pool volume for that tape and it will restore the damaged file (s) from the copy pool only. Is there any way to keep this volume from being marked destroyed since it's only the one file that is damaged automatically by TSM? Since there is only 1 file that is the problem. Question 2 - If the file on the copy pool volume is damaged also and causes the same message above after I do a Audit volume ## fix=? how do I get rid of the ANR1162W message that is appears for that ONE file which causes reclamation to fail? TSM 5.3.2 Thanks in Advance! * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.
Re: Audit restore storage volume tape
One thing concerned me, you referred to having only one bad file, I think more along the lines that I have a bad tape. I want to get the surviving data off before more is killed by this failing tape. The odds of data being lost in both the primary and copy pools is pretty low. TSM, as you have found out, will not copy an object the has some error, which means the tape in the copy pool with the copy of the object does not get expired and returned to scratch. Andy Huebner From: ADSM: Dist Stor Manager on behalf of Ford, Phillip Sent: Fri 7/28/2006 10:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Audit restore storage volume tape You can do a move volume and it should move all the good files. You may have to do this a couple of times. This should get all the good files off the tape. Now try the restore. If that wont work then the only thing is delete the volume with discard=yes and you have lost data. If it is current data on the system the next backup will pick it up. -- Phillip Ford Senior Software Specialist Enterprise Computing Services Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, July 28, 2006 10:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Audit restore storage volume tape Hello, We were receiving the message below on a tape volume file in our primary storage pool during reclamation on 101645 processing causing it to fail. I performed a Audit Volume 101645 fix=yes on the volume in question. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 53454652 hdr version 0002 hdr length 0032 sequence number 0061 data length server id segment id 60002793965424476 48 crc 003D.(PROCESS: 187) ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0061 server id segment id 08602819.(PROCESS The following message is now reoccurring during reclamation on the same tape volume (101645) in our primary sequential pool and causing reclamation to fail. This started to occur after I performed a Audit Volume 101645 Fix=Yes on a tape. ANR1162W Space reclamation skipping damaged file on volume 100646: Node XX200, Type Backup, File space /u14, File name /oradat/archive/TSIC/ TSIC_1_88894_525973123.arc. ANR0985I Process 193 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at Reclamation of storage pool LPOOL has ended. Files reclaimed 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0. Question 1 - If I do a Restore Storage Pool volume for that tape and it will restore the damaged file (s) from the copy pool only. Is there any way to keep this volume from being marked destroyed since it's only the one file that is damaged automatically by TSM? Since there is only 1 file that is the problem. Question 2 - If the file on the copy pool volume is damaged also and causes the same message above after I do a Audit volume ## fix=? how do I get rid of the ANR1162W message that is appears for that ONE file which causes reclamation to fail? TSM 5.3.2 Thanks in Advance! * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Audit restore storage volume tape
do a move data to copy the good files from that tape to another, then a upd vol to destroy the defective tape, then a restore stgpool which should then only have to restore the missing file. [EMAIL PROTECTED] 07/28/06 11:57 AM One thing concerned me, you referred to having only one bad file, I think more along the lines that I have a bad tape. I want to get the surviving data off before more is killed by this failing tape. The odds of data being lost in both the primary and copy pools is pretty low. TSM, as you have found out, will not copy an object the has some error, which means the tape in the copy pool with the copy of the object does not get expired and returned to scratch. Andy Huebner From: ADSM: Dist Stor Manager on behalf of Ford, Phillip Sent: Fri 7/28/2006 10:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Audit restore storage volume tape You can do a move volume and it should move all the good files. You may have to do this a couple of times. This should get all the good files off the tape. Now try the restore. If that wont work then the only thing is delete the volume with discard=yes and you have lost data. If it is current data on the system the next backup will pick it up. -- Phillip Ford Senior Software Specialist Enterprise Computing Services Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, July 28, 2006 10:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Audit restore storage volume tape Hello, We were receiving the message below on a tape volume file in our primary storage pool during reclamation on 101645 processing causing it to fail. I performed a Audit Volume 101645 fix=yes on the volume in question. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 53454652 hdr version 0002 hdr length 0032 sequence number 0061 data length server id segment id 60002793965424476 48 crc 003D.(PROCESS: 187) ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0061 server id segment id 08602819.(PROCESS The following message is now reoccurring during reclamation on the same tape volume (101645) in our primary sequential pool and causing reclamation to fail. This started to occur after I performed a Audit Volume 101645 Fix=Yes on a tape. ANR1162W Space reclamation skipping damaged file on volume 100646: Node XX200, Type Backup, File space /u14, File name /oradat/archive/TSIC/ TSIC_1_88894_525973123.arc. ANR0985I Process 193 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at Reclamation of storage pool LPOOL has ended. Files reclaimed 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0. Question 1 - If I do a Restore Storage Pool volume for that tape and it will restore the damaged file (s) from the copy pool only. Is there any way to keep this volume from being marked destroyed since it's only the one file that is damaged automatically by TSM? Since there is only 1 file that is the problem. Question 2 - If the file on the copy pool volume is damaged also and causes the same message above after I do a Audit volume ## fix=? how do I get rid of the ANR1162W message that is appears for that ONE file which causes reclamation to fail? TSM 5.3.2 Thanks in Advance! * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or
Re: Audit restore storage volume tape
Thanks everyone for you help! regards Lawrence Clark wrote: do a move data to copy the good files from that tape to another, then a upd vol to destroy the defective tape, then a restore stgpool which should then only have to restore the missing file. [EMAIL PROTECTED] 07/28/06 11:57 AM One thing concerned me, you referred to having only one bad file, I think more along the lines that I have a bad tape. I want to get the surviving data off before more is killed by this failing tape. The odds of data being lost in both the primary and copy pools is pretty low. TSM, as you have found out, will not copy an object the has some error, which means the tape in the copy pool with the copy of the object does not get expired and returned to scratch. Andy Huebner From: ADSM: Dist Stor Manager on behalf of Ford, Phillip Sent: Fri 7/28/2006 10:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Audit restore storage volume tape You can do a move volume and it should move all the good files. You may have to do this a couple of times. This should get all the good files off the tape. Now try the restore. If that wont work then the only thing is delete the volume with discard=yes and you have lost data. If it is current data on the system the next backup will pick it up. -- Phillip Ford Senior Software Specialist Enterprise Computing Services Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: Friday, July 28, 2006 10:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Audit restore storage volume tape Hello, We were receiving the message below on a tape volume file in our primary storage pool during reclamation on 101645 processing causing it to fail. I performed a Audit Volume 101645 fix=yes on the volume in question. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 53454652 hdr version 0002 hdr length 0032 sequence number 0061 data length server id segment id 60002793965424476 48 crc 003D.(PROCESS: 187) ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0061 server id segment id 08602819.(PROCESS The following message is now reoccurring during reclamation on the same tape volume (101645) in our primary sequential pool and causing reclamation to fail. This started to occur after I performed a Audit Volume 101645 Fix=Yes on a tape. ANR1162W Space reclamation skipping damaged file on volume 100646: Node XX200, Type Backup, File space /u14, File name /oradat/archive/TSIC/ TSIC_1_88894_525973123.arc. ANR0985I Process 193 for SPACE RECLAMATION running in the BACKGROUND completed with completion state FAILURE at Reclamation of storage pool LPOOL has ended. Files reclaimed 0, Bytes reclaimed: 0, Files reconstructed: 0, Unreadable files: 0. Question 1 - If I do a Restore Storage Pool volume for that tape and it will restore the damaged file (s) from the copy pool only. Is there any way to keep this volume from being marked destroyed since it's only the one file that is damaged automatically by TSM? Since there is only 1 file that is the problem. Question 2 - If the file on the copy pool volume is damaged also and causes the same message above after I do a Audit volume ## fix=? how do I get rid of the ANR1162W message that is appears for that ONE file which causes reclamation to fail? TSM 5.3.2 Thanks in Advance! * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you
Re: Fw: Restore in DR site is very slow
Thanks for your reply Nick. That's the good point. I am wondering, I did not change anything, why the first time, it used 4 drives but the second time only used 2 drives. On 7/28/06, Nicholas Cassimatis [EMAIL PROTECTED] wrote: Increase the number of processes used for the offsite copy. With only 2 processes, you have 2 target tapes, so the data may only be on 2 tapes in the copypool. If you use more processes, you're more likely to have the data spread across more tapes. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 07/28/2006 08:31 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/28/2006 07:54:05 AM: Production side: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 8 LTO3 drives DB2 database: 8.2, 1.2TB with 7 backup drives, backup time 1.2 hour offisite copy, 2 processes, with 4 drives. DR site: TSM Server: 5.3.3 on AIX 5.3 Tape Library: 3584 with 4 LTO3 drives My problem is, when I did twice restore test, the first time it used 4 drives to do restore, used 5 hours to restore. The second test, it only used 2 drives to do restore and it used 12 hours. My question is, how can I ensure the restore can constantly use 4 drives to do restore? TIA.
Re: Configuring TSM on Sun Cluster
No replies. At 08:42 AM 7/28/2006, Bernaldo de Quiros, Iban 1 wrote: Have you received any replies ¿? -Mensaje original- De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de Paul Zarnowski Enviado el: martes, 18 de julio de 2006 21:09 Para: ADSM-L@VM.MARIST.EDU Asunto: [ADSM-L] Configuring TSM on Sun Cluster I know it's not officially supported, but has anyone figured out how to configure TSM in a Sun Cluster environment? Thanks. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Linux SLES FC LTO3 IBMtape
Good evening, I've got the following setup: TSM 5.3.2 server on AIX 5.3 TSM 5.3.2 clients on SLES 9 (SP2) on x86_64 HW Adic library with IBM LTO3 FC drives The linux clients can access the library through the SAN and have the IBMtape drivers installed. But if a modification to the library is made (eg a new drive), the Linux servers must reboot in order to detect the new tape drive. Is it not possible to perform some kind of online device discovery in order to update the contents of /proc/scsi/IBMtape without doing the reboot? I've checked already the latest redbooks and IBM Ultrium tape user guide, but they all say 'reboot'. Even on Windows this is not required any more. Or is this a feature of the IBMtape device driver? thanks, Kurt *** Disclaimer *** Vlaamse Radio- en Televisieomroep Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer
Re: Failure: return code 4 ? SOLVED
Thanks to Andrew for his invaluable help! I am running an older Client version that has been shown to display this bug from time to time. I will need to update the client shortly. About the incremental backup problem. Unfortunately, I have never watched as an incremental was performed on this system and found that some of the filesystems that are not desired to be backup were not excluded in the inclexcl.def file. I corrected this and the incremental ran as expected. Dave Zarnoch Dave Zarnoch [EMAIL PROTECTED] From: Andrew Raibeck [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Failure: return code 4 ? Date: Fri, 28 Jul 2006 07:20:44 -0600 MIME-Version: 1.0 Received: from smtp-outbound1.marist.edu ([148.100.49.24]) by bay0-mc9-f12.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Fri, 28 Jul 2006 06:24:17 -0700 Received: from mailer390.marist.edu (mailer390.marist.edu [148.100.80.47])by smtp-outbound1.marist.edu (Spam Firewall) with ESMTPid 96B3180292; Fri, 28 Jul 2006 09:21:16 -0400 (EDT) Received: from VM.MARIST.EDU (vm.marist.edu [148.100.80.40])by mailer390.marist.edu (Postfix) with ESMTPid 7A8D512533; Fri, 28 Jul 2006 09:21:13 -0400 (EDT) Received: by VM.MARIST.EDU (IBM VM SMTP Level 510) via spool with SMTP id 5701 ; Fri, 28 Jul 2006 09:22:23 EDT Received: from VM.MARIST.EDU (NJE origin [EMAIL PROTECTED]) by VM.MARIST.EDU (LMail V1.2b/1.8b) with BSMTP id 7642; Fri, 28 Jul 2006 09:22:18 -0400 Received: by VM.MARIST.EDU (LISTSERV release 14.4) with spool id 6683 for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 09:22:13 -0400 Received: from MARIST (NJE origin [EMAIL PROTECTED]) by VM.MARIST.EDU (LMail V1.2b/1.8b) with BSMTP id 7615; Fri, 28 Jul 2006 09:22:12 -0400 Received: from smtp-inbound1.marist.edu [148.100.49.21] by VM.MARIST.EDU (IBM VM SMTP Level 510) via TCP with SMTP ; Fri, 28 Jul 2006 09:22:11 EDT Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by smtp-inbound1.marist.edu (Spam Firewall) with SMTP id 92AA0C4FA1 for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 09:20:47 -0400 (EDT) Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e36.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6SDKkW8025814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 09:20:46 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k6SDKk5D285890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 07:20:46 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k6SDKkqt030653 for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 07:20:46 -0600 Received: from d03nm119.boulder.ibm.com (d03nm119.boulder.ibm.com [9.17.195.145]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6SDKktE030650 for ADSM-L@VM.MARIST.EDU; Fri, 28 Jul 2006 07:20:46 -0600 X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo= X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 X-MIMETrack: S/MIME Sign by Notes Client on Andrew Raibeck/Tucson/IBM(Release 7.0 HF85|November 04, 2005) at 07/28/2006 06:20:43 AM, Serialize by Notes Client on Andrew Raibeck/Tucson/IBM(Release 7.0 HF85|November 04, 2005) at 07/28/2006 06:20:43 AM, Serialize complete at 07/28/2006 06:20:43 AM, S/MIME Sign failed at 07/28/2006 06:20:43 AM: The cryptographic key was not found, Serialize by Router on D03NM119/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 07/28/2006 07:20:46, Serialize complete at 07/28/2006 07:20:46 X-Virus-Scanned: by Email Relay at marist.edu Precedence: list Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 28 Jul 2006 13:24:17.0236 (UTC) FILETIME=[20631940:01C6B249] Look up the help information for message ANR2579E, that will give you some direction. Also would be helpful to know the full server and client versions you are using, output from Q EV F=D for this event and node name, and Q SCHED F=D for this schedule. Regarding the include/exclude question: more information is needed. Look at dsmc query inclexcl output to make sure that the directories are indeed excluded. Maybe someone changed the include-exclude file, or changed the inclexcl option to point to a different file, or changed a client option set on the server, or changed the node to use a different client option set, Or maybe your dsm.sys file has multiple stanzas, and you are using a stanza with different include-exclude settings. Or you might have EXCLUDE instead of EXCLUDE.DIR, etc. Regards, Andy Andy Raibeck IBM
Slow Exchange Restore
The facts... TSM server v5.3.1.2 TDP for Exchange 5.2.1.0 Exchange data resides on VTL emulating 3584 The exchange box runs 1 Gbps, but we're only receiving data at 5 to 7 MB/Sec What all tuning can I do on the client machine, in dsm.opt, on server, anything? Thanks! God bless you!!! Chip Bell Network Engineer I IBM Tivoli Certified Deployment Professional (ITSM 5.2) Baptist Health System Birmingham, AL Office (205) 715-5106 Pager (205) 817-0357 Home (256) 739-0947 Cell (256) 347-7294 - Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
3592 tape read performance
We are seeing increasingly frequent problems reading data from 3592 tapes. TSM sometimes spends as much as a couple of hours reading a single file with a size of a few hundred megabyes. In some cases, TSM reports a hardware or media error at the end of that time. In other cases TSM eventually reads the file successfully. In the latter case there are, as far as we can tell, no error indications at all: no TSM messages, nothing logged by the OS, and no indicators on the front panel of the tape drive. In some case the same tape volume suffers this type of problem repeatedly. The problems seem to spread roughly evenly over our whole population of 3592 drives. We have just removed one 3592 volume from service because of recurrent read problems, and are about to remove a second volume from service. We only have about 120 3592 volumes, and losing two of them within a week is disturbing, to put it mildly. The possiblity that the volumes with non-recurring (so far) problems will eventually need replacement is even more disturbing. Our TSM server is at 5.2.6.0, running under mainframe Linux. The 3592 tapes drives are all the J1A model. Does anyone have any suggestions for getting to the bottom of this?
Re: inventory expiration time
Richard Hammersley a écrit : 300 gig fibre channel attached through a brocade switch. raid5 9 spindles. topas shows between 94% and 100% busy for the hdiskpower0 device that has the database and only the database on it. 1500 to 3000 tps, 5000 to 1 KB-read Allen S. Rout wrote: On Thu, 27 Jul 2006 16:13:41 -0400, Richard Hammersley [EMAIL PROTECTED] said: The machine is a new dual processor P520 with 4 gig of memory attached to an EMC cx300 san. What's the underlying disk in the cx300? - Allen S. Rout We also have our ITSM DATABASE (5.2.8.1/AIX 5.2ML5/Powerpath 4.5.1) on Clariion CX600 with 10k disk (146GB) on p695 partition (4 processors/8GB memory). But we have among 55Mo/s (20 = 80) troughput for each hdiskpower in dual path with load balancing. We have 4 luns (each 50GB) all created on 4 +1 RAID Group (4+1 is optimized for write and read) balance between the 2 storage processors for the db. Inventory run in about 3-6 hours. dbfile is build with file of 10GB.
Re: Error reading label
Hi, Are these scratch tapes new tapes? Did you used the label libv command on the checkin? TSM puts unlabeled tapes on the private list unless you configure your library to autolabel new tapes. Regards, Karel -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Mochnaczewski Sent: vrijdag 28 juli 2006 16:21 To: ADSM-L@VM.MARIST.EDU Subject: Error reading label Hi Everybody, We recently had a new rack addition installed in our 3494 library this Sunday. Since that was done, we have been getting about 75 scratch tapes since Monday being changed from scratch to a private state because of errors reading the label. I've checked about 30 of these tapes and they look fine. Has anyone run into this problem ? Could it be an alignment issue with the gripper ? Rich Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Origin supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Origin exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
