help:can tsm server manage multi-library?
Hi all,can tsm server manage more than one library in lan-free backup environment?Thx!
Re: 3590 K series
Try the ibm storage media web page. Look in the datasheet for each type of media. The link for the 3592 media is ftp://ftp.software.ibm.com/common/ssi/rep_sp/n/TSD00063USEN/TSD00063USEN.PDF Here are the specs from the data sheet: Long-length durability 300 full file passes Short-length durability 40,000 cycles at ambient Load/unload 20,000 load, unload, and initialization cycles Estimated archive life Up to 30 years Warranty 10 years 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. David E Ehresman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 03/31/2005 12:26 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: 3590 K series Our 3590K tapes have a 10 year warrenty. >>> [EMAIL PROTECTED] 03/30/05 9:58 AM >>> Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD "Stapleton, Mark" <[EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ERBEE.COM> cc: Sent by: "ADSM: Subject: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 03/30/2005 09:58 AM Please respond to "ADSM: Dist Stor Manager" (from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: Can I exclude he WinSxS folder on Windows2003 server?
Bill, I just found your message while catching up on email. That folder holds Windows' "side-by-side" executables. Those are used by Windows for downward compatibility with older applications. So excluding them won't affect *Windows*, but whatever old application you're running that is using them will probably fail to start. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 03/29/2005 08:10:36 AM: > I have a client with a Windows2003 server with Exchange 2003 on it. > Lately he started seeing errors in his nightly non-Exchange > backups relating to a file in the C:\Windows\WinSxS folder. I've > search the archives and came up dry. No hits on IBM either. I > Google search brought up some information on package assemblies. > > > > Would it be safe to EXCLUDE.DIR the C:\WINDOWS\WINSXS directory? The > error(s) the client is getting are: > > > > 03/28/2005 03:32:13 ANS1228E Sending of object > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy' failed > > 03/28/2005 03:32:13 ANS4023E Error processing > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy': file input/output error > > 03/28/2005 03:32:44 ANS1512E Scheduled event 'BD70330' failed. > Return code = 12. > > > > > > And the backup schedule indicates failed. > > > > Bill Boyer > > "Growing old is mandatory, growing up is optional" - ??
Re: another storage agent question
hi chris, i have this setup working in our AIX TSM environment. Library Manager : AIX 5.2 TSM 5.2.3.5 Library Client : AIX 5.2 TSM 5.2.3.5 LANfree Client : Solaris 9 TSM 5.2.3.4 + Storage Agent 5.2.3.5 + TDP for R/3 3.3.12.0 you have to do the following things: 1. setup the Storage Agent dsmsta setstorageserver myname= mypassword= myhladdress= servername= serverpassword= hladdress= lladdress 2. define a server to server communication from the Storage Agent to the Library Manager via "define server .. " define server serverpass= hladdr= lladdr= 3. define a server to server communication from the Storage Agent to the Library Client via "define server ..." define server serverpass= hladdr= lladdr= 4. define the pathes for the drives for the Storage Agent at the Library Manager via "define path ..." now you should be able to start the Storage Agent in forground at the LANfree Client and see at least one client session for the LANfree Client at the Library Client TSM-Server Regards Uwe [EMAIL PROTECTED] Sent by: ADSM-L@VM.MARIST.EDU 31.03.2005 17:18 Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject another storage agent question Hi All Env = Win2k TSM Server and Storage agent 5.2.2.3 3584 mixed lto1/lto2 libraries 1 tsm server library manager , 1 tsm server library client The 5.2 and 5.3 manual on the storage agent seems to indicate that I should be able to do lanfree backups to a tsm server that is a library client which I don't quite understand because surely there would be no tape paths defined on the library client. Quotes from manual "When the Tivoli Storage Manager server (data manager server) is also the library manager for the devices where data is stored by the storage agent, then the storage agent communicates requests to this Tivoli Storage Manager server. When the Tivoli Storage Manager server (data manager server) is another library client, then the storage agent communicates requests for itself or the metadata server directly to the library manager. " "A library client requests shared library resources, such as drives or media, from the library manager, but uses the resources independently. The library manager coordinates the access to these resources. Data moves over the SAN between the storage device and either the library manager or the library client. Either the library manager or any library client can manage the LAN-free movement of client data as long as the client system includes a storage agent. " Has anyone got this working? I have only been able to get lanfree backups working in the normal way to the tsm server which is the library manager. What am I missing here? Cheers ___ Disclaimer Notice This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore the E.ON Group does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of the E.ON Group. E.ON UK plc, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England & Wales No. 2366970 E.ON UK Trading Ltd, Westwood Way, Westwood Business Park, Coventry, CV4 8LG Registered in England & Wales No. 4178314 E.ON UK Trading Ltd is regulated by the Financial Services Authority to carry out investment activities. Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: NDMP TOC (was Re: TSM 5.3 new goody)
Just a quick update on our NDMP/TSM implementation we have been working on: RECAP - We were attempting to get NDMP to work with TSM, at the qtree level (as opposed to the whole volume) and get a TOC for the files. We had ~some~ qtrees succeed but many failed. We've spent the last month with IBM and NetApp trying to figure out who's fault it was with logs and traces. Resolution: For those of you using NDMP on NetApp servers, here is the bug we ran into: __ Bug ID 152072 Title Tape backups are larger than expected or appear to loop in Phase V. Description Formatted If a data set has more than ~4,000 ACLs, then file data may be mistakenly written out in addition to NT ACL data during Phase V (NT ACLs) of dump. Symptoms of this bug include: Data written taking up significantly more space than what is being dumped or dump appearing to loop in Phase V. The behavior may be seen with dumps initiated from either the filer console or NDMP. Related Solutions Fixed-In Version Data ONTAP 7.0.0.1P2 __ The additional symptom that we bumped into is the inability to create a Table of Contents for the TSM session. I'm kinda surprised that nobody else has stumbled across this bug... Ben -Original Message- From: bbullock Sent: Tuesday, March 22, 2005 10:03 AM To: 'ADSM: Dist Stor Manager' Subject: RE: NDMP TOC (was Re: TSM 5.3 new goody) Hmm, I haven't seen a good rule-of-thumb for the TOC. Perhaps others who are using it more can address this. In my limited testing, I sometimes get a TOC much larger than I would expect on qtrees with the same approx number of files. Might it depend on if there are ACLs for the NTFS qtrees? I'm not sure in NDMP if that type of information is in the actual image file or in the TOC... Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stewart Sent: Tuesday, March 22, 2005 9:47 AM To: ADSM-L@VM.MARIST.EDU Subject: NDMP TOC (was Re: TSM 5.3 new goody) Anyone know how to estimate the size required for a TOC? I'm looking at NDPM for our filer, that has about 3 million files. [EMAIL PROTECTED]
Re: 3590 K series
We have only been using 3590K's for about 3 years, but we see more bad tapes from the freshly added tapes than we see from all of the older tapes. In general we see 1-2 tapes fail per month out of about 4,000 tapes. We move about 40-60 tapes per day off-site, with 40-60 making the return trip. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Thursday, March 31, 2005 12:26 PM To: ADSM-L@VM.MARIST.EDU Subject:Re: [ADSM-L] 3590 K series Our 3590K tapes have a 10 year warrenty. >>> [EMAIL PROTECTED] 03/30/05 9:58 AM >>> Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD "Stapleton, Mark" <[EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ERBEE.COM> cc: Sent by: "ADSM: Subject: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 03/30/2005 09:58 AM Please respond to "ADSM: Dist Stor Manager" (from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: curious behavior
You are correct, I verified this myself with a MOVE DATA against a full read/write volume. QUERY MOUNT shows it mounted as R/O. Sorry for passing on misinformation. I'm gonna go back to the server guys and ask for their clarification. 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. "ADSM: Dist Stor Manager" wrote on 2005-03-31 14:34:45: > David > > I never thought I'd say this, but I don't entirely agree with Andy. > > From my observations, during a reclamation, COPY STGPOOL or MOVE DATA > process, the source volume may be mounted R/O if its status is FULL > regardless of it's access. > > Regards > Neil Schofield > Yorkshire Water Services Ltd. > > > tsm: TSM1>q vol G01081 f=d > >Volume Name: G01081 > Storage Pool Name: LOC_TAPEPOOL_GENERAL_ARCHIVE > Device Class Name: LOC_STKL5500 >Estimated Capacity (MB): 79,379.7 >Scaled Capacity Applied: > Pct Util: 71.8 > Volume Status: Full > Access: Read/Write > Pct. Reclaimable Space: 28.2 >Scratch Volume?: Yes >In Error State?: No > Number of Writable Sides: 1 >Number of Times Mounted: 8 > Write Pass Number: 1 > Approx. Date Last Written: 05-01-2005 11:28:21 > Approx. Date Last Read: 09-11-2004 11:43:48 >Date Became Pending: > Number of Write Errors: 0 > Number of Read Errors: 0 >Volume Location: > Volume is MVS Lanfree Capable : No > Last Update by (administrator): > more... ( to continue, 'C' to cancel) > > Last Update Date/Time: 09-11-2004 11:43:16 > > > tsm: TSM1>move data G01081 > ANR2232W This command will move all of the data stored on volume G01081 to > other volumes within the same storage pool; the data will be inaccessible > to > users until the operation completes. > > Do you wish to proceed? (Yes (Y)/No (N)) y > ANS8003I Process number 3887 started. > > tsm: TSM1>q pro > > Process Process Description Status > Number > > - >3,887 Move DataVolume G01081 (storage pool >LOC_TAPEPOOL_GENERAL_ARCHIVE), Target Pool >LOC_TAPEPOOL_GENERAL_ARCHIVE, Moved Files: > 2447, >Moved Bytes: 168,867,360, Unreadable Files: > 0, >Unreadable Bytes: 0. Current Physical File >(bytes): None Current input volume: G01081. >Current output volume: G00676. > > tsm: TSM1>q mount > ... > ANR8330I ECARTRIDGE volume G01081 is mounted R/O in drive TSM1_GS02STKL5500 > (\\.\mt13.0.1.9), status: IN USE. > ANR8330I ECARTRIDGE volume G00676 is mounted R/W in drive TSM1_GS02STKL5500 > (\\.\mt1.0.1.6), status: IN USE. > ... > > tsm: TSM1> > > > > > > Visit cool-fuel.com to see our fun, interactive website for children > > YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD > > The information in this e-mail is confidential and may also be legally > privileged. The contents are intended for recipient only and are subject > to the legal notice available at http://www.keldagroup.com/email.htm > Yorkshire Water Services Limited > Registered Office Western House Halifax Road Bradford BD6 2SZ > Registered in England and Wales No 2366682
Restore performance problem
We recently restored a large mail server. We restored about nine million files with a total size of about ninety gigabytes. These were read from nine 3490 K tapes. The node we were restoring is the only node using the storage pool involved. We ran three parallel streams. The restore took just over 24 hours. The client is Intel Linux with 5.2.3.0 client code. The server is mainframe Linux with 5.2.2.0 server code. 'Query session' commands run during the restore showed the sessions in 'Run' status most of the time. Accounting records reported the sessions in media wait most of the time. We think most of this time was spent waiting for movement of tape within a drive, not waiting for tape mounts. Our analysis has so far turned up only two obvious problems: the movebatchsize and movesizethreshold options were smaller than IBM recommends. On the face of it, these options affect server housekeeping operations rather than restores. Could these options have any sort of indirect impact on restore performance? For example, one of my co-workers speculated that the option values might be forcing migration to write smaller blocks on tape, and that the restore performance might be degraded by reading a larger number of blocks. We are thinking of running a test restore with tracing enabled on the client, the server, or both. Which trace classes are likely to be informative without adding too much overhead? We are particularly interested in information on the server side. The IBM documentation for most of the server trace classes seems to be limited to the names of the trace classes.
Re: How to schedule the backup?
As has already been mentioned, TSM 5.3 has an enhanced schedule feature that allows you to do with with one schedule. Otherwise you will need to define 5 schedules, one for each day the event should run. While it might take slightly more effort to set up 5 schedules instead of 1, once they are defined, you're done. While admin schedules can be used to define and delete client schedules, you'll lose prior event information when the schedules are deleted. 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. "ADSM: Dist Stor Manager" wrote on 2005-03-31 13:01:11: > I want to setup one client schedule which only starts at > Tue/Wed/Thu/Fri/Sat. How can I do it? TIA.
Re: curious behavior
David I never thought I'd say this, but I don't entirely agree with Andy. >From my observations, during a reclamation, COPY STGPOOL or MOVE DATA process, the source volume may be mounted R/O if its status is FULL regardless of it's access. Regards Neil Schofield Yorkshire Water Services Ltd. tsm: TSM1>q vol G01081 f=d Volume Name: G01081 Storage Pool Name: LOC_TAPEPOOL_GENERAL_ARCHIVE Device Class Name: LOC_STKL5500 Estimated Capacity (MB): 79,379.7 Scaled Capacity Applied: Pct Util: 71.8 Volume Status: Full Access: Read/Write Pct. Reclaimable Space: 28.2 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 8 Write Pass Number: 1 Approx. Date Last Written: 05-01-2005 11:28:21 Approx. Date Last Read: 09-11-2004 11:43:48 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): more... ( to continue, 'C' to cancel) Last Update Date/Time: 09-11-2004 11:43:16 tsm: TSM1>move data G01081 ANR2232W This command will move all of the data stored on volume G01081 to other volumes within the same storage pool; the data will be inaccessible to users until the operation completes. Do you wish to proceed? (Yes (Y)/No (N)) y ANS8003I Process number 3887 started. tsm: TSM1>q pro Process Process Description Status Number - 3,887 Move DataVolume G01081 (storage pool LOC_TAPEPOOL_GENERAL_ARCHIVE), Target Pool LOC_TAPEPOOL_GENERAL_ARCHIVE, Moved Files: 2447, Moved Bytes: 168,867,360, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): None Current input volume: G01081. Current output volume: G00676. tsm: TSM1>q mount ... ANR8330I ECARTRIDGE volume G01081 is mounted R/O in drive TSM1_GS02STKL5500 (\\.\mt13.0.1.9), status: IN USE. ANR8330I ECARTRIDGE volume G00676 is mounted R/W in drive TSM1_GS02STKL5500 (\\.\mt1.0.1.6), status: IN USE. ... tsm: TSM1> Visit cool-fuel.com to see our fun, interactive website for children YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
FW: How to schedule the backup?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Stewart >Hmm, that is a creative workaround. > >Mark gets kudos for using the other half of his brain. Thank you, sir. I have oft been accused of being a right-brained guy stuck in a left-brained body. :o) The real enterprise-smart solution is to use a third-party application like Tivoli Workload Scheduler to schedule *all* server operations. Doing so gives you centralized management, flexibility as to what to do when you get non-zero return codes, email notifications, etc. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627
Re: How to schedule the backup?
Hmm, that is a creative workaround. Mark gets kudos for using the other half of his brain. I was thinking about an administrative schedule that would run on Sunday morning that delete's the nodes association with the schedule, then another one on Monday that would recreate it. However, doing this loses all the history of its success or failures. One client schedule, two administrative schedules. Or, just use CRON. [EMAIL PROTECTED]
Re: How to schedule the backup?
Hmm, that is a creative workaround. Mark gets kudos for using the other half of his brain. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Thursday, March 31, 2005 2:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: How to schedule the backup? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William >I want to setup one client schedule which only starts at >Tue/Wed/Thu/Fri/Sat. How can I do it? TIA. From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock > I believe you can only get that granularity with the TSM v5.3 server. > I haven't tried it, but the docs say it can be done. > On earlier versions of TSM, you would have to create 2 schedules, 1 >for weekdays and an identical one for Saturdays. There's a clumsy workaround. Create an administrative schedule that creates the client schedule; run it on Monday. Create another administrative schedule that deletes the client schedule, run it on Sunday. Yeah, yeah, I know, it's a Stupid TSM Trick. Yet another reason to consider moving to TSM 5.3... -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627
Re: How to schedule the backup?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William >I want to setup one client schedule which only starts at >Tue/Wed/Thu/Fri/Sat. How can I do it? TIA. From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock > I believe you can only get that granularity with the TSM v5.3 >server. > I haven't tried it, but the docs say it can be done. > On earlier versions of TSM, you would have to create 2 >schedules, 1 for weekdays and an identical one for Saturdays. There's a clumsy workaround. Create an administrative schedule that creates the client schedule; run it on Monday. Create another administrative schedule that deletes the client schedule, run it on Sunday. Yeah, yeah, I know, it's a Stupid TSM Trick. Yet another reason to consider moving to TSM 5.3... -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627
Re: How to schedule the backup?
I believe you can only get that granularity with the TSM v5.3 server. I haven't tried it, but the docs say it can be done. On earlier versions of TSM, you would have to create 2 schedules, 1 for weekdays and an identical one for Saturdays. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Sent: Thursday, March 31, 2005 1:01 PM To: ADSM-L@VM.MARIST.EDU Subject: How to schedule the backup? I want to setup one client schedule which only starts at Tue/Wed/Thu/Fri/Sat. How can I do it? TIA.
How to schedule the backup?
I want to setup one client schedule which only starts at Tue/Wed/Thu/Fri/Sat. How can I do it? TIA.
Re: curious behavior
The mount mode (R/O, R/W) should match the volume's current access, as shown by the QUERY VOLUME command with FORMAT=DETAILED. The mount mode does not correspond to the current read/write usage of the volume. 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. "ADSM: Dist Stor Manager" wrote on 2005-03-31 11:19:43: > (Running TSM 5.2.2 on Win2k with 4 LTO2 drives in a Powervault 136T) > > > > I've been seeing this for quite a while on our system. It's not an issue > but it sure does look strange. > > > > Unless I'm missing something here, if you are running a process that is > copying data from the tapepool to the copypool shouldn't the results of > a Q mount show that you have a tape with R/O and another one showing > R/W? > > > > I've seen this in other processes that involve multiple drives. If you > do the q proc it tells you where it is reading from and where it is > writing to. But if you go back and do a q mount then it doesn't match up > with the info from the q proc. > > I know which tape is in which drive and I know that the data is actually > going where I want it to but the q mount info kinda startles every once > in a while. > > > > > > As you can see here, it looks like the q mo is telling that I'm writing > to both tapes. The q proc tells me otherwise. I've done a quick series > of q mounts back to back and the drives always show the same. It looks > like I'm writing to both drives in this case. > > > > > > tsm: BACKUP1>q mo > > ANR8330I LTO volume 26L2 is mounted R/W in drive DRV2 (mt0.3.0.5), > status: IN USE. > > ANR8330I LTO volume 33L2 is mounted R/W in drive DRV3 (mt0.4.0.5), > status: IN USE. > > ANR8334I 2 matches found. > > > > tsm: BACKUP1>q pr > > > > Process Process Description Status > > Number > > > - > > 582 Backup Storage Pool Primary Pool NEWTAPEPOOL, Copy > Pool NEWCOPYPOOL, > >Files Backed Up: 2, Bytes Backed > Up: 16,792,685, > >Unreadable Files: 0, Unreadable > Bytes: 0. > >Current Physical File (bytes): > 59,738,060,746 > >Current input volume: 26L2. > Current output > >volume: 33L2. > > > > Even if I have all four drives churning away on different processes the > q mo will tell me one thing and the q proc will tell me something else. > It's completely random. If a drive shows up as "right" for one process > then the next time it gets used for another process then it might show > up "wrong". > > > > Again, everything is actually working as it should it just looks > strange. > > > > Is this a bug or a "feature"? > > > > Thanks... > > > > David Tyree > Enterprise Backup Administrator > South Georgia Medical Center > 229.333.1155 > > Confidential 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. > >
curious behavior
(Running TSM 5.2.2 on Win2k with 4 LTO2 drives in a Powervault 136T) I've been seeing this for quite a while on our system. It's not an issue but it sure does look strange. Unless I'm missing something here, if you are running a process that is copying data from the tapepool to the copypool shouldn't the results of a Q mount show that you have a tape with R/O and another one showing R/W? I've seen this in other processes that involve multiple drives. If you do the q proc it tells you where it is reading from and where it is writing to. But if you go back and do a q mount then it doesn't match up with the info from the q proc. I know which tape is in which drive and I know that the data is actually going where I want it to but the q mount info kinda startles every once in a while. As you can see here, it looks like the q mo is telling that I'm writing to both tapes. The q proc tells me otherwise. I've done a quick series of q mounts back to back and the drives always show the same. It looks like I'm writing to both drives in this case. tsm: BACKUP1>q mo ANR8330I LTO volume 26L2 is mounted R/W in drive DRV2 (mt0.3.0.5), status: IN USE. ANR8330I LTO volume 33L2 is mounted R/W in drive DRV3 (mt0.4.0.5), status: IN USE. ANR8334I 2 matches found. tsm: BACKUP1>q pr Process Process Description Status Number - 582 Backup Storage Pool Primary Pool NEWTAPEPOOL, Copy Pool NEWCOPYPOOL, Files Backed Up: 2, Bytes Backed Up: 16,792,685, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 59,738,060,746 Current input volume: 26L2. Current output volume: 33L2. Even if I have all four drives churning away on different processes the q mo will tell me one thing and the q proc will tell me something else. It's completely random. If a drive shows up as "right" for one process then the next time it gets used for another process then it might show up "wrong". Again, everything is actually working as it should it just looks strange. Is this a bug or a "feature"? Thanks... David Tyree Enterprise Backup Administrator South Georgia Medical Center 229.333.1155 Confidential 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.
Re: 3590 K series
Our 3590K tapes have a 10 year warrenty. >>> [EMAIL PROTECTED] 03/30/05 9:58 AM >>> Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD "Stapleton, Mark" <[EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ERBEE.COM> cc: Sent by: "ADSM: Subject: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 03/30/2005 09:58 AM Please respond to "ADSM: Dist Stor Manager" (from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
tsm & acsls
Hello All! I had an issue where the /tmp directory filled up and acsls stopped running. At that time TSM was doing a backup stgpool process. The TSM server is at 5.2.2.5 and is running on AIX 5.2 and we have ACSLS 7.1. I tried to cancel the job, but it will not. The tapes are in the drives, but I think that something got messed up when the connection was lost and now it doesn't appear to be backing up, but it won't let me cancel it or dismount the tapes. Has anyone ever had this issue before and if so, what did you have to do to fix it? Thanks! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED]
Re: Expiration
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hefty >When this process completes, there is a listing of objects examined and >deleted outputted to the activity log. What is the objects a reference >to; is it filespaces, files, directories...etc? > > >03/31/2005 02:26:38 ANR0984I Process 31 for EXPIRE INVENTORY >started in the BACKGROUND at 02:26:38. (SESSION: 1677, PROCESS: 31) >03/31/2005 02:26:38 ANR0811I Inventory client file expiration >started as process 31. (SESSION: 1677, PROCESS: 31) >03/31/2005 03:03:35 ANR0812I Inventory file expiration process 31 >completed: examined 1200811 objects, deleting 214852 backup objects, >0 archive objects, 0 DB backup volumes, and 0 recovery plan files. >0 errors were encountered. (SESSION: 1677, PROCESS: 31) Yes. ;o) The references are to pointers that have been deleted from the TSM database; those pointers relate to all objects that have to do with backups, archives, and other miscellaneous items that require expiration due to management class settings and other parameters. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627
Expiration
Hello all, When this process completes, there is a listing of objects examined and deleted outputted to the activity log. What is the objects a reference to; is it filespaces, files, directories...etc? 03/31/2005 02:26:38 ANR0984I Process 31 for EXPIRE INVENTORY started in the BACKGROUND at 02:26:38. (SESSION: 1677, PROCESS: 31) 03/31/2005 02:26:38 ANR0811I Inventory client file expiration started as process 31. (SESSION: 1677, PROCESS: 31) 03/31/2005 03:03:35 ANR0812I Inventory file expiration process 31 completed: examined 1200811 objects, deleting 214852 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. (SESSION: 1677, PROCESS: 31) 03/31/2005 03:03:35 ANR0987I Process 31 for EXPIRE INVENTORY running in the BACKGROUND processed 214852 items with a completion state of SUCCESS at 03:03:35. (SESSION: 1677, PROCESS: 31) Server version: 5.2.3.2 Server OS: Win2k3 Client versions: 5.2.3.4 Clients OS: Win2k & Win2k3 Thanks, Rob
Re: Archive very, very slow
One of our AIX machines had a similiar (only in such that backup performance was exceedingly slow) due to an undocumented vmtune parm that set the read aheads to zero after a patch. The instrument trace I think will help tell you if you are spending alot of the time in file I/o (I think). Either way, if this is an Aix v5.3 machine you can access the filesystem tuning options via smitty tuning (for most tuning stuff), it's worth checking out. Also have you tried local backups of other data not on those filesystems to see if all backups on the local system are slow, or only specific filesystems. I also assume you are not sharing FC adapters with both tape and disk? Have tried changing the "Maximum Transfer Size" on the adapter (our FC cards have this), it has helped to bump up our performance with our 3484 library (using Ultrium 2 drives) Jonathan Kaufman Andrew Raibeck <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 03/31/2005 10:36 AM Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: Archive very, very slow I doubt very much that tracing did anything to improve the performance. If anything, it impedes performance. There is most likely something else going on in the environment, though what I do not know. The data transfer time of 323 seconds suggests that it took TSM 5 minutes and 23 seconds to move the data, but the elapsed processing time of 55:13 minutes makes me wonder what was going on during the other 50 minutes. Unless memory is suspect, I would not recommend turning on the MEMORY trace flag since that generates a tremendous amount of data. The SERVICE trace might show some large gaps between timestamps that might lead to more info regarding the performance problem. You can also get an instrumentation trace by adding the following option when you invoke dsmc: -testflags=instrument:detail This will create a file named dsminstr.report that will have instrumentation info about the operation. Other questions: - While the operation is running, what does the administrative QUERY SESSION command show for the client? - Are there any error messages in the dsmerror.log file? - What does your client options file look like? - What does the client option set defined on the server for this client look like? - Are there any anomalous messages in the server activity log between the time the client operations begins and ends? 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. "ADSM: Dist Stor Manager" wrote on 2005-03-30 14:32:43: > I turned on tracing and ran an archive with the following command: > > dsmc archive -traceflag=service,memory > -tracefile=/tmp/tsm/trace/dbext_trace.out -tracemax=5000 -verbose > -desc="Old IDX Tape Backups for /restore/dbext - 2005Mar30" > -filelist=/tmp/tsm/archive_list_dbext_2005Mar30 -archmc=AIX-1YEAR > > Here is the summary: > > > > > IBM Tivoli Storage Manager > Command Line Backup/Archive Client Interface - Version 5, Release 2, > Level 3.0 > (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights > Reserved. > > Archive function invoked. > > Node Name: IDX_RESTORE > Session established with server TSMNIM01: AIX-RS/6000 > Server Version 5, Release 2, Level 4.0 > Data compression forced off by the server > Server date/time: 03/30/05 14:16:48 Last access: 03/30/05 > 14:13:11 > > > Total number of objects inspected: 865 > Total number of objects archived: 8 > Total number of objects updated: 0 > Total number of objects rebound: 0 > Total number of objects deleted: 0 > Total number of objects expired: 0 > Total number of objects failed: 0 > Total number of bytes transferred:98.15 GB > Data transfer time: 323.03 sec > Network data transfer rate:318,611.16 KB/sec > Aggregate data transfer rate: 31,063.43 KB/sec > Objects compressed by:0% > Elapsed processing time: 00:55:13 > > > > > Can someone explain how tuning on tracing would give me increased > transfer rate? > > This is not the same archive we have been having issues with, but this > same one took almost 3 ours earlier this week. > > Gary Galloway > ___ > ___ > Health Care Information Systems > University of Iowa Hospitals & Clinics > [EMAIL PROTECTED] > Phone: 319.356.7036 > > -Original Message- > From: ADSM: Dist Stor Manager [ma
Re: Archive very, very slow
I doubt very much that tracing did anything to improve the performance. If anything, it impedes performance. There is most likely something else going on in the environment, though what I do not know. The data transfer time of 323 seconds suggests that it took TSM 5 minutes and 23 seconds to move the data, but the elapsed processing time of 55:13 minutes makes me wonder what was going on during the other 50 minutes. Unless memory is suspect, I would not recommend turning on the MEMORY trace flag since that generates a tremendous amount of data. The SERVICE trace might show some large gaps between timestamps that might lead to more info regarding the performance problem. You can also get an instrumentation trace by adding the following option when you invoke dsmc: -testflags=instrument:detail This will create a file named dsminstr.report that will have instrumentation info about the operation. Other questions: - While the operation is running, what does the administrative QUERY SESSION command show for the client? - Are there any error messages in the dsmerror.log file? - What does your client options file look like? - What does the client option set defined on the server for this client look like? - Are there any anomalous messages in the server activity log between the time the client operations begins and ends? 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. "ADSM: Dist Stor Manager" wrote on 2005-03-30 14:32:43: > I turned on tracing and ran an archive with the following command: > > dsmc archive -traceflag=service,memory > -tracefile=/tmp/tsm/trace/dbext_trace.out -tracemax=5000 -verbose > -desc="Old IDX Tape Backups for /restore/dbext - 2005Mar30" > -filelist=/tmp/tsm/archive_list_dbext_2005Mar30 -archmc=AIX-1YEAR > > Here is the summary: > > > > > IBM Tivoli Storage Manager > Command Line Backup/Archive Client Interface - Version 5, Release 2, > Level 3.0 > (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights > Reserved. > > Archive function invoked. > > Node Name: IDX_RESTORE > Session established with server TSMNIM01: AIX-RS/6000 > Server Version 5, Release 2, Level 4.0 > Data compression forced off by the server > Server date/time: 03/30/05 14:16:48 Last access: 03/30/05 > 14:13:11 > > > Total number of objects inspected: 865 > Total number of objects archived: 8 > Total number of objects updated: 0 > Total number of objects rebound: 0 > Total number of objects deleted: 0 > Total number of objects expired: 0 > Total number of objects failed: 0 > Total number of bytes transferred:98.15 GB > Data transfer time: 323.03 sec > Network data transfer rate:318,611.16 KB/sec > Aggregate data transfer rate: 31,063.43 KB/sec > Objects compressed by:0% > Elapsed processing time: 00:55:13 > > > > > Can someone explain how tuning on tracing would give me increased > transfer rate? > > This is not the same archive we have been having issues with, but this > same one took almost 3 ours earlier this week. > > Gary Galloway > ___ > ___ > Health Care Information Systems > University of Iowa Hospitals & Clinics > [EMAIL PROTECTED] > Phone: 319.356.7036 > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Ben Bullock > Sent: Wednesday, March 30, 2005 2:01 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Archive very, very slow > >We also recently migrated from SCSI attached 3590E drives to SAN > attached 3592 drives (both in a 3494 library). > >Unfortunately, we only saw an increase in the performance with > the new tape drives. > >As Richard mentioned, it may be an issue with the mounting of > the data on the host, but I will throw in a few things to perhaps check > on the Tape drive configuration. > >- Are you using the latest and greatest ATAPE and ATLDD drivers? > Mine are a little old, but you should at least be at these > levels: >Atape.driver 9.0.7.0 >atldd.driver 5.5.1.0 > >- Are the drives defined to TSM as a 3592 drives and not > "Generic" or something? >Here is a little look at one of mine: > tsm: TSMX>q drive f=d > > Library Name: BOITAPELIB1 > Drive Name: 3592DRV0 > Device Type: 3592 >
another storage agent question
Hi All Env = Win2k TSM Server and Storage agent 5.2.2.3 3584 mixed lto1/lto2 libraries 1 tsm server library manager , 1 tsm server library client The 5.2 and 5.3 manual on the storage agent seems to indicate that I should be able to do lanfree backups to a tsm server that is a library client which I don't quite understand because surely there would be no tape paths defined on the library client. Quotes from manual "When the Tivoli Storage Manager server (data manager server) is also the library manager for the devices where data is stored by the storage agent, then the storage agent communicates requests to this Tivoli Storage Manager server. When the Tivoli Storage Manager server (data manager server) is another library client, then the storage agent communicates requests for itself or the metadata server directly to the library manager. " "A library client requests shared library resources, such as drives or media, from the library manager, but uses the resources independently. The library manager coordinates the access to these resources. Data moves over the SAN between the storage device and either the library manager or the library client. Either the library manager or any library client can manage the LAN-free movement of client data as long as the client system includes a storage agent. " Has anyone got this working? I have only been able to get lanfree backups working in the normal way to the tsm server which is the library manager. What am I missing here? Cheers ___ Disclaimer Notice This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore the E.ON Group does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of the E.ON Group. E.ON UK plc, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England & Wales No. 2366970 E.ON UK Trading Ltd, Westwood Way, Westwood Business Park, Coventry, CV4 8LG Registered in England & Wales No. 4178314 E.ON UK Trading Ltd is regulated by the Financial Services Authority to carry out investment activities. Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Integrating ITSM with Iron Mountain's SecureSync
A few questions regarding using Iron Mountain (IM): 1) Is anyone using TSM and IM's SecureSync application? 1A) If so how do you integrate TSM with SecureSync? 2) Since TSM sends tapes to the vault and requests return of vaulted tapes in a random sequence, does anyone allow their Vault Vendor to sign that they picked-up a closed container of tapes but not document the individual tapes in the container until after the container has been received at their vault? In other words the vault company says I don't want my courier to take the time to verify each tape he's picking up, only that he picked up "something". After that container arrives at the vault we'll note what that something was. This sounds undesirable to me but I was wondering if anyone followed this practice? Thanks, H. Milton Johnson
Re: Archive very, very slow
> We recently migrated from a locally attached 3590 E11 tape drive to two > 3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a > p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day > we quiese the application and flash copy it then mount the flash copy > volume groups to another system and backup. We were just doing the > native backup to the 3590 E11 locally attached drives. Then we mounted > the flash copy to the TSM server and did an archive. The four volume > groups comprise about 400G of data 95% being in CACHE.DAT files, one > which is about 200G in size. > > The problem is the archive over fibre is taking 12-14 hours to complete. > We were backing up to the 3590 local attached tape drives using native > commands in about 8 hours. The Aggregate data transfer rate: > 10,793.34 KB/sec seems network speed and we are using fibre attached > tape drives and ESS storage. The data is mounted to the TSM server so > the TSM server is also the client and the data should not be going over > the network at all. > > We have looked at ESS 800 performance of LUNs, software compression, > various settings including shmport and commMethod sharedmem and have not > been able to come up with anything to make the backup run faster. We > have a pmr open at IBM but it has not produced any useful information > that would resolve the problem. > > Has anyone else ever seen anything like this? Did the recent tape drive migration end up with the TSM server using the same HBA for both disk and tape?
storage agent question
Hi I think what I want to do is probably not supported/configurable but thought I would ask anyway. Env Win2k TSM Server and Storage agent 5.2.2.3 Basically I want the win2k server to be able to do lan free backups to two different tsm servers dependant on the optfile used. I tried adding in another storage agent instance via the wizard which seemed to work, i.e it updated dsmsta and devconfig files, but when I tried to run an image backup the storage agent still queried the original tsm server even though the TSMSERVERADDRESS in the optfile points to the other tsm server. Is it possible to configure two instances of the storage agent so that lan free backups can be run against either tsm server depending on the optfile used? Hope that makes sense.. Chris Rees UK Services +44 (0)24 76424303 or +44(0)1623 685875 [EMAIL PROTECTED] ___ Disclaimer Notice This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore the E.ON Group does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of the E.ON Group. E.ON UK plc, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England & Wales No. 2366970 E.ON UK Trading Ltd, Westwood Way, Westwood Business Park, Coventry, CV4 8LG Registered in England & Wales No. 4178314 E.ON UK Trading Ltd is regulated by the Financial Services Authority to carry out investment activities. Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: ADSM.org URL added to the TSM support website!
Interesting that IBM would do this, given that the website has never disclosed ownership. Richard Sims On Mar 30, 2005, at 5:03 PM, Prather, Wanda wrote: ADSM.org URL added to the TSM support website!
