Trying to tun on tracing in the Windows 5.3 client.
Hi *SM-ers! I'm trying to create a trace, using the Windows 5.3.3.0 client. The most recent Trace Facility Guide I could find was SH26-4121-01 for TSM 4.2. I added the following lines to the dsm.opt file: Tracefile c:\temp\trace.txt Traceflags instr When I start dsm.exe, it complains about the traceflags line. The syntax is not correct. When I change it to traceflags all, I can start the TSM client (after waiting for a minute and a trace file which is already more than 100 Mb!), but I only want the instrumental tracing details. Why isn't the instr flag working, while the manual lists this as a valid flag? Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** 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: Trying to tun on tracing in the Windows 5.3 client.
On May 1, 2006, at 8:31 AM, Loon, E.J. van - SPLXM wrote: I'm trying to create a trace, using the Windows 5.3.3.0 client. The most recent Trace Facility Guide I could find was SH26-4121-01 for TSM 4.2. ... Eric - Use the TSM Problem Determination Guide: it is the current reference for tracing. Richard Sims
Re: Trying to tun on tracing in the Windows 5.3 client.
Hi Richard! Thank you VERY much for putting me on the right track! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: maandag 1 mei 2006 14:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: Trying to tun on tracing in the Windows 5.3 client. On May 1, 2006, at 8:31 AM, Loon, E.J. van - SPLXM wrote: I'm trying to create a trace, using the Windows 5.3.3.0 client. The most recent Trace Facility Guide I could find was SH26-4121-01 for TSM 4.2. ... Eric - Use the TSM Problem Determination Guide: it is the current reference for tracing. Richard Sims ** 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: NDMP Backups keep failing after upgrading to 5.3.2.4
I apologize for the wrong information: The NDMP backup started failing when we went to 5.3.3.0 on 2 of our TSM Servers. The TSM Server with 5.3.2.4 works fine. Rajesh - Original Message - From: Richard Sims [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Subject: Re: NDMP Backups keep failing after upgrading to 5.3.2.4 Date: Sun, 30 Apr 2006 12:32:44 -0400 On Apr 30, 2006, at 11:58 AM, Rajesh Oak wrote: ...After upgrading from 5.3.2.0 to 5.3.2.4 the NDMP backup started failing. ... Rajesh - 5.3.2.4 sounds to me like a patch level, rather than a upgrade path. Patch levels are intended to fix certain problems, are are not rigorously tested for all uses. Beware. Richard Sims -- ___ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
tsm script continuation character
Hello, I have the script below setup to run on Sunday. I understand the dash (-) is a continuation character that is placed at the end of the line, But I saw in the server log it did not accept the dash, Should there be a space on the next line before the continuation of a script? Administrator XXissued command: BACKUP DB devclass=BKP type=full scratch=yes -= wait=yes (SESSION: ANR2020E BACKUP DB: Invalid parameter - -. (SESSION: 988) This is the way it looks way when I click on the script serial backup db devclass=bkp type=full scratch=yes - wait=yes serial BA STG backuppool remotepool maxpr=2 wait=yes serial migrate stgpool backuppool lowmig=0 wait=yes serial Ba STG LTOpool REMOTEpool maxpr=2 wait=yes This is the way it looks when I update date the the script serial backup db devclass=bkp type=full scratch=yes - wait=yes serial BA STG backuppool remotepool maxpr=2 wait=yes serial migrate stgpool backuppool lowmig=0 wait=yes serial Ba STG LTOpool REMOTEpool maxpr=2 wait=yes Thanks in Advance!
TSM client problem with Novell Autoexec.ncf
Novell has a beta patch out now that should fix the problem. Haven't tried yet. - Fixed a problem where FileServername and cluster names were not able to be gathered by uname() until after autoexec.ncf had run. This affected products like IBM Tivoli's backup agents from being loaded properly in the Autoexec.ncf. http://support.novell.com/cgi-bin/search/searchtid.cgi?/2973643.htm
Re: tsm script continuation character
On Mon, 1 May 2006 11:31:10 -0400, Timothy Hughes [EMAIL PROTECTED] said: I have the script below setup to run on Sunday. I understand the dash (-) is a continuation character that is placed at the end of the line, But I saw in the server log it did not accept the dash, Should there be a space on the next line before the continuation of a script? Administrator XXissued command: BACKUP DB devclass=BKP type=full scratch=yes -= wait=yes (SESSION: ANR2020E BACKUP DB: Invalid parameter - -. (SESSION: 988) As a 'continuation character', it needs to come at the end of a line. The way to think about it is that the byte sequence -[newline] is magically removed from the script stream. Therefore a '-' other than before a newline is a syntax error. Thanks in Advance! You're welcome, a posteriori. - Allen S. Rout
Mainframe backups...
Greetings, all. I've gotten a request to update my opinions on ways that TSM can help the mainframe do backups. What I'm recalling from previous discussions we've had here is that the MVS filesystem structure, and the files theron, are sufficiently different from the heirarchical structures of byte streams we're accustomed to, that much of TSM is inapplicable to MVS data. So, for those of you in a mixed-mode shop, is TSM anywhere in the backup picture for your mainframe data? How are you doing offsites for the mainframe? Is it a VTS thing, or are there other methods you prefer? - Allen S. Rout
Re: Mainframe backups...
Hello Allen, The only role for mvs that tsm can play, at least to my limited knowledge, is to back up the unix oe file system. And the tsm server does not have to be on the mainframe. len -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Monday, May 01, 2006 1:29 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Mainframe backups... Greetings, all. I've gotten a request to update my opinions on ways that TSM can help the mainframe do backups. What I'm recalling from previous discussions we've had here is that the MVS filesystem structure, and the files theron, are sufficiently different from the heirarchical structures of byte streams we're accustomed to, that much of TSM is inapplicable to MVS data. So, for those of you in a mixed-mode shop, is TSM anywhere in the backup picture for your mainframe data? How are you doing offsites for the mainframe? Is it a VTS thing, or are there other methods you prefer? - Allen S. Rout
Domino TDP and MountWait parm
Solaris 9 - TSM 5.3.0 client Domino TDP - 5.3.0 We have been having lot of issues with Domino servers/processes hanging/stalling when the TDP backups kick off, especially when doing transaction log dumping. Everything would seize up while the transaction logs were dumped. We also have been noticing slowdowns caused by the actual backups. Through accident and experimentation, we discovered this can minimize/stop these hangups by adding the /MOUNTWAIT=NO parm to the DOMDSMC command. This makes no sense since the book describes this as waiting for tape resources when in fact, all backups to all Domino systems go directly to a 2TB disk LZ. Can someone (Del ?) please explain this and what are the consequences of using this parm and why do I seem to need it ?
Re: Mainframe backups...
Hi Allen, What you recall is correct. MVS doesn't understand open file systems, and a non-MVS OS doesn't understand MVS filesystems. You can't use TSM to do your mainframe backups in any way (except for the O/E component of MVS, which is a unix-style filesystem. If you use mainframe software to backup O/E, you get a backup of an HFS filesystem in 1 big clump. The TSM client for O/E can read inside the HFS and back it up by directory/file.) Offsites for the mainframe are just as they've always been: * Some sites rotate older generations offsite, keep newer generations onsite * Some sites have the software (like DFHSM) do it the TSM way, with a copy onsite and another copy offsite generated by the same software. * Sites with $$$ to work with are starting to use replication tecnology to fling the bits cross country instead of using traditional CTAM (Chevy Truck Access Method) to move the tapes physically. VTS (I assume you really mean VTS, not generic VTLs) in general is not a good fit for mainframe (or TSM) backups, because the 3494/3584 VTS was designed to work with small volumes, and the backup software (either DFHSM or TSM) wants to write big, full volumes. Although it can be made to work, you get better performance out of raw tape than a VTS for backup. If you need more info on that issue, let me know... Wanda -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Monday, May 01, 2006 1:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Mainframe backups... Greetings, all. I've gotten a request to update my opinions on ways that TSM can help the mainframe do backups. What I'm recalling from previous discussions we've had here is that the MVS filesystem structure, and the files theron, are sufficiently different from the heirarchical structures of byte streams we're accustomed to, that much of TSM is inapplicable to MVS data. So, for those of you in a mixed-mode shop, is TSM anywhere in the backup picture for your mainframe data? How are you doing offsites for the mainframe? Is it a VTS thing, or are there other methods you prefer? - Allen S. Rout
Re: tsm script continuation character
Richard, Allen Thanks, I retyped that line a couple of times and I finally think it's correct. I did a run script preview and it showed the script to run as the following so I think it's correct now. RUN: Executing command script SUN_TSM_TASKS. Line 1 : serial. Line 5 : backup db devclass=bkp type=full scratch=yes wait=yes. Line 15 : serial. Line 20 : BA STG backuppool remotepool maxpr=2 wait=yes. Line 25 : serial. Line 30 : migrate stgpool backuppool lowmig=0 wait=yes. Line 35 : serial. Line 40 : Ba STG LTOpool remotepool maxpr=2 wait=yes. SUN_TSM_TASKS completed successfully (PREVIEW mode). Richard Sims wrote: Tim - Perhaps there's an inadvertent space after the hyphen? Richard
Re: Domino TDP and MountWait parm
Hi Zoltan, The /MOUNTWAIT=NO says that if the backups need to be stored on offline media that would require a tape mount, then don't proceed with the operation. If what you say is correct... and all log backups are going to disk and not tape, using the /MOUNTWAIT=NO parameter should have absolutely no effect. I have a feeling that the accident and experimentation are probably more of a coincidence... but you never know. I would recommend placing a call with the IBM Support Team so they can help you can get this sorted out. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 05/01/2006 01:42:22 PM: Solaris 9 - TSM 5.3.0 client Domino TDP - 5.3.0 We have been having lot of issues with Domino servers/processes hanging/stalling when the TDP backups kick off, especially when doing transaction log dumping. Everything would seize up while the transaction logs were dumped. We also have been noticing slowdowns caused by the actual backups. Through accident and experimentation, we discovered this can minimize/stop these hangups by adding the /MOUNTWAIT=NO parm to the DOMDSMC command. This makes no sense since the book describes this as waiting for tape resources when in fact, all backups to all Domino systems go directly to a 2TB disk LZ. Can someone (Del ?) please explain this and what are the consequences of using this parm and why do I seem to need it ?
Re: Domino TDP and MountWait parm
Thanks for the reply. You are saying exactly what I said/read and felt. We did go through IBM and Notes support and they couldn't come up with anything tangible to explain the hangs. People were constantly complaining about the slow-downs/hangs. When we tracked them for a while, we noticed they always occured during the archlog dumps being performed, every 2-hours. I think IBM was the one who suggested the MOUNTWAIT parm (the Domino person handled this). I told them that none of the management classes go straight to tape. *ALL* backups (logs, daily, weekly) go to disk, first, and this parm shouldn't make any difference. When we added the MOUNTWAIT=NO, the complaints stopped and our monitoring showed no more seizures. I too realize it doesn't make sense but it did make a noticible difference. Del Hoobler [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 05/01/2006 03:37 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Domino TDP and MountWait parm Hi Zoltan, The /MOUNTWAIT=NO says that if the backups need to be stored on offline media that would require a tape mount, then don't proceed with the operation. If what you say is correct... and all log backups are going to disk and not tape, using the /MOUNTWAIT=NO parameter should have absolutely no effect. I have a feeling that the accident and experimentation are probably more of a coincidence... but you never know. I would recommend placing a call with the IBM Support Team so they can help you can get this sorted out. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 05/01/2006 01:42:22 PM: Solaris 9 - TSM 5.3.0 client Domino TDP - 5.3.0 We have been having lot of issues with Domino servers/processes hanging/stalling when the TDP backups kick off, especially when doing transaction log dumping. Everything would seize up while the transaction logs were dumped. We also have been noticing slowdowns caused by the actual backups. Through accident and experimentation, we discovered this can minimize/stop these hangups by adding the /MOUNTWAIT=NO parm to the DOMDSMC command. This makes no sense since the book describes this as waiting for tape resources when in fact, all backups to all Domino systems go directly to a 2TB disk LZ. Can someone (Del ?) please explain this and what are the consequences of using this parm and why do I seem to need it ?
GENERATE BACKUPSET fails
Hello all, I'm having problems generating backupsets, and I'm new to TSM so I'm not sure how to troubleshoot this. I'm running a Linux server TSM version 5.3.2. Here's what I see: Mon May 1 14:02:25 2006 ANR2017I Administrator MUSSULMA issued command: GENERATE BACKUPSET endeavour.cs.uiuc.edu 2006-05 /var devc=dltclass Mon May 1 14:02:25 2006 ANR0984I Process 92 for GENERATE BACKUPSET started in the BACKGROUND at 02:02:25 PM. Mon May 1 14:02:25 2006 ANR3500I Backup set for node ENDEAVOUR.CS.UIUC.EDU as 2006-05.1099170 being generated. Mon May 1 14:03:40 2006 ANR8337I DLT volume TSM010 mounted in drive DRIVE2 (/dev/tsmscsi/mt2). Mon May 1 14:03:40 2006 ANR0513I Process 92 opened output volume TSM010. Mon May 1 14:04:58 2006 ANR1360I Output volume TSM010 opened (sequence number 1). Mon May 1 14:05:16 2006 ANRD bfgenset.c(3614): ThreadId38 Unknown result code (17) from bfRtrv. Mon May 1 14:05:16 2006 ANR3520E GENERATE BACKUPSET: Internal error encountered in accessing data storage. Mon May 1 14:05:16 2006 ANR3503E Generation of backup set for ENDEAVOUR.CS.UIUC.EDU as 2006-05.1099170 failed. Mon May 1 14:05:18 2006 ANR1361I Output volume TSM010 closed. Mon May 1 14:05:18 2006 ANR0515I Process 92 closed volume TSM010. Mon May 1 14:05:22 2006 ANR0987I Process 92 for GENERATE BACKUPSET running in the BACKGROUND processed 349 items with a completion state of FAILURE at 02:05:22 PM. It fails the same way if I try a different filespace on the client, or a different client, or write to a different devclass. Restores from that filespace seem to work okay. I tried some web searches but came up cold. Any advice? Dave
W2k systemobject restore puzzle
server 5.2.2.0 client 5.3.0.5 I have a w2k machine (vm guest running sindie an ESX 2.5.3 host) that I have been trying to do a complete BMR on, with some flaky results. Programs now show up in the add/remove programs list, but none of the services or sharepoints came back. I'm suspecting some issue with replace on reboot, since both the c: restore and the systemobject restore came back with zero failures. Anyone seen something similar, or how do I go about tracking it down? I've tried several different points-in-time, all with the same result. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Domino Backups
I was wondering if someone could answer this that has knowledge having done something similar. The scenario is a Domino server does a full backup of all DB's on Sunday. Sometime during the week the node will be migrated to now back up to a new TSM server. The next schedule is actually an Incremental. Will it really be doing a FULL since it has never backed up to this server or will it really do a small incremental? I'm trying to avoid a manual full if it doesn't need it. We do want a full for all DB's so we don't have a full on one system and incrementals on another. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
