Re: Problem deleting filespace SYSTEM OBJECT
My responses are within the text ... On Tue, 24 Sep 2002, Gerhard Rentschler wrote: Hello, in the meantime I upgraded to 5.1.1.6. With this level I could delete the filespace without problem. However, I couldn't resist to try cleanup backupgroup again. Under 5.1.1.4 it worked. It only seemed strange that it obviously didn't finish its work, as Joel described: On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the system objects. I reran the cleanup command numerous times and each time it reported inspecting and deleting fewer objects than the previous run. On 5.1.1.6 cleanup backupgroup stopped immediately with return code 4. In the activity log I found the following messages: 09/24/02 10:31:51 ANR2017I Administrator GERHARD issued command: CLEANUP BACKUPGROUPS 09/24/02 10:31:51 ANRD imutil.c(6663): ThreadId67 Failure deleting member 0 585368742 for group 1637 3 - encountered repeatedly in loop. 09/24/02 10:31:51 ANRD imutil.c(3931): ThreadId67 Error 19 deleting dependents for node 0 fs 0 and leader 1637 3. Now I'm little bit concerned. Is cleanup backupgroup broken or is it my database? The CLEANUP did the same thing for me on 5.1.1.6 until I did an AUDITDB FIX=YES. After doing the auditdb, it ran properly. My suggestion to all TSM admins is to do a QUERY OCCUPANCY * SYSTEM OBJECT to verify that you do not have excessive copies. How can you tell from the output of the q occ command how many excessive copies you have? For most of my servers, the system object consists of about 1800 objects and require 230 MB. Do the math and you will know if you have excessive backups. BTW, I cannot confirm that system objects are not expired. I used the following SQL statement in the middle and at the end of an expiration process: select sum(num_files) from occupancy where filespace_name='SYSTEM OBJECT' The first number I got was 1043479, the last 1012998. So I got rid of at least 30481 files. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: help:label tape question
Feng, Hmm, you want to take 800 tapes out of your library, then label 200 more, but you only have two drives. I'd suggest that you have some serious problems here. Are you running expire inventory regularly? does it complete? Are you reclaiming your tape storage pools regularly? Before you post again, have a look at the Administrator's Guide, Chapter 11 Implementing Policies for Client Data in the section File Expiration and Expiration Processing and follow the links to Reclaiming Space in Sequential Storage Pools and Running Expiration Processing to Delete Expired Files The Administrator's Guide is available in HTML and pdf format on a CD that came with TSM. It may already be installed on your server. If you can't work your problem out from that, you need to buy some consulting time from an expert in your region. There may be problems with your client retention policies, with Database backup processing, with obsolete filespaces that need to be deleted or any number of other things, more than we can help you with on this list. Good luck. Steve Harris AIX and TSM Admin, Queensland Health, Brisbane Australia [EMAIL PROTECTED] 26/09/2002 13:31:06 Hi all, I have a 3494 library with two dirve,the backup-archive server with ADSM .When the library must label 200 tapes a time,at the same time ADSM must have backup some date,can these two operations be doing at the same time? Another question is if I take the opertion: ADSMlabel libvol libname search=yes labelsouce=barcode can library auto label all those tapes in the library? Last can you tell me what's the scratch pool ? Thanks and regards Feng ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Re: Withdrawal of 3570 Magstar
It's about 45 seconds load time on 3584 library. That's what TSM shows by doing q process while waiting for tape mounts. But, when it gets mounted it goes into 5th gear! David Longo [EMAIL PROTECTED] 09/26/02 12:58AM 3570 users, I notice that IBM is withdrawing all 3570 items from marketing in December 2002.(announcemet letter WG02-0316) Looks like time to consider an upgrade if you are using these. IBM suggests Ultrium as the replacement, but that hardly has a six second load time does it? Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. ** MMS health-first.org made the following annotations on 09/26/2002 02:36:19 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Invalid parameter passed
Hi all, We are trying to make a full restore from one client to another, and get the following error: Invalid parameter passed - has anybody seen this before? (IBM 8668-2SX Xseries 232 med Windows 2000 Service pack 2 med IBM Serveraid adapter 4LX) Thanks, David
Re: starting TSM without it doing anything
Dear Listreaders: Some time ago I had a problem with TSM (I believe it was V4.1.2) server for OS/390. I had managed to make some kind of error in specifying threshholds (For migration as far as I remember) that caused TSM to go into a loop as soon as it was started. While in the loop, commands were not processed. The support center gave me an undocumented parameter for the server options file: NOMIGRRECL This option prevented migration and reclamation from starting and allowed me to issue commands to reset the threshholds. I don't know if it still works ( It's always the case for undocumented features, of course.) - William White Service Delivery Section International Computing Centre (ICC) e-mail: [EMAIL PROTECTED]
Re: How to backup an NFS partition
That worked a treat, Many thanks All the best Farren Minns David Longo [EMAIL PROTECTED]@VM.MARIST.EDU on 25/09/2002 15:26:47 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: How to backup an NFS partition By default, NFS fs are not backed up. To back one up do the following. In your dsm.opt file on client, put in a DOMAIN /nfs ALL-LOCAL statement. (/nfs is whatever fs you want backed up.) You can put more than one, separated by spaces. You can also use this if you want /tmp backed up, which is not backed by default on unix systems. Remember to restart scheduler on client after making changes. David Longo [EMAIL PROTECTED] 09/25/02 06:25AM Hi all Running Solaris Server 4.2.2.12 on a Solaris 2.7 box I want to NFS mount a partition from one Solaris machine to another and then have TSM back this file system up. Will TSM automatically backup a remotely mounted NFS partition or do I have to tell it specifically to do so. Many thanks in advance for your help Farren Minns - TSM and Solaris System Admin - John Wiley Sons Our Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged ** MMS health-first.org made the following annotations on 09/25/2002 10:28:22 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. == Our Chichester based offices have amalgamated and relocated to a new address John Wiley Sons Ltd The Atrium Southern Gate Chichester West Sussex PO19 8SQ Main phone and fax numbers remain the same: Phone +44 (0)1243 779777 Fax +44 (0)1243 775878 Direct dial numbers are unchanged Address, phone and fax nos. for all other Wiley UK locations are unchanged **
Re: Reading data from tape
Geoff, you do not know what questions to ask or they are classified and you cannot ask them :-) If you need to hold classified material - do not mix it with non-classified and the problem is eliminated from the beginning. Collocation ought to help and you may consider usage of separate stgpools (both primary and copy) over same devclass to ensure separation of data. This might answer to how to retrieve classified tape question. If you need to ensure data does not exist anymore on the tape cartridge you have at least two options - usage of a drive to write some fill pattern over whole tape before retrieve from secure vault and reuse - simple degauss and recycle the cartridge - more expensive but might be acceptable depending on security requirements Other possibilities can also be invented after few minutes of thought. Zlatko Krastev IT Consultant Gill, Geoffrey L. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 24.09.2002 01:08 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Reading data from tape I hope someone has a real good knowledge of how TSM data is written to/read from tape. I'm in a predicament that I may never be able to get tapes back to read any node data off of them unless I can satisfactorily answer questions. Unfortunately I don't know the questions yet so I don't even know what to ask here. Perhaps someone who is knowledgeable about 3590 tape technology or someone from Tivoli monitoring the list can help with this. I hate to have to call Tivoli since so far I haven't got much in the way of answers on the other questions I've been asking on classified material on tape. What kind of questions would you expect to answer if a tape was removed from the library with mixed node data on it and it was needed to restore some other node's data. Keep in mind that the tape was removed because it originally had classified material stored on it. It may or may not still have the data depending on expiration. I already know how to explain the ins and outs of expiration/reclamation but we all know the DATA is really still there. My guess is I'm never really going to be able to get these tapes back and whatever data was on them is probably gone forever but I need to at least be able to answer some questions like are they indexed or how the data is stored, how it's read back etc. Thanks for the help, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Shortly speaking - try to disable compression and things can speed up dramatically. The reason: You have to take in the consideration that client-side TSM compression is single-threaded and thus is limited by the (single) processor power. And your Domino server might be busy enough. 566kB/s compressed data rate on low-freq Pentium II/III (even on 4-way server) might be the best you can squeeze from the processor. The best compression rate I've ever seen was about 3 MB/s compressed per processor on 750 MHz RS64-IV (RS/6000 M80). SMP can be utilized only if you increase resource utilization in dsm.opt Zlatko Krastev IT Consultant Barbara Andrews [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 24.09.2002 22:05 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ? ... 5) I have very little knowledge of networking. Could someone comment on the throughput values we are seeing? Our max of 566 Kb/sec is no where near the 100 Mb/sec I have been told our ethernet connection is.
Does anyone implement Space Mgr + NFS on windows + AIX successfully?
Dear TSMers, Does anyone have experience on using Tivoli Space Manager with NFS windows client? I'm facing a problem and seems to be in NFS Client side. If anyone have successfully implemented this, appreciate you can let me know what NFS client you are using and what specific settings I need to have. Many thanks. My problem encountered: When a NFS Client (haven't installed HSM Client) is trying to access files that are previously migrated to the tape library, the files are unaccessible. For instance, when using MSWord to open a .doc file, the file would not be opened and the application hangs. When checking from the AIX Server end, it indicates that the file was retrieved from the tape successfully, in another words, no error is reported from TSM nor Tivoli Space Manager. . However, if files are retrieved locally from the server (through NFS Client also), there is no problem in opening any of them. My environment is like this: Server * Product: TSM Server, TSM API Client, Tivoli Space Manager Version: 5.1 Platform: AIX 5L . * Client * Platform: Windows 2000 Professionalw/ SP2 NFS Client Software: (a) InterDrive Client (b) Omni-NFS-Enterprise v5.1 . * Other * LTO 3583 Library with one tape drive installed. 100BaseT Network Best Regards, Molly Pui
archiving with different management classes
Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Disk volumes
Hello, TSM: 5.1.1.6 OS: AIX 4.3.3 Machine: IBM 6M1 Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. Thanks. Mahesh
Antwort: archiving with different management classes
You do not need a new optionsfile. Use the client option -archmc =mgmtclass_name instead! MfG Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Re: archiving with different management classes
Yep, don't complicate things... just use the -archmc=blah to bind a specific archive run's data to a specific management class... just add an addition option of -archmc=MGMT2_SWS Dwight -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 7:29 AM To: [EMAIL PROTECTED] Subject: archiving with different management classes Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Re: archiving with different management classes
Kurt, I have the exact same requirements. I solved the problem by putting the management class in the schedule options. You can not override the DSM.OPT file used through the scheduler. It will use the one that was in effect when the client scheduler started. The schedule I run is listed below. The -archmc=7yeararch declares the management class to use. Matt Policy Domain Name NTPOLICY1 Schedule Name YEARLY-ARCH-NT1-USCLES324 Description yearly archival of uscles324 Action ARCHIVE Options -archmc=7yeararch -subdir=yes Objects f:\*.* E:\CA_APPSW Priority5 Start date 2002-02-22 Start time 23:00:00 Duration1 Duration units HOURS Period 12 Period unitsMONTHS Day of Week THURSDAY Expiration - Last Update Date/Time 2002-02-28 07:54:15.00 Last Update by (administrator) ADMIN Managing profile- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 8:29 AM To: [EMAIL PROTECTED] Subject: archiving with different management classes Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Re: archiving with different management classes
Thanks, I've just discovered the archmc option myself and it's working. One problem less ;-) Kurt ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote: Yep, don't complicate things... just use the -archmc= to bind a specific archive run's data to a specific management class... just add an addition option of -archmc=MGMT2_SWS Dwight -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 7:29 AM To: [EMAIL PROTECTED] Subject: archiving with different management classes Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Re: archiving with different management classes
In unix you use the archmc= paramter not sure in Windows though. --Justin kurt.beyers@pand ora.be To: [EMAIL PROTECTED] kurt.beyers cc: Sent by: ADSM: Subject: archiving with different management classes Dist Stor Manager [EMAIL PROTECTED] .EDU 09/26/2002 08:29 AM Please respond to ADSM: Dist Stor Manager Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Re: Netware Clustering
John, We are backing up a 3 node NW5 cluster (soon to be NW6) with TSM client 5.1 going to TSM Server 4.1.4.2 on OS\390. Having said that (and this is getting to be old news) TSM does NOT currently support Netware clustering. At one time I was told to expect support in the 5.1.4(?) NW client due this fall but don't know if that's still planned or not. Problems revolve around the client not recognizing volume failover and inability to backup the _NETWARE/TRUSTMIG.FIL. There is also a TID from Novell on how to configure a Netware 6 server for ADSM and non cluster aware backup systems. It is # 10065605. The most current TSA's from Novell are packaged as tsa5up10 but I think one of the problems in Novell needs to rewrite the tsa's to interact correctly with TSM. Hope this helps. John Stephens wrote: Does anyone have any experience with TSM and Netware clustering. Does TSM support the backup of the Netware cluster. Thank You John Stephens -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Does anyone implement Space Mgr + NFS on windows + AIXsuccessfully?
Hi We currently using HSM on AIX for NFS mounts and the way we currently set this up is to have the HSM client installed on the NFS server as well as the NFS client server. This set-up works on AIX NFS file systems. I am almost sure it should work the same way for Windows. You are required to install the HSM client on both servers. I hope this helps your problem Thks Sean Ramnarayan Unix/TSM Administrator EDS (South Africa) -Original Message- From: Molly YM Pui [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 1:31 PM To: [EMAIL PROTECTED] Subject: Does anyone implement Space Mgr + NFS on windows + AIXsuccessfully? Dear TSMers, Does anyone have experience on using Tivoli Space Manager with NFS windows client? I'm facing a problem and seems to be in NFS Client side. If anyone have successfully implemented this, appreciate you can let me know what NFS client you are using and what specific settings I need to have. Many thanks. My problem encountered: When a NFS Client (haven't installed HSM Client) is trying to access files that are previously migrated to the tape library, the files are unaccessible. For instance, when using MSWord to open a .doc file, the file would not be opened and the application hangs. When checking from the AIX Server end, it indicates that the file was retrieved from the tape successfully, in another words, no error is reported from TSM nor Tivoli Space Manager. . However, if files are retrieved locally from the server (through NFS Client also), there is no problem in opening any of them. My environment is like this: Server * Product: TSM Server, TSM API Client, Tivoli Space Manager Version: 5.1 Platform: AIX 5L . * Client * Platform: Windows 2000 Professionalw/ SP2 NFS Client Software: (a) InterDrive Client (b) Omni-NFS-Enterprise v5.1 . * Other * LTO 3583 Library with one tape drive installed. 100BaseT Network Best Regards, Molly Pui MMS caltex.com made the following annotations on 09/26/2002 03:28:36 PM -- DISCLAIMER This message may contain confidential information that is legally privileged and is intended only for the use of the parties to whom it is addressed. If you are not an intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any information in this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete the message. Thank you. ==
Re: Does anyone implement Space Mgr + NFS on windows + AIX successfully?
I had the problem you described, but with AIX participants (AIX server, AIX clients). The problem is that the client machine (that has the nfs mount) tries to access a file that is HSM'd. The wait messages that you would see if you tried to access the file from the server are not passed to the client, hence the client doesn't know to wait for the file. All it sees is the stub file, which it knows is not a complete file. It can't get the whole file immediately, so it poops an error to you. If you tried accessing the file again from the client, it would probably work, since HSM has probably had time to recall the file. Anyway, what I did to solve the problem was to make those nfs mounts hard mounts (as opposed to a soft mount) on the clients. Not sure how this relates to nfs on a windows client - but a hard mount will continue to try the mount request until the server responds. A soft mount will just return an error if it can't get the file immediately. Of course, you also run the risk of hosing up your client if there is a true problem with the nfs server, the hard mount request will keep trying and will take forever to time out. Check out your nfs documentation for your client, see if there is a similar parameter. M. --- Molly YM Pui [EMAIL PROTECTED] wrote: Dear TSMers, Does anyone have experience on using Tivoli Space Manager with NFS windows client? I'm facing a problem and seems to be in NFS Client side. If anyone have successfully implemented this, appreciate you can let me know what NFS client you are using and what specific settings I need to have. Many thanks. My problem encountered: When a NFS Client (haven't installed HSM Client) is trying to access files that are previously migrated to the tape library, the files are unaccessible. For instance, when using MSWord to open a .doc file, the file would not be opened and the application hangs. When checking from the AIX Server end, it indicates that the file was retrieved from the tape successfully, in another words, no error is reported from TSM nor Tivoli Space Manager. . However, if files are retrieved locally from the server (through NFS Client also), there is no problem in opening any of them. My environment is like this: Server * Product: TSM Server, TSM API Client, Tivoli Space Manager Version: 5.1 Platform: AIX 5L . * Client * Platform: Windows 2000 Professionalw/ SP2 NFS Client Software: (a) InterDrive Client (b) Omni-NFS-Enterprise v5.1 . * Other * LTO 3583 Library with one tape drive installed. 100BaseT Network Best Regards, Molly Pui __ Do you Yahoo!? New DSL Internet Access from SBC Yahoo! http://sbc.yahoo.com
Re: Does anyone implement Space Mgr + NFS on windows + AIX successfully?
= On Thu, 26 Sep 2002 19:31:03 +0800, Molly YM Pui [EMAIL PROTECTED] said: My problem encountered: When a NFS Client (haven't installed HSM Client) is trying to access files that are previously migrated to the tape library, the files are unaccessible. For instance, when using MSWord to open a .doc file, the file would not be opened and the application hangs. When checking from the AIX Server end, it indicates that the file was retrieved from the tape successfully, in another words, no error is reported from TSM nor Tivoli Space Manager. . What NFS client are you using on the windows box? It's my bet that the client has an unreasonable timeout, and gives up. If you even _can_ set that timeout, set it for (say) three times the amount of time you think is reasonable for a retrieval, and see if that helps. Real NFS implementations quietly block on read there, and the timeout is usually the human getting impatient and killing the process. For the patient computer, the delay is not an issue. - Allen S. Rout - HSM for DB/2 load files and logs is pretty nice.
Re: Disk volumes
= On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: archiving with different management classes
Hi, I would like to unsubscribe to this mail letter. Please do the needfull. Thanks and Regards, VeluMani Jaganathan mailto:[EMAIL PROTECTED] www.eds.com -Original Message- From: Justin Bleistein [mailto:[EMAIL PROTECTED]] Sent: Thursday, 26 September 2002 6:59 PM To: [EMAIL PROTECTED] Subject: Re: archiving with different management classes In unix you use the archmc= paramter not sure in Windows though. --Justin kurt.beyers@pand ora.be To: [EMAIL PROTECTED] kurt.beyers cc: Sent by: ADSM: Subject: archiving with different management classes Dist Stor Manager [EMAIL PROTECTED] .EDU 09/26/2002 08:29 AM Please respond to ADSM: Dist Stor Manager Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
Re: Windows 2000 Restore Example
I was wondering about this restore. 1. Was any 'active' virus scanning running at the time of the restore? I have seen alot of performance improvements with TSM restores by disabling the virus scanning temorarily during the large restore, and then running a manual virus scan afterwards. (some security people don't like this idea though) 2. Was this data compressed by the TSM client? If it was and the Win2K server had really slow CPU's that could have caused this restore to take along time. (Combine that with the virus scanning and things are really slow). 3. What was the situation of the file system/disk array that the restore was done to? Various things happening on the disks slow stuff down. Raid-5 parity checking running at the same time as the restore, (especialy on freshly setup array). Also various file system defragmentations running at the same time as a large restore slow things down. Some paranoid windows admins run defrags on their arrays every day, some large very full arrays that defrage takes all day just to run, thus they are defragmenting 24x7. Combine that with slow cpu's, TSM compression and active virus scanning and things are all ready for a painful TSM restoration. I hope one of those things will help you get more performance out of this configuration. Matthew Glanville Eastman Kodak Kelly J. Lipp [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/25/2002 01:06 PM Please respond to lipp To: [EMAIL PROTECTED] cc: Subject:Windows 2000 Restore Example Gang, Environment: TSM Server V5.1.1.4 on Win2K, TSM Client 5.1.1.0 on Win2K Fileserver drive. Data Restoration Statistics: 233,002 Objects 52.54 GB Elapsed Time: 12:57:01 Other stats appeared quite normal, i.e., Network Data transfer rate. resourceutilization = 4, Maxnummp = 4 Four tapes/drives used at least at the beginning, tapering down to one as time wore on. No judgment about the overall performance of this test. Just information for all of you. I believe this is a file create issue on the Win2K server rather than anything in TSM. Anybody have any ideas how to increase the performance of this type of restore in this environment? Frankly, I was not surprised by this. I would like to have seen a three hour restore rather than 13, but it is what it is. Thanks Kelly J. Lipp STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175
TSM 5.1 and Windows200 SP3
Can anyone tell me if TSM 5.1.1.0 (Windows 2000 advanced server platform) will backup a windows 2000 client (5.1.1.0) that is running w2K service pack 3? Or if there are any known issues with it? Many thanks Jon Evans Halliburton
Re: TSM 5.1 and Windows200 SP3
I wouldn't be using 5.1.1.0, if I were you. There are problems backing-up SYSTEM STATE with that level. In fact, on my machine, if I selected SYSTEM STATE via the GUI, it would crash every time. 5.1.1.3 and higher addressed this issue. I am running SP3 and TSM 5.1.1.5 with no issues. Jon Evans [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 09/26/2002 10:56 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM 5.1 and Windows200 SP3 Can anyone tell me if TSM 5.1.1.0 (Windows 2000 advanced server platform) will backup a windows 2000 client (5.1.1.0) that is running w2K service pack 3? Or if there are any known issues with it? Many thanks Jon Evans Halliburton
Re: archiving with different management classes
Just curious: what exactly is the difference anyway? Ok, I'm probably missing something real obvious, but ... If you're taking a monthly archive, then why would you need a yearly one? It's still the same archive right, just labelled differently? I'm not understanding the difference. Also, while on this topic, can someone explain the pros cons of the following three? a) archive (which I understand to basically be a backup but simply with longer data retention values b) backup set c) image backup Thanks. johnn Thanks, I've just discovered the archmc option myself and it's working. One problem less ;-) Kurt ADSM: Dist Stor Manager [EMAIL PROTECTED] wrote: Yep, don't complicate things... just use the -archmc= to bind a specific archive run's data to a specific management class... just add an addition option of -archmc=MGMT2_SWS Dwight -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 7:29 AM To: [EMAIL PROTECTED] Subject: archiving with different management classes Hi, I've got to take every month a monthly archive and once a year a yearly archive. Of course the protection of the latter archive is longer. The default management class has the correct archive copy group for the monthly archive (management class MGMT_SWS). I've created a second management class (MGMT2_SWS) for the yearly archive. The default dsm.opt client options file binds the archive to the correct management class for the monthly archive. I've created a second client options file dsm2.opt with an include.archive statement towards the management class MGMT2_SWS If I launch the archive from the command prompt as: dsmc archive -optfile=c:\temp\dsm2.opt -subdir=yes c:\*.* d:\*.* the archive of the files is indeed done with the management class MGMT2_SWS If I specify a schedule: Policy Domain Name POL_SWS Schedule Name TEST4 Description - Action ARCHIVE Options -optfile=c:\temp\dsm2.opt -subdir=yes Objects c:\hp\* d:\windows\winzip81\* the archives are bind towards the management class MGMT_SWS and not towards the management class MGMT2_SWS. The scheduler is bound to the dsm.opt file but if I specify another client options file in the options, this should override the default settings. Am I missing something? Kurt
volume management in tsm
We are in a bit of a pickle or soon will be anyway We have an IBM/3494 atl in our TSM environment. Which has about 1,000 slots in it. These slots are filling and fast. We're trying to make room for more scratch tapes. Now I've tried everything from move data to weird reclaimation sinareos. And we just can't seem to free up sificiant slots. I had an idea of ejecting all tapes which haven't been written to in a while there just waiting to expire, this way migration or backup storage pool processes won't call for them, and once they're out rack them in the data center and mark there location as: rack. Now that will free up a ton of spots in the atl. The problem is how can TSM manage those tapes even though they are not in the ATL. I can check them in with check label = no, and just mark there location as: rack this way the database will keep updating them. The problem is what if reclaimation runs, now you can't do it because the tapes can't be mounted they're in the rack outside the atl. Unless the robot comes out to get them I don't see how this can work. It seems that trying to come up with a solution to the problem of lack of slots in the atl will just create more of a problem. Any thoughts? Or ideas? on how I can manage these tapes even though they can't be mounted?. P.S. = Yes it is collocated. Let me know if anyone has done this thanks!. --Justin Richard Bleistein
TSM Encryption
Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: volume management in tsm
Justin, I've experienced this on several occasions including having close to 1000 tapes outside of a 3494. Obviously, someone has miscalculated the size necessary to house all your primary storage pool volumes - the easiest solution is to bolt on a couple more 'S' frames on the ATL. TSM will manage the tapes automatically outside of the ATL - there is no need to update their location as 'rack'. If needed, TSM will request a tape volume until the tape is checked in or the mount wait of the device class is exceeded. When put in the ATL, the tape is automatically checked in and used by TSM. If the mount wait is exceeded, the tape is then updated to unavailable and causes a restore/retrieve to fail and reclamation to move on to the next candidate tape. Predicting which tapes will be reclaimed can be a challenge, since TSM splits files and often needs a highly utilized tape to move a file segment. If you can identify a set of tapes which are full and not expiring too fast and they are not needed to often for restores, you can rotate them out of the ATL. I had the luxury of having tape operators monitor the requests, so we made it work until more slots were installed. That took a bit of training and documentation, but is fairly simple. Regards, - Paul Paul Thorson Levi, Ray Shoup, Inc. Tivoli Specialist - LRS IT Solutions (217) 793-3800 x1704 -Original Message- From: Justin Bleistein [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 10:52 AM To: [EMAIL PROTECTED] Subject: volume management in tsm We are in a bit of a pickle or soon will be anyway We have an IBM/3494 atl in our TSM environment. Which has about 1,000 slots in it. These slots are filling and fast. We're trying to make room for more scratch tapes. Now I've tried everything from move data to weird reclaimation sinareos. And we just can't seem to free up sificiant slots. I had an idea of ejecting all tapes which haven't been written to in a while there just waiting to expire, this way migration or backup storage pool processes won't call for them, and once they're out rack them in the data center and mark there location as: rack. Now that will free up a ton of spots in the atl. The problem is how can TSM manage those tapes even though they are not in the ATL. I can check them in with check label = no, and just mark there location as: rack this way the database will keep updating them. The problem is what if reclaimation runs, now you can't do it because the tapes can't be mounted they're in the rack outside the atl. Unless the robot comes out to get them I don't see how this can work. It seems that trying to come up with a solution to the problem of lack of slots in the atl will just create more of a problem. Any thoughts? Or ideas? on how I can manage these tapes even though they can't be mounted?. P.S. = Yes it is collocated. Let me know if anyone has done this thanks!. --Justin Richard Bleistein
Re: Disk volumes
I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: volume management in tsm
Justin, You're on the right track. Unfortunately, there is no ideal solution. If you need more slots, you have to move tapes out of the library (use the move media command). TSM will track the locations, and if a reclamation needs a tape, you'll get a mount message in the activity log. Then you have to check the tape back in (stat=private). We are in the same situation we upgraded from an ATL P3000 to a HP 20/700 with 678 slots and now even that is full. I'm considering putting the ATL back into service, but i need to upgrade the drives to DLT8000 first. Regards Robin Sharpe Berlex Labs Justin Bleistein justin.bleistein@SU NGARD.COM To:[EMAIL PROTECTED] Sent by: ADSM: Dist cc: Stor ManagerSubject: [EMAIL PROTECTED]volume management in tsm U 09/26/02 11:51 AM Please respond to ADSM: Dist Stor Manager We are in a bit of a pickle or soon will be anyway We have an IBM/3494 atl in our TSM environment. Which has about 1,000 slots in it. These slots are filling and fast. We're trying to make room for more scratch tapes. Now I've tried everything from move data to weird reclaimation sinareos. And we just can't seem to free up sificiant slots. I had an idea of ejecting all tapes which haven't been written to in a while there just waiting to expire, this way migration or backup storage pool processes won't call for them, and once they're out rack them in the data center and mark there location as: rack. Now that will free up a ton of spots in the atl. The problem is how can TSM manage those tapes even though they are not in the ATL. I can check them in with check label = no, and just mark there location as: rack this way the database will keep updating them. The problem is what if reclaimation runs, now you can't do it because the tapes can't be mounted they're in the rack outside the atl. Unless the robot comes out to get them I don't see how this can work. It seems that trying to come up with a solution to the problem of lack of slots in the atl will just create more of a problem. Any thoughts? Or ideas? on how I can manage these tapes even though they can't be mounted?. P.S. = Yes it is collocated. Let me know if anyone has done this thanks!. --Justin Richard Bleistein
Re: TSM Encryption
Jim, The TSM Backup/Archive client uses 56-bit DES encryption. Thanks, Jim Smith TSM Development Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: Disk volumes
John, We just when through setting up our disk staging pool with TSM 5.1 on Solaris 8. We had 6x36G to work with. The initial config used large files on the filesystem. This is incredibly slow. We then configured Disk Suite to mirror the disks and we configured TSM to use the raw devices e.g. /dev/md/rdsk/d0. Performance was significantly better. So TSM saw 3x36. From what we saw, it seemed the mirroring affected the performance more than the lack of spindles. As others have said, TSM seems to be pretty good at spreading the data around so it minimizes contention on the spool volumes. I never tested more, smaller mirrors. We then gave TSM the raw slices /dev/rdsk/c1t0d0s0 so he saw 6x36. This was the fastest by far. We were able to max the bandwidth (100M) for over an hour (38G in one hour). We lose the fault tolerance of mirrored disks, but we figure since it is only a staging area who cares? If a disk goes bad, we will lose the data backed up to it, but we can always back it up again. We felt the performance gains are well worth the redundancy hit. Though we have not tested pulling a disk from the staging pool and seeing what happens. I don't know your environment, but I would go with a single slice on all disks and tell TSM to use the raw device. If you really feel you need the redundancy I would just create 6 mirrors and use the raw mirrored device. From all of the benchmarking I've done it seems that once you get your setup decently tuned (don't tell TSM to use files for DB/LOG/DISKPOOLS) that the bottlenecks are either network capacity to your TSM server, or disk/cpu performance on the client (compression on). But I've only tested in one environment, ymmv. Hope this helps. scott Johnn D. Tan wrote: I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout -- Scott Walters Packet Pusher - The world speaks IP Mack Trucks, WHQhttp://www.MackTrucks.com 2100 Mack Boulevard Ph: 610.709.3728 Allentown, PA 18103 Fx: 610.709.2809
Re: Disk volumes
Thanks Scott. Hmm, never saw anyone else mention this, though I've been on the list for about a year. (Though, given the volume of this list, I definitely could've missed some mails.) Well, we are planning to move to new hardware and to TSM 5.1.1.x, so I guess that's as good a time as any to try using raw volumes for DB/log/diskpool. We definitely need any performance gains we can get as our daily automated procedures run very late into the day. Thanks again! johnn John, We just when through setting up our disk staging pool with TSM 5.1 on Solaris 8. We had 6x36G to work with. The initial config used large files on the filesystem. This is incredibly slow. We then configured Disk Suite to mirror the disks and we configured TSM to use the raw devices e.g. /dev/md/rdsk/d0. Performance was significantly better. So TSM saw 3x36. From what we saw, it seemed the mirroring affected the performance more than the lack of spindles. As others have said, TSM seems to be pretty good at spreading the data around so it minimizes contention on the spool volumes. I never tested more, smaller mirrors. We then gave TSM the raw slices /dev/rdsk/c1t0d0s0 so he saw 6x36. This was the fastest by far. We were able to max the bandwidth (100M) for over an hour (38G in one hour). We lose the fault tolerance of mirrored disks, but we figure since it is only a staging area who cares? If a disk goes bad, we will lose the data backed up to it, but we can always back it up again. We felt the performance gains are well worth the redundancy hit. Though we have not tested pulling a disk from the staging pool and seeing what happens. I don't know your environment, but I would go with a single slice on all disks and tell TSM to use the raw device. If you really feel you need the redundancy I would just create 6 mirrors and use the raw mirrored device. From all of the benchmarking I've done it seems that once you get your setup decently tuned (don't tell TSM to use files for DB/LOG/DISKPOOLS) that the bottlenecks are either network capacity to your TSM server, or disk/cpu performance on the client (compression on). But I've only tested in one environment, ymmv. Hope this helps. scott Johnn D. Tan wrote: I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout -- Scott Walters Packet Pusher - The world speaks IP Mack Trucks, WHQhttp://www.MackTrucks.com 2100 Mack Boulevard Ph: 610.709.3728 Allentown, PA 18103 Fx: 610.709.2809
Re: Disk volumes
John, Overall, the biggest gain in performance we got was changing the DB to use a raw slice instead of disk file (it even sped up the responsiveness of the web interface). We then tell TSM to mirror the DB with another raw slice. We've done this for the recovery log as well with it set to rollforward. From what i read in the archives of this list and the docs *make sure* that MirrorWrite DB and MirrorWrite LOG are set to Sequential in the server options. scott Johnn D. Tan wrote: Thanks Scott. Hmm, never saw anyone else mention this, though I've been on the list for about a year. (Though, given the volume of this list, I definitely could've missed some mails.) Well, we are planning to move to new hardware and to TSM 5.1.1.x, so I guess that's as good a time as any to try using raw volumes for DB/log/diskpool. We definitely need any performance gains we can get as our daily automated procedures run very late into the day. Thanks again! johnn John, We just when through setting up our disk staging pool with TSM 5.1 on Solaris 8. We had 6x36G to work with. The initial config used large files on the filesystem. This is incredibly slow. We then configured Disk Suite to mirror the disks and we configured TSM to use the raw devices e.g. /dev/md/rdsk/d0. Performance was significantly better. So TSM saw 3x36. From what we saw, it seemed the mirroring affected the performance more than the lack of spindles. As others have said, TSM seems to be pretty good at spreading the data around so it minimizes contention on the spool volumes. I never tested more, smaller mirrors. We then gave TSM the raw slices /dev/rdsk/c1t0d0s0 so he saw 6x36. This was the fastest by far. We were able to max the bandwidth (100M) for over an hour (38G in one hour). We lose the fault tolerance of mirrored disks, but we figure since it is only a staging area who cares? If a disk goes bad, we will lose the data backed up to it, but we can always back it up again. We felt the performance gains are well worth the redundancy hit. Though we have not tested pulling a disk from the staging pool and seeing what happens. I don't know your environment, but I would go with a single slice on all disks and tell TSM to use the raw device. If you really feel you need the redundancy I would just create 6 mirrors and use the raw mirrored device. From all of the benchmarking I've done it seems that once you get your setup decently tuned (don't tell TSM to use files for DB/LOG/DISKPOOLS) that the bottlenecks are either network capacity to your TSM server, or disk/cpu performance on the client (compression on). But I've only tested in one environment, ymmv. Hope this helps. scott Johnn D. Tan wrote: I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout -- Scott Walters Packet Pusher - The world speaks IP Mack Trucks, WHQhttp://www.MackTrucks.com 2100 Mack Boulevard Ph: 610.709.3728 Allentown, PA 18103 Fx: 610.709.2809 -- Scott Walters Packet Pusher - The world speaks IP
BMR scripts
Has anyone tried to script a BMR solution for NT or AIX using tsm. Everyone keeps saying the Bare Metal Restore is just a bunch of scripts that access TSM but has anyone tried create those scripts themselves. Thanks ***EMAIL DISCLAIMER*** This email and any files transmitted with it may be confidential and are intended solely for the use of th individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.996.3941.
Re: volume management in tsm
yeah that's what I figured. I took particular interest in one of you statements below, when you said that if TSM is calling for a tape mount, all the operator has to do is put a tape in the ATL I/o slots drawer and the robot will take it and check it in to TSM and use it?. Did I read that right? Or do the operators have to physically open of the the 3494 bays/doors and physically mount the tape as if it were manual? --Justin Thorson, Paul [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: Sent by: ADSM: Subject: Re: volume management in tsm Dist Stor Manager [EMAIL PROTECTED] .EDU 09/26/2002 12:46 PM Please respond to ADSM: Dist Stor Manager Justin, I've experienced this on several occasions including having close to 1000 tapes outside of a 3494. Obviously, someone has miscalculated the size necessary to house all your primary storage pool volumes - the easiest solution is to bolt on a couple more 'S' frames on the ATL. TSM will manage the tapes automatically outside of the ATL - there is no need to update their location as 'rack'. If needed, TSM will request a tape volume until the tape is checked in or the mount wait of the device class is exceeded. When put in the ATL, the tape is automatically checked in and used by TSM. If the mount wait is exceeded, the tape is then updated to unavailable and causes a restore/retrieve to fail and reclamation to move on to the next candidate tape. Predicting which tapes will be reclaimed can be a challenge, since TSM splits files and often needs a highly utilized tape to move a file segment. If you can identify a set of tapes which are full and not expiring too fast and they are not needed to often for restores, you can rotate them out of the ATL. I had the luxury of having tape operators monitor the requests, so we made it work until more slots were installed. That took a bit of training and documentation, but is fairly simple. Regards, - Paul Paul Thorson Levi, Ray Shoup, Inc. Tivoli Specialist - LRS IT Solutions (217) 793-3800 x1704 -Original Message- From: Justin Bleistein [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 10:52 AM To: [EMAIL PROTECTED] Subject: volume management in tsm We are in a bit of a pickle or soon will be anyway We have an IBM/3494 atl in our TSM environment. Which has about 1,000 slots in it. These slots are filling and fast. We're trying to make room for more scratch tapes. Now I've tried everything from move data to weird reclaimation sinareos. And we just can't seem to free up sificiant slots. I had an idea of ejecting all tapes which haven't been written to in a while there just waiting to expire, this way migration or backup storage pool processes won't call for them, and once they're out rack them in the data center and mark there location as: rack. Now that will free up a ton of spots in the atl. The problem is how can TSM manage those tapes even though they are not in the ATL. I can check them in with check label = no, and just mark there location as: rack this way the database will keep updating them. The problem is what if reclaimation runs, now you can't do it because the tapes can't be mounted they're in the rack outside the atl. Unless the robot comes out to get them I don't see how this can work. It seems that trying to come up with a solution to the problem of lack of slots in the atl will just create more of a problem. Any thoughts? Or ideas? on how I can manage these tapes even though they can't be mounted?. P.S. = Yes it is collocated. Let me know if anyone has done this thanks!. --Justin Richard Bleistein
WIN2k Clients Backing up Executables ALL THE TIME
Hi folks, TSM Server 5.1.1.6 (was 4.1.1 but behavior is the same) (on AIX 4.3.3) TSM Windows Client 5.1.1.5 (was 4.2.1 but behavior is the same) Windows W2K SP2 My problem is that the W2K clients are always backing up a whack of .exe's and .dll's. The reason that it is backing them up is that the modified date/time keeps getting updated. Interestingly enough, the time seems to be when the TSM schedule starts! These files are obviously not changing. The other thing is it seems to be backing up the files as system objects and not files. If I run 'dsmc inc c:', it backs up about 10mb. If I run 'dsmc inc' it backs up around 800mb. Any ideas? Miles -- Miles Purdy System Manager Agriculture and Agri-Food Canada, Information Systems Team, Farm Income Programs Directorate Winnipeg, MB, CA [EMAIL PROTECTED] ph: (204) 984-1602 fax: (204) 983-7557 If you hold a UNIX shell up to your ear, can you hear the C? -
Re: AUTOMOUNT options file option?
On Wed, 25 Sep 2002, Thomas A. La Porte wrote: We are also backing up Netapp filers over NFS, and we have used several solutions, none of which are completely satisfactory to us. We are trying to see if we can't work under a supported configuration, since TSM claims to support automounted filesystems.. Assuming you have a client initiated (CRON) method to do backups and not server scheduled Because with server -scheduled, we could not have the the below options to work at all *domain all-nfs *domain all-auto-nfs (I have an explanation to what happens here, I even had a PMR level 2.. and they could not figure out why the error messages. At the end it was the solaris automounter which was sending wrong messages back to TSM) and also that I had about 30 netapp volumes exported via NIS on each of our proxy TSM clients (I call them proxy, 'cause they help to backup up my netappps :)). I did not want to hit the media server at once. So here is what I did, for the TSM client to run a complete incremental backup on a automounted map, we have cron scripts which initiate these from the proxy client. We mount the NIS maps (Snapshots exported via NIS) stay mounted until the backup completes. Then force umount it, because a new nightly snapshot run from an admin host will over write the old snapshot on the filer. The key is to *cd* to the map! it is a simple script below. but the trick was to get it work where, process are spawned per file-system in the background hope this helps,. offcourse the whole traffic is on the LAN, that could be a bottle neck for you though #!/bin/ksh #-- # Just check to see if the maps are available # for mounts in `cat /var/tsm/local/vol_mounts1`; do ls -a $mounts /dev/null if [[ $? != 0 ]]; then print $mounts auto_mount_MAP had a problem on SANDERS /var/tsm/loca l/message_file print Please verify and check with the Filers admin.. /var/tsm/local/message_file /usr/ucb/Mail -s TSM backup error on NFS-admin Sanders names /var/tsm/local/message_file rm /var/tsm/local/message_file # Don't exit continue with the next one else # Spin-off dsmc incr commands on multiple file-systems and when done, unmount # them ( cd $mounts;/bin/dsmc inc $mounts -sub=y ;cd ../..;sleep 5;umount -f $mounts ) fi done Hope this helps!
Veritas volumes for db storage
Hi you gurus I am planning to use veritas (0+1) volumes defined into TSM as db volumes, anyone seen any performnace issue here. Platform SUN solaris 2.8 TSM 5.x.x. (not sure yet) Your experience will be a great help many thanks Chetan
select for active versions
Does anyone have a sql to see which tapes contain only the active data from an offsite pool? anyone ideas would be helpful. I'm trying to limit the amount of tapes I bring to D.R. Joseph Dawes I/T Infrasctructure - Unix Technical Support Chubb Son, a Division of Federal Insurance Company 15 MountainView Road Warren,New Jersey 07059 Office:908.903.3890
SAN and TSM
I know this has been discussed before but I need some info. We are in the early stages of implementing TSM on the new SAN environment. What are the different components that we would need for a LAN free and Serverless Backup? Like San Client, Storage agent, etc, etc... What needs to be done to use the Tape Drives which will be in the IBM3584 on the SAN (for Serverless backup)? Any help is appreciated. Rajesh Oak Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS http://www.mail.lycos.com/brandPage.shtml?pageId=plus
Re: Withdrawal of 3570 Magstar
Try 3 minute :( to get a LTO loaded and started spinning ... great for bulk store, but not up to 'interactive' response needs :( ... Using LTO for HSM would seem counterproductive IMHO. -Original Message- From: Steve Harris [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 11:58 PM To: [EMAIL PROTECTED] Subject: Withdrawal of 3570 Magstar 3570 users, I notice that IBM is withdrawing all 3570 items from marketing in December 2002.(announcemet letter WG02-0316) Looks like time to consider an upgrade if you are using these. IBM suggests Ultrium as the replacement, but that hardly has a six second load time does it? Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
how to keep all data on disk for quicker restores
Hi as the subject refers to how to keep all data on disk for quicker restores I have been tasked, again, to change the way TSM operates and to do a scheduled full backup once a week and incrementals in between. ( stop laughing! ) we currently have an H70 running AIX with an ATL P2000 100 tape library. and others in the dept want to have data so that at any point we can restore a system from disk. and not tape unless of a disaster. we currently have vers set for 30 and no co-location. our diskpool is currently 60gb we seem to backup approx 80gb a night. if anyone would like to share thier thoughts... because mine are going very quickly thanks Paul Paul J Coviello Sr Systems Analyst Catholic Medical Center 2456 Brown Ave Manchester, NH 03103 603 663-5326
Re: Withdrawal of 3570 Magstar
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Coats, Jack Try 3 minute :( to get a LTO loaded and started spinning ... great for bulk store, but not up to 'interactive' response needs There's something seriously wrong. Maybe it's 3 minutes to 1) mount the tape 2) spin forward to the point where business can begin If your LTO mounts alone are taking 3 minutes, you need to have your system looked at, sir. Also, keep in mind that 3570 tapes held, tops, 20 GB. I've seen LTOs that hold as much as 240GB. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Disk volumes
can I just ask, are these drives external attached on a SCSI array types or internal to the box, (I mean internal bays) depending on the server!? 'cause I have similar situation, when we went into using T3 storage for db and spools. The inherent limitation to configure T3's as raw or JBOD there was as significant slowness in performance. Yes at first we were using filesystems. we saw 1meg a min :( After going to raw disks we saw 20 - 25 MB /sec writes. Which is still way less than what a T3 is advertized to do though (80MB sustained). Oh well may be T3 's were not a right storage for TSM is what I have learnt. Offcourse with 256MB cache and write ahead enabled. I was told that the TSM server uses variable 4 to 64k and the T3 with 64K fixed block size was also the cause for the low performance .. -Chetan On Thu, 26 Sep 2002, Johnn D. Tan wrote: Date: Thu, 26 Sep 2002 12:42:45 -0400 From: Johnn D. Tan [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Disk volumes I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: WIN2k Clients Backing up Executables ALL THE TIME
Windows 2000 backs up the system files (a whole whack of dll's and exe's) as part of the system object. The default domain for an incremental includes the System Object. You can change the default ALL-LOCAL domain to not include the system object BUT be aware that the SYSTEM OBJECT also contains the registry, event logs, cluster db, active db, comm db ...) All system files are backed up every time regardless of whether they are changed. Tim Rushforth City of Winnipeg -Original Message- From: Miles Purdy [mailto:[EMAIL PROTECTED]] Sent: September 26, 2002 1:57 PM To: [EMAIL PROTECTED] Subject: WIN2k Clients Backing up Executables ALL THE TIME Hi folks, TSM Server 5.1.1.6 (was 4.1.1 but behavior is the same) (on AIX 4.3.3) TSM Windows Client 5.1.1.5 (was 4.2.1 but behavior is the same) Windows W2K SP2 My problem is that the W2K clients are always backing up a whack of .exe's and .dll's. The reason that it is backing them up is that the modified date/time keeps getting updated. Interestingly enough, the time seems to be when the TSM schedule starts! These files are obviously not changing. The other thing is it seems to be backing up the files as system objects and not files. If I run 'dsmc inc c:', it backs up about 10mb. If I run 'dsmc inc' it backs up around 800mb. Any ideas? Miles -- Miles Purdy System Manager Agriculture and Agri-Food Canada, Information Systems Team, Farm Income Programs Directorate Winnipeg, MB, CA [EMAIL PROTECTED] ph: (204) 984-1602 fax: (204) 983-7557 If you hold a UNIX shell up to your ear, can you hear the C? -
Re: TSM Encryption
Jim, Thanks for the info. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: Jim, The TSM Backup/Archive client uses 56-bit DES encryption. Thanks, Jim Smith TSM Development Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: starting TSM without it doing anything
It works in 4.2. I haven't tried 5.1 yet. Nici -- Nici Albrecht MDR Consulting Education 210-860-4641 William White wrote: Dear Listreaders: Some time ago I had a problem with TSM (I believe it was V4.1.2) server for OS/390. I had managed to make some kind of error in specifying threshholds (For migration as far as I remember) that caused TSM to go into a loop as soon as it was started. While in the loop, commands were not processed. The support center gave me an undocumented parameter for the server options file: NOMIGRRECL This option prevented migration and reclamation from starting and allowed me to issue commands to reset the threshholds. I don't know if it still works ( It's always the case for undocumented features, of course.) - William White Service Delivery Section International Computing Centre (ICC) e-mail: [EMAIL PROTECTED]
Re: BMR scripts
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Dearman, Richard Has anyone tried to script a BMR solution for NT or AIX using tsm. Everyone keeps saying the Bare Metal Restore is just a bunch of scripts that access TSM but has anyone tried create those scripts themselves. BMR procedures for AIX are a no-brainer. Boot from installation media, restore your bootable mksysb backup image to get rootvg back, recreate the volume groups and filesystems, install the TSM client if it wasn't installed in rootvg, and restore all non-rootvg files. Easy, peezy. The problem with scripting a BMR procedure for Windows is that Windows simply lacks the required abilities. True BMR has the following requirements: 1. The OS must support booting from a network-attached image. NT cannot do this, and although I've been told Win2K will do it, I've never met anyone who has been able to make it work. 2. The OS must support the ability to insert missing drivers from local (or remote) installation media; this ability is vital for restoration to dissimilar hardware. (For instance, if the installation image lacks a driver for the NIC or SCSI adapter in the target box, it must be able to fetch that driver from installation media.) Windows completely lacks this ability during OS installation, except for SCSI-based RAID controllers. 3. The OS must support the ability to either overwrite hot (i.e., open) files, or support the ability to copy cold restored files to a hot location during a reboot. Windows can't do that. The application Bare Metal Restore (now published by Veritas, formerly published by The Kernel Group) found a handful of workarounds in order to get BMR to work with Windows. What I discovered in my work with BMR is that restores were absolutely breath-taking--as long as that restore is done in carefully controlled environments to exactly the same hardware. In the real world, on the two occasions that I witnessed, BMR failed to delivery despite the presence of a TKG engineer flown in to assist. We just couldn't get it to work. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: TSM Encryption
Hello Jim Follow up question, Can you ask if there is anyway for us to get clients that do stronger encryption, eg tripledes? If not, are there plans in the future to offer strong encryption? This relates to the HIPAA requirements that are coming. Thanks again. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: Jim, The TSM Backup/Archive client uses 56-bit DES encryption. Thanks, Jim Smith TSM Development Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: Does anyone implement Space Mgr + NFS on windows + AIXsuccessfully?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ramnarayan, Sean A [EDS] We currently using HSM on AIX for NFS mounts and the way we currently set this up is to have the HSM client installed on the NFS server as well as the NFS client server. This set-up works on AIX NFS file systems. I am almost sure it should work the same way for Windows. You are required to install the HSM client on both servers. That might work, except that Tivoli doesn't publish an HSM client (or server) for Windows. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Withdrawal of 3570 Magstar
Accually, every now and again I used to see 3570 CLX tapes get about 60 GB on them compressed. But that was only for storage pools made up entirely of Solaris machines. Never really understood that, except to think that Solaris is real weird in places. Normally, I was lucky to get 13 GB on CXL tapes. But then, 357X hardware normally stinks. Had a 3575 that used to break on a weekly basis. David N. Reiss TSM Support Engineer [EMAIL PROTECTED] 407-736-3912 -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 4:33 PM To: [EMAIL PROTECTED] Subject: Re: Withdrawal of 3570 Magstar From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Coats, Jack Try 3 minute :( to get a LTO loaded and started spinning ... great for bulk store, but not up to 'interactive' response needs There's something seriously wrong. Maybe it's 3 minutes to 1) mount the tape 2) spin forward to the point where business can begin If your LTO mounts alone are taking 3 minutes, you need to have your system looked at, sir. Also, keep in mind that 3570 tapes held, tops, 20 GB. I've seen LTOs that hold as much as 240GB. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
W2K Recovery
Anyone had a problem on a W2K recovery where the Server service would not start?? All events seem to go ok. The application riding on the server works fine. But this service and its dependents will not start. Used B/A client version 5.1.0.1 on TSM server v4.2.1.11 on AIX 4.3.3. Any thoughts or suggestions?? Thanks, Matt - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: Withdrawal of 3570 Magstar
Hot Diggety! Coats, Jack was rumored to have written: Try 3 minute :( to get a LTO loaded and started spinning ... great for bulk store, but not up to 'interactive' response needs :( ... Using LTO for HSM would seem counterproductive IMHO. 3 minutes?! Something sounds wrong there. I've got a 3584 with 12 LTO drives attached to host system via SCSI, and it takes 3-9 seconds to have the robot fetch the tape from storage slot, move it to drive, load it in the drive, and about 46 seconds to read the volser on the tape and other mount-related processing, for a total of about 55 seconds from issuing command to load to start using a tape. We've got a L32 and D32 frame; guess it could conceivably be a little longer in worst case scenarios if had a decked out setup (one L32 and five D32s) but I can't see it being much more than 1m to 1m10s or so. However, that 55 seconds is a little painful in certain situations. For example: client-disk stgpool (10MB max)-tape stgpool Client sends data to TSM server As long as client data is 10MB, streams to disk pool Soon as client sends a 11 MB or 500 MB file, then... TSM fetches a tape, mounts it (55 sec wait) TSM starts writing file to tape Once done, TSM dismounts the tape (!) Client continues sending data If it hits another 10MB file, the whole mount-write-dismount process repeats. This results in a significant performance hit from all the mounts/dismounts. To alleviate this, I've set the node's KEEPMP option to YES, so it ends up mounting the tape once on first access, then keeps it mounted throughout the entire client run so that we get no more subsequent 55 sec mount delays. When does it dismount the tape? After the tape retention in drive period expires, but usually the next client session grabs the same tape if it's got free space. The above was with a TSM 4.2 setup; I just installed TSM 5.1, so I've got to retest to see if this is any different without the KEEPMP option being enabled. Anyway, I'd strongly urge you to get that 3 minute wait looked at! -Dan
Re: WIN2k Clients Backing up Executables ALL THE TIME
All system files are backed up every time regardless of whether they are changed. This is thanks to the stupidity of Microsoft's inclusion of the event logs as part of the system objects. On Thu, 26 Sep 2002, Rushforth, Tim wrote: Windows 2000 backs up the system files (a whole whack of dll's and exe's) as part of the system object. The default domain for an incremental includes the System Object. You can change the default ALL-LOCAL domain to not include the system object BUT be aware that the SYSTEM OBJECT also contains the registry, event logs, cluster db, active db, comm db ...) All system files are backed up every time regardless of whether they are changed. Tim Rushforth City of Winnipeg -Original Message- From: Miles Purdy [mailto:[EMAIL PROTECTED]] Sent: September 26, 2002 1:57 PM To: [EMAIL PROTECTED] Subject: WIN2k Clients Backing up Executables ALL THE TIME Hi folks, TSM Server 5.1.1.6 (was 4.1.1 but behavior is the same) (on AIX 4.3.3) TSM Windows Client 5.1.1.5 (was 4.2.1 but behavior is the same) Windows W2K SP2 My problem is that the W2K clients are always backing up a whack of .exe's and .dll's. The reason that it is backing them up is that the modified date/time keeps getting updated. Interestingly enough, the time seems to be when the TSM schedule starts! These files are obviously not changing. The other thing is it seems to be backing up the files as system objects and not files. If I run 'dsmc inc c:', it backs up about 10mb. If I run 'dsmc inc' it backs up around 800mb. Any ideas? Miles -- Miles Purdy System Manager Agriculture and Agri-Food Canada, Information Systems Team, Farm Income Programs Directorate Winnipeg, MB, CA [EMAIL PROTECTED] ph: (204) 984-1602 fax: (204) 983-7557 If you hold a UNIX shell up to your ear, can you hear the C? -
Re: TSM upgrade from 3.7 to 5.1
I have an upgrade doc for my HP system you are welcome to have if you want? I just upgraded from 3.7 to 4.2.2.5 on HP-UX 11.0. I know there are some subtle differences. Bill -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:11 AM To: [EMAIL PROTECTED] Subject: Re: TSM upgrade from 3.7 to 5.1 It is AIX 4.3.3 -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 10:13 AM To: [EMAIL PROTECTED] Subject:Re: TSM upgrade from 3.7 to 5.1 Sachin, What platform are you on? The upgrade procedure varies based upon the operating system the TSM server is running on. Please provide the OS version and release for us to assist you with the installation further. Also, you should have received a Quick Start guide with your TSM upgrade. Installation info can also be found there. It can also be downloaded at the TSM web site www.tivoli.com/tsm. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Ganu Sachin, IBM Sent: Monday, September 23, 2002 8:20 PM To: [EMAIL PROTECTED] Subject: TSM upgrade from 3.7 to 5.1 Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
Re: select for active versions
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph Dawes Does anyone have a sql to see which tapes contain only the active data from an offsite pool? anyone ideas would be helpful. I'm trying to limit the amount of tapes I bring to D.R. If the number of tapes you take to DR is important, make backupsets and bring them. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Disk volumes
Ours are SCSI-attached external subsystem (2104). Wow... from 1 MB/min to 20 MB/sec! We are definitely going to investigate raw devices! johnn can I just ask, are these drives external attached on a SCSI array types or internal to the box, (I mean internal bays) depending on the server!? 'cause I have similar situation, when we went into using T3 storage for db and spools. The inherent limitation to configure T3's as raw or JBOD there was as significant slowness in performance. Yes at first we were using filesystems. we saw 1meg a min :( After going to raw disks we saw 20 - 25 MB /sec writes. Which is still way less than what a T3 is advertized to do though (80MB sustained). Oh well may be T3 's were not a right storage for TSM is what I have learnt. Offcourse with 256MB cache and write ahead enabled. I was told that the TSM server uses variable 4 to 64k and the T3 with 64K fixed block size was also the cause for the low performance .. -Chetan On Thu, 26 Sep 2002, Johnn D. Tan wrote: Date: Thu, 26 Sep 2002 12:42:45 -0400 From: Johnn D. Tan [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Disk volumes I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: Disk volumes
On Thu, 26 Sep 2002, Johnn D. Tan wrote: Ours are SCSI-attached external subsystem (2104). Wow... from 1 MB/min to 20 MB/sec! We are definitely going to investigate raw devices! wait this did not just come from moving to raw volumes, there were more issues. We had the Recover logs on the system disk, which got moved to external SCSI D130s and the striping parameter was tunned to be optimal on the T3+ storge. Again beleive it or not I am looking into JBOD (D2 arrays) for spools and getting better faster speeds than T3+ Cheers.. johnn can I just ask, are these drives external attached on a SCSI array types or internal to the box, (I mean internal bays) depending on the server!? 'cause I have similar situation, when we went into using T3 storage for db and spools. The inherent limitation to configure T3's as raw or JBOD there was as significant slowness in performance. Yes at first we were using filesystems. we saw 1meg a min :( After going to raw disks we saw 20 - 25 MB /sec writes. Which is still way less than what a T3 is advertized to do though (80MB sustained). Oh well may be T3 's were not a right storage for TSM is what I have learnt. Offcourse with 256MB cache and write ahead enabled. I was told that the TSM server uses variable 4 to 64k and the T3 with 64K fixed block size was also the cause for the low performance .. -Chetan On Thu, 26 Sep 2002, Johnn D. Tan wrote: Date: Thu, 26 Sep 2002 12:42:45 -0400 From: Johnn D. Tan [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Disk volumes I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: TSM Encryption
Jim, I would recommend that you open a requirement against the product for stronger encryption. By the way, what are the HIPAA requirements as they relate to data encryption? Are these well documented? Thanks, Jim Smith TSM development Hello Jim Follow up question, Can you ask if there is anyway for us to get clients that do stronger encryption, eg tripledes? If not, are there plans in the future to offer strong encryption? This relates to the HIPAA requirements that are coming. Thanks again. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: Jim, The TSM Backup/Archive client uses 56-bit DES encryption. Thanks, Jim Smith TSM Development Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
HP UX Restore from one mountpoint to another mountpoint Question
TSM Server 5.1.1.4, HP-UX Client 5.1.1.0 We've backed up a bunch of mountpoints: /sapprd01/install /sapprd01/db01 etc. They are mountpoints on the original system. At the DR site, we create a single filesystem/mountpoint: /sapprd01 We would like to select some of the original mountpoints and restore them to the new /sapprd01 mountpoint and preserve the directory structure. We're finding that the file in /install won't end up in a directory called install at /sapprd01. Must we have all of the original mountpoints established to make this work? Is there a clever trick to help us out here? Thanks gang. Kelly J. Lipp STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175
Re: select for active versions
It is more complex than a select. The BACKUPS table contains the entry information you want and for each active version file there is a object id. That object id is used against an internal bit file object table to determine the tape volumes that the object is on for all copy pools. The key here is the bit file object table is not externalized and no select can do what you want. What I have done to find the volume of an object is create a file with a select of show bfo commands and use it as a macro to pipe the output into a file and post process with a perl script to gather the information that I need. SHOW BFO is not supported. The select of the active versions is going to run forever unless you do it a filespace at a time and then if you have a lot of them it will take a while. So, this may be useful for say database backups where you only have 100 objects to deal with. But, it is not practical for a file server that hundreds of thousands of files. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 5:18 PM To: [EMAIL PROTECTED] Subject: Re: select for active versions From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph Dawes Does anyone have a sql to see which tapes contain only the active data from an offsite pool? anyone ideas would be helpful. I'm trying to limit the amount of tapes I bring to D.R. If the number of tapes you take to DR is important, make backupsets and bring them. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Disk volumes
I would never use T3 or T3+ for my Solaris 8 TSM servers. T3 is just not a good performer. It's pretty decent for redundancy and availability and lots of disk in a small foot print. I'm using D2 arrays on one of my TSM servers and think the disk throughput is great. We use raw volumes and multiple HBA's and don't have any issues with throughput or being I/O bound. U160 JBOD (like the D2) seems to be a good solution for TSM. Eric Cowperthwaite EDS -Original Message- From: Chetan H. Ravnikar [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 3:48 PM To: [EMAIL PROTECTED] Subject:Re: Disk volumes On Thu, 26 Sep 2002, Johnn D. Tan wrote: Ours are SCSI-attached external subsystem (2104). Wow... from 1 MB/min to 20 MB/sec! We are definitely going to investigate raw devices! wait this did not just come from moving to raw volumes, there were more issues. We had the Recover logs on the system disk, which got moved to external SCSI D130s and the striping parameter was tunned to be optimal on the T3+ storge. Again beleive it or not I am looking into JBOD (D2 arrays) for spools and getting better faster speeds than T3+ Cheers.. johnn can I just ask, are these drives external attached on a SCSI array types or internal to the box, (I mean internal bays) depending on the server!? 'cause I have similar situation, when we went into using T3 storage for db and spools. The inherent limitation to configure T3's as raw or JBOD there was as significant slowness in performance. Yes at first we were using filesystems. we saw 1meg a min :( After going to raw disks we saw 20 - 25 MB /sec writes. Which is still way less than what a T3 is advertized to do though (80MB sustained). Oh well may be T3 's were not a right storage for TSM is what I have learnt. Offcourse with 256MB cache and write ahead enabled. I was told that the TSM server uses variable 4 to 64k and the T3 with 64K fixed block size was also the cause for the low performance .. -Chetan On Thu, 26 Sep 2002, Johnn D. Tan wrote: Date: Thu, 26 Sep 2002 12:42:45 -0400 From: Johnn D. Tan [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Disk volumes I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. You have a total of 28 spindles, 14 each on two busses, right? I'd suggest making a RAID-5 out of the fourteen free spindles, and then make the individual volumes A reasonable size. What's a reasonable size? Uh... ;) I just did this with a drawer of 36G SSA, and I chose 10G volumes, because I have about a dozen (and growing) disk pools amongst which I need to divide things up. Even if you only have one or two disk pools, it's useful to have more than a few volumes per pool, because instantaneously only on thing can write to a volume at a time. So, for example, if you have 12 clients backing up, and one 70G disk volume, there is contention for the thread controlling that one volume. So calculate the size so that you'll have as many volumes as you feel like keeping track of, but not many more than that. - Allen S. Rout
Re: BMR scripts
Hi, I did perfect a method on my AIX SP cluster, but I havent visited it for a while. 1. Use NIM to build a new rootvg, with TSM installed. ( it could be a tape image or rebuild from install media in your case) 2. Use alt_disk_install functionality to create an alternate rootvg 3. Use TSM to restore latest versions of / /var /usr etc to alternate filesystems 4. Boot from alternate filesystem 5. in the SP world, run a CUSTOMIZE on the node to get the ODM updated with node-specific SP stuff. Its not really all that difficult. The only bit that threw me was getting the SP Stuff to work. Regards Steve Harris AIX and TSM Admin [EMAIL PROTECTED] 27/09/2002 4:57:27 Has anyone tried to script a BMR solution for NT or AIX using tsm. Everyone keeps saying the Bare Metal Restore is just a bunch of scripts that access TSM but has anyone tried create those scripts themselves. Thanks ***EMAIL DISCLAIMER*** This email and any files transmitted with it may be confidential and are intended solely for the use of th individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.996.3941. ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
TSM 4.2.1 client and 32-bit AIX 5.1 machines
Hi all, I have two 32-bit AIX 5.1 machines. The TSM 4.2.1 clients only have 64-bit version for AIX 5.1. Can I use the client for AIX 4.3 (32-bit)? Thanks Fred
Re: how to keep all data on disk for quicker restores
Paul, There are a number of SCSI-IDE or FC-IDE raid arrays out there. One of these I was looking at had 16 slots and 16 IDE busses, with 200GB disk on each. Thats 3TB of disk.It also had virtual tape support - which on the surface seems intriguing too. If this was configured mostly as TSM sequential file storage, on a filesystem with huge capacity (AIX JFS2 for instance), then you could possibly get away with what your management wants and only have to do a selective say once every three months to keep the active data on disk. This is where a migrate inactive command would be handy. Now such disk subsystems aren't cheap, but compared to Enterprise class EMC or IBM arrays they are peanuts and sequential backup pool performance won't be much of an issue. I know people have talked about this sort of thing on the list before. Is anybody doing it? Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia [EMAIL PROTECTED] 27/09/2002 6:00:22 Hi as the subject refers to how to keep all data on disk for quicker restores I have been tasked, again, to change the way TSM operates and to do a scheduled full backup once a week and incrementals in between. ( stop laughing! ) we currently have an H70 running AIX with an ATL P2000 100 tape library. and others in the dept want to have data so that at any point we can restore a system from disk. and not tape unless of a disaster. we currently have vers set for 30 and no co-location. our diskpool is currently 60gb we seem to backup approx 80gb a night. if anyone would like to share thier thoughts... because mine are going very quickly thanks Paul Paul J Coviello Sr Systems Analyst Catholic Medical Center 2456 Brown Ave Manchester, NH 03103 603 663-5326 ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Re: volume management in tsm
In an open environment TSM will not automatically checkin the tape, nor does it do the checkin on S/390. OAM does the checkin on S/390. I am betting he is using S/390. And, yes, TSM is then able to mount the tape. If I were a real good C programmer I would write a task to connect to the lmcpd that listens for the the insert function and runs a script passing the volume inserted as the parameter. The script could then be tailored to my business needs. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Justin Bleistein [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:22 PM To: [EMAIL PROTECTED] Subject: Re: volume management in tsm yeah that's what I figured. I took particular interest in one of you statements below, when you said that if TSM is calling for a tape mount, all the operator has to do is put a tape in the ATL I/o slots drawer and the robot will take it and check it in to TSM and use it?. Did I read that right? Or do the operators have to physically open of the the 3494 bays/doors and physically mount the tape as if it were manual? --Justin Thorson, Paul [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: Sent by: ADSM: Subject: Re: volume management in tsm Dist Stor Manager [EMAIL PROTECTED] .EDU 09/26/2002 12:46 PM Please respond to ADSM: Dist Stor Manager Justin, I've experienced this on several occasions including having close to 1000 tapes outside of a 3494. Obviously, someone has miscalculated the size necessary to house all your primary storage pool volumes - the easiest solution is to bolt on a couple more 'S' frames on the ATL. TSM will manage the tapes automatically outside of the ATL - there is no need to update their location as 'rack'. If needed, TSM will request a tape volume until the tape is checked in or the mount wait of the device class is exceeded. When put in the ATL, the tape is automatically checked in and used by TSM. If the mount wait is exceeded, the tape is then updated to unavailable and causes a restore/retrieve to fail and reclamation to move on to the next candidate tape. Predicting which tapes will be reclaimed can be a challenge, since TSM splits files and often needs a highly utilized tape to move a file segment. If you can identify a set of tapes which are full and not expiring too fast and they are not needed to often for restores, you can rotate them out of the ATL. I had the luxury of having tape operators monitor the requests, so we made it work until more slots were installed. That took a bit of training and documentation, but is fairly simple. Regards, - Paul Paul Thorson Levi, Ray Shoup, Inc. Tivoli Specialist - LRS IT Solutions (217) 793-3800 x1704 -Original Message- From: Justin Bleistein [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 10:52 AM To: [EMAIL PROTECTED] Subject: volume management in tsm We are in a bit of a pickle or soon will be anyway We have an IBM/3494 atl in our TSM environment. Which has about 1,000 slots in it. These slots are filling and fast. We're trying to make room for more scratch tapes. Now I've tried everything from move data to weird reclaimation sinareos. And we just can't seem to free up sificiant slots. I had an idea of ejecting all tapes which haven't been written to in a while there just waiting to expire, this way migration or backup storage pool processes won't call for them, and once they're out rack them in the data center and mark there location as: rack. Now that will free up a ton of spots in the atl. The problem is how can TSM manage those tapes even though they are not in the ATL. I can check them in with check label = no, and just mark there location as: rack this way the database will keep updating them. The problem is what if reclaimation runs, now you can't do it because the tapes can't be mounted they're in the rack outside the atl. Unless the robot comes out to get them I don't see how this can work. It seems that trying to come up with a solution to the problem of lack of slots in the atl will just create more of a problem. Any thoughts? Or ideas? on how I can manage these tapes even though they can't be mounted?. P.S. = Yes it is collocated. Let me know if anyone has done this thanks!. --Justin Richard Bleistein
Re: Disk volumes
I think I understand what is going on here. In the case of a filesystem you stripe your data across a bunch of disks. But, when you define the files you now have conflicting IO points on the disks. However, if you were to use TSM volumes that fully filled each defined filesytem you will probably do fine on performance given the filesystem is tuned correctly. In AIX vmtune allows you to set the maxperm down so it will not conflict with the memory required for the bufferpool. On Solaris, I do not know how to do this with UFS+ file systesms or Veritas file systems, but I am sure someone will chime in on that subject. I also find that if you define all the volumes (files) simultaneously on a filesytem you fragment the logical TSM volume all over the physical volumes when what you probably want is them to have contiguous space. So, I define them one at a time. This is particularly important on a high end disk solution like an IBM ESS otherwise the sequential prestage can be disrupted into looking like sequential data. Especially on the Database or the Log because they typically write sequentially. Reads are mostly buffer hits except during a backup. That is when you really take the hit. File System overhead is an issue by itself, but what is probably causing most file system implementation performance issues is the physical layout of the data. I have not figured out all of the gotchas for file systems yet, but I am getting there. I will have to think about this some more. But, maybe this will kindle some ideas from others. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Johnn D. Tan [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:35 PM To: [EMAIL PROTECTED] Subject: Re: Disk volumes Thanks Scott. Hmm, never saw anyone else mention this, though I've been on the list for about a year. (Though, given the volume of this list, I definitely could've missed some mails.) Well, we are planning to move to new hardware and to TSM 5.1.1.x, so I guess that's as good a time as any to try using raw volumes for DB/log/diskpool. We definitely need any performance gains we can get as our daily automated procedures run very late into the day. Thanks again! johnn John, We just when through setting up our disk staging pool with TSM 5.1 on Solaris 8. We had 6x36G to work with. The initial config used large files on the filesystem. This is incredibly slow. We then configured Disk Suite to mirror the disks and we configured TSM to use the raw devices e.g. /dev/md/rdsk/d0. Performance was significantly better. So TSM saw 3x36. From what we saw, it seemed the mirroring affected the performance more than the lack of spindles. As others have said, TSM seems to be pretty good at spreading the data around so it minimizes contention on the spool volumes. I never tested more, smaller mirrors. We then gave TSM the raw slices /dev/rdsk/c1t0d0s0 so he saw 6x36. This was the fastest by far. We were able to max the bandwidth (100M) for over an hour (38G in one hour). We lose the fault tolerance of mirrored disks, but we figure since it is only a staging area who cares? If a disk goes bad, we will lose the data backed up to it, but we can always back it up again. We felt the performance gains are well worth the redundancy hit. Though we have not tested pulling a disk from the staging pool and seeing what happens. I don't know your environment, but I would go with a single slice on all disks and tell TSM to use the raw device. If you really feel you need the redundancy I would just create 6 mirrors and use the raw mirrored device. From all of the benchmarking I've done it seems that once you get your setup decently tuned (don't tell TSM to use files for DB/LOG/DISKPOOLS) that the bottlenecks are either network capacity to your TSM server, or disk/cpu performance on the client (compression on). But I've only tested in one environment, ymmv. Hope this helps. scott Johnn D. Tan wrote: I have 12 36-GB drives available for spool. Based on recommendations made to this list earlier this year, I went with 12 mirrored disk spools of 16 GB each (keep in mind disk overhead). As I understood it, the issue was you want many spools so that, as Allen mentioned, you can have many threads for backups and even migrations (assuming you have a good number of tape drives). However, you don't want so many spools per disk, otherwise there is contention for head movement on the drive which would result in poorer performance. johnn = On Thu, 26 Sep 2002 08:54:01 -0400, Mahesh Tailor [EMAIL PROTECTED] said: Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI
Re: WIN2k Clients Backing up Executables ALL THE TIME
You noticed the system object includes stuff you would think it should not, also. I cannot remember, but I think they discussed this issue at Share and the need to perform incremental object checking for the objects in the system object. If they did that, then I think the problem will go away. The system object has been a real pain. I also found out today that the 4.2.2.12 patch includes the CLEANUP BACKUPGROUPS command. I have been running it off and on for 3 days now. Boy is it waxing a bunch of stuff. We did not know how bad we had the system object problem. I am hoping they will consider including a correction to this uncontrolled growth area. One thing for sure we have implemented a management class for the system object so that it will get trimmed. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Miles Purdy [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 2:57 PM To: [EMAIL PROTECTED] Subject: WIN2k Clients Backing up Executables ALL THE TIME Hi folks, TSM Server 5.1.1.6 (was 4.1.1 but behavior is the same) (on AIX 4.3.3) TSM Windows Client 5.1.1.5 (was 4.2.1 but behavior is the same) Windows W2K SP2 My problem is that the W2K clients are always backing up a whack of .exe's and .dll's. The reason that it is backing them up is that the modified date/time keeps getting updated. Interestingly enough, the time seems to be when the TSM schedule starts! These files are obviously not changing. The other thing is it seems to be backing up the files as system objects and not files. If I run 'dsmc inc c:', it backs up about 10mb. If I run 'dsmc inc' it backs up around 800mb. Any ideas? Miles -- Miles Purdy System Manager Agriculture and Agri-Food Canada, Information Systems Team, Farm Income Programs Directorate Winnipeg, MB, CA [EMAIL PROTECTED] ph: (204) 984-1602 fax: (204) 983-7557 If you hold a UNIX shell up to your ear, can you hear the C? -
Re: BMR scripts
Hi, all, I also would likes to know if anyone has BMR for Netware servers. I couldn't find doc from anywhere. Bad thing is that Netware doesn't support USB port for local backupset restore ( for example, DVD ROM). They support SCSI though. I wonder what would be the portable media drive of choice for Netware. I was thinking external DVD ROM for Windows. Once I install the proper driver, the restore from backupset is going to be fast for Windows servers. Thanks for your input! Jin Bae Chi (Gus) System Admin/Tivoli Data Center 614-287-2496/5922 614-287-5488 Fax [EMAIL PROTECTED] [EMAIL PROTECTED] 09/26/02 02:57PM Has anyone tried to script a BMR solution for NT or AIX using tsm. Everyone keeps saying the Bare Metal Restore is just a bunch of scripts that access TSM but has anyone tried create those scripts themselves. Thanks ***EMAIL DISCLAIMER*** This email and any files transmitted with it may be confidential and are intended solely for the use of th individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management 312.996.3941.
Re: Disk volumes
What you do not want is the heads jumping all over the disks servicing many different files (TSM Volumes). You have received many responses on this question. My lean would be to stripe the database either RAID1 or RAID5 on a given set of volumes across both arrays (depends on you IO activity). The reality is the database does not have that much write activity. It is mostly read except during expiration. For the storage pools disks I would try to use 1 physical disk per volume and go RAID1, TSM Mirroring, (RAID0 if you can deal with the non protection). Or a RAID-5 if you need the space and use a JFS file system. Others have better experience with this than myself. I have IBM ESS with a non-volatile cache, so it is a different ball game. You may want to try several things to see what works for you best. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: Mahesh Tailor [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 8:54 AM To: [EMAIL PROTECTED] Subject: Disk volumes Hello, TSM: 5.1.1.6 OS: AIX 4.3.3 Machine: IBM 6M1 Hopefully this is a simple question: I have fourteen 36GB drives that are available for the diskpool and I was wondering whether it is better to have seven 5GB files or three 10GB files or one 35GB file or something else? The drives are mounted in two IBM-2014 Ultra-Wide SCSI disk drawers with separate Ultra-Wide contollers. The other 14 drives are used for DB, LOG, and spare. Thanks. Mahesh
Re: help:label tape question
Yes and know. The label operation will grab a drive if it is available and label the tapes. Otherwise, it will fail with no devices available. The backup operation will use the other drive. So start the label operation before the backup operation if you really want to do the labeling. A library cannot auto label a tape. But: label libvol [libname] search=yes labelsource=barcode volrange=[start],[end] Will probably do what you are looking for. select library_name, volume_name, status from libvolumes where status='Scratch' Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -Original Message- From: fenglimian [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 11:31 PM To: [EMAIL PROTECTED] Subject: help:label tape question Hi all, I have a 3494 library with two dirve,the backup-archive server with ADSM .When the library must label 200 tapes a time,at the same time ADSM must have backup some date,can these two operations be doing at the same time? Another question is if I take the opertion: ADSMlabel libvol libname search=yes labelsouce=barcode can library auto label all those tapes in the library? Last can you tell me what's the scratch pool ? Thanks and regards Feng
