Windows TSM server 4.1.3 finally supports SCSI attached 3583 for W2K!
Finally some good new for us happy people with 358X Libraries and W2K on SAN. The latest level of the Windows TSM server 4.1.3 is available (although Tivoli's Website is behind with the information as usual) see: ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/ server/v4r1/NT/LATEST/ Hurry before they remove it ...:-). Some minor problems with the upgrade from RSM to SCSI for 3583: -I had to use the LB1.X.Y.Z as the library name, don't know why I couldn't use any name but there might be a limitation for SCSI libraries that I missed. -I also had to change the device class for the old RSM tape to point to the new library name. Time to try the SAN backups this week. Happy upgrading. Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-25233507 Fax : +31 40 2783962
FW: SAP and 3494 performance.
Hi, Following is a log (slightly altered in size and names)for SAP backup. AIX 4.3.3 on the SAP system and the TSM 4.1.2 server. ESS SAN attached disks, 3590-E SAN attached (2) tape drives. All backups over Gbit Ethernet today with ~20MB/s and session. Note: -Multiplexing is still using 4 disks to read from (kept from our SSA days). Multiplexing has got nothing to do with tape drive allocations on the TSM server and you might need it to get enough disk to read from so that each session can fully use the tape drives speed . -2 parallel sessions thus 2 drives allocated for the backup (redologs goes to disk) -No client compression for SAP backups! Never ever unless you have a very good reason (CPU heavy). -RL compression gives me 1.32, this can differ a lot depending on the DB, in production we usually see below 2, mostly between 1.2-1.5. RL-compression is CPU light. BR061I 383 files found for backup, total size 523133.822 MB. Tivoli Data Protection for SAP R/3 Interface between SAPDBA Utilities and Tivoli Storage Manager - Version 2, Release 7, Level 25.1 for AIX LF - (c) Copyright IBM Corporation, 1996, 1999, All Rights Reserved. Program Number : 5799-QZG -- Parameters -- Input File : /oracle/SIDX/sapbackup/.bdexttba.lst Output File: stdout Profile: /oracle/SIDX/dbs/initSIDX.utl Configfile : /oracle/SIDX/dbs/initSIDX.bki Manual sorting file: disabled Tracefile : none Traceflags : disabled Parallel sessions : 2 Multiplexed files : 4 RL compression : enabled TCPWait: 3 sec. Retries to ADSM : 3 Retries for files : 3 Exit on error : disabled BATCH : enabled Redologcopies : N/A Versioning : enabled Current Version : 623 Versions to keep : 7 Delete Versions : <= 616 Backup Type: file SNMPTRAP : disabled Performance Monitor: disabled ADSM log server: host 'XYZ', level 'WARNING' ADSM server: XYZ with 2 sessions configured, using 2 sessions TSM client node : SIDX Server-Version: 4.1.2.0 Server Host IP: X.Y.Z.U Server Host name : HOST Server Type : AIX-RS/6000 Sign-in id name : SIDX Compression : client determined Archive deletion : allowed Days for backups : Sun Mon Tue Wed Thu Fri Sat Backup mgmt class : SAP_ON_OFF Archiv mgmt class : SAP_LOG_1 SAP_LOG_2 BKI0005I: Start of backint program at: Wed Mar 21 00:16:54 2001. BKI0013I: 383 Objects to backup. BKI0008I: Number of bytes to save: '510.873 GB'. .. BKI0020I: End of backint program at: Wed Mar 21 02:55:03 2001. BKI0022I: Average transmission rate was 196.532 GB/h (55.902 MB/sec). BKI2019I: Compression ratio for backup was 1.32. BKI0021I: Elapsed time: 02 h 38 min 09 sec. Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-25233507 Fax : +31 40 2783962 -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 20, 2001 8:02 PM To: [EMAIL PROTECTED] Subject: Re: SAP and 3494 performance. Our client is a Sun E10K with ?24 processors? maybe more if that is possible... it has a bunch And we have other AIX & SUN... Tsm server is an S70 and runs less than 30% cpu util during the backups... Here is the poop on multiplexing...(check in your TDP for SAPR3 manual) mainly if you are going straight to tape 'cause each session will require a tape drive. By going to a diskpool, you aren't limited by the number of tape drives you have... BUT remember there will only be a single migration process for a single client's data within a diskpool no matter what your migration process limit is or how many tape drives you have... and a single migration going to 3590B1A (what I see) averages out to be just over 20 GB/hr... so I can load up my diskpool with 600 GB at 41 GB/hr but can only empty it at 20 GB/hr :-( I'm looking into having the client use two management classes, direct it to two different diskpools (say 10 processes dumping into each diskpool) then their total rate into the tsm server will be 41 GB/hr, the limit of the fast ethernet card, AND I'll be able to bleed the data off to tape at 40 GB/hr (a migration process for each diskpool with each migration process moving 20 GB/hr) Now maybe if I'd upgrade the B1A's to E1A's I could get about 35 GB/hr average on the migration but I don't know... Anyway, also if one of your multiplexed files goes bad then you have multiple .dbf files bad and makes a recovery a little harder... just the way we do it. Dwight -Original Message- From: Richard L. Rhodes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 20, 2001 7:23 AM To: Cook, Dwight E; [EMAIL PROTECTED] Subject: Re: SAP and 3494 performance. Thanks for great info!
Re: tsm mirroring vs pprc
Richard, PPRC is a true copy of the original (at least that is how it is supposed to be) thus partially written files will be partial writhed files on the PPRC copy too. I suggest that you use TSM mirroring (I assume you use the ESS in RAID 5). I hope your customer understands the statement about using PPRC "mirroring" as it might not be exactly what they like to have in real life, we are using it on a number of systems (not for TSM)and there is some more to it then what might be obvious. Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -Original Message- From: Richard Bates [mailto:[EMAIL PROTECTED]] Sent: Friday, June 08, 2001 1:25 PM To: [EMAIL PROTECTED] Subject: tsm mirroring vs pprc Folks, Customer site: TSM running on AIX. 2 x IBM Enterprise Storage Server, one per data centre. SAN connecting it all together. Problem: I've seen and read all the posts about TSM mirroring vs AIX mirroring vs RAID mirroring. I understand the probem with partial page writes and prefer TSM mirroring. We had planned to implement TSM mirroring with a copy of the database and recovery log on IBM ESS in both of the data centres. However company strategy says that *all* mirroring must be done via PPRC. Does anyone have any experience with PPRC? Can it cope with partial page writes? Am I safer to use TSM mirroring? Regards Richard. Richard Bates Storage Specialist ITS - SB - Enterprise Consultancy Services == Voice : 00 44 (0) 1926 462298 (HICOM : 662298) (MOBEX : 270798) [EMAIL PROTECTED]
Re: TSM tapes out of Sync with Library manager
James, Start here: http://people.bu.edu/rbs/ADSM.funcdir Richard Sims has put together an excellent howto with an introduction to almost anything in TSM. Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -
Re: Server to Server reclamaiton vs move data
Jack, I you work server-to-server all your reclaims will go from the remote to the local and back to the remote again thus passing your network twice! Same thing for move data. This, hopefully, should be nicer in a SAN environment but I have not seen that yet. Regards, Jan Norback Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-25233507 Fax : +31 40 2783962 -Original Message- From: Palmadesso Jack [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 01, 2000 4:29 PM To: [EMAIL PROTECTED] Subject: Server to Server reclamaiton vs move data Boy sure is quiet in here lately. Maybe this can stir things up a bit ;) Correct me if I am wrong: I have 2 servers at remote sites that perform server to server db backups and copy storage pools over our WAN. Reclamation usually takes a really long time to complete. Especailly as I approach lower reclamation values. If I set reclamation for the server to server pool at 80 then I have to send at most 20% of each tape down over the WAN. DLT 4000s have 20/40 compression so I could send up to 5/10 gigs of data down the pipe for just for one volume!! That could take all day over the WAN! I am considering using "move data" instead. Again correct me if I am wrong please. When I issue a move data on a server to server volume that volume should be mounted in the remote library as well as another filling volume from that storage pool or just use a new scratch volume. Since these two volumes are mounted in the same library the amount of data that needs to be sent over the WAN is now minimal (I'm not sure about this) In this case the data would be moved much quicker freeing up my scratch volumes. Also communication over the WAN is now minimized because no files are being sent only ADSM DB communication is going on. I know I would need at least 2 mount points available to the storage pool. Can anybody enlighten me on this. Thanks for any help as always, Jack
RSM, 3583, W2K and SAN LAN free backups + DRM
Hi, One of our customers have got a 3583 tape library with W2K and RSM that we got working thanks to some of the previous input (we are on TSM 4.1.1, awaiting 4.1.2 to come back soon for W2K). Now I only need to get LAN free backups and DRM working... Some question marks: -DRM is usually easy with 3494 libraries and AIX but here on a 3583 accessed through W2K RSM the information about tapes seems to a large degree be outside of TSM, I can't see how the checkin's are to be done? -Implementing LAN free backup by following the TSM Manage systems for SAN Storage Agent seems to indicate that I need to define a shared SCSI library which is not the same as a RSM library? Has anyone done this before that can give me some info on how it is to be done? IBM: I really look forward to the patch that removes RSM from the control of the Library. Is it coming soon or will you at least improve the documentation for RSM usage? Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-25233507 Fax : +31 40 2783962
3494 Library Sharing
I would like to implement library sharing for 4 x TSM 4.1.4.1 servers (AIX) accessing 2 3494 libraries. The problem I have is that it looks like my in-between state (slowly moving from SCSI to SAN) might not work. Please advice. Current setup: 2 servers S1 and S2 accessing L1 in site A 2 servers S3 and S4 accessing L2 in site B -S1 has got 2 x 3590(-E1A) SCSI and 2 x 3590 SAN attached tape drives in L1, the AIX system can see 2 SAN drives from L2 too -S2 has got 2 x 3590 SCSI in L1 -S3 has got 2 x 3590 SAN in L2, the AIX system can see 2 SAN drives from L1 too -S4 has got 3 x 3590 SCSI in L2 All SCSI drives are dedicated to a server. The offsiting is done by server-to-server (S1-S3, S2-S4) over Gbit. Each server has got its own dedicated tape ranges. Goal: I would like to abolish server-to-server for offsiting on S1-S3 (keep it for DB backup and prepare) by using the SAN drives together with one Library Manager on each side (to get away from dedicated tape ranges). I don't think that will work in this mixed SCSI/SAN environment as I don't see anyway of addressing the SCSI drives? Maybe I could continue to use S2-S4 as before and have S1/S3 as library manager for each other, would that allow S1 to use all 4 drives while also allowing access for both to the SAN drives? The only other alternative I see would be to use partitioning of the 3494s with dedicated tape ranges on each side thus allowing the 3494 to assign SAN drives on request for S1/S3 without the TSM Library Manager. Comments/suggestions? Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962
Re: configuring TSM with HACMP and Informix : help needed
Arnaud, This is how you could set it up in HACMP cluster: -Node A and node B. SAP SID1 and SID2 (or for you Informix DB) that are moving resources. 4 nodes defined in TSM: Node_A, Node_B, Node_SID1, Node_SID2. 4 schedulers running in the cluster, one for each physically system (Node_A and Node_B), one for each of the SIDs. Each schedule is backing up the disks that belongs to it using include/exclude lists. I don't know about onbar bat for SAP it is easy to select what nodename to use for the backup/restore. None-local schedule start: /usr/bin/nohup /usr/bin/dsmc sched -virtualnodename=$VIRTUALNODE -quiet -password=X > /dev/null 2>&1 < /dev/null & Filelevel restores with dsmc -virtualnodename=$VIRTUALNODE Regards, Jan Norback Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -Original Message- From: PAC Brion Arnaud [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 11:54 AM To: [EMAIL PROTECTED] Subject: configuring TSM with HACMP and informix : help needed Hi *'SM Gurus ! A probably easy question for anybody involved in this kind of installation : we are planing to install HACMP between two AIX boxes, let's call them A and B. The A box is hosting an informix db, wich is doing it's online backups thru onbar, using it's own dsm.sys with hostname A. The B box is also hosting an informix db, wich also has it's own online backup, using it's own dsm.sys, hostname B. Imagine the A box fails : machine B will automatically relay it, and temporarily host the A informix db. Problem is as follows : what about a restoration of my informix db back to sytem A ? Probably a full level 0 backup was made at the time the db was on server A, but all intermediary logs (logical logs) have been made as my informix db was hosted on system B : how do I do a restore of my db if part of the files belong hostname A and other part hostname B ? Do I need to install two different instances of tsm on each node, to be able to do my restore ? Lots of questions in fact, and absolutely no idea how to do it ! :-(( I'm not an informix specialist nor HACMP, so please, if you give me some infos, try to be as basical as possible ;-) Many many thanks in advance to any informix-hacmp god(esss) willing to help me ! Arnaud =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | Arnaud Brion, Panalpina Management Ltd., IT Group | | Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland | | Phone: +41 61 226 19 78/Fax: +41 61 226 17 01 | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Persistent binding problem with W2K and SAN attached tape dri ves using Qlogic QLA-2200F
FYI: We had to go to Emulex LP8000 SAN adapters to solve the problem with persistent binding. Emulex has a configuration utility that allows persistent mapping of the WWN to a selected SCSI ID. Beware of using Qlogic until they have the same functionality. >-It is currently not possible to use persistent binding with W2K and SAN attached tape drives using the Qlogic QLA-2200F HBA > Regards, > Jan Norback > > Atos Origin-IT (MS/DS/OSS Unix) > VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands > Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands > Email: [EMAIL PROTECTED] > Tel: +31 (0)40-2780289 > Mobile: +31 (0)6-12994492 > Fax : +31 40 2783962 >
Re: tsm 4.2 on win2k in lanfree
Giuseppe, Look at: -Drive mapping. Your client might think it needs to write to another drive then to what the TSM server have mounted the tape. -There is a new redpiece/redbook about LTO and SAN that you should look at (SG24-6268-00). In that book there are also some info regarding persistent mapping that might be an area that you should look at. -Make sure that you have the latest device drivers for the tape drives, it also sounds that you need to upgrade to a later version of TSM 4.2.X too as I recall that the version you are running can create data corruption with lanfree. Regards, Jan Norback -Original Message- From: Giuseppe Taccone [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 28, 2001 10:24 AM To: [EMAIL PROTECTED] Subject: tsm 4.2 on win2k in lanfree Hello, is there anybody that already experience about this configuration for lan free backup: TSM 4.2.0.1 server on win2k sp2 TSM client 4.2.0.1 on win2k sp2 library lto 3584 fibre channel My problem is that doesn't work lan free backup for this environment. All installation in goes good and the san agent tivoli too. All service work fine, but when i try to run lan free backup for this client the library take a cartridge , mount it and wait for one minute without do nothing operation. After this time the library unload the cartridge e reload again doing the same operation that i described before. I haven't any error messages, it there anybody that use this configuration? many thank's Giuseppe Taccone TSM Team Manager I.A.N. srl V.le Fulvio Testi, 11 20092 Cinisello Balsamo (Mi ) Tel. +39.02.61866362 Fax +39.02.61866315 Email:[EMAIL PROTECTED] WEB: www.ian.it
CommonStore for SAP and TSM
Hi, I am in the process of planning for the TSM setup of CommonStore for SAP and hope that there are some good advice out there on the following questions: -Is there a way to configure Commonstore to store 2 copies in parallel to 2 different TSM servers for redundancy or is the only alternative an offsite copy within one TSM server through normal backup storage pool? It doesn't look like I can use 2 TSM servers from the documentation that I have seen so far. -What impact will the Commonstored objects have on the TSM DB? Is there a one-to-one mapping or can X CommonStore objects be represented as 1 TSM object through some internal commonstore DB? I am looking for advice regarding the TSM DB growth. -IBM has sold our customer a solution that stores the data directly to optical storage. Any comments? Are you using a disk pool first or are you storing directly to optical storage and/or tape? -Anyone got any better documentation then the manual? Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-173, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962
Re: Has anyone else seen a performance hit going from backint 2.4 .17. 3 to TDP/R3 3.4.0.6?
Tom, We have just upgraded from V2.7 to V3.2.0.6 in the weekend (I guess your 3.4.0.6 is a typo). Our HW is similar with Gbit (one), AIX 4.3.3 and ESS. We am not using the new option SORT_FILE. I tested with different MULTIPLEXING and ended with 5 as the best value for performance (probably depends on the layout of the filesystem in the ESS). 2 streams. 2 x 3590 E Tape drives (probably faster then yours but we only use 2), TSM 4.1 server, 4.2.1 client and rl_compression ~1.4 BKI1215I: Average transmission rate was 210.716 GB/h (59.937 MB/sec). BKI0020I: End of backint program at: Tue Jan 22 02:10:11 2002 . BKI0021I: Elapsed time: 01 h 50 min 51 sec . BKI0024I: Return code is: 0. Or old backups was slower but we have also moved to new HW and ESS in connection with the upgrade which all improved the performance. A backup test with the old SW and the new HW gave use ~2.5 hours but that also depends on which tape drive it hits (2 are Ultra SCSI attached, 1 is FW SCSI). Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -Original Message- From: Kauffman, Tom [mailto:[EMAIL PROTECTED]] Sent: Monday, January 21, 2002 5:14 PM To: [EMAIL PROTECTED] Subject: Has anyone else seen a performance hit going from backint 2.4.17. 3 to TDP/R3 3.4.0.6? We migrated from backint 2.4.17.3 to Tivoli Data Protection for SAP just after the first of the year; no other changes in the supporting infrastructure. I'm seeing a 19 MB/sec drop in throughput. Has anyone else run into this? Is this just a stupid tuning parm thing I missed? We're running the same init.utl we ran prior to the upgrade. Short overview of config - SAP/R3 database on ESS, spread evenly over 3 fiber channels (not using SSD). DB server is an S7A, AIX 4.3.3-06; TSM server is an S7A, AIX 4.3.3-06, TSM 3.7.4.0. Running five seperate strams, two on one gigabit ethernet, three on the second gigbit ethernet. TSM configured to write the data directly to tape, IBM LTO in a 3584 library -- using five of our ten drives. We are using TDP/backint rl_compression; we are not using TSM client compression. This is from the 2.4.17.3 run: KI0020I: End of backint program at: Sun Dec 16 02:28:46 2001. BKI0022I: Average transmission rate was 251.035 GB/h (71.406 MB/sec). BKI2019I: Compression ratio for backup was 1.23. BKI0021I: Elapsed time: 02 h 25 min 35 sec. and this is from the 3.4.0.6 run: BKI1215I: Average transmission rate was 184.671 GB/h (52.529 MB/sec). BKI0020I: End of backint program at: Sun Jan 13 03:30:03 2002 . BKI0021I: Elapsed time: 03 h 27 min 14 sec . BKI0024I: Return code is: 0. This is a weekly off-line backup. We also run nightly on-line backups, to four tape drives. I'm seeing roughly the same hit, down from 60 MB/sec to 51 MB/sec. As can bee seen, I no longer get any benefit from running the additional tape drive for the off-line backup. So -- is this real, or is this a stupid config/tuning issue? Tom Kauffman NIBCO, Inc
Mixed SCSI/SAN drives in LAN free, is that possible?
Hi, I have been asked by my customer if it is possible to mix SCSI and SAN attached drives on TSM servers that are to perform LAN free backup. I know that I need to drivemapp all the SAN drives but what will TSM do with the SCSI attached drives, is it cleaver enough to make sure that it doesn't mount any tapes for LAN free backups and restores in those drives? Why not upgrade all drives? Money, money... This setup: -TSM server 4.2 on AIX 4.3.3 -3494 libraries -3590E tapes (SCSI and SAN) Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962
Re: Mixed SCSI/SAN drives in LAN free, is that possible?
Becky, the fact that TSM doesn't care how the drives are attached is the part that scares me. To me it sounds like: -TSM might mount a tape in driveX, which could be SCSI attached -TSM tell the storage agent to use driveX (which it doesn't have a clue about as it is SCSI) and the backup will fail. Is the above assumption correct or does TSM understand that it can't mount a tape in a drive for which there is no drive mapping for this client? SAN DGW isn't an option for this customer, I have used it for other customers. I am used to SAN and SCSI attached drives for LAN free but I haven't tried the mixture... Maybe there is a way to partition the 3494 so it looks like 2 different libraries, one with SCSI and one with SAN or there might not be a problem? /Jan Norback -Original Message- From: Davidson, Becky [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 6:11 PM To: [EMAIL PROTECTED] Subject: Re: Mixed SCSI/SAN drives in LAN free, is that possible? Jan Not a problem at all. TSM does not care how they are attached. TSM depends completely on the operating system for the intelligence on the attaching. The 3494 is also intelligent enough to know if someone else is using the drive that it can't. Drive map all the SAN drives??? What you could do which is relatively inexpensive is attach your 3590's to San Data Gateways which attach to the SAN and then they would all be SAN attached. Good luck Becky -Original Message- From: Norback, Jan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 10:53 AM To: [EMAIL PROTECTED] Subject: Mixed SCSI/SAN drives in LAN free, is that possible? Hi, I have been asked by my customer if it is possible to mix SCSI and SAN attached drives on TSM servers that are to perform LAN free backup. I know that I need to drivemapp all the SAN drives but what will TSM do with the SCSI attached drives, is it cleaver enough to make sure that it doesn't mount any tapes for LAN free backups and restores in those drives? Why not upgrade all drives? Money, money... This setup: -TSM server 4.2 on AIX 4.3.3 -3494 libraries -3590E tapes (SCSI and SAN) Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962
Re: Upgradeing 3494 drives
Lawrence, I guess you are talking about 3590 drives in a 3494 library? For that there are some good info in the README file for the server (see below). We upgraded all the drives to E drives at the same, if you only got 2 then it makes sense to do both at the same time. Just remember to put all existing none-scratch tapes into readonly, they can't be written to until they have gone back to scratch through expire (and move data). (Read is no problem from the upgraded drives). Make sure you are upto date with all SW including TSM/library/drives. = README.SRV=== 1. All 3590 drives within physical library are upgraded with 3590E drives at the same time. Consider an example with one 3590 drive physically defined as /dev/rmt0. Assume that there were originally defined devclass, logical library, and storage pool for 3590 drive. There were also some volumes (tape cartridges) checked in the library with data written on that drive. Replaced 3590 drive with 3590E drive. Steps below will allow you to use the new 3590E drives with minimum changes to TSM server: - Using SMIT utility or manually, remove /dev/rmt0 device example: rmdev -l 'rmt0' '-d; - Using SMIT utility or manually, define the 3590E device example: mkdev -c tape -t '3590' -s 'scsi' -p 'scsi0' -w '0,0' -l 'rmt0'; - Run TSM server (dsmserv); - Issue TSM command: UPDate DEVclass devclassname FORMAT=DRIVE update devclass devclass_3590 FORMAT=DRIVE; - Issue TSM command: DELete DRive libname drivename delete drive lib_3590 drive_3590; - Issue TSM command: DEFine DRive libname drivename DEVIce=devicename define drive lib_3590 drive_3590 device=/dev/rmt0; - Users must update storage pool volumes to have ACCESS=READONLY under the following conditions. Users do not have to follow this procedure for database backup, dump or export volumes. For storage pool volumes: 1) The volume currently has READWRITE access. 2) The volume was previously written on 3590 drive. For example, UDPATE VOLUME volname ACCESS=READONLY WHEREACCESS=READWRITE This also applies to DRM-managed copy storage pool volumes that are in the MOUNTABLE state. For DRM-managed volumes that are not available to the TSM server (i.e., the volumes are not in MOUNTABLE state), the user does not need to take any action. If copy storage pool volumes are brought back on-site to recover the ADSM server, the COPYSTGPOOL VOLUMES AVAILABLE macro will update the access of the copy storage pool volumes to READONLY. For any other off-site volume (ACCESS=OFFSITE), the user must update the access to READONLY after the volumes are brought back on-site. ... Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 14, 2002 3:43 PM To: [EMAIL PROTECTED] Subject: Upgradeing 3494 drives We are upgradeing the drives in our 3494 library to: -double the storage capacity of the J cartridges -convert from SCSI to fibre There seems to be a question of if we need to convert just one drive and move the data to the newly defined lib / drive or can we simply convert both drives, as long as the drives remain in the same library defined to TSM. Has anyone done this? The existing cartridges can be read by the upgraded drives ( but noit written to ). I guess the question is will TSM use the newly defined drives when a call for a cartridge with existing data is made.
Advanced initSID.utl for TDP for SAP R/3 (Backint)
Hi, I am using TDP for SAP R/3 V3.2.0.8 and I would appreciate your help in accomplishing the following: -2 copies of the REDO logs, each copy is to go to a different TSM server (different sites) -I would like to switch between the TSM servers on a daily base so that the on/offline backup on day 1 goes to site A's server and on day 2 goes to site B (this is easy in the utl except for the fact that 2 days in a week it will go to the same site) -If one TSM server isn't available I would like both redolog copies to the other server and also the on/offline to the other server All of this to: -Avoid having to do offsiting through tape to tape copy every day of ~10TB of SAP data -To get highly available data as a restore with the new setup should in worst case involve going back 3 days + redo logs if I have a site failure (or a TSM server down). (Tape to tape copy doesn't solve this as it takes ages to do ~10TB a day). My problem is the setup within one utl file to accomplish both the switch and the 2 copies of the REDO LOGS. It looks like it is easy for 1 tape drive used for on/off but it seems that I need to have 3 redolog copies if I would like to use 2 tape drives for the on/offline backups. (And 4 if using 3 drives). This is a lot of copies to store... Does anyone of you have a more simpler setup that can do the same trick? HACMP for TSM will take care of the unavailable TSM server but I will still need to switch to be able to store the data in two different libraries/sites. Our SAP gurus prefer to use only one utl file... Attached is a file with: -Example 1 with 1 tape drive used for the on/offline backups. -Example 2 with 2 tape drives used for the on/offline backups, one high speed LAN. -Example 3 with 3 tape drives used for the on/offline backups, one high speed LAN. -Example 4 with 2 tape drives used for the on/offline backups, one drive per ATM adapter. (Redologs goes always first to disk) <> Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 Hi, I am using TDP for SAP R/3 V3.2.0.8 and I would appreciate your help in accomplishing the following: -2 copies of the REDO logs, each copy is to go to a different TSM server (different sites) -I would like to switch between the TSM servers on a daily base so that the on/offline backup on day 1 goes to site A's server and on day 2 goes to site B (this is easy in the utl except for the fact that 2 days in a week it will go to the same site) -If one TSM server isn't available I would like both redolog copies to the other server and also the on/offline to the other server All of this to: -Avoid having to do offsiting through tape to tape copy every day of ~10TB of SAP data -To get highly available data as a restore with the new setup should in worst case involve going back 3 days + redo logs if I have a site failure (or a TSM server down). (Tape to tape copy doesn't solve this as it takes ages to do ~10TB a day). My problem is the setup within one utl file to accomplish both the switch and the 2 copies of the REDO LOGS. It looks like it is easy for 1 tape drive used for on/off but it seems that I need to have 3 redolog copies if I would like to use 2 tape drives for the on/offline backups. (And 4 if using 3 drives). This is a lot of copies to store... Does anyone of you have a more simpler setup that can do the same trick? HACMP for TSM will take care of the unavailable TSM server but I will still need to switch to be able to store the data in two different libraries/sites. Our SAP gurus prefer to use only one utl file... Below are: -Example 1 with 1 tape drive used for the on/offline backups. -Example 2 with 2 tape drives used for the on/offline backups, one high speed LAN. -Example 3 with 3 tape drives used for the on/offline backups, one high speed LAN. -Example 4 with 2 tape drives used for the on/offline backups, one drive per ATM adapter. (Redologs goes always first to disk) # Example 1 with 1 tape drive used for the on/offline backups. ... MAX_BACK_SESSIONS 1 MAX_ARCH_SESSIONS 2 REDOLOG_COPIES 2 MAX_RESTORE_SESSIONS1 ... # Days 0 2 4 6 to Site A #Normal on/offline on 0 2 4 6 and copy 1 of redologs SERVER SITE_A_DAY_X# Servername SESSIONS1 # Max sessions PASSWORDREQUIREDYES # Use a password ADSMNODESID # ADSM Nodename BRBACKUPMGTCLASSSAP_ON_OFF # Mngm-Classes BRARCHIVEMGTCLASS SAP_LOG_1 SAP_LOG_2 # Mngm-Classes USE_AT
Re: 3583 LTO problems
Sam, We had a similar problem. The library reconfigure itself every time you have had the door open, it reads some barcode labels internally that tells it what HW is installed and the barcode could be dirty/destroyed such that it isn't aware of the magazines in the door. HW support should be able to fix it (they had to replace parts in it for us). Regards, Jan Norback Tivoli Certified Consultant: ADSM/TSM IBM Cert. Adv. Technical Expert RS/6000 AIX Atos Origin-IT (MS/DS/OSS Unix) VA-106, PO-box 218, 5600 MD Eindhoven, The Netherlands Groenewoudseweg 1 5621 BA Eindhoven, The Netherlands Email: [EMAIL PROTECTED] Tel: +31 (0)40-2780289 Mobile: +31 (0)6-12994492 Fax : +31 40 2783962 -Original Message- From: Sam Schrage [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 28, 2002 4:23 PM To: [EMAIL PROTECTED] Subject: 3583 LTO problems Any one have a problem with TSM auditing a LTO 3583 library. Some of my tapes are missing but when I open the door of the library I see all the tape slots full. I use the I/O door to input tapes only as SCRATCH so all tapes in the library should be known to TSM as SCRATCH or PRIVATE. When the 3583 reinitializes after the door is open sometime it sees the magazines in the door...sometimes not. I think it's more a hardware problem than TSM...until the hardware sees the tapes correctly TSM won't. Any ideas. Call has been logged to hardware support. Sam Schrage TRW Systems 615-360-4716
Re: 2 identical libraries and 1 TSM Server.
Fran, You can find a device table on here: http://www.tivoli.com/support/storage_mgr/devices/atab101.htm Note: we use W2K with the TSM device driver (TSM 4.2.1) and started with device 257 in our 3584. Regards, Jan Norback -Original Message- From: Francisco Molero [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 11:15 AM To: [EMAIL PROTECTED] Subject: 2 identical libraries and 1 TSM Server. Hi all, I have 2 libraries 3584. When I define the drives in the first library no pb. def drive lib1 drive1 element=256 But when I define de drive in de second library. def drive LIB2 DRIVE55 element=256 I get a msg : ANR8419E DEFINE DRIVE: element conflicts... 1.- What should the element be?? 2.- Has somebody a similar configuration, 2 identical libraries and 1 tsm server ? Thanks in advance, FRAN. ___ Do You Yahoo!? Yahoo! Messenger Comunicacisn instantanea gratis con tu gente. http://messenger.yahoo.es
Re: Backint / Brarchive (SAP) Errors
Eugene, The version you are running, Version 2, Release 4, Level 25.5 for AIX LF, is rather old. Have you checked if it is supported on your OS/TSM: http://www-5.ibm.com/de/entwicklung/tdp/matrix.html : "The minimum ADSM / TSM API level depends on the operating system level. This version does not work with TSM API level 4.1 ! AIX 4.2, 4.3 2.4.15.5 multi-threaded ADSM API level 3.1.0.6 AIX 4.2, 4.3 2.4.25.5 multi-threaded TSM API level 3.7.0 HP-UX 10.20 2.4.10.5 single-threaded ADSM API level 3.1.0.3 HP-UX 11 2.4.15.5 multi-threaded ADSM API level 3.1.0.5 HP-UX 11 2.4.25.5 multi-threaded TSM API level 3.7.1 ONLY Sun Solaris 2.5.1 2.4.15.5 multi-threaded ADSM API level 3.1.0.3 Sun Solaris 2.6, 7 2.4.15.5 multi-threaded ADSM API level 3.1.0.6 Sun Solaris 7 2.4.25.5 multi-threaded TSM API level 3.7.0 Tru64 Unix 4.0 2.4.15.5 multi-threaded ADSM API level 3.1.0.3 Windows NT 3.51, 4.0 2.4.15.5 multi-threaded ADSM API level 3.1.0.5 Windows NT 3.51, 4.0 2.4.25.5 multi-threaded TSM API level 3.7.0 " Regards, Jan Norback -Original Message- From: Eugene Awyong - Singapore [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 11:07 AM To: [EMAIL PROTECTED] Subject: Backint / Brarchive (SAP) Errors Hello, I am having problems with the setting up of brarchive/backint. Not sure if it is a TSM problem or R3 one. The errors I get are 'Segmentation violation' and 'Illegal instruction'. Anyone able to help? TIA! sepco_dev:oraph1 12> brarchive -sd -p /oracle/PH1/dbs/initPH1.sap -c -l E -d util_file -u system/ph2ok BR002I BRARCHIVE 4.6D (16) BR006I Start of offline redo log processing: adhvhcbw.svd 2002-04-24 16.44.48 BR049W Last BRARCHIVE run was probably killed BR280I Time stamp 2002-04-24 16.44.49 BR008I Offline redo log processing for database instance: PH1 BR009I BRARCHIVE action ID: adhvhcbw BR010I BRARCHIVE function ID: svd BR011I 83 offline redo log files found for processing, total size 1659.963 MB BR130I Backup device type: util_file BR109I Files will be saved by backup utility BR126I Unattended mode active - no operator confirmation required BR280I Time stamp 2002-04-24 16.44.49 BR229I Calling backup utility... BR278I Command output of '/usr/sap/PH1/SYS/exe/run/backint -u PH1 -f backup -i /oracle/PH1/sapbackup/.adhvhcbw.lst -t file -p /oracle/PH1/dbs/initPH1.utl -c': Tivoli Data Protection for SAP R/3 Interface between SAPDBA Utilities and Tivoli Storage Manager - Version 2, Release 4, Level 25.5 for AIX LF - (c) Copyright IBM Corporation, 1996, 1999, All Rights Reserved. Segmentation violation Illegal instruction ^C BR281W Program interrupted by signal 2 BR269W Wait situation interrupted - probably cannot continue BR280I Time stamp 2002-04-24 16.45.06 BR256I Please enter 'cont' to continue, 'stop' to cancel the program: stop BR257I Your reply: 'stop' BR280I Time stamp 2002-04-24 16.45.08 BR260E BRARCHIVE canceled by user BR007I End of offline redo log processing: adhvhcbw.svd 2002-04-24 16.45.08 BR280I Time stamp 2002-04-24 16.45.09 BR005I BRARCHIVE terminated with errors sepco_dev:oraph1 13>
Re: TDP for R3 and MSSQL
Stefan, You need to use TDP for SQL Server to backup your SAP DB in this case. See: http://www.tivoli.com/support/public/Prodman/public_manuals/td/DataProtectio nforMicrosoftSQLServer2.2.1.html /Jan Norback -Original Message- From: Stefan Holzwarth [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 2:09 PM To: [EMAIL PROTECTED] Subject: TDP for R3 and MSSQL Hallo, does anyone knows whether TDP for SAP R3 has support for R3 running with MS SQL Server? The documentation i found only refers to Oracle. With Regards, Stefan Holzwarth -- Stefan Holzwarth ADAC e.V. (Informationsverarbeitung - Systemtechnik - Basisdienste) Am Westpark 8, 81373 München, Tel.: (089) 7676-5212, Fax: (089) 76768924 mailto:[EMAIL PROTECTED]
