Re: Help with brbackup
Cud u send me the .utl and the .sap files. Anoop T.Das 'Before you discover, you need to explore' Richard van Denzel To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: ROUP.COM>Subject: Help with brbackup Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 03/26/2004 09:05 PM Please respond to "ADSM: Dist Stor Manager" Hi All, I've installed TDP for ERP on AIX 5.1 (2 SAP servers) and on both servers I run into the same problem when I try to specify the Parameter file within SAPDBA. When I enter the filename initB01.utl, SAPDBA keep comming up with the following message: SAPDBA: Error in brbackup profile/ expected '=', but read 'B01___' On the other server it gives me the exact same error but then for Oracle SID L02. I'm starting the sapdba from the b01adm (or l02adm) account on the server in question. Has anyone got a clue to what is going wrong or did I miss out something during the configuration? Regards, Richard.
Re: Tape library eval
We are a differnet case than Tom's, it appears. We have been extremely happy with our STK unit: was an L40, upgraded to L80. Just our 2-bits... Chris Murphy IT Network Analyst Idaho Dept. of Lands [EMAIL PROTECTED] -Original Message- From: James Lepre [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 8:35 AM To: [EMAIL PROTECTED] Subject: Re: Tape library eval I do not like storage tek however using the gresham software does seem like a good thing to do. we chose the IBM 3584 LTO, it is the best thing we could have done >>> [EMAIL PROTECTED] 03/25/04 09:19AM >>> Hello - I will soon be purchasing a new library, and am evaluating an Overland NEO 4100 and StorageTek L80. Both appear to be very good and are well suited for my environment. I like the Overland's scalability. Does anyone have any experience with either of these libraries, and if so, how is the support? thanks, Tom Bull Partners Healthcare System, Inc.
Re: Incremental backup hanging
>We are running TSM 5.2.1 on an AIX 5.2 platform. Until recently we have had no >problems >with our incremental backups. Now one of our servers hangs in the /usr directory >during >incremental backups. Any experienced this problem before? What diagnostic work have you done? Have you done a Selective on that file system to find out where it "hangs"? Or a 'find ... -ls'? What does Query SEssion show on the server when it occurs? Any problem indications in the AIX Error Log? Richard Sims
Incremental backup hanging
** Proprietary ** We are running TSM 5.2.1 on an AIX 5.2 platform. Until recently we have had no problems with our incremental backups. Now one of our servers hangs in the /usr directory during incremental backups. Any experienced this problem before? James Fletcher Supervisor, Operating Systems Washington Metro Transit Authority Tele: (202) 962-2482 e-mail: [EMAIL PROTECTED]
Re: DB2 and TSM
It is built into DB2. Andrew Lathrop Olympia, WA 98504 (360) 664-8115 -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 9:09 AM To: [EMAIL PROTECTED] Subject: DB2 and TSM Please forgive my ignorance on this but someone is looking to add a server to TSM for backups and wants to know if TSM has an agent for DB2. From what I can tell there is no agent out there on the FTP site. I'm wondering if IBM has functionality built in to the product to back up the DB direct to TSM without shutting it down or if there is some other way to back up this DB. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
Re: ?Can Linux or (Win?) replace AIX for I/O intensive TSM service?
First, take what you've got and throw a LOT more RAM at it. I can't believe you're getting what you are actually getting out of only 3GB, without memory constraint showing up somewhere, such as lowered database cache hit ratios, or tape I/O buffers being too small which will slow down your tape drives. Just because you're not paging doesn't mean that more memory wouldn't help. (The TSM image working set probably stays in real memory regardless.) That 6F1 is a pretty muscular I/O engine, which will be tough to beat. They'e showing up on the used market now - get a second one if you think you can split your clients. (You'd have to split them a lot more ways if you went to another platform.) Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Thu, 25 Mar 2004, James R Owen wrote: >?Can Linux (or Win?) replace AIX for hosting an I/O intensive TSM service? > >After scanning the past year's ADSM-L postings including Linux in the subject >I have the impression that a few people are playing with Linux hosting a TSM >service, but real I/O intensive TSM services are still mainly hosted by AIX. > >?Is anyone already using or actively planning to use Linux (RedHat EL 3.0?) >to host an I/O intensive TSM service similar to any described under the >recent ADSM-L thread, "Sizing an AIX platform and tape libraries"? > >We believe we are approaching the maximum that can be achieved w/ >TSM:v5.2.1.3 >OS: AIX 5.1 (64bit) >CPU:IBM 7025-6F1 w/ 4 * 750Mhz proc's + 3GB RAM >SAN:1 Gb w/ EMC Symmetrix 8830 >LAN:1 Gb Ethernet >ATL:IBM 3494 w/ 6 * 3590E drives >IBM 3584 w/ 4 * 3580 LTO1 + 2 * 3580 LTO2 drives > >This configuration is successfully supporting our current ITS TSM service >(see details below), but we believe we either need a major performance >boost or to split this load onto an additional host platform: >Linux, Win*, or must we remain w/ AIX for I/O performance? >to handle expected additional growth. > >Which platform have you chosen (or would you choose) for similar TSM service? > >Yale ITS TSM Service: > >Active Clients: 2400 <= 3d, 2500 <= 7d, 2700 <= 35days > >Servers:151 >WinNT,2K* 105 >Linux 20 >Solaris 9 >AIX 7 >SQL-BT (Oracle) 3 >Mac 2 >TDP's: MSSQL,MSexchg: 2 + 1 >[new]2 > >Personals: 2549 >WinNT,2K*,XP 2230 >Win98,ME26 >Mac183 >Linux 50 >Solaris 5 >AIX,DEC*X,HPUX,IRIX: 1 ea. >[new] 51 > >Expected growth: +500-600 clients for several years >+20% data for existing clients/year? > >TSM DB: 75.7% of 160GB >BAckup DB w/ LTO1 HCmpr. takes 2.3h >EXPIre Inv examines ~6M obj, deletes ~1M obj. in 8-9h > > >Disk STGpools: 600 + 180GB >Nightly Backup Period: 15:30-08:00+ >Weeknight Backup Load: 500-650GB+ > >Thanks for any experience/insight you are willing to share with us! >-- >[EMAIL PROTECTED] (203.432.6693) >
Re: Question about recovery log
Roger makes an EXCELLENT point that everyone should follow, I found out the hard way as I had a recovery log fill up and only had 100 MB for emergency, it wasn't enough and I ended up spending 8 hours restoring a TSM server. I now follow the practice of leaving the emergency space, everyone should because you WILL need it someday. Ryan Miller Principal Financial Group Tivoli Certified Consultant Tivoli Storage Manager v4.1 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Roger Deschner Sent: Friday, March 26, 2004 12:36 PM To: [EMAIL PROTECTED] Subject: Re: Question about recovery log 1. Never make it larger than 12GB! Someday, your log will fill up, and you've got to have room under the 13gb limit to be able to add an emergency extent, otherwise you'll find yourself dug in so deep you can't dig out. 2. You will find it a convenience to make it two 6gb halves. That way you can move it around with the server up. Also you can move from your present configuration with the server up - trim down to six 1gb pieces, add your first new 6gb chunk, delete the six old 1gb pieces, and now add the second 6gb extent. All without ever bringing the server down. It is OK to put the two 6gb extents on the same physical volume. (Best if adjacent to one another.) The log is write-mostly, and it is written sequentially. It will fill up one half and then start writing the second. Therefore there is no penalty to splitting it even on the save PV, and also there is little advantage to splitting it across two different PVs. The log has a COMPLETELY different I/O model than the database. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] "Have you ever, like, tried to put together a bicycle in public? Or a grill?" Astronauts David Wolf and Piers Sellers, explaining the difficulties encountered in attaching equipment to the Space Station On Thu, 25 Mar 2004, Thach, Kevin G wrote: >It's not a requirement, I am just acting on IBM's recommendation to put >the log on a single volume for performance reasons. 2 would still be >better than the 8 I have now. > >Thanks! > >-Original Message- >From: Prather, Wanda [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 3:01 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >I believe you are correct. >But why do you have a requirement to have only 1 log file? >The log is written sequentially, so I don't see that it would hurt you >to have two 6.5 GB logs, instead of one 13GB log... > >-Original Message- >From: Thach, Kevin G [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 2:57 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >That's what I do with my DB, but by defining the new log volume and >adding it, I will be over the 13GB limit until I've removed all the old >volumes. Will TSM let me do that? I guess I could try it and see. > >-Original Message- >From: Davidson, Becky [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 2:50 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >Define the new and add it and then delete the old. Don't forget to >mirror. > >-Original Message- >From: Thach, Kevin G [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 1:42 PM >To: [EMAIL PROTECTED] >Subject: Question about recovery log > > >I'm confused about how I should go about changing the configuration of >my recovery log. I'm hoping someone can point me in the right >direction. > >I currently have eight, 1GB log volumes, and I'm wanting to replace >these with a single 13GB volume. > >Normally, I would just create and define the new volume using the def >dbvol command, and then remove the old volumes, but since there is a >13GB limit on the recovery log, I can't do that. > >What's the best way for me to do this? Is there any way I can do it >with the server up and running? Switch to Normal mode, remove the old >volumes, create the new one, etc. I'm assuming that TSM will not allow >me to completely get rid of all my log volumes while the server is up >(even if in Normal mode), which is what I would have to do in order to >add the 13GB one. > > >Do I need to shut down the server, remove the old volumes and define the >new one with the dsmfmt -m -log command? > >I'm running TSM 5.1.7.3 on AIX 5.1 > >Thanks! >
total storage ultrium autoloader
Hi All, We are planning to buy IBM 3581L23 200/400 LTO2 total storage ultrium autoloader. Our environment is not really huge, and we think that this tape would be sufficient for us. Our primary pool is disk and we would use this tape drive only for copy pool. Is there anything I should be worrying about this tape autoloader? Joe C.
Re: Question about recovery log
1. Never make it larger than 12GB! Someday, your log will fill up, and you've got to have room under the 13gb limit to be able to add an emergency extent, otherwise you'll find yourself dug in so deep you can't dig out. 2. You will find it a convenience to make it two 6gb halves. That way you can move it around with the server up. Also you can move from your present configuration with the server up - trim down to six 1gb pieces, add your first new 6gb chunk, delete the six old 1gb pieces, and now add the second 6gb extent. All without ever bringing the server down. It is OK to put the two 6gb extents on the same physical volume. (Best if adjacent to one another.) The log is write-mostly, and it is written sequentially. It will fill up one half and then start writing the second. Therefore there is no penalty to splitting it even on the save PV, and also there is little advantage to splitting it across two different PVs. The log has a COMPLETELY different I/O model than the database. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] "Have you ever, like, tried to put together a bicycle in public? Or a grill?" Astronauts David Wolf and Piers Sellers, explaining the difficulties encountered in attaching equipment to the Space Station On Thu, 25 Mar 2004, Thach, Kevin G wrote: >It's not a requirement, I am just acting on IBM's recommendation to put >the log on a single volume for performance reasons. 2 would still be >better than the 8 I have now. > >Thanks! > >-Original Message- >From: Prather, Wanda [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 3:01 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >I believe you are correct. >But why do you have a requirement to have only 1 log file? >The log is written sequentially, so I don't see that it would hurt you >to have two 6.5 GB logs, instead of one 13GB log... > >-Original Message- >From: Thach, Kevin G [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 2:57 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >That's what I do with my DB, but by defining the new log volume and >adding it, I will be over the 13GB limit until I've removed all the old >volumes. Will TSM let me do that? I guess I could try it and see. > >-Original Message- >From: Davidson, Becky [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 2:50 PM >To: [EMAIL PROTECTED] >Subject: Re: Question about recovery log > > >Define the new and add it and then delete the old. Don't forget to >mirror. > >-Original Message- >From: Thach, Kevin G [mailto:[EMAIL PROTECTED] >Sent: Thursday, March 25, 2004 1:42 PM >To: [EMAIL PROTECTED] >Subject: Question about recovery log > > >I'm confused about how I should go about changing the configuration of >my recovery log. I'm hoping someone can point me in the right >direction. > >I currently have eight, 1GB log volumes, and I'm wanting to replace >these with a single 13GB volume. > >Normally, I would just create and define the new volume using the def >dbvol command, and then remove the old volumes, but since there is a >13GB limit on the recovery log, I can't do that. > >What's the best way for me to do this? Is there any way I can do it >with the server up and running? Switch to Normal mode, remove the old >volumes, create the new one, etc. I'm assuming that TSM will not allow >me to completely get rid of all my log volumes while the server is up >(even if in Normal mode), which is what I would have to do in order to >add the 13GB one. > > >Do I need to shut down the server, remove the old volumes and define the >new one with the dsmfmt -m -log command? > >I'm running TSM 5.1.7.3 on AIX 5.1 > >Thanks! >
Element addresses for new scsi LTO drive
Hey all, I noticed that others of the list seem to have similar element address problems but I didnt see my solution so I was hoping to throw this one out and see what sticks. I just added a new LTO (ver1) drive to our Scalar 100 Library. I used lbtest and can see the element address reported by the new drive is 258 (the 2 previous drives are 256 and 257). When I try to move the media to the 258 address or define the new drive to tsm I receive an error. hal> lsdev -Cc tape rmt0 Available 2A-09-00-3,0 LTO Ultrium Tape Drive rmt1 Available 2A-09-00-4,0 LTO Ultrium Tape Drive rmt2 Available 2A-09-00-2,0 LTO Ultrium Tape Drive <-- new drive enter selection: 8 Library Element Count: compcode = 0 number of drives = 3 number of storage slots= 42 number of transport elem = 1 number of entry exit ports = 12 analyze rc 0 err 0 (Successful,Error 0) cc 0 (Successful) resid 0 data 0 Total elapsed time in seconds = 3.00 Library Inventory: Drive 1 (address 256 EMPTY) abnormal_state = 0, accessible = 1, scsi_bus_not_pres = 0, scsi_bus_id_flag = 1, scsi_bus_id = 3, lun_flag = 0, lun = 0, source_addr_flag = 0, source_elem_addr = 0, invert_media_flag = 0, barcode_flag = 1, barcode_len = 36 Drive 2 (address 257 EMPTY) abnormal_state = 0, accessible = 1, scsi_bus_not_pres = 0, scsi_bus_id_flag = 1, scsi_bus_id = 4, lun_flag = 0, lun = 0, source_addr_flag = 0, source_elem_addr = 0, invert_media_flag = 0, barcode_flag = 1, barcode_len = 36 Drive 3 (address 258 EMPTY) abnormal_state = 0, accessible = 1, scsi_bus_not_pres = 0, scsi_bus_id_flag = 1, scsi_bus_id = 2, lun_flag = 0, lun = 0, source_addr_flag = 0, source_elem_addr = 0, invert_media_flag = 0, barcode_flag = 1, barcode_len = 36 enter selection: 11 transport element address: 1 source address moving from: 11 destination address moving to: 258 invert option: (1) invert (0) not invert: execute move_medium taddr = 1 saddr = 11 daddr = 258 invert = 0 analyze rc -1 err 22 (EINVAL,Invalid argument) cc 0 (Successful) resid 0 data 0 error_state last_status 22 (EINVAL) last_compcode 207 (DD_ILLEGAL_REQUEST) information 0 number_sense 18 Sense KEY/ASC/ASCQ = 5/21/ 1 KEY meaning is illegal request ASC/ASCQ meaning is invalid element address sense bytes 000-015: 70 0 5 0 0 0 0 a 0 0 0 0 21 1 0 c0 sense bytes 016-031: 0 4 analyze return_error cc 207 (DD_ILLEGAL_REQUEST) analyze conclusion ... ERROR not as expected ERROR, test failed! Total elapsed time in seconds = 7.00 Return to continue: tsm: TSM>define drive autolib drive1 online=yes element=258 cleanfreq=asneeded ANR8366E DEFINE DRIVE: Invalid value for ELEMENT parameter. ANS8001I Return code 3. Any help is appreciated. Rick.
Re: DB2 and TSM
The "Agent" for DB2 is built in to DB2. Look at the DB2 command BACKUP for the parameter "USE TSM" Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. "Gill, Geoffrey L." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 11:08 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:DB2 and TSM Please forgive my ignorance on this but someone is looking to add a server to TSM for backups and wants to know if TSM has an agent for DB2. From what I can tell there is no agent out there on the FTP site. I'm wondering if IBM has functionality built in to the product to back up the DB direct to TSM without shutting it down or if there is some other way to back up this DB. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
Re: Bare metal restore, ASR etc.
TSM_User <[EMAIL PROTECTED]> wrote: "ASR is only available on Win2003 not on other versions of windows." This is not true. ASR is available on both Windows XP and Windows 2003. Regards, Mike Dile Tivoli Storage Manager Client Development Tivoli Software, IBM Software Group [EMAIL PROTECTED]
Re: DB2 and TSM
Geoff, Try checking the IBM web site at http://www.ibm.com. In the search box at the top of the page even simple criteria like +tsm +db2 will yield fruitful results. (There a lot of hits, but you should find something pertinent in the top 2 hits!) Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Gill, Geoffrey L." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 10:08 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject DB2 and TSM Please forgive my ignorance on this but someone is looking to add a server to TSM for backups and wants to know if TSM has an agent for DB2. From what I can tell there is no agent out there on the FTP site. I'm wondering if IBM has functionality built in to the product to back up the DB direct to TSM without shutting it down or if there is some other way to back up this DB. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
DB2 and TSM
Please forgive my ignorance on this but someone is looking to add a server to TSM for backups and wants to know if TSM has an agent for DB2. From what I can tell there is no agent out there on the FTP site. I'm wondering if IBM has functionality built in to the product to back up the DB direct to TSM without shutting it down or if there is some other way to back up this DB. Thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
Re: define script problem
But Wanda, that takes all the fun out of it! :-) It is a good alternative, though. Just one caveat: the file has to reside on the TSM server machine, not the local machine from which you are running the admin client. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 09:53 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: define script problem This stuff will make you crazy. Give up your pain!!! Use notepad (or vi, or whatever) to create your script in a flat file. Type the SELECT just as you would from the command line, no worry about extra quotes. Then DEFINE SCRIPT VAULTING desc="Create Vault Lists" file=\pathname\filename -Original Message- From: Smith, Rachel [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 10:03 AM To: [EMAIL PROTECTED] Subject: define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: define script problem
This stuff will make you crazy. Give up your pain!!! Use notepad (or vi, or whatever) to create your script in a flat file. Type the SELECT just as you would from the command line, no worry about extra quotes. Then DEFINE SCRIPT VAULTING desc="Create Vault Lists" file=\pathname\filename -Original Message- From: Smith, Rachel [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 10:03 AM To: [EMAIL PROTECTED] Subject: define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Although your cache hit pct is great, the most obvious thing I see is that you just have ONE physical volume for this size DB! Spreading this size DB out over multiple volumes will probably increase your performance. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 03/25/04 03:38PM >>> Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke "Stapleton, Mark" wrote: > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Luke Dahl > >We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last > >week. Prior to the upgrade our expiration usually lasted about 24 > hours > >(53Gb database). It would generally post results like this: examined > >16446439 objects, deleting 59582 backup objects > >Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. > >util. > > What is your db's cache hit ratio? 24 hours for a 53GB database is > manifestly too long. It should get through expiration in 2-3 hours. Give > us the output from Q DB F=D. > > >Any idea why expiration wasn't running properly prior to the upgrade? > >Data integrity looks good but we've just cleared out loads of space. I > >don't recall a known bug in expiration processing in 5.1.6.4 but may > >have missed something. Thanks for your thoughts and input. > > How, exactly, did you "clear out loads of space"? > > -- > Mark Stapleton ## 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. ##
TSM on-line backup
Hi, I have Oracle 9.2 databases on RedHat Linux 7.3 and want made on-line (hot) backup them on TSM server. What is release TSM server and backup-archive client supported on-line backup? May be another advices anybody give me? Thanks much.
Re: define script problem
How about single quotes on the outside and "as" after volume_name. At 03:02 PM 3/26/2004 +, you wrote: Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again. Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: question about share library
Yep. (B (BIf it is a SCSI library, you can set up library sharing so that 1 TSM server (Bis the library "master", and the other is a library "client". The "master" (Bis the traffic cop and does all the mounts and drive sharing. (B (BIf it is a 3583, 3584, or 3494 library you can also logically partition the (Blibrary so that the TSM servers share the slots and the robot arm, but each (BTSM server has dedicated drives. (B (BThere are several more combinations/permutations of ways to share, depending (Bon your hardware/software. (B (BLots of ways to skin this cat; we need more information about your (Bconfiguration and situation to give more specific info. (B (BWanda Prather (B"I/O, I/O, It's all about I/O" -(me) (B (B (B (B (B-Original Message- (BFrom: fenglimian [mailto:[EMAIL PROTECTED] (BSent: Friday, March 26, 2004 4:13 PM (BTo: [EMAIL PROTECTED] (BSubject: question about share library (B (B (BHi all $B!$ (Jcan more than one TSM servers share a library $B!) (J (BThanks $B!* (J
Re: Help with brbackup
check if "backint -p initB01.ult -f inquire" works. If that works, the the utl-file should be fine. Then the problem can be in initB01.sap. In there you should have an entry like "util_par_file = /oracle/B01/920_64/dbs/initB01.utl" Jeroen -Original Message- From: Richard van Denzel [mailto:[EMAIL PROTECTED] Sent: vrijdag 26 maart 2004 16:35 To: [EMAIL PROTECTED] Subject: Help with brbackup Hi All, I've installed TDP for ERP on AIX 5.1 (2 SAP servers) and on both servers I run into the same problem when I try to specify the Parameter file within SAPDBA. When I enter the filename initB01.utl, SAPDBA keep comming up with the following message: SAPDBA: Error in brbackup profile/ expected '=', but read 'B01___' On the other server it gives me the exact same error but then for Oracle SID L02. I'm starting the sapdba from the b01adm (or l02adm) account on the server in question. Has anyone got a clue to what is going wrong or did I miss out something during the configuration? Regards, Richard.
Re: 9840 vs 9940 Performance
You are right about the 9840's; they are just screaming fast; I like them even better than 3590's for TSM for that reason. Also incredibly robust. We had some 9840's that we ran days on end, 20 hours a day, doing enormous amounts of reclaims (read LOTS of start/stop activity), with no drive or I/O errors. We had to give them up because, as you said, the cartridges are only 20 GB native, and we outgrew our (non-expandable) 9710 robot before the 9840C became available. I've never used the 9940's, but if you dig around the web site, STK clearly says that the 9840's are performance and the 9940's are for capacity. I asked our CE at the time, and he said there is no real difference in the 9940 drive mechanics, it should be as reliable as the 9840. BUT, the big difference is that the 9840 is a 2-reel cartridge that loads from the middle; and that is one big reason it is so spritely. The 9940 is a single-reel cartridge, loads from the end. So I don't believe it is physically possible to maintain the same performance on small file restores. That being said, the only cartridges I am aware of that have the middle load point are the 9840 and the old Magster 3570 (no longer marketed). The LTO standard called for a fast, 2 reel LTO Accelis cartridge to be built for speed as well as the Utrium cartridge that was built for capacity; but the last time I checked the LTO web site it said that the LTO Ultrium as worked so well that no vendor is ever going to build an Accelis drive. And I don't know that the 9940 wouldn't still give you adequate performance, just offering some points for you to consider. I would call and ask your local STK office to provide you with some stats for the 9940 vs. the 9840C, I'm sure they'll be HAPPY to comply. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: John Benik [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 9:33 AM To: [EMAIL PROTECTED] Subject: Re: 9840 vs 9940 Performance I'd be interested in seeing this also, we are looking at 9940's as well. You may want to look at the 9840C cartridges which have a lot more capacity, and will allow you to keep the same drives... John Benik Blue Cross Blue Shield of Minnesota Storage Administration and Performance W. (651)-662-4955 P. (651)-610-5080 "Frost, Dave" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 04:23 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject 9840 vs 9940 Performance Hello all, Does anybody have any experience with TSM performance of STK 9940's ? We are running 9840's with colocation and have found the performance for large restores of a small file nature to be very good. The only problem with 9840 is the 20GB limitation. I know that large servers will span multiple tapes and the multi-thread restore works exceptionally well with this. The only problem is that with growing data quantities, an L700 fills up very quickly. Using 9940's would triple the capacity of an L700. But we need to ensure we would maintain the performance that we are seeing on the 9840's. I understand that a 9940 is going to be a physically longer tape and as such certain stats are not comparable to the 9840. But does the repositioning and backhitching that is so evident with a large TSM restore compare to that of a 9840. -=Leigh=-
Re: Antwort: define script problem
Ah, OK. Now that makes sense. Thanks for confirming that I'm not not nuts (at least not because of this!) Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:59 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem I ran it with single quotes around MOUNTABLE: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state='MOUNTABLE' order by volume_name" desc="Create vaulting lists" ANR1462I RUN: Command script VAULTING completed successfully. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:49 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem While I agree that it is difficult to argue with success, I don't see how the script could possibly run as written below. You had to have changed something else. Here are the results if you run the script as written (I simply copy & pasted it into the admin command line): tsm: SS2_ADSM_GROUP_SERVER>DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" ANR2023E DEFINE SCRIPT: Extraneous parameter - MOUNTABLE. ANS8001I Return code 3. tsm: SS2_ADSM_GROUP_SERVER> SQL doesn't like double quotes around MOUNTABLE; string comparisons must be done with single quotes. Would you mind showing me the output from QUERY SCRIPT VAULTING? And if it is defined with double quotes around MOUNTABLE, can I see the output from RUN VAULTING? Not trying to be argumentative, but simply trying to understand how it can work as written. Thanks, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:29 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem I changed the name for vol_to_go... and ran successfully with no errors. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem The script may get defined, but it probably won't run. See my other post on this subject. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:22 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Antwort: define script problem
I ran it with single quotes around MOUNTABLE: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state='MOUNTABLE' order by volume_name" desc="Create vaulting lists" ANR1462I RUN: Command script VAULTING completed successfully. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:49 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem While I agree that it is difficult to argue with success, I don't see how the script could possibly run as written below. You had to have changed something else. Here are the results if you run the script as written (I simply copy & pasted it into the admin command line): tsm: SS2_ADSM_GROUP_SERVER>DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" ANR2023E DEFINE SCRIPT: Extraneous parameter - MOUNTABLE. ANS8001I Return code 3. tsm: SS2_ADSM_GROUP_SERVER> SQL doesn't like double quotes around MOUNTABLE; string comparisons must be done with single quotes. Would you mind showing me the output from QUERY SCRIPT VAULTING? And if it is defined with double quotes around MOUNTABLE, can I see the output from RUN VAULTING? Not trying to be argumentative, but simply trying to understand how it can work as written. Thanks, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:29 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem I changed the name for vol_to_go... and ran successfully with no errors. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem The script may get defined, but it probably won't run. See my other post on this subject. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:22 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Antwort: define script problem
Hi Christian, I am curious as to why a column name longer than 18 characters presents a problem? You can simply put it in quotes, as I showed in a previous response on this subject. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Christian Demnitz <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:19 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
AW: TDP for Oracle
On Windows I use: DSMC QUERY BACKUP -SUBDIR=YES -NODE=xx {\adsmorc}*
On UNIX:DSMC QUERY BACKUP "/adsmorc/*" -SUBDIR=YES -VIRTUALN=xx
You have to replace \adsmorc with the name of your TDPO filespace.
Thomas Rupp
-Ursprüngliche Nachricht-
Von: Frank Scolieri [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 26. März 2004 16:54
An: [EMAIL PROTECTED]
Betreff: TDP for Oracle
Is there a way to query all files backed up through TDP for Oracle?
Thanks
TDP for Oracle
Is there a way to query all files backed up through TDP for Oracle? Thanks
Re: Antwort: define script problem
While I agree that it is difficult to argue with success, I don't see how the script could possibly run as written below. You had to have changed something else. Here are the results if you run the script as written (I simply copy & pasted it into the admin command line): tsm: SS2_ADSM_GROUP_SERVER>DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" ANR2023E DEFINE SCRIPT: Extraneous parameter - MOUNTABLE. ANS8001I Return code 3. tsm: SS2_ADSM_GROUP_SERVER> SQL doesn't like double quotes around MOUNTABLE; string comparisons must be done with single quotes. Would you mind showing me the output from QUERY SCRIPT VAULTING? And if it is defined with double quotes around MOUNTABLE, can I see the output from RUN VAULTING? Not trying to be argumentative, but simply trying to understand how it can work as written. Thanks, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:29 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem I changed the name for vol_to_go... and ran successfully with no errors. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem The script may get defined, but it probably won't run. See my other post on this subject. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:22 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: DRM question !
When you run DRM PREPARE, it creates a file with recovery instructions to help you rebuild your TSM server (presumably at a new location). DRM also gives you the opportunity to create your OWN files containing instructions that YOU write explaining how to restore your other machines (presumably the ones you would care most about rebuildling in a disaster). I believe the idea is that this way, when you get to your "hot site" and recover your TSM server, you know that you have a copy of your other instructions as well. This message is referring to one of those files. If you read the chapter in the admin guide on using DRM, there is information about setting this stuff up; it is not required (and it presumes that the TSM admin knows everything that you need to know to get your other applications up and running, or can get that info from other people AND keep it up to date.) If you don't want to do it, you can: 1) ignore the message 2) create a file by that name 3) look in the admin guide for the commands to delete the filename. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -Original Message- From: goran [mailto:[EMAIL PROTECTED] Sent: Friday, March 26, 2004 10:32 AM To: [EMAIL PROTECTED] Subject: DRM question ! hi all, i got this message on PREPARE command : ANR6918W PREPARE: Recovery instructions file /usr/tivoli/tsm/server/backup/instr_plan.RECOVERY.IN- STRUCTIONS.DATABASE not found . . . in messages stands : ANR6918W Command: Recovery instructions file file name not found. Explanation: A source file for recovery instructions was not found. System Action: The recovery plan will not contain recovery instructions. User Response: To get recovery instructions in the recovery plan, ensure the corresponding instructions source file exists. If it does, check authorizations to the file. Q: what source file ? thanks. # # goran konjich # senior unix systems admin # vipnet # env: pSeries 640 SSA Disk Subsystem LTO3584 2109 FC
Help with brbackup
Hi All, I've installed TDP for ERP on AIX 5.1 (2 SAP servers) and on both servers I run into the same problem when I try to specify the Parameter file within SAPDBA. When I enter the filename initB01.utl, SAPDBA keep comming up with the following message: SAPDBA: Error in brbackup profile/ expected '=', but read 'B01___' On the other server it gives me the exact same error but then for Oracle SID L02. I'm starting the sapdba from the b01adm (or l02adm) account on the server in question. Has anyone got a clue to what is going wrong or did I miss out something during the configuration? Regards, Richard.
AW: define script problem
Hi, you are on the right path, it has to do with parameters parsing, an issue common to all command line interpreteres, including tsm command line. You DEFINE SCRIPT command is interpreted as follows: parameter1=VAULTING parameter2=select volume_name Why it end here? It is a string defined by pair of quotes. parameter3=Volumes parameter4=to etc. etc. Solution: Tell the (dsmadmc) interpreter not to interpret some quotes, e.g. those two: "Volumes to go offsite" but to accept them as characters. How to do it? While many common shells accept an special character for it, e.g. backslash: "select volume_name \"Volumes to go offsite\", voltype as \"Volume Type\" from drmedia where state=\"MOUNTABLE \" order by volume_name" would be in many shells interpreted like that (numbers mean character number #) : 1 " opening quote, defines begining of a string, thus any space characters found within will NOT be interpreted as delimiter 2 scommon character, pass it further as (a part of a ) string 3 ecommon character, pass it further as (a part of a ) string 4 lcommon character, pass it further as (a part of a ) string 5 ecommon character, pass it further as (a part of a ) string 6 ccommon character, pass it further as (a part of a ) string 7 tcommon character, pass it further as (a part of a ) string 8 [space] normall parameter delimiter, but because quoted it is common character, pass it further as (a part of a ) string 9 vcommon character, pass it further as (a part of a ) string 10 ocommon character, pass it further as (a part of a ) string ... etc. etc. 21 \backlash means: not to interpret the following character but accept it as a common character 22 "because of above, do not interpret as quote, only pass it further as (a part of a ) string 23 Vcommon character, pass it further as (a part of a ) string 24 ocommon character, pass it further as (a part of a ) string 25 lcommon character, pass it further as (a part of a ) string etc. etc. 115 common character, pass it further as (a part of a ) string 116 " closing qoute, end of quoted string 117 [space] parameter delimiter, thus the above´s string is to be understodd as end of one parameter BUT I am afraid backslash does not work this way in dsmadmc interpreter, so you are to use quoting of quotes instead: "select volume_name """Volumes to go offsite""", voltype as """Volume Type""" from drmedia where state="""MOUNTABLE """ order by volume_name" Wait - I always have doubts about proper count of """ quotes, While I guess I made a proper suggestion for this case, play around, maybe " is to be used here instead :-))) hope I was not annoying Juraj -Ursprüngliche Nachricht- Von: Smith, Rachel [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 26. März 2004 16:03 An: [EMAIL PROTECTED] Betreff: define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
DRM question !
hi all, i got this message on PREPARE command : ANR6918W PREPARE: Recovery instructions file /usr/tivoli/tsm/server/backup/instr_plan.RECOVERY.IN- STRUCTIONS.DATABASE not found . . . in messages stands : ANR6918W Command: Recovery instructions file file name not found. Explanation: A source file for recovery instructions was not found. System Action: The recovery plan will not contain recovery instructions. User Response: To get recovery instructions in the recovery plan, ensure the corresponding instructions source file exists. If it does, check authorizations to the file. Q: what source file ? thanks. # # goran konjich # senior unix systems admin # vipnet # env: pSeries 640 SSA Disk Subsystem LTO3584 2109 FC
Re: Antwort: define script problem
I changed the name for vol_to_go... and ran successfully with no errors. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Andrew Raibeck Sent: 26 March 2004 15:27 To: [EMAIL PROTECTED] Subject: Re: Antwort: define script problem The script may get defined, but it probably won't run. See my other post on this subject. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:22 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Antwort: define script problem
The script may get defined, but it probably won't run. See my other post on this subject. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Smith, Rachel" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:22 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Antwort: define script problem that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Antwort: define script problem
Correct, but the embedded quotes also makes this a bit tricky. Note that the string comparison in the WHERE clause requires single quotes around MOUNTABLE. So how about this: define script vaulting "select volume_name as ""Volumes to go offsite"", voltype as ""Volume Type"" from drmedia where state='MOUNTABLE' order by volume_name" desc="Create vault lists" Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Christian Demnitz <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 08:12 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Antwort: define script problem Hi, i think you' forgot the "as" between volume_name and "volumes to go Offsite" DEFINE SCRIPT VAULTING "select volume_name as "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Antwort: define script problem
that worked, thanks for that:> -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Christian Demnitz Sent: 26 March 2004 15:19 To: [EMAIL PROTECTED] Subject: Antwort: define script problem sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Antwort: define script problem
sorry my first answer was wrong!!! please try: DEFINE SCRIPT VAULTING "select volume_name as Vol_to_go_offsite, voltype as Volume_Type from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" the only restriction is: the name for vol_to_go... should not longer than 18 characters! it will work fine Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Retaining Deleted files
I do not quite understand your specification. The user wishes to keep up to 6 months worth of transaction files on disk. But this does not necessarily map to a restore requirement. For example, the user might wish to keep 6 months worth of transaction files on disk, but may also wish to be able to *restore* transaction files up to 12 months ago. So a better understanding of the restore requirements is necessary. Without understanding the nature of the transaction files (when they are created, how often they are changed, etc.) It is difficult to assess the usefulness of your given copy group definition. What I can tell you is this: If the file is created once and never touched again, then TSM will keep one backup copy forever (due to NOLIMIT settings). If the file changes once, TSM will make a second backup copy, and keep both backup versions forever. If the file changes daily, then TSM will keep a maximum of two backup versions of each file. The oldest backup version will expire when the backup version is made. If the file stops changing (or is deleted) so TSM makes no new backup copies, then the existing versions will be kept forever. If the user requires a restore capability of up to 6 months ago, then the following criteria is suggested: VEREXISTS=NOLIMIT VERDELETED=NOLIMIT RETEXTRA=190 RETONLY=190 If the user needs to keep everything forever (a requirement whose needs should be thoroughly investigated and confirmed) then you can specify: VEREXISTS=NOLIMIT VERDELETED=NOLIMIT RETEXTRA=NOLIMIT RETONLY=NOLIMIT These are just some examples. As I mentioned above, without a more comprehensive description of the restore needs and the file usage pattern, it is difficult to develop the TSM management criteria. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Yiannakis Vakis <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 02:15 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Retaining Deleted files Hi, I have the following situation and I need a confirmation here. System information is : TSM 5.2. on Windows 2000, TSM BA client 5.2. on Windows 2000. I'm backing up a folder with the "incremental" option, that contains a complex subfolder tree. The contents of the subfolders are mainly transaction files from various applications. The user wants to keep the transaction files for 6 months on disk and then deletes the older ones (the 6th month) to make space for the new month. This is a user task and here I don't have any involvement. The user doesn't want to lose the deleted transaction files, because he might want to restore something for investigation reasons. I have set up a special policy for this. The backup copygroup definition is as follows: Policy Domain Name TSM_DOMAIN Policy Set Name ACTIVE Mgmt Class Name TSM_MGMT_CLASS Copy Group Name STANDARD Versions Data Exists2 Versions Data Deleted 2 Retain Extra Versions NOLIMIT Retain Only Version NOLIMIT Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy Destination3590STGPOOL Table of Contents (TOC) Destination - Last Update Date/Time 2004-03-12 12:37:03.00 Last Update by (administrator) YIANNAKIS Managing profile- I have specified NOLIMIT on retain extra versions and retain only version so that I don't lose the deleted files. Is that correct ? Thanks Yiannakis
Antwort: define script problem
Hi, i think you' forgot the "as" between volume_name and "volumes to go Offsite" DEFINE SCRIPT VAULTING "select volume_name as "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" Christian Demnitz mailto:[EMAIL PROTECTED] "Smith, Rachel" <[EMAIL PROTECTED]> Gesendet von: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 26.03.2004 16:02 Bitte antworten an "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> An [EMAIL PROTECTED] Kopie Thema define script problem Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
define script problem
Hi, I am trying to create a script that will produce a list of media to send offsite. I defined a script: DEFINE SCRIPT VAULTING "select volume_name "Volumes to go offsite", voltype as "Volume Type" from drmedia where state="MOUNTABLE " order by volume_name" desc="Create vault lists" And it fails with: ANR2023E DEFINE SCRIPT: Extraneous parameter I know it is something to do with the double quotes, but I also tried single quotes but it failed with the same error. Could someone tell me what I'm missing. Thanks again.
Re: Windows Backup and mixed case filenames
There was also some discussion in the autumn of last year. Searching the adsm-l archives at http://search.adsm.org or http://my.adsm.org/adsm-l.php with the following criteria: +ntfs +posix will yield some pertinent information. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 07:44 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Re: Windows Backup and mixed case filenames ... >So, my question is: is there a way to backup NTFS where some filenames >differ only in uppercase/lowercase? Maybe a newer version of the client? This issue was extensively discussed some six weeks ago. Please check the List archives for such issues.
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
>Just because I'm currently trying to boost expiration processing: I see your >database is rather large, how long did it take you to expire those 23194393 >objects? >I really tried almost everything, from moving to 15k speed disks, multiple >database volumes, moving to RAW's, the best I have seen in my environment is >60 objects per second. ... In the context of this discussion, the following doc makes some interesting observations on disk performance and expectations: http://www.ibm.com/support/docview.wss?uid=swg21141810 Richard Simshttp://people.bu.edu/rbs
Re: Windows Backup and mixed case filenames
Although the NTFS file system technically permits case-sensitive file names, the Windows operating system provides insufficient mechanisms for applications to distinguish between files whose names differ in casing only. As you have noticed, even the operating system facilities that come with Windows have difficulty with these kinds of files. For similar reasons, TSM is unable to manage all files whose names differ only in case. Take a look at the most current client level (5.2.2.0 and up). The README file includes documentation on the new CASESENSITIVEAWARE option. This option does not allow TSM to manage all files whose names differ in case only, but it does make TSM "tolerate" the situation better. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Rainer Schöpf <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 07:35 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Windows Backup and mixed case filenames Hello all, we have an IBM NAS 100 Box (a W2K based server appliance) running Services for Unix 2.2 to provide NFS service for our Linux workstations. An NFS client can create two files in the same directory whose names differ only in case, eg. "makefile" and "Makefile". The NTFS on the NAS 100 can handle that. On the Windows side, I see both files, but have some problems accessing both of them: irregardless of upper/lowercase, I usually can only access the contents of one file. No surprise so far (except that the NT file replication service replicates only one file) However, it seems that the same is true for TSM: it backs up only one of these two files. I looked through the options for the TSM client, but could not find anything relevant to the problem. So, my question is: is there a way to backup NTFS where some filenames differ only in uppercase/lowercase? Maybe a newer version of the client? TSM client version: 4.2.1.20 on W2K TSM server version: 5.2.2.0 on W2K Rainer Schöpf ProteoSys AG Carl-Zeiss-Straße 51 55129 Mainz Dr. Rainer Schöpf Leiter Software/Softwareentwicklung Mail: [EMAIL PROTECTED] Phone: +49-(0)6131-50192-41 Fax:+49-(0)6131-50192-11 WWW:http://www.proteosys.com/
Re: Windows Backup and mixed case filenames
... >So, my question is: is there a way to backup NTFS where some filenames >differ only in uppercase/lowercase? Maybe a newer version of the client? This issue was extensively discussed some six weeks ago. Please check the List archives for such issues.
Windows Backup and mixed case filenames
Hello all, we have an IBM NAS 100 Box (a W2K based server appliance) running Services for Unix 2.2 to provide NFS service for our Linux workstations. An NFS client can create two files in the same directory whose names differ only in case, eg. "makefile" and "Makefile". The NTFS on the NAS 100 can handle that. On the Windows side, I see both files, but have some problems accessing both of them: irregardless of upper/lowercase, I usually can only access the contents of one file. No surprise so far (except that the NT file replication service replicates only one file) However, it seems that the same is true for TSM: it backs up only one of these two files. I looked through the options for the TSM client, but could not find anything relevant to the problem. So, my question is: is there a way to backup NTFS where some filenames differ only in uppercase/lowercase? Maybe a newer version of the client? TSM client version: 4.2.1.20 on W2K TSM server version: 5.2.2.0 on W2K Rainer Schöpf ProteoSys AG Carl-Zeiss-Straße 51 55129 Mainz Dr. Rainer Schöpf Leiter Software/Softwareentwicklung Mail: [EMAIL PROTECTED] Phone: +49-(0)6131-50192-41 Fax:+49-(0)6131-50192-11 WWW:http://www.proteosys.com/
Re: 9840 vs 9940 Performance
I'd be interested in seeing this also, we are looking at 9940's as well. You may want to look at the 9840C cartridges which have a lot more capacity, and will allow you to keep the same drives... John Benik Blue Cross Blue Shield of Minnesota Storage Administration and Performance W. (651)-662-4955 P. (651)-610-5080 "Frost, Dave" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/26/2004 04:23 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject 9840 vs 9940 Performance Hello all, Does anybody have any experience with TSM performance of STK 9940's ? We are running 9840's with colocation and have found the performance for large restores of a small file nature to be very good. The only problem with 9840 is the 20GB limitation. I know that large servers will span multiple tapes and the multi-thread restore works exceptionally well with this. The only problem is that with growing data quantities, an L700 fills up very quickly. Using 9940's would triple the capacity of an L700. But we need to ensure we would maintain the performance that we are seeing on the 9840's. I understand that a 9940 is going to be a physically longer tape and as such certain stats are not comparable to the 9840. But does the repositioning and backhitching that is so evident with a large TSM restore compare to that of a 9840. -=Leigh=-
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Eric, From our activity log: 03/20/04 06:00:07 ANR0811I Inventory client file expiration started as proc cess 26. (SESSION: 5656, PROCESS: 26) 03/25/04 17:24:44 ANR0812I Inventory file expiration process 26 completed: examined 23979559 objects, deleting 21479290 backup obj jects, 0 archive objects, 0 DB backup volumes, and 0 rec covery plan files. 1 errors were encountered. (SESSION: 5656, PROCESS: 26) 03/25/04 17:24:44 ANR0987I Process 26 for EXPIRE INVENTORY running in the B BACKGROUND processed 21479290 items with a completion st tate of FAILURE at 17:24:44. (SESSION: 5656, PROCESS: 26) We've seen much better *overall* performance after moving to raw volumes, but nowhere near what we saw on two very old AIX boxes. We're running a Sun 420R with three cpu's. Load averages nightly peak around 20. We're moving to two Sun V480's with two cpu's to start. We haven't run expiration yet again but I'm hoping it doesn't take nearly as long. I'm still confused as to why after the upgrade we're seeing this. If it's significantly different the next time around I'll report to the list with my findings. Good luck! Luke "Loon, E.J. van - SPLXM" wrote: > Hi Luke! > Just because I'm currently trying to boost expiration processing: I see your > database is rather large, how long did it take you to expire those 23194393 > objects? > I really tried almost everything, from moving to 15k speed disks, multiple > database volumes, moving to RAW's, the best I have seen in my environment is > 60 objects per second. > I posted a question some time ago (2002) where I requested for other > people's performances, Tom Kauffman was the winner at that time with a > dazzling 3112 objects per second! > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > -Original Message- > From: Luke Dahl [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 25, 2004 21:39 > To: [EMAIL PROTECTED] > Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 > > Hi Mark, > Output from q db f=d: > Available Space (MB): 118,780 > Assigned Capacity (MB): 70,000 > Maximum Extension (MB): 48,780 > Maximum Reduction (MB): 15,924 > Page Size (bytes): 4,096 > Total Usable Pages: 17,920,000 > Used Pages: 11,215,255 > Pct Util: 62.6 > Max. Pct Util: 77.3 > Physical Volumes: 1 > Buffer Pool Pages: 32,768 > Total Buffer Requests: 2,151,221,843 > Cache Hit Pct.: 99.04 >Cache Wait Pct.: 0.00 >Backup in Progress?: No > Type of Backup In Progress: > Incrementals Since Last Full: 0 > Changed Since Last Backup (MB): 2,785.80 > Percentage Changed: 6.36 > Last Complete Backup Date/Time: 03/24/04 17:33:13 > > This is the standard amount of expiration we see: > 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 > completed: >examined 23194393 objects, deleting 1690917 backup > objec >cts, 0 archive objects, 0 DB backup volumes, and 0 > recov >very plan files. 0 errors were encountered. > > This is currently running: > Process Process Description Status > s Number > > - > 26 Expiration Examined 22853888 objects, deleting 20518954 > bac >ckup objects, 0 archive objects, 0 DB backup > vo >olumes, 0 recovery plan files; 1 errors > encount >tered. > > I don't think the policies were correctly expiring data prior to the > upgrade. We've had numerous nodes that seemed to be storing much more than > their policy dictated. We tried to force expiration on the files and it > didn't seem to make much of a difference. Unfortunately we've been tweaking > policies and trying to force a lot of data to drop off prior to the upgrade > so I can't point to any particular reason why expiration is now expiring so > much data. You can see the db size has dropped as well due to the > expiration - and we performed an unload/reload less than a month ago prior > to the upgrade. Being the db volume is one volume it could be disk > contention, but it's a raw volume fiber attached (Sun T-3's). > > Luke > > "Stapleton, Mark" wrote: > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > > Luke Dahl > > >We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last > > >week. Prior to the upgrade our expiration usually lasted about 24 > > hours > > >(53Gb database). It would generally post results like this: examined > > >16446439 objects, deleting 59582 back
Re: question about share library
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of fenglimian >Hi all,can more than one TSM servers share a library? Yes. Refer to "Library sharing" in your TSM server administrator's guide. -- Mark Stapleton
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Sent this too fast... Must have hit the a wrong key... Not enough coffee yet I have 4 rather large tsm servers, db over 30 gb. 2 are AIX, 2 are sun. The performance on the 2 aix boxes is similar. One server is very old, installed in 97, db is 60 db, and goes through 12 million objects, deleting between 300,000 and 1 million objects. 3000 objects/sec examined, but between 70 and 100 deleted. Expiration lasts between 60 and 90 minutes. The other aix server is brand new. Db is 40 gb, moslty du to 2 imap servers whose backups are kept 180 days (OUCH!!). Expiration goes through 150,000 objects, deleting 100,000. 200 objects examined/sec, 150 deleted. The old server is a f80, the new one a p615, soon to be a p630. As for the SUN servers, performance is nowhere near as good. I can't get more than 40 objects/second, examined or deleted. I moved the database on raw volumes, didn't help much. I can't seem to get these servers to perform well. The 2 instances are on a 480 with 2 cpu's. Disks are the same as the AIX servers (HDS 9960). Is anyone getting good expiration performance on SUN servers. If so, how are you setup? Guillaume Gilbert Backup Administrator CGI - ITM (514) 415-3000 x5091 [EMAIL PROTECTED] > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Loon, E.J. van - SPLXM > Sent: Friday, March 26, 2004 8:23 AM > To: [EMAIL PROTECTED] > Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 > > > Hi Luke! > Just because I'm currently trying to boost expiration > processing: I see your > database is rather large, how long did it take you to expire > those 23194393 > objects? > I really tried almost everything, from moving to 15k speed > disks, multiple > database volumes, moving to RAW's, the best I have seen in my > environment is > 60 objects per second. > I posted a question some time ago (2002) where I requested for other > people's performances, Tom Kauffman was the winner at that time with a > dazzling 3112 objects per second! > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > > -Original Message- > From: Luke Dahl [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 25, 2004 21:39 > To: [EMAIL PROTECTED] > Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 > > > Hi Mark, > Output from q db f=d: > Available Space (MB): 118,780 > Assigned Capacity (MB): 70,000 > Maximum Extension (MB): 48,780 > Maximum Reduction (MB): 15,924 > Page Size (bytes): 4,096 > Total Usable Pages: 17,920,000 > Used Pages: 11,215,255 > Pct Util: 62.6 > Max. Pct Util: 77.3 > Physical Volumes: 1 > Buffer Pool Pages: 32,768 > Total Buffer Requests: 2,151,221,843 > Cache Hit Pct.: 99.04 >Cache Wait Pct.: 0.00 >Backup in Progress?: No > Type of Backup In Progress: > Incrementals Since Last Full: 0 > Changed Since Last Backup (MB): 2,785.80 > Percentage Changed: 6.36 > Last Complete Backup Date/Time: 03/24/04 17:33:13 > > This is the standard amount of expiration we see: > 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 > completed: >examined 23194393 objects, deleting > 1690917 backup > objec >cts, 0 archive objects, 0 DB backup > volumes, and 0 > recov >very plan files. 0 errors were encountered. > > This is currently running: > Process Process Description Status > s Number > > - > 26 Expiration Examined 22853888 objects, > deleting 20518954 > bac >ckup objects, 0 archive > objects, 0 DB backup > vo >olumes, 0 recovery plan files; 1 errors > encount >tered. > > I don't think the policies were correctly expiring data prior to the > upgrade. We've had numerous nodes that seemed to be storing > much more than > their policy dictated. We tried to force expiration on the > files and it > didn't seem to make much of a difference. Unfortunately > we've been tweaking > policies and trying to force a lot of data to drop off prior > to the upgrade > so I can't point to any particular reason why expiration is > now expiring so > much data. You can see the db size has dropped as well due to the > expiration - and we performed an unload/reload less than a > month ago prior > to the upgrade. Being the db volume is one volume it could be disk > contention, but it's a raw volume fiber attached (Sun T-3's). > > Luke > > "Stapleton, Mark" wrote: > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of > > Luke Dahl > > >We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to > 5.2.2.1 last > > >week.
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
I have 4 rather large tsm servers, db over 30 gb. 2 are AIX, 2 are sun. The performance on the 2 aix boxes is similar. One server is very old, installed in 97, db is 60 db, and goes through 12 million objects, deleting between 300,00 and 1 million objects. 3000 objects/sec examined, but between 70 and 100 deleted. Expiration lasts between 60 and 90 minutes. The other aix server is brand new. Db is 40 gb, moslty du to 2 imap servers whose backups are kept 180 days (OUCH!!). Expiration goes through 150,000 objects, deleting 100,000. 200 objects examined/sec, 150 deleted. The old server is a f80, the new one a p615, soon to be a p630. As for the SUN servers, performance is nowhere near as good. I can't get more than 40 objects/second, examined or deleted. I moved the database on raw volumes, didn't help much. I can,T seem to get these servers to perform well. The 2 instances are on a 480 with 2 cpu's. Disks are the same as the AIX Guillaume Gilbert Backup Administrator CGI - ITM (514) 415-3000 x5091 [EMAIL PROTECTED] > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Loon, E.J. van - SPLXM > Sent: Friday, March 26, 2004 8:23 AM > To: [EMAIL PROTECTED] > Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 > > > Hi Luke! > Just because I'm currently trying to boost expiration > processing: I see your > database is rather large, how long did it take you to expire > those 23194393 > objects? > I really tried almost everything, from moving to 15k speed > disks, multiple > database volumes, moving to RAW's, the best I have seen in my > environment is > 60 objects per second. > I posted a question some time ago (2002) where I requested for other > people's performances, Tom Kauffman was the winner at that time with a > dazzling 3112 objects per second! > Kindest regards, > Eric van Loon > KLM Royal Dutch Airlines > > > -Original Message- > From: Luke Dahl [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 25, 2004 21:39 > To: [EMAIL PROTECTED] > Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 > > > Hi Mark, > Output from q db f=d: > Available Space (MB): 118,780 > Assigned Capacity (MB): 70,000 > Maximum Extension (MB): 48,780 > Maximum Reduction (MB): 15,924 > Page Size (bytes): 4,096 > Total Usable Pages: 17,920,000 > Used Pages: 11,215,255 > Pct Util: 62.6 > Max. Pct Util: 77.3 > Physical Volumes: 1 > Buffer Pool Pages: 32,768 > Total Buffer Requests: 2,151,221,843 > Cache Hit Pct.: 99.04 >Cache Wait Pct.: 0.00 >Backup in Progress?: No > Type of Backup In Progress: > Incrementals Since Last Full: 0 > Changed Since Last Backup (MB): 2,785.80 > Percentage Changed: 6.36 > Last Complete Backup Date/Time: 03/24/04 17:33:13 > > This is the standard amount of expiration we see: > 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 > completed: >examined 23194393 objects, deleting > 1690917 backup > objec >cts, 0 archive objects, 0 DB backup > volumes, and 0 > recov >very plan files. 0 errors were encountered. > > This is currently running: > Process Process Description Status > s Number > > - > 26 Expiration Examined 22853888 objects, > deleting 20518954 > bac >ckup objects, 0 archive > objects, 0 DB backup > vo >olumes, 0 recovery plan files; 1 errors > encount >tered. > > I don't think the policies were correctly expiring data prior to the > upgrade. We've had numerous nodes that seemed to be storing > much more than > their policy dictated. We tried to force expiration on the > files and it > didn't seem to make much of a difference. Unfortunately > we've been tweaking > policies and trying to force a lot of data to drop off prior > to the upgrade > so I can't point to any particular reason why expiration is > now expiring so > much data. You can see the db size has dropped as well due to the > expiration - and we performed an unload/reload less than a > month ago prior > to the upgrade. Being the db volume is one volume it could be disk > contention, but it's a raw volume fiber attached (Sun T-3's). > > Luke > > "Stapleton, Mark" wrote: > > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of > > Luke Dahl > > >We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to > 5.2.2.1 last > > >week. Prior to the upgrade our expiration usually lasted about 24 > > hours > > >(53Gb database). It would generally post results like > this: examined > > >16446439 objects, deleting 59582
AW: Retaining Deleted files
yup, it will do. It will cause the tsm server grow NOLIMIT as well :-) Alternatively, you can offer incrementals to files keep 6 or 7 months only and do archives with deletefiles option for older files. this differntiates from the upper solution in that: - you would be responsible for deleting files, not the custommer (responsibility move, more service from you) - there would be 100% security that only files backed-up are deleted - TSM storage usage and media maintenance, redundancy etc. could be easily differentiated for young and old files - at later timer, you could delete portions of your customer?s archived files (in contrast to incremental where you only can delete backup of whole file system easily) - on the other side, only the very last version of files would be kept forever, not the last two - assumption: there is an easy way for you/tarchive sm to determine which files are to be considered to be over 6 months old regards Juraj -Ursprungliche Nachricht- Von: Yiannakis Vakis [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 26. Marz 2004 10:15 An: [EMAIL PROTECTED] Betreff: Retaining Deleted files Hi, I have the following situation and I need a confirmation here. System information is : TSM 5.2. on Windows 2000, TSM BA client 5.2. on Windows 2000. I'm backing up a folder with the "incremental" option, that contains a complex subfolder tree. The contents of the subfolders are mainly transaction files from various applications. The user wants to keep the transaction files for 6 months on disk and then deletes the older ones (the 6th month) to make space for the new month. This is a user task and here I don't have any involvement. The user doesn't want to lose the deleted transaction files, because he might want to restore something for investigation reasons. I have set up a special policy for this. The backup copygroup definition is as follows: Policy Domain Name TSM_DOMAIN Policy Set Name ACTIVE Mgmt Class Name TSM_MGMT_CLASS Copy Group Name STANDARD Versions Data Exists2 Versions Data Deleted 2 Retain Extra Versions NOLIMIT Retain Only Version NOLIMIT Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy Destination3590STGPOOL Table of Contents (TOC) Destination - Last Update Date/Time 2004-03-12 12:37:03.00 Last Update by (administrator) YIANNAKIS Managing profile- I have specified NOLIMIT on retain extra versions and retain only version so that I don't lose the deleted files. Is that correct ? Thanks Yiannakis
Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1
Hi Luke! Just because I'm currently trying to boost expiration processing: I see your database is rather large, how long did it take you to expire those 23194393 objects? I really tried almost everything, from moving to 15k speed disks, multiple database volumes, moving to RAW's, the best I have seen in my environment is 60 objects per second. I posted a question some time ago (2002) where I requested for other people's performances, Tom Kauffman was the winner at that time with a dazzling 3112 objects per second! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Luke Dahl [mailto:[EMAIL PROTECTED] Sent: Thursday, March 25, 2004 21:39 To: [EMAIL PROTECTED] Subject: Re: Expiration after TSM upgrade from 5.1.6.4 to 5.2.2.1 Hi Mark, Output from q db f=d: Available Space (MB): 118,780 Assigned Capacity (MB): 70,000 Maximum Extension (MB): 48,780 Maximum Reduction (MB): 15,924 Page Size (bytes): 4,096 Total Usable Pages: 17,920,000 Used Pages: 11,215,255 Pct Util: 62.6 Max. Pct Util: 77.3 Physical Volumes: 1 Buffer Pool Pages: 32,768 Total Buffer Requests: 2,151,221,843 Cache Hit Pct.: 99.04 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 2,785.80 Percentage Changed: 6.36 Last Complete Backup Date/Time: 03/24/04 17:33:13 This is the standard amount of expiration we see: 03/14/04 17:27:07 ANR0812I Inventory file expiration process 1692 completed: examined 23194393 objects, deleting 1690917 backup objec cts, 0 archive objects, 0 DB backup volumes, and 0 recov very plan files. 0 errors were encountered. This is currently running: Process Process Description Status s Number - 26 Expiration Examined 22853888 objects, deleting 20518954 bac ckup objects, 0 archive objects, 0 DB backup vo olumes, 0 recovery plan files; 1 errors encount tered. I don't think the policies were correctly expiring data prior to the upgrade. We've had numerous nodes that seemed to be storing much more than their policy dictated. We tried to force expiration on the files and it didn't seem to make much of a difference. Unfortunately we've been tweaking policies and trying to force a lot of data to drop off prior to the upgrade so I can't point to any particular reason why expiration is now expiring so much data. You can see the db size has dropped as well due to the expiration - and we performed an unload/reload less than a month ago prior to the upgrade. Being the db volume is one volume it could be disk contention, but it's a raw volume fiber attached (Sun T-3's). Luke "Stapleton, Mark" wrote: > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Luke Dahl > >We upgraded our TSM Server (Solaris 9) from 5.1.6.4 to 5.2.2.1 last > >week. Prior to the upgrade our expiration usually lasted about 24 > hours > >(53Gb database). It would generally post results like this: examined > >16446439 objects, deleting 59582 backup objects > >Our 3494 library showed est. capacity of 60Tb and approximately 88 pct. > >util. > > What is your db's cache hit ratio? 24 hours for a 53GB database is > manifestly too long. It should get through expiration in 2-3 hours. Give > us the output from Q DB F=D. > > >Any idea why expiration wasn't running properly prior to the upgrade? > >Data integrity looks good but we've just cleared out loads of space. I > >don't recall a known bug in expiration processing in 5.1.6.4 but may > >have missed something. Thanks for your thoughts and input. > > How, exactly, did you "clear out loads of space"? > > -- > Mark Stapleton ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.
Re: TDP for MS SQL - Restore DB
Yiannakis, That is correct. Please refer to the User's Guide for the exact syntax. Thanks, Del "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 03/26/2004 01:29:12 AM: > Thanks Del. > So after my full restore I do a second restore with the "difffull" parameter > instead of "full" ? > Thanks > Yiannakis > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of > Del Hoobler > Sent: 24 March 2004 15:33 > To: [EMAIL PROTECTED] > Subject: Re: TDP for MS SQL - Restore DB > > > Yiannakis, > > Saturday. > > If you want to restore it to a later point, > you will need to specify /RECOVERY=NO on the > restore of the full and then restore the last > differential backup with /RECOVERY=YES (default). > > Thanks, > > Del > > > "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 03/24/2004 > 02:33:02 AM: > > > Hi, > > I have the following schedules for a SQL dbase: > > Saturdays - full backup of dbase > > Weekdays - difffull backup of dbase > > > > I wanted to restore the dbase on Wednesday to another server, so I used > the > > command line as follows: > > > > tdpsqlc restore ChequeEnquiry full /relocate=ChequeEnquiryuiry_Data > > /to=H:\tsmrestore\cheqenq.mdf /relocate=ChequeEnquiryuiry_Log > > /to=H:\tsmrestore\cheqenq.lgf /fromsqlserver=IBCHQENQ > > -TSMPassword=x > > > > Have I restored the dbase as of last Saturday, or as of Tuesday ? > > Thanks > > Yiannakis
9840 vs 9940 Performance
Hello all, Does anybody have any experience with TSM performance of STK 9940's ? We are running 9840's with colocation and have found the performance for large restores of a small file nature to be very good. The only problem with 9840 is the 20GB limitation. I know that large servers will span multiple tapes and the multi-thread restore works exceptionally well with this. The only problem is that with growing data quantities, an L700 fills up very quickly. Using 9940's would triple the capacity of an L700. But we need to ensure we would maintain the performance that we are seeing on the 9840's. I understand that a 9940 is going to be a physically longer tape and as such certain stats are not comparable to the 9840. But does the repositioning and backhitching that is so evident with a large TSM restore compare to that of a 9840. -=Leigh=-
Retaining Deleted files
Hi, I have the following situation and I need a confirmation here. System information is : TSM 5.2. on Windows 2000, TSM BA client 5.2. on Windows 2000. I'm backing up a folder with the "incremental" option, that contains a complex subfolder tree. The contents of the subfolders are mainly transaction files from various applications. The user wants to keep the transaction files for 6 months on disk and then deletes the older ones (the 6th month) to make space for the new month. This is a user task and here I don't have any involvement. The user doesn't want to lose the deleted transaction files, because he might want to restore something for investigation reasons. I have set up a special policy for this. The backup copygroup definition is as follows: Policy Domain Name TSM_DOMAIN Policy Set Name ACTIVE Mgmt Class Name TSM_MGMT_CLASS Copy Group Name STANDARD Versions Data Exists2 Versions Data Deleted 2 Retain Extra Versions NOLIMIT Retain Only Version NOLIMIT Copy Mode MODIFIED Copy Serialization SHRSTATIC Copy Frequency 0 Copy Destination3590STGPOOL Table of Contents (TOC) Destination - Last Update Date/Time 2004-03-12 12:37:03.00 Last Update by (administrator) YIANNAKIS Managing profile- I have specified NOLIMIT on retain extra versions and retain only version so that I don't lose the deleted files. Is that correct ? Thanks Yiannakis
