Re: tape status
Hi Deon, Q vol gpc027 f=d gives me nothing, however if i do q volhist type=dbb then it shows Date/Time: 10/21/2003 09:45:43 Volume Type: BACKUPFULL Backup Series: 214 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS Volume Name: GPC027 Volume Location: Command: Regards Dat -Original Message- From: Deon George [mailto:[EMAIL PROTECTED] Sent: Friday, 24 October 2003 3:32 PM To: [EMAIL PROTECTED] Subject: Re: tape status Dat, No, TSM will NEVER let you (re)label a tape, if the tape is already known to the current TSM server (ie: it is defined in Q VOLHIST or Q VOL). If you try, in your activity log you'll see a label libv failure and the reason why (and the existing label)... If the tape was previously defined (you saw it in Q VOL), and now you cant see it in Q VOL, then it is one of two things: * It was a SCRATCH volume, that became empty and TSM deleted it. * It was not a scratch volume, but a defined volume (DEF VOL command) and somebody deleted it. (You will know if volumes are scratch when you do a Q VOL F=D and look at the Scratch: line. ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 24/10/2003 02:10:47 PM: Deon, Sorry if i was a bit vague, the question i am asking is does relable destroy existing known tsm tapes or does tsm smart enough to know and prevent you from doing it. Secondly the tape was already define to tsm previous, why now does it give me this error (we havent use it elsewhere) ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11 I've also tried q libvol , but the tape isnt there either. Regards Dat -Original Message- From: Deon George [mailto:[EMAIL PROTECTED] Sent: Friday, 24 October 2003 1:36 PM To: [EMAIL PROTECTED] Subject: Re: tape status Dat, Q VOL will only show SCRATCH tapes that have data on them, or DEFINED tapes (when you use the define vol command), or sometimes (as you've captured below), you will also see SCRATCH tapes that are EMPTY - this will be because: * They recently became empty and TSM hasnt yet deleted them (returning them to the scratch pool) - very rare, * They are empty and offsite (as your example is below), (Offsite SCRATCH volumes that are empty, remain in Q VOL so that you can bring them back onsite - as soon as you mark them as onsite, they will be deleted from Q VOL). Now, if your tapes are empty and in your library and you CANT see them with q VOL, then you will be able to see the with Q LIBV. If you do a HELP UPDATE VOL - it'll tell you when TSM will delete SCRATCH volumes from Q VOL. To answer your question, do you need to relabel them - no. (You would only need to relabel tapes if they were used by something outside of TSM - which overwrote the TSM label.) ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 24/10/2003 10:34:24 AM: Hi, I got LTO tapes that that was labelled into a 3583 library some months back, now when i do a query volume, ie q vol gpc027 f=d I get a message: ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. If the tape has expired as tape as part of the system policy, wouldnt i get a message like below, eg Volume Status: Empty: Volume Name: GPC093 Storage Pool Name: COPYSAP_LOG1 Device Class Name: LTOCLASS Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 3 Write Pass Number: 1 Approx. Date Last Written: 08/04/2003 03:33:02 Approx. Date Last Read: 08/02/2003 15:04:23 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): SCRIPT Last Update Date/Time: 08/04/2003 11:31:55 Can someone confirm if at this stage i will need to to relabel the tape into the library. Thank you Dat Vo System Administrator # * CONFIDENTIAL * We apologise if this message has
Re: Backing up SAP on Adabas
I have no problem access this page through my IBM ID. http://www-5.ibm.com/de/entwicklung/adint_tsm/ Another goal is that this product is very expensive (as I find out) and the customer decided not to use it for backup, because they plan to migrate this system to Oracle in 6 months. Tom -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Zlatko Krastev Sent: Thursday, October 23, 2003 4:28 PM To: [EMAIL PROTECTED] Subject: Re: Backing up SAP on Adabas I have visited successfully that page in the past. Now it is protected and I was unable to access it. Maybe according to new IBM's policies we are supposed to pay to look at their advertizing and product info :-((( Well done web! Congratulations to the corporation which constantly is shooting itself in the foot! Zlatko Krastev IT Consultant - (on mbox.infotel.bg) email-body was scanned and no virus found -
Re: TDP for Lotus Domino 5.1.5.1
Rainer I don't know the answer to your 1st question - we just accept the thousands of messages on the log. We run the log through a filter script to select the ones we're interested in, so we keep the full log on the server in case we need to read it, and use the filtered version for daily monitoring. The standard answer to your 2nd question is to put the backup command into the background (possibly by using a script), so that the scheduler returns control immediately and can then go on and do other things like archiving logs. We've had to do this for all large backups (SAP, Domino and filesystems), otherwise disk areas for archive logs fill up, as you predict. You lose the return code in TSM, but if you write a script you can monitor that yourself. See the ADSM-L archives for many discussions of this. Richard Foster *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. ***
Solaris TSM device driver and STK9840 FC drives
Hi all, I need solve some problem or rather TSM system strategy concerning using (or not) of TSM device driver on Solaris. I am not Solaris guru, I have only basic knowledge, in oposit our Solaris people have no idea about TSM. We have stabilized TSM environment with TSM server on W2000 using STK9310 Powderhorn with STK9840 and STK9940 drives. Drives are connected to W2000 through SN/6000. Library is controled by Gresham EDT. In W2000 system we need to use STK drivers (no problem) for FC drives, so TSM device driver is not started and used. Now we decided put ito operation TSM Solaris with similar TSM environment - it means the same FC STK drives connected through SN/6000, using Gresham EDT to control library. Now in solaris system I see 16 virtual drives (2x 8 on 2 FC HBA). There is STK driver module instaled in system (st device driver in /kernel/drv) an loaded (when I put 'modinfo | grep -i scsi' ... I see st (scsi tape device driver)). In /dev/rmt I see 24 different devices for each FC drive numbered 0*-15* (see attached ls.txt). Question: 1. Do I need install and use TSM device driver to use this FC drives through Gresham EDT? I expect that TSM device driver create its own *mt devices linked to some of existing /dev/rmt devices and I will use these *mt devices in Gresham configuration file. I tried to install it but if failed to attach with drives and create *mt devices. 2. If not, which of existing devices am i supposed to use with Gresham and TSM to use this drives? Environment: Solaris 9 at SunFire 6800, TSM v5.2.1.0 server STK drives are configured at HBAs through jnic164x drivers Thanks for any suggestion. Tomas
/ /OREF:CPTCEFC8 Need info re configuring disks for AIX Sanergy MDC
We are trying to share SAN disks from a AIX 4.3.3 32-bit MDC, but since SANergy doesn't support LVM how do you configure the disks outside of LVM, and how do you configure it under SANergy? Also, is anyone using IBM's SDD and vpaths under SANergy MDC.?? Cecily Hewlett
3494 Library and dual gripper?
Hello. It's more hardware than software problem, but I think it's the best place to ask. What are the advantages of using dual gripper instead of single one? Did You observe any improvement in library's performance? Currently we have few 'traffic jams' during the day and are thinking about changing our single gripper to dual one. But I'm not sure will it help solve our performance problems :( -- Przemysaw Maciuszko Agora SA
Re: tape status
I got LTO tapes that that was labelled into a 3583 library some months back, now when i do a query volume, ie q vol gpc027 f=d I get a message: ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. Refer to the Admin Ref description of the Query Volume command: Use this command to display information about one or more storage pool volumes. It is simply the case that that volume is not currently in a storage pool: it is an unused tape in your library which could be used for various purposes, one of which is data storage in a storage pool. I would strongly recommend going through the redbook Tivoli Storage Management Concepts as well as the Admin Guide manual, to gain a solid understanding of the product before venturing into its more difficult terrain. Richard Sims, http://people.bu.edu/rbs
Re: 3494 Library and dual gripper?
It's more hardware than software problem, but I think it's the best place to ask. What are the advantages of using dual gripper instead of single one? Did You observe any improvement in library's performance? Currently we have few 'traffic jams' during the day and are thinking about changing our single gripper to dual one. But I'm not sure will it help solve our performance problems :( To ask such a question, you must not have children. :-) When things get busy in the household called the tape library, the accessor saves travel by being able to pick up two nearby tapes in order to feed drives, or remove two tapes from adjacent drives which have unloaded them. It does make a difference. Whether the difference is worth that much extra cost has to be determined by how busy your system is and how much time costs your company. Keep in mind that tape shuffling by the robot constitutes only a small fraction of the time that it takes a tape to become available: load/unload/positioning times are usually substantial (a minute or more), being the largest factor in data availability time. A dual gripper shaves some seconds off the overall time. We happen to have a dual gripper, and our LM stats show it being used about 40% of the time. Looking in on your tape library with a stopwatch, with a TSM console nearby, is a good way to see where time is consumed when data/service is requested and tape work has to be done. Your choice of tape drive technology is the major factor in overall access speed. Richard Sims, BU
NO tapes!!!
I am still a rookie with TSM... There is no tape backup produced at all since wednesday. We are using the TSM Operational Reporting and nothing showing us that there is a problem... Is there a way to know what exactlty is causing this kind of behavior... We used to have 2-3 tapes to send every day! Now, it is started with 1-2 and nothing at all... Where do I need to check in order to, at least, know what is going on? Stephan
Re: NO tapes!!!
Check to see if migration is working/setup -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stephan Dinelle Sent: Friday, October 24, 2003 7:27 AM To: [EMAIL PROTECTED] Subject: NO tapes!!! I am still a rookie with TSM... There is no tape backup produced at all since wednesday. We are using the TSM Operational Reporting and nothing showing us that there is a problem... Is there a way to know what exactlty is causing this kind of behavior... We used to have 2-3 tapes to send every day! Now, it is started with 1-2 and nothing at all... Where do I need to check in order to, at least, know what is going on? Stephan
write speed for LTO2 drive using LTO1 tape
Hi, has anyone tried backing up an image to a LTO2 drive using LTO1 tapes, if yes what throughput did you get? we tried LAN free backups using an EMC Clariion CX400 and pathlight SAN gateway with 1 G switches, the max throughput was only 26 MB/sec suggesting that LTO2 drives can only write at LTO1 drive max write speed. (specs 30MB/s compressed) Any confirmation of this would be appreciated. TSM Server 5.2.1.1, STA 5.2.1.1, TSM client 5.2.0.3 W2k environment Mit freundlichen Grüßen / Best Regards Markus Veit
Re: NO tapes!!!
Where and how? I am using the Web interface of TSM for Windows 5.1.64... Wholey, Joseph (IDS DMDS) [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 10/24/2003 07:29 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: NO tapes!!! Check to see if migration is working/setup -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Stephan Dinelle Sent: Friday, October 24, 2003 7:27 AM To: [EMAIL PROTECTED] Subject: NO tapes!!! I am still a rookie with TSM... There is no tape backup produced at all since wednesday. We are using the TSM Operational Reporting and nothing showing us that there is a problem... Is there a way to know what exactlty is causing this kind of behavior... We used to have 2-3 tapes to send every day! Now, it is started with 1-2 and nothing at all... Where do I need to check in order to, at least, know what is going on? Stephan
Re: Cleaning Machine for 3590 cartridges
You did not called it IBM but I assumed it being unaware of the device. Thanks to Richard's clarification I was able to figure it out. Now to the topic: if you really need to use such machine, it would certainly mean your server room environment is *dirty*! If it indeed is, the risk of losing data would be rather close to the risk when you are not doing backups at all. I can only quote a sentence not invented by me: Poor security is worse than no security at all, as it provides fake sense of security! If your library environment is clean enough (through using and regular cleaning of appropriate filters in conditioners) and your operators are handling tapes only through library I/O station - you should not need such a device. At that point I personally would react nearly as Tom suggested. Zlatko Krastev IT Consultant Pearson, Dave [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 23.10.2003 17:26 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Cleaning Machine for 3590 cartridges I apolgise for calling the 3599 model an IBM My mistake. I was just giving one model of cartridge cleaning machine called 3599 (Yes there are cartridge cleaning meachine out there.) There is another cleaning machine called.. STAR 3590 cartridge cleaning machine. I'm sure there are many other 'brand' of machine that clean tapes/cartridge. Ziatko, does you company clean their cartridges on these type of machine? If so, Is it worth it? if not... why you don't use them? Thanks again Ziatko. Dave Pearson -Original Message- From: Zlatko Krastev [SMTP:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 5:13 AM To: [EMAIL PROTECTED] Subject: Re: Cleaning Machine for 3590 cartridges IBM 3599 is not a machine, but so called machine type / model for ordering any Magstar cartridges. 3599-001, -002, -003 are 3590 J cartridges (10/20/30 GB) 3599-004, -005, -006 are 3590 K cartridges (20/40/60 GB) 3599-007 is 3590 cleaning cartridge (what probably you are looking for!!!) 3599-011, -012, -013 are 3592 cartridges (300 GB) 3599-017 is 3592 cleaning cartridge. This is a second method to order cartridges through IBM Storage channel. The first is as components of 3590 drives. Same is for LTO - they can be ordered as part of 358x unit or separately as 3589-xxx media. If you need short confirm: Yes, this is working/supported cleaning media for any IBM 3590 drives (standalone, within IBM 3494, or within StorageTek silo)! Machine type does not mean automatically hardware. For example before joining Passport Advantage, TSM was machine type/model 5697-TSM and later 5698-TSM! Zlatko Krastev IT Consultant
Re: 3494 Library and dual gripper?
A dual gripper shaves some seconds off the overall time. It may be worth pointing out that a dual gripper loses you some library tape slots - 10% of them, in fact. The upper gripper cannot reach the lowest 2 slot levels, nor can the lower gripper reach the highest 2 levels. Therefore these 4 levels are lost (and are physically blanked off in our library). It's an open question why IBM chose to do it that way, because it was surely possible to program the control PC to use the appropriate gripper for these levels. Probably that nice warm feeling of redundancy. Richard Foster *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. ***
Re: SV: Query from z/OS-platform to intel-platform
Hot Diggety! Richard Sims was rumored to have written: 3. What does the rumor say - when can we expect a real DB2 ;-) Imagine what the licensing fee for TSM would be then!! ;-)) Might jack up the price quite a bit... but would likely still be several orders of magnitude cheaper than licensing Oracle ;) /tongue-in-cheek We've got various of the major databases in-house, and the licensing costs for each is just simply... *amazing*. On some days, I get the distinct impression we're singlehandedly paying for Oracle CEO Larry Ellison's private high-performance jet. -Dan
Re: NO tapes!!!
There is no tape backup produced at all since wednesday. We are using the TSM Operational Reporting and nothing showing us that there is a problem... You learn the limits of generalized monitoring aids... Pursue the basics: Look in your server Activity Log for indications of problems in general. Was the client machine even up to run a backup? Was it supposed to produce the backup via a Client Schedule, and was the scheduler not running on that client (or the alternate dsmcad not running)? Any errors in the client's dsmerror.log? Basically, gather facts from all the places where things are supposed to be done to facilitate the backup, and see what happened. The obvious thing is to determine what happened in the Wednesday timeframe to cause the backups to stop. The is where the discipline of a system change log comes in handy at a data processing site: who changed what, when, why. Richard Sims, BU
Re: 3494 Library and dual gripper?
We happen to have a dual gripper, and our LM stats show it being used about 40% of the time. Where/how is this information reported?
Re: tape status
The q volhist indicates that the tape is currently inuse as a tsm database backujp. [EMAIL PROTECTED] 10/24/2003 3:14:13 AM Hi Deon, Q vol gpc027 f=d gives me nothing, however if i do q volhist type=dbb then it shows Date/Time: 10/21/2003 09:45:43 Volume Type: BACKUPFULL Backup Series: 214 Backup Operation: 0 Volume Seq: 1 Device Class: LTOCLASS Volume Name: GPC027 Volume Location: Command: Regards Dat -Original Message- From: Deon George [mailto:[EMAIL PROTECTED] Sent: Friday, 24 October 2003 3:32 PM To: [EMAIL PROTECTED] Subject: Re: tape status Dat, No, TSM will NEVER let you (re)label a tape, if the tape is already known to the current TSM server (ie: it is defined in Q VOLHIST or Q VOL). If you try, in your activity log you'll see a label libv failure and the reason why (and the existing label)... If the tape was previously defined (you saw it in Q VOL), and now you cant see it in Q VOL, then it is one of two things: * It was a SCRATCH volume, that became empty and TSM deleted it. * It was not a scratch volume, but a defined volume (DEF VOL command) and somebody deleted it. (You will know if volumes are scratch when you do a Q VOL F=D and look at the Scratch: line. ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 24/10/2003 02:10:47 PM: Deon, Sorry if i was a bit vague, the question i am asking is does relable destroy existing known tsm tapes or does tsm smart enough to know and prevent you from doing it. Secondly the tape was already define to tsm previous, why now does it give me this error (we havent use it elsewhere) ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11 I've also tried q libvol , but the tape isnt there either. Regards Dat -Original Message- From: Deon George [mailto:[EMAIL PROTECTED] Sent: Friday, 24 October 2003 1:36 PM To: [EMAIL PROTECTED] Subject: Re: tape status Dat, Q VOL will only show SCRATCH tapes that have data on them, or DEFINED tapes (when you use the define vol command), or sometimes (as you've captured below), you will also see SCRATCH tapes that are EMPTY - this will be because: * They recently became empty and TSM hasnt yet deleted them (returning them to the scratch pool) - very rare, * They are empty and offsite (as your example is below), (Offsite SCRATCH volumes that are empty, remain in Q VOL so that you can bring them back onsite - as soon as you mark them as onsite, they will be deleted from Q VOL). Now, if your tapes are empty and in your library and you CANT see them with q VOL, then you will be able to see the with Q LIBV. If you do a HELP UPDATE VOL - it'll tell you when TSM will delete SCRATCH volumes from Q VOL. To answer your question, do you need to relabel them - no. (You would only need to relabel tapes if they were used by something outside of TSM - which overwrote the TSM label.) ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote on 24/10/2003 10:34:24 AM: Hi, I got LTO tapes that that was labelled into a 3583 library some months back, now when i do a query volume, ie q vol gpc027 f=d I get a message: ANR2034E QUERY VOLUME: No match found using this criteria. ANS8001I Return code 11. If the tape has expired as tape as part of the system policy, wouldnt i get a message like below, eg Volume Status: Empty: Volume Name: GPC093 Storage Pool Name: COPYSAP_LOG1 Device Class Name: LTOCLASS Estimated Capacity (MB): 0.0 Pct Util: 0.0 Volume Status: Empty Access: Offsite Pct. Reclaimable Space: 0.0 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 3 Write Pass Number: 1 Approx. Date Last Written: 08/04/2003 03:33:02 Approx. Date Last Read: 08/02/2003 15:04:23 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): SCRIPT Last Update Date/Time: 08/04/2003 11:31:55 Can someone confirm if at this stage i will need to to relabel the tape into the library. Thank you Dat Vo System
Re: 3494 Library and dual gripper?
We happen to have a dual gripper, and our LM stats show it being used about 40% of the time. Where/how is this information reported? David - See http://people.bu.edu/rbs/ADSM.QuickFacts for such factoids: Dual Gripper usage statistics Gripper usage info is available from the 3494's Service Mode... Go to the Service menu thereunder, and select View Usage Info. Richard
Re: Move nodedata - what is moved first
What would happen if there was a site disaster and the data was only on the disk which is no longer available to perform restores? I guess what I am asking is, without sending DIRMC off-site, can you recover from a site disaster? |-+--- | | Deon George | | | [EMAIL PROTECTED]| | | .COM | | | Sent by: ADSM: | | | Dist Stor | | | Manager| | | [EMAIL PROTECTED]| | | T.EDU | | | | | | | | | 10/23/2003 08:07| | | PM | | | Please respond | | | to ADSM: Dist | | | Stor Manager | | | | |-+--- ---| | | |To: [EMAIL PROTECTED] | |cc: | |Subject: Re: Move nodedata - what is moved first | ---| Peter, servers . Currently, our main file server has data on over 200 3590 tapes therefore a directory restore can potentially have hours added to the process directly related to tape mounts. Is the directory information you referring about related to Windows systems? You should use the DIRMC client option to store all your directory information in a DISK based storage pool (DISK or FILE), so that it remains on faster quicker access media for restore purposes. (Dont let that stuff go to tape for the reasons you have outlined below.) The DIRMC client option is not really required for Unix based systems, as the database has enough space to store that information. ...deon --- Have you looked at the A/NZ Tivoli User Group website? http://www.tuganz.org Deon George, IBM Tivoli Software Engineer, IBM Australia Office: +61 3 9626 6058, Fax: +61 3 9626 6622, Mobile: +61 412 366 816, IVPN +70 66058 mailto:[EMAIL PROTECTED], http://www.ibm.com/tivoli
Re: Move nodedata - what is moved first
What would happen if there was a site disaster and the data was only on the disk which is no longer available to perform restores? I guess what I am asking is, without sending DIRMC off-site, can you recover from a site disaster? Marc - That would be the moral equivalent of a -FILESOnly restoral, wherein TSM creates default directories and attributes...not necessarily the best thing, but usually workable. Note that TSM typically performs restorals via this paradigm, restoring file system objects in the order that it finds them on tapes, to avoid reprocessing tapes, creating surrogate directories until the actual directory info may be found later in the current or subsequent tape. See topic Restore Order in http://people.bu.edu/rbs/ADSM.QuickFacts . Richard Sims, BU
Re: Cleaning Machine for 3590 cartridges
Hi Zlatko, Thanks for replying... The problems we are having is we been getting a lots of read/write error on our 3590 J tapes. We have about 1300 tapes in our 3494library and in just the last 2 months, we have gotten 13 read/write errors on our tapes. Before the upgrade we very rarely see a bad tape and now we see too many. Last summer, we did expand our 3494library adding two frame and another assessor to the library. We also upgraded our 3590 tape drive from B1A to H1A. We are on the latest ATAPE driver too. David C. Pearson IS Production Support Analyst System Network Service Snohomish County PUD # 1 ole0.bmp Phone: 425.347.4420 Pager: 425.290.0944 FAX: 425.267.6380 E-mail: [EMAIL PROTECTED] -Original Message- From: Zlatko Krastev [SMTP:[EMAIL PROTECTED] Sent: Friday, October 24, 2003 4:50 AM To: [EMAIL PROTECTED] Subject:Re: Cleaning Machine for 3590 cartridges You did not called it IBM but I assumed it being unaware of the device. Thanks to Richard's clarification I was able to figure it out. Now to the topic: if you really need to use such machine, it would certainly mean your server room environment is *dirty*! If it indeed is, the risk of losing data would be rather close to the risk when you are not doing backups at all. I can only quote a sentence not invented by me: Poor security is worse than no security at all, as it provides fake sense of security! If your library environment is clean enough (through using and regular cleaning of appropriate filters in conditioners) and your operators are handling tapes only through library I/O station - you should not need such a device. At that point I personally would react nearly as Tom suggested. Zlatko Krastev IT Consultant Pearson, Dave [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 23.10.2003 17:26 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Cleaning Machine for 3590 cartridges I apolgise for calling the 3599 model an IBM My mistake. I was just giving one model of cartridge cleaning machine called 3599 (Yes there are cartridge cleaning meachine out there.) There is another cleaning machine called.. STAR 3590 cartridge cleaning machine. I'm sure there are many other 'brand' of machine that clean tapes/cartridge. Ziatko, does you company clean their cartridges on these type of machine? If so, Is it worth it? if not... why you don't use them? Thanks again Ziatko. Dave Pearson -Original Message- From: Zlatko Krastev [SMTP:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 5:13 AM To: [EMAIL PROTECTED] Subject: Re: Cleaning Machine for 3590 cartridges IBM 3599 is not a machine, but so called machine type / model for ordering any Magstar cartridges. 3599-001, -002, -003 are 3590 J cartridges (10/20/30 GB) 3599-004, -005, -006 are 3590 K cartridges (20/40/60 GB) 3599-007 is 3590 cleaning cartridge (what probably you are looking for!!!) 3599-011, -012, -013 are 3592 cartridges (300 GB) 3599-017 is 3592 cleaning cartridge. This is a second method to order cartridges through IBM Storage channel. The first is as components of 3590 drives. Same is for LTO - they can be ordered as part of 358x unit or separately as 3589-xxx media. If you need short confirm: Yes, this is working/supported cleaning media for any IBM 3590 drives (standalone, within IBM 3494, or within StorageTek silo)! Machine type does not mean automatically hardware. For example before joining Passport Advantage, TSM was machine type/model 5697-TSM and later 5698-TSM! Zlatko Krastev IT Consultant ole0.bmp
Re: Cleaning Machine for 3590 cartridges
Dave, Remember that by going from B drives to H drives you are now writing 3 times as many tracks (128 vs 384) per tape, and 3 times as much data per cartridge. Consequently, you will almost certainly have some marginal tapes that would work at the lower density that will now likely give problems. Every site that we have assisted with such an upgrade has experienced some number of cartridges that have shown up as bad after the upgrade. Upgrading Atape will probably not be much help here. If these are IBM cartridges, remember that these have a lengthy warranty that you can take advantage of (800-IBM-MEDIA); if they are another brand, check their warranty policies. Regards, -Lloyd On Fri, 24 Oct 2003 07:27:01 -0700 Pearson, Dave [EMAIL PROTECTED] wrote thusly: Hi Zlatko, Thanks for replying... The problems we are having is we been getting a lots of read/write error on our 3590 J tapes. We have about 1300 tapes in our 3494library and in just the last 2 months, we have gotten 13 read/write errors on our tapes. Before the upgrade we very rarely see a bad tape and now we see too many. Last summer, we did expand our 3494library adding two frame and another assessor to the library. We also upgraded our 3590 tape drive from B1A to H1A. We are on the latest ATAPE driver too. David C. Pearson IS Production Support Analyst System Network Service Snohomish County PUD # 1 ole0.bmp Phone: 425.347.4420 Pager: 425.290.0944 FAX: 425.267.6380 E-mail: [EMAIL PROTECTED] -Original Message- From: Zlatko Krastev [SMTP:[EMAIL PROTECTED] Sent: Friday, October 24, 2003 4:50 AM To: [EMAIL PROTECTED] Subject:Re: Cleaning Machine for 3590 cartridges You did not called it IBM but I assumed it being unaware of the device. Thanks to Richard's clarification I was able to figure it out. Now to the topic: if you really need to use such machine, it would certainly mean your server room environment is *dirty*! If it indeed is, the risk of losing data would be rather close to the risk when you are not doing backups at all. I can only quote a sentence not invented by me:Poor security is worse than no security at all, as it provides fake sense of security! If your library environment is clean enough (through using and regular cleaning of appropriate filters in conditioners) and your operators are handling tapes only through library I/O station - you should not need such a device. At that point I personally would react nearly as Tom suggested. Zlatko Krastev IT Consultant Pearson, Dave [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 23.10.2003 17:26 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Cleaning Machine for 3590 cartridges I apolgise for calling the 3599 model an IBM My mistake. I was just giving one model of cartridge cleaning machine called 3599 (Yes there are cartridge cleaning meachine out there.) There is another cleaning machine called.. STAR 3590 cartridge cleaning machine. I'm sure there are many other 'brand' of machine that clean tapes/cartridge. Ziatko, does you company clean their cartridges on these type of machine? If so, Is it worth it? if not... why you don't use them? Thanks again Ziatko. Dave Pearson -Original Message- From: Zlatko Krastev [SMTP:[EMAIL PROTECTED] Sent: Thursday, October 23, 2003 5:13 AM To: [EMAIL PROTECTED] Subject: Re: Cleaning Machine for 3590 cartridges IBM 3599 is not a machine, but so called machine type / model for ordering any Magstar cartridges. 3599-001, -002, -003 are 3590 J cartridges (10/20/30 GB) 3599-004, -005, -006 are 3590 K cartridges (20/40/60 GB) 3599-007 is 3590 cleaning cartridge (what probably you are looking for!!!) 3599-011, -012, -013 are 3592 cartridges (300 GB) 3599-017 is 3592 cleaning cartridge. This is a second method to order cartridges through IBM Storage channel. The first is as components of 3590 drives. Same is for LTO - they can be ordered as part of 358x unit or separately as 3589-xxx media. If you need short confirm: Yes, this is working/supported cleaning media for any IBM 3590 drives (standalone, within IBM 3494, or
Re: Move nodedata - what is moved first
On Fri, 24 Oct 2003 09:12:34 -0400 Marc Levitan [EMAIL PROTECTED] wrote: What would happen if there was a site disaster and the data was only on the disk which is no longer available to perform restores? I guess what I am asking is, without sending DIRMC off-site, can you recover from a site disaster? Even better, directories are never stored in storagepools, just in the database, so in case of a disaster, you will never loose any data as long as you have off-site db backups. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: Move nodedata - what is moved first
Even better, directories are never stored in storagepools, just in the database, so in case of a disaster, you will never loose any data as long as you have off-site db backups. True for simple directories, as found in Unix...same as empty files. But the more complex ones (Unix ACLs, Windows) have more attributes than can be accommodated in a TSM database entry so they have to be treated like non-empty files, and thus are stored in storage pools. This naturally extends the length of backup and restore sessions for such systems. Watching a substantial Unix restoral is beautiful, as all the directories come back right away, reconstructing the framework of the file system area long before any tape is mounted to restore data files. Richard Sims, BU
Re: Move nodedata - what is moved first
Not entirely true, I believe. If the directory tree for a particular node exceeds a certain size, it DOES get stored in a storage pool...although I'm a little foggy as to what that size is. That's the whole idea behind the DIRMC parameter...sot that you can control where the directory info winds up in the event that it does go to a storage pool. -Lloyd On Fri, 24 Oct 2003 18:02:07 +0200 Remco Post [EMAIL PROTECTED] wrote thusly: On Fri, 24 Oct 2003 09:12:34 -0400 Marc Levitan [EMAIL PROTECTED] wrote: What would happen if there was a site disaster and the data was only on the disk which is no longer available to perform restores? I guess what I am asking is, without sending DIRMC off-site, can you recover from a site disaster? Even better, directories are never stored in storagepools, just in the database, so in case of a disaster, you will never loose any data as long as you have off-site db backups. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: Move nodedata - what is moved first
Hi Peter, Actually I do not know the perfect answer for you. Anyway, for sure the move nodedata does not depend on what the oldest/newest data is. I believe the first thing what TSM does is to build a list of volumes were the node data is located and then processes each volume sequentally untill all data has been moved (copyed). How TSM picks the order of volumes I don't know (the volume holding the most data first or perhaps in alfabetical order). One volume can hold the oldest and newest data, imagine if oldest data is reclaimed to new volume and the same day, new data is migrated or backed up to that volume. You can start the move nodedata process and when the disk pool is full, the process probably ends with failure, but that is ok. After you have migrated the data from diskpool, you can start the move again and TSM goes on where it stopped. Best regards, Kolbeinn Josepsson · Systems Engineer Tivoli Certified Consultant - IBM Tivoli Storage Manager V5.1 www.nyherji.is StorageGroupAdmin StorageGroupAdmin [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 23.10.2003 04:07 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Move nodedata - what is moved first --- This email is to be read subject to the disclaimer below. --- In an attempt to negate the mount time issue in the restore process I am currenlty using move nodedata to co-locate data for some of our servers . Currently, our main file server has data on over 200 3590 tapes therefore a directroy restore can potentially have hours added to the process directly related to tape mounts. back to the point.. Does any know the what method is used in determining which media within a storage pool is mounted first. For example, is it; - tape last write date, ie oldest tape first - newest data first (active files) and all other data on that media is moved - biggest file then all other data on the media is moved. Why do I want to know? To experdite the process, where possible, I read from multiple tapes onto our disk pool and then drain the pool to a single tape. The problem is the disk storage is not large enough or I have to cancel the process prior the night process being impacted. Therefore, I need to know what is being moved next time I run the process. Am I moving the same data again or will a subsequent execution of the command basically start where I left off Peter Griffin Sydney Water --- Mandatory water restrictions now apply in Sydney, Blue Mountains and the Illawarra. Fines of $220 apply from 1 November 2003. No sprinklers or watering systems at any time. No hosing of hard surfaces including vehicles at any time. For more information visit www.sydneywater.com.au --- NOTICE: This email is confidential. If you are not the nominated recipient, please immediately delete this email, destroy all copies, and inform the sender. Sydney Water Corporation (Sydney Water) prohibits the unauthorised copying or distribution of this email. This email does not necessarily express the views of Sydney Water. Sydney Water does not warrant nor guarantee that this email communication is free from errors, virus, interception or interference. --- ForwardSourceID:NT0003F952
Re: 3494 Library and dual gripper?
Our dual gripper is used 6% of the time, but we also have an HA setup (2 accessors) which requires dual grippers. You do lose storage slots at the top and bottom as noted, but the thing I don't understand is why the top 2 slots of the I/O door aren't blocked out like the shelves because the bottom gripper can't reach these either. Just one of those odd observations. -Al Richard Foster [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 10/24/03 06:58 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: 3494 Library and dual gripper? A dual gripper shaves some seconds off the overall time. It may be worth pointing out that a dual gripper loses you some library tape slots - 10% of them, in fact. The upper gripper cannot reach the lowest 2 slot levels, nor can the lower gripper reach the highest 2 levels. Therefore these 4 levels are lost (and are physically blanked off in our library). It's an open question why IBM chose to do it that way, because it was surely possible to program the control PC to use the appropriate gripper for these levels. Probably that nice warm feeling of redundancy. Richard Foster *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. ***
FLASH: TSM Mac client and MacOS X 10.3 new case sensitive HFS+ file system
I have been asked to post the following item: Customers using Apple MacOS X 10.3 (Panther)'s new optional Case Sensitive HFS+ file system with the IBM TSM Mac client should read this flash Apple MacOS X 10.3 (Panther) customers using the new optional Case Sensitive HFS+ filesystem with the IBM TSM Mac client need to apply interim fix 5.2.0.3, and ensure the new CS HFS+ volume does not have the same name as existing TSM volumes on the node. Immediate Action needed: If planning to use the new MacOS X 10.3 optional Case Sensitive HFS+ filesystem, before backing up any files in that filesystem: - Apply interim fix 5.2.0.3 (or later deliverables such as the 5.2.2 maintenance when available) - Ensure the new Case Sensitive HFS+ volume does not have the same name as existing TSM volumes for the node. Either the TSM volumes can be renamed on the TSM server, or the CS HFS+ volume can be renamed locally. Customers using the default HFS+ or other filesystem with MacOS X 10.3 do not need to do anything. Problem Description: The new optional Case Sensitive HFS+ filesystem in MacOS X 10.3 is case sensitive, not case-preserving like previous Mac filesystems. The existing TSM Mac clients do not treat file names in a case sensitive manner on backup or restore. With the new filesystem, if two files have the same path and the same name, but different casing on the name, the existing TSM Mac clients will not be able to distinguish between the two files on backup and restore. Both files will be backed up on the very first incremental backup, but both will be treated as the same file, so the backup of the first file will become the inactive version, and the second file will become the active backup version. On the next incremental, the file that is the inactive version won't be found and will be backed up, becoming the new active version, and the second file's backup will become the inactive version. This problem only occurs with the new Case Sensitive HFS+ filesystem and MacOS X 10.3. This problem is described in APAR IC37907, and is fixed in TSM Mac client interim fix 5.2.0.3 and subsequent V5.2 deliverables. The interim fix client will recognize the Case Sensitive HFS+ filesystem type, and will treat its files in a case sensitive manner on backup and restore. The volume name for the new Case Sensitive HFS+ filesystem must be a unique TSM volume name for that node, to ensure correct backup and restore operations. Recommended Action: Before backing up any files in a Case Sensitive HFS+ filesystem: 1. Install the TSM Mac client interim fix 5.2.0.3 or a later V5.2 deliverable. 2. If the Case Sensitive HFS+ filesystem volume is the same name as an existing TSM volume, either rename that existing TSM volume or rename the new CS HFS+ volume, to prevent case sensitive files from being mixed with case preserving files. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence.
SUSE Openexchange backup
Hi, Has anyone experience in backing up SUSE OpenExchange? Is it possible to backup the open files, or is it better to use Snapshot Image backup (filesystem created with Linux LVM)? Best regards, Kolbeinn Josepsson · Systems Engineer Tivoli Certified Consultant - IBM Tivoli Storage Manager V5.1 www.nyherji.is