Timo Kilchenmann, Bechtle Data AG ist abwesend.
Ich werde ab 12.01.2004 nicht im Büro sein. Ich kehre zurück am 19.01.2004. Die E-Mail wurde nicht weitergeleitet! Bitte wenden Sie sich an Herrn Paul Glauser, Telefon 043 388 7277 oder E-Mail [EMAIL PROTECTED]
Timo Kilchenmann, Bechtle Data AG ist abwesend.
Ich werde ab 17.11.2003 nicht im Büro sein. Ich kehre zurück am 05.12.2003. Die E-Mail wurde nicht weitergeleitet!
Timo Kilchenmann, Bechtle Data AG ist abwesend.
Ich werde ab 24.03.2003 nicht im Büro sein. Ich kehre zurück am 01.04.2003. Die E-Mail wurde nicht weitergeleitet!
Problems with IBM 3584-L32 library with IBM prelabeld LTO cartridges
Dear all, We run into the following problem: Bought 80 additional labeled LTO cartridges through IBM. Inserted the cartridges into the library. BUT the library/picker is not able the get the cartridges out of the slots nor the tape drives. Doing the procedure by hand I found out, that I need to apply allot of force. I opened a hardware call. IBM guy showed up, updated microcode on library and drives. The guy told me that the problems with the cartridges are our business - not his or IBM's. I responded back that both the library and the cartridges are from IBM! - no good :-(. Has anyone out there experienced similar problems? How were the problems solved? Timo Kilchenmann E-Mail [EMAIL PROTECTED] Phone +41 1 843 34 91 (direct) Bechtle Data AG or +41 1 843 32 32 Bahnstrasse 58/60Telefax +41 1 843 34 24 CH-8105 Regensdorf Mobile +41 79 417 43 55 Switzerland http://www.bechtle-data.ch
Re: Problems with IBM 3584-L32 library with IBM prelabeld LTO car tridges
Yes as a result of the hardware problem. First cartrige is labeled ok. But the umount of the volumes fails, because the gripper is not able to get the cartridge out of the drive (to much forced needed). Timo Kilchenmann E-Mail [EMAIL PROTECTED] Phone +41 1 843 34 91 (direct) Bechtle Data AG or +41 1 843 32 32 Bahnstrasse 58/60Telefax +41 1 843 34 24 CH-8105 Regensdorf Mobile +41 79 417 43 55 Switzerland http://www.bechtle-data.ch -- Externe Mail : ADSM: Dist Stor Manager [EMAIL PROTECTED] 29.01.200310:02 -- Gesendet von: ADSM: Dist Stor Manager An:[EMAIL PROTECTED] [EMAIL PROTECTED] Kopie: Thema: Re: Problems with IBM 3584-L32 library with IBM prelabeld LTO car tridges Bitte antworten an ADSM: Dist Stor Manager Do you mean the label libv command failed? What was the error? -Mensaje original- De: Kilchenmann Timo [mailto:[EMAIL PROTECTED]] Enviado el: miercoles, 29 de enero de 2003 9:54 Para: [EMAIL PROTECTED] Asunto: Problems with IBM 3584-L32 library with IBM prelabeld LTO cartridges Dear all, We run into the following problem: Bought 80 additional labeled LTO cartridges through IBM. Inserted the cartridges into the library. BUT the library/picker is not able the get the cartridges out of the slots nor the tape drives. Doing the procedure by hand I found out, that I need to apply allot of force. I opened a hardware call. IBM guy showed up, updated microcode on library and drives. The guy told me that the problems with the cartridges are our business - not his or IBM's. I responded back that both the library and the cartridges are from IBM! - no good :-(. Has anyone out there experienced similar problems? How were the problems solved? Timo Kilchenmann E-Mail [EMAIL PROTECTED] Phone +41 1 843 34 91 (direct) Bechtle Data AG or +41 1 843 32 32 Bahnstrasse 58/60Telefax +41 1 843 34 24 CH-8105 Regensdorf Mobile +41 79 417 43 55 Switzerland http://www.bechtle-data.ch Este mensaje de correo electronico y sus documentos adjuntos estan dirigidos EXCLUSIVAMENTE a los destinatarios especificados. La informacion contenida puede ser CONFIDENCIAL y/o estar LEGALMENTE PROTEGIDA y no necesariamente refleja la opinion de ENDESA. Si usted recibe este mensaje por ERROR, por favor comuniqueselo inmediatamente al remitente y ELIMINELO ya que usted NO ESTA AUTORIZADO al uso, revelacion, distribucion, impresion o copia de toda o alguna parte de la informacion contenida. Gracias. This e-mail message and any attached files are intended SOLELY for the addressee/s identified herein. It may contain CONFIDENTIAL and/or LEGALLY PRIVILEGED information and may not necessarily represent the opinion of ENDESA. If you receive this message in ERROR, please immediately notify the sender and DELETE it since you ARE NOT AUTHORIZED to use, disclose, distribute, print or copy all or part of the contained information. Thank you.
Total number of bytes transferred / Differences between two systems
Doing an archive operation for the same file on two different systems results in different amount of data getting transferred. I am clueless about the cause of this. Can someone explain this? Environment: TSM Server Version 3.7.04 on AIX 4.3.3 TSM Client Version 3.1.07 on HP-UX 10.20 A Many thanks in advance! system1: root@system1:/usr/adsmdsmc archive /tmp/phkl_16751/patches.zip ADSTAR Distributed Storage Manager Command Line Backup Client Interface - Version 3, Release 1, Level 0.7 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Archive function invoked. Node Name: system1 Session established with server TSMSERV1: AIX-RS/6000 Server Version 3, Release 7, Level 4.0 Data compression forced off by the server Server date/time: 15.01.2003 10:16:27 Last access: 12.01.2003 10:06:39 Directory-- 1,024 /tmp/phkl_16751 [Sent] Normal File-- 5,456,956 /tmp/phkl_16751/patches.zip ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File-- 5,456,956 /tmp/phkl_16751/patches.zip [Sent] Archive processing of '/tmp/phkl_16751/patches.zip' finished without failure. Total number of objects inspected: 110 Total number of objects archived: 2 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects failed: 0 Total number of bytes transferred: 5.45 MB Data transfer time: 357.24 sec Network data transfer rate: 15.63 KB/sec Aggregate data transfer rate: 13.95 KB/sec Objects compressed by:0% Elapsed processing time: 00:06:40 root@system1:/usr/adsm --- system2: system2 /tmp dsmc archive /tmp/patches.zip ADSTAR Distributed Storage Manager Command Line Backup Client Interface - Version 3, Release 1, Level 0.7 (C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. Archive function invoked. Node Name: system2 Session established with server TSMSERV1: AIX-RS/6000 Server Version 3, Release 7, Level 4.0 Data compression forced off by the server Server date/time: 15.01.2003 10:23:19 Last access: 15.01.2003 00:24:20 Directory-- 2,048 /tmp/ [Sent] Normal File-- 5,456,956 /tmp/patches.zip ** Unsuccessful ** ANS1114I Waiting for mount of offline media. Retry # 1 Normal File-- 5,456,956 /tmp/patches.zip [Sent] Archive processing of '/tmp/patches.zip' finished without failure. Total number of objects inspected: 183 Total number of objects archived: 2 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects failed: 0 Total number of bytes transferred:10.41 MB Data transfer time: 86.59 sec Network data transfer rate: 123.09 KB/sec Aggregate data transfer rate:111.08 KB/sec Objects compressed by:0% Elapsed processing time: 00:01:35 Timo Kilchenmann E-Mail [EMAIL PROTECTED] Phone +41 1 843 34 91 (direct) Bechtle Data AG or +41 1 843 32 32 Bahnstrasse 58/60Telefax +41 1 843 34 24 CH-8105 Regensdorf Mobile +41 79 417 43 55 Switzerland http://www.bechtle-data.ch
Timo Kilchenmann, Bechtle Data AG ist abwesend.
Ich werde ab 24.12.2002 nicht im Büro sein. Ich kehre zurück am 06.01.2003. Die E-Mail wurde nicht weitergeleitet!
Does TSM use all DB Volumes for I/O?
Dear all, I have looked through the adsm.org archives. The answers I got from the archives are not consistent. I would vary much appreciate an answer to the question: Does TSM use all DB volumes for I/O (like round-robin) or does it fill a volume and then goes to the next one? What about LOG volumes? Many thanks in advance Timo
What stripe size to use for TSM DB, LOG
Dear all, From a previous threat I learned, that TSM fills a DB volume an than goes to the next one. Same is true for the LOG volumes - no load balancing like on STG Volumes via client sessions. In this case (DB LOG) I plan to use AIX LVM to stripe the logical volumes over the available physical disks. The question here is what stripe size should I use? Any suggestions? Many thanks in advance!!! Timo
Timo Kilchenmann, Bechtle Data AG ist abwesend.
Ich werde ab 10.06.2002 nicht im Büro sein. Ich kehre zurück am 21.06.2002. Die E-Mail wurde nicht weitergeleitet! Bitte wenden Sie sich während meiner Abwesenheit an Paul Glauser, Telefon +41 1 843 3751, E-Mail [EMAIL PROTECTED]
Re: Problems setting compression on SDLT drives in a Compaq MSL50 26SL library
According the Tivoli the Problem ist fixed at server level 4.2.1.13. I will give level 4.2.1.15 a try. Will inform the list about the result! Timo Kilchenmann, Bechtle Data AG Regensdorf, Tel: (+41) 1 843 34 91 -- Externe Mail : ADSM: Dist Stor Manager [EMAIL PROTECTED] 06.06.200212:20 -- Gesendet von: ADSM: Dist Stor Manager An:[EMAIL PROTECTED] [EMAIL PROTECTED] Kopie: Thema: Re: Problems setting compression on SDLT drives in a Compaq MSL50 26SL library Bitte antworten an ADSM: Dist Stor Manager Hi Timo, We are also experiencing this problem. I found APAR IC32694 on Tivoli's website, which states that TSM is turning off compression at the drive, but doesn't really give a resolution. We are going to be opening a PMR with Tivoli in the future. Regards Stuart Infrastructure Services Operations Bridge Innogy Swindon * 01793 896060 Fax 01793 896065 * mailto:[EMAIL PROTECTED] Pleas note the change of company name from National Power to Innogy -Original Message- From: Kilchenmann Timo [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, June 04, 2002 5:40 PM To: [EMAIL PROTECTED] Subject: Re: Problems setting compression on SDLT drives in a Compaq MSL5026SL library Thanks for your answer! So what is the value SDLTC in device class DLT for? Probably to choice between compression/nocompression - right? Because of the hardware/os combination the TSM device driver is used - IT is a Tivoli TSM thing! No one having the same problem? Cherrs, Timo Kilchenmann, Bechtle Data AG Regensdorf, Tel: (+41) 1 843 34 91 -- Externe Mail : ADSM: Dist Stor Manager [EMAIL PROTECTED] 04.06.200213:24 -- Gesendet von: ADSM: Dist Stor Manager An:[EMAIL PROTECTED] [EMAIL PROTECTED] Kopie: Thema: Re: Problems setting compression on SDLT drives in a Compaq MSL5026SL library Bitte antworten an ADSM: Dist Stor Manager From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Kilchenmann Timo We use a Compaq MSL5026SL tapelibrary. Device class DLT is configured to use SDLTC recording format. Compression is ON until TSM does access the drives for the first time - after that compression is OFF (according to library/drive configuration information). TSM Server is 4.2.1.0 on W2K. Can someone advice me how to configure TSM so that it uses drive compression? Many thanks in advance! TSM does not contain a mechanism for setting hardware parameters. (Almost impossible with the thousands of drive/OS combinations possible!) It sounds like a bug in the tape driver. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MSCE The information contained in this email is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination or copying of the message or associated attachments is strictly prohibited. If you have received this email in error, please contact the sender by return email or call 01793 87 and ask for the sender and then delete it immediately from your system. Please note that neither Innogy nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any). *
Problems setting compression on SDLT drives in a Compaq MSL5026SL library
Hi all, We use a Compaq MSL5026SL tapelibrary. Device class DLT is configured to use SDLTC recording format. Compression is ON until TSM does access the drives for the first time - after that compression is OFF (according to library/drive configuration information). TSM Server is 4.2.1.0 on W2K. Can someone advice me how to configure TSM so that it uses drive compression? Many thanks in advance! Timo Kilchenmann Bechtle Data AG Regensdorf CH-8105 Regensdorf Tel: (+41) 1 843 34 91 E-Mail: [EMAIL PROTECTED] Internet: http://www.bechtle-data.ch
Re: Problems setting compression on SDLT drives in a Compaq MSL5026SL library
Thanks for your answer! So what is the value SDLTC in device class DLT for? Probably to choice between compression/nocompression - right? Because of the hardware/os combination the TSM device driver is used - IT is a Tivoli TSM thing! No one having the same problem? Cherrs, Timo Kilchenmann, Bechtle Data AG Regensdorf, Tel: (+41) 1 843 34 91 -- Externe Mail : ADSM: Dist Stor Manager [EMAIL PROTECTED] 04.06.200213:24 -- Gesendet von: ADSM: Dist Stor Manager An:[EMAIL PROTECTED] [EMAIL PROTECTED] Kopie: Thema: Re: Problems setting compression on SDLT drives in a Compaq MSL5026SL library Bitte antworten an ADSM: Dist Stor Manager From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Kilchenmann Timo We use a Compaq MSL5026SL tapelibrary. Device class DLT is configured to use SDLTC recording format. Compression is ON until TSM does access the drives for the first time - after that compression is OFF (according to library/drive configuration information). TSM Server is 4.2.1.0 on W2K. Can someone advice me how to configure TSM so that it uses drive compression? Many thanks in advance! TSM does not contain a mechanism for setting hardware parameters. (Almost impossible with the thousands of drive/OS combinations possible!) It sounds like a bug in the tape driver. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MSCE
Large TSM database due to no. of files and versions
Dear all, We have the following problem: We are backing up some large Novell servers (more than 1 million files per Server). The users want to be able to restore every version of a file 30 days back and every version of a file at the end of a month 12 months back. In order to meet these requirements at least partly we set the backup management class as follows: Versions Data Exists: 10 Versions Data Deleted: 5 Retain Extra Versions: 366 Retain Only Version: 366 Because of these settings, the TSM database grew to 15 GB in the last 6 months and is growing fast even further. Restore performance is bad for these servers as well. Is there a possibility / idea to get over this apart from using archives? Is it possible to create archives (not backupsets) from existing data on the TSM server? Any idea is welcome! Eurodis Schweiz AG Data Division Timo Kilchenmann Systems Engineer --- Timo Kilchenmann E-Mail [EMAIL PROTECTED] Eurodis Schweiz AG Phone +41 1 843 34 91 (direct) Bahnstrasse 58/60or +41 1 843 32 32 CH-8105 Regensdorf Telefax +41 1 843 34 24 Switzerland Mobile +41 79 417 43 55 http://www.eurodis.ch ---
