Error Message - ANS1512E
Hi to all When i am trying to run a scheduled backup i receive the following error message: Executing Operating System command or script: c:\tsmscripts\backupnas_daily.bat The process cannot access the file because it is being used by onother process I have looked to the Task Manager but i did not find any process that is using the above file. Any ideas? Thanks Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended recipient is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents) or take any action in reliance on it. In such case, you should destroy this message, and notify us immediately. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail from any computer. If you or your employer does not consent to internet e-mail messages of this kind, please notify us immediately. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As we cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by Laiki Group unless otherwise indicated by an authorised representative independent of this message.
[no subject]
Hi all. I need your help for this. We have a HPUX 11.0 and TSM Server 5.1.5 running with an IBM library 3584 connected to server with IBM switch, fibre channel and tachyon cards. Every time the Tsm server make the disk migration or stgp reclamation, hpux server is full wio: 10:44:31%usr%sys%wio %idle 10:44:32 14 1 85 0 10:44:33 12 4 84 0 10:44:34 16 2 82 0 10:44:35 7 0 93 0 10:44:36 18 3 79 0 10:44:37 8 4 88 0 10:44:38 3 0 97 0 10:44:39 10 1 89 0 10:44:40 25 2 73 0 10:44:41 23 0 77 0 Is it normal ?.
TSM licensing again
Hi. I've read all the previous messages about this topic, but I still have some questions. We've been asked by IBM to count our client's processors number. IBM says that now we will have to pay for licensing: 1. TSM Server - this is based on the number of processors used by clients being backuped up on this server 2. TSM Clients - number of nodes using the TSM Server The overall cost consists of those two. Maybe I'm missing something in here, but the first part is somehow... We have few machines but highly equipped (mostly 10+ CPUs per unit), so the fees for us are very high. Is it the _right_ way of licensing or just the Polish sales team is missing something important in their way of thinking? -- Przemysław Maciuszko Agora SA
[no subject]
"Winchester" IO is really any block-device IO: disk or tape. So it's not abnormal to see that; but it does look pretty high. Are you getting the performance you expect? Does vmstat say you're paging at these times? - Mr. Lindsay Morris Lead Architect www.servergraph.com 512-482-6138 ext 105 > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of > Juan Manuel Lopez Azanon > Sent: Friday, November 07, 2003 4:53 AM > To: [EMAIL PROTECTED] > Subject: > > > Hi all. > > I need your help for this. > We have a HPUX 11.0 and TSM Server 5.1.5 running with an IBM > library 3584 connected to server with IBM switch, fibre channel and > tachyon cards. > Every time the Tsm server make the disk migration or stgp > reclamation, hpux server is full wio: > > 10:44:31%usr%sys%wio %idle > 10:44:32 14 1 85 0 > 10:44:33 12 4 84 0 > 10:44:34 16 2 82 0 > 10:44:35 7 0 93 0 > 10:44:36 18 3 79 0 > 10:44:37 8 4 88 0 > 10:44:38 3 0 97 0 > 10:44:39 10 1 89 0 > 10:44:40 25 2 73 0 > 10:44:41 23 0 77 0 > > Is it normal ?. >
Hanging TSM backup invalidates journal?
Dear TSMville, Hanging Backup Invalidates TSM Journal o - TSM Client 5.1.5.0, Journaling engine backing up c 12,000,000 files with a daily addition/update of around 80,000. When it works = 40 minutes. When it doesn't = 13 hours... o - TSM Server 5.1.6.2 WinNT A couple of nights ago, a journal backup hung and just kinda stayed around on the TSM server in IdleW without anyone noticing. The next day's backup began and, I'm guessing from hereon, it couldn't get access to the TSM journal, so it reverted to a long normal incremental backup. I subsequently spotted this, killed off the two IdleW sessions and kicked off a new backup on the journal client. However, it failed to do a journal backup and started a normal incremental again... Looking in the dsmerror.log, I spy a 'NpOpen: Named pipe error connecting to server WaitOnPipe failed. > NpOpen: call failed with return code:121 pipe name //./pipe.jnl'. I understand that this named pipe is opened up at the initiation of a journal backup as the b/a client attempts to connect to the journal daemon - the return code 121 suggests that the connect failed, and possibly the tsmjbbd.exe process wasn't up and running. I look at task manager, and it is, but consuming a 'healthy' 263,632K of memory. Observing its behaviour, I see it is still doing some work 'I/O Other' in Task Manager's useful extra columns, but nothing in the 'I/O Writes' or 'Reads' section, is this suspect... I'm guessing that the journal became invalidated somewhere down the line during the hung backup, or that the subsequent attempt at a backup failed as maybe the old TSM backup still has a lock on it? The tsmjbbd.exe is still present, and there is nothing from these dates in the jbberror.log. Any ideas what may be going on here? I seem to be able to get around 6 or 7 days of JBB backups before it starts to break and I have to hand-hold it to get it up again... In terms of automatically monitoring this, sticking a Tivoli process monitor to make sure the tsmjbbd.exe process is running is only useful to a point (i.e. it wouldn't have spotted the above), so it looks as though I'm going to have to trawl the stdout of our backup logs to make sure that 'using journal for x$' is present. Any ideas where else I should be looking - perhaps in the (what we've called) jbberror.log for 'Journal will be restarted for FS x'? So, questions are: o - any ideas what might be behind the above? A dead/alive tsmjbbd.exe, and if so, how? o - tsmjbbd.exe - how big should it be in 'healthy' usage? Is 263MB a bit excessive? o - any ideas about the best way to monitor (preferably using Tivoli e.g. ITM, logfile adapters etc) jbb backups? Quite a lot there - sorry! Rgds, David McClelland Global Management Systems Reuters 85 Fleet Street London EC4P 4AJ E-mail [EMAIL PROTECTED] Reuters Messaging [EMAIL PROTECTED] -- -- Visit our Internet site at http://www.reuters.com Get closer to the financial markets with Reuters Messaging - for more information and to register, visit http://www.reuters.com/messaging Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.
AW: [tsm] Perl TSM daily reporting script.
hello, me was bitten as well. Had I not tested full server restore I would only have recognised missing backup of whole file system in real disaster recovery case :( Had I tested it before the acces rights change the result would be quite same. I find this suggestion (see below) *must* be part of documentation at the least (Andy?) regards Juraj Salak -Ursprüngliche Nachricht- Von: Jurjen Oskam [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 07. November 2003 07:54 An: [EMAIL PROTECTED] Betreff: Re: [tsm] Perl TSM daily reporting script. On Thu, Nov 06, 2003 at 06:37:15PM +, Patrick Audley wrote: > David> Patrick, Looks nice. But I hope you aren't going to rely > David> on the schedule completion status to tell you whether a > David> backup has been successful. You really need to mine the > David> last backup dates of q filespace f=d (or the equiv select). > > Ah... no I hadn't realized that :) I'm actually quite new to TSM > and this is exactly the feedback that I was hoping to get. I've added > that to the todo list. Yes, I've been bitten by this. A Windows 2000 client ran the Client Acceptor under the LocalSystem account. One day, the Windows administrator changed a drive to exclude LocalSystem from having access. The TSM client didn't use a DOMAIN statement. This resulted in that drive to be skipped without *any* message, warning or error. If the drive would have been in a DOMAIN statement, an error would have been issued. There is an APAR for this behaviour, but that is closed as a suggestion because IBM finds it too much trouble to fix. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: TSM licensing again
You can find my detailed explanations on licensing in list archives. In short - the sales team is right, you must sum processor count of both TSM server and TSM server-type nodes (file servers, RDBMS, web/appl. servers, etc.) and obtain necessary number of "Processor" licenses. For non-server nodes (workstations not serving anything over the network) you get "Client" license regardless of processor number. For a 10-way server you need 10 ITSM or ITSM XE "Processor" licenses. For a 6-cpu LPar/nPar/vPar in 10-way system you need 6 TSM licenses if other partition(s) do not use TSM. Zlatko Krastev IT Consultant Przemysław Maciuszko <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07.11.2003 13:35 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:TSM licensing again Hi. I've read all the previous messages about this topic, but I still have some questions. We've been asked by IBM to count our client's processors number. IBM says that now we will have to pay for licensing: 1. TSM Server - this is based on the number of processors used by clients being backuped up on this server 2. TSM Clients - number of nodes using the TSM Server The overall cost consists of those two. Maybe I'm missing something in here, but the first part is somehow... We have few machines but highly equipped (mostly 10+ CPUs per unit), so the fees for us are very high. Is it the _right_ way of licensing or just the Polish sales team is missing something important in their way of thinking? -- Przemysław Maciuszko Agora SA
TSM-client under FreeBSD?
Hi, I'd like to use the 5.x-TSM-client for Linux in order to back up a FreeBSD-system. FreeBSD comes with Linux-compatiblity so the binaries should be compatible/runable. When trying to install the required .rpms ("TIVsm-API.i386.rpm, TIVsm-BA.i386.rpm) I end up with: bash-2.05b# rpm -i TIVsm-API.i386.rpm error: failed dependencies: /bin/sh is needed by TIVsm-API-5.2.0-0 ld-linux.so.2 is needed by TIVsm-API-5.2.0-0 libcrypt.so.1 is needed by TIVsm-API-5.2.0-0 libcrypt.so.1(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 libc.so.6 is needed by TIVsm-API-5.2.0-0 libc.so.6(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 libc.so.6(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 libc.so.6(GLIBC_2.2) is needed by TIVsm-API-5.2.0-0 libdl.so.2 is needed by TIVsm-API-5.2.0-0 libdl.so.2(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 libdl.so.2(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 libm.so.6 is needed by TIVsm-API-5.2.0-0 libm.so.6(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 libpthread.so.0 is needed by TIVsm-API-5.2.0-0 libpthread.so.0(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 libpthread.so.0(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 libpthread.so.0(GLIBC_2.2) is needed by TIVsm-API-5.2.0-0 libstdc++-libc6.2-2.so.3 is needed by TIVsm-API-5.2.0-0 bash-2.05b# So there are some libs missing on the target (FreeBSD) system. Has anybody out there got the Linux-TSM client running under FreeBSD? Thanks much in advance for any clue, -ewald
Re: Cannot restore Database
Thanks, it turns out that I had not installed the tape drivers which are not installed by default for a WIN2K server instance. Just a little too much pressure lately. I'm not likely to forget again however! (: Take care, Al -Original Message- From: Brenda Collins [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 1:32 PM To: [EMAIL PROTECTED] Subject: Re: Cannot restore Database We just ran into this same situation yesterday at a D.R. test. We found that it was because we set up the new server with raw logical disk volumes and the production server was actually set up with it's disk as filesystems. Brenda Collins, ING - Americas Infrastructure Services Office: (612) 342-3839 Cell: (612) 290-0785 [EMAIL PROTECTED] Alan Davenport <[EMAIL PROTECTED]To: [EMAIL PROTECTED] ECTIVE.COM>cc: Subject: Cannot restore Database 11/05/2003 02:35 PM Please respond to "ADSM: Dist Stor Manager" Hello Group, I'm trying to restore a TSM database to a disaster recovery copy of one of our remote TSM servers without success. I installed TSM onto the DR box, copied the DEVCFG.OUT and VOLHIST.OUT files into the directory where the new server was built. When I try to restore the database I get the following error. Any idea where I am going wrong? ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.o- pt. ANR7800I DSMSERV generated at 09:58:50 on Jun 13 2003. Tivoli Storage Manager for Windows Version 5, Release 2, Level 0.0 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990,2003. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR8200I TCP/IP driver ready for connection with clients on port 1500. ANR0200I Recovery log assigned capacity is 1000 megabytes. ANR0201I Database assigned capacity is 2000 megabytes. ANR4621I Database backup device class TAPE2. ANR4622I Volume 1: B4. ANR4632I Starting point-in-time database restore (no commit). ANRD icrest.c(2076): ThreadId<0> Rc=33 reading header record. ANR2032E RESTORE DB: Command failed - internal server error detected. Entering exception handler. Thanks, Al Alan Davenport Senior Storage Administrator Selective Insurance Co. of America [EMAIL PROTECTED] (973) 948-1306
APAR IC35953 (was "Re: [tsm] Perl TSM daily reporting script.")
> This resulted in that drive to be skipped without *any* > message, warning or error. If the drive would have been > in a DOMAIN statement, an error would have been issued. > There is an APAR for this behaviour, but that is closed > as a suggestion because IBM finds it too much trouble to > fix. This mischaracterizes the situation, as it tells only half the story. The APAR you refer to is IC35953. The reason it was closed SUG is due to the extent of the code changes required to fix it; it is not as trivial as it sounds. Such code changes are beyond the scope of an APAR fix (not every problem can be fixed within an APAR) -- believe me, we tried. However, this APAR is still on the "to do" list, and has certainly not been closed and forgotten. 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. Jurjen Oskam <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/06/2003 23:54 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: [tsm] Perl TSM daily reporting script. On Thu, Nov 06, 2003 at 06:37:15PM +, Patrick Audley wrote: > David> Patrick, Looks nice. But I hope you aren't going to rely > David> on the schedule completion status to tell you whether a > David> backup has been successful. You really need to mine the > David> last backup dates of q filespace f=d (or the equiv select). > > Ah... no I hadn't realized that :) I'm actually quite new to TSM > and this is exactly the feedback that I was hoping to get. I've added > that to the todo list. Yes, I've been bitten by this. A Windows 2000 client ran the Client Acceptor under the LocalSystem account. One day, the Windows administrator changed a drive to exclude LocalSystem from having access. The TSM client didn't use a DOMAIN statement. This resulted in that drive to be skipped without *any* message, warning or error. If the drive would have been in a DOMAIN statement, an error would have been issued. There is an APAR for this behaviour, but that is closed as a suggestion because IBM finds it too much trouble to fix. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: Macintosh OS X include/exclude & domain list
On Thu, 6 Nov 2003 11:37:37 -0700 John Bremer <[EMAIL PROTECTED]> wrote: > Greetings, > > TSM Server 5.1.6.2, AIX 5.1 > > Mac OS X 10.2 > TSM Mac OS X client 5.2.0.0 > > I'm trying to exclude the Macintosh HD domain and backup only one folder > from the drive. The GUI is not very cooperative in Edit Preferences. > > Documentation says : > > DOMAIN "-Macintosh HD:" > > in TSM User Preferences should exclude my Mac HD. Then in TSM System > Preferences, I want to include a certain folder. However, I am having > trouble getting the GUI to "choose" the folder and add an include > statement to the System Preferences. > > Assuming the folder is "Documents", what would be the syntax? Below? > > include "Macintosh HD:Documents:...:*" > > I can't get this to be added through the GUI, but can BBEDIT the > Preferences files. > I guess using bbedit on the prefs file is sensible... the TSM clinet gui is somewhat limitted wrt the possible selections of include-exclude rules > Any assistance is appreciated. > > Regards, John -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: Include/exclude not working
Yes, I tried to set up from client side as much as possible since server is in the remote location, the only communication is through email. Sometimes it is not easy to describe clearly what I wanted. But to make things simple, I have to ask server people to help. I did use a lot of exclude.dir with include option. My question is how to read log file. It seems everything is sent to server including the exclude.dir. In my log file I have entries like the following: 11/06/2003 15:56:16 Expiring-->0 \\machineName\c$\tsm_images_v52\System32\Redist\MS\System [Sent] Does this ( Expiring--> ) mean this is an excluded directory? Thank you very much for your help. Lan At 08:14 AM 11/6/2003 -0700, you wrote: A second response to my post from a few moments ago: Why not simply run dsmc incremental g:\inetpub\ -subdir=yes Or create a schedule that backs up this directory only, as I described a day or two ago? 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. Lan Wu-Cavener <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/06/2003 08:04 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Include/exclude not working Thanks much, Andy! I am glad that I asked the question, although it is very stupid one. I did read the user manual again. It seems that the DOMAIN is for defining 1) drives, (I just assumed the entries shown in my domain list window which mostly are directories could be used as domain objects.) or 2) share names which could be used to a directory (authentic shared one or not (cheating)). I do have a network shared directory needs backup on the d drive of the machine where TSM client resides. I will think this directory can be defined as share name. Am I correct? My question is that is "net share inetpub=g:\inetpub" a command line or I can put it into opt file? Lan Lan Wu-Cavener Dept. of Landscape Architecture PennState Lan Wu-Cavener Dept. of Landscape Architecture
Hanging TSM backup invalidates journal?
Based on your description, a couple things are going on. The following message: >>> Named pipe error >>> connecting to server WaitOnPipe failed. > NpOpen: call failed with >>> return code:121 pipe name //./pipe.jnl'. indicates that another backup session is attempting to connect to the journal daemon while another journal based backup session is in progress. This can happen if multiple backup client processes attempt to perform a journal based backup at the same time, or if the ResourceUtilization option setting is higher than 2 and produces multiple backup sessions. The level of client you are running will only wait about 2 minutes for a connection to the journal daemon to become free and will then timeout. A testflag was implemented in the 5.1.6.2 level fixtest to allow a client to specify a timeout value that the client will wait for a connection to the journal daemon to become free (that is, the currently running jbb session to finish). You might also consider reducing the ResourceUtilization setting to 2 or less. Multi session journal based backup isn't currently supported and is a know requirement for a future release (apar IC36361 is currently opened against this problem). I have also recently discovered a problem in which a valid journal gets invalidated anytime a journal based backup starts but doesn't complete (due to a session drop, client terminated by the user, etc.). The result of this is that the next backup will not be journal based (will be a normal full incremental) and journal based backup won't be available until a full backup completes and re-validates the journal. Apar IC37908 has been opened against this problem and should be fixed in the 5.22 level client. It is reasonable for the journal daemon process to utilize a large amount of memory while processing a large journal query, which involves building a sorted list of objects to send to the client, but the memory should eventually be released when the journal based backup completes. I have notices that very large journal queries and journal based backups can create prolonged delays in the journal daemon, and I am looking at ways of making these queries more efficient, both in terms of memory utilization and in terms of processing time. Hope this helps answer your questions Regards, Pete Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" -- Forwarded by Pete Tanenhaus/San Jose/IBM on 11/07/2003 10:11 AM --- Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Hanging TSM backup invalidates journal? Dear TSMville, Hanging Backup Invalidates TSM Journal o - TSM Client 5.1.5.0, Journaling engine backing up c 12,000,000 files with a daily addition/update of around 80,000. When it works = 40 minutes. When it doesn't = 13 hours... o - TSM Server 5.1.6.2 WinNT A couple of nights ago, a journal backup hung and just kinda stayed around on the TSM server in IdleW without anyone noticing. The next day's backup began and, I'm guessing from hereon, it couldn't get access to the TSM journal, so it reverted to a long normal incremental backup. I subsequently spotted this, killed off the two IdleW sessions and kicked off a new backup on the journal client. However, it failed to do a journal backup and started a normal incremental again... Looking in the dsmerror.log, I spy a 'NpOpen: Named pipe error connecting to server WaitOnPipe failed. > NpOpen: call failed with return code:121 pipe name //./pipe.jnl'. I understand that this named pipe is opened up at the initiation of a journal backup as the b/a client attempts to connect to the journal daemon - the return code 121 suggests that the connect failed, and possibly the tsmjbbd.exe process wasn't up and running. I look at task manager, and it is, but consuming a 'healthy' 263,632K of memory. Observing its behaviour, I see it is still doing some work 'I/O Other' in Task Manager's useful extra columns, but nothing in the 'I/O Writes' or 'Reads' section, is this suspect... I'm guessing that the journal became invalidated somewhere down the line during the hung backup, or that the subsequent attempt at a backup failed as maybe the old TSM backup still has a lock on it? The tsmjbbd.exe is still present, and there is nothing from these dates in the jbberror.log. Any ideas what may be going on here? I seem to be able to get around 6 or 7 days of JBB backups before it starts to break and I have to hand-hold it to get it up again... In terms of automatically monitoring this, sticking a Tivoli process monitor to make sure the tsmjbbd.exe process is running is only useful to a point (i.e. it wouldn't have spotted the above), so it looks as though I'm going to have
Re: APAR IC35953 (was "Re: [tsm] Perl TSM daily reporting script.")
On Fri, Nov 07, 2003 at 07:30:42AM -0700, Andrew Raibeck wrote: > The APAR you refer to is IC35953. The reason it was closed SUG is due to > the extent of the code changes required to fix it; it is not as trivial as > it sounds. It would have been nice if this information was included in the documentation or the README of the Windows clients. That doesn't involve large code changes. > However, this APAR is still on the "to do" list, and has certainly not > been closed and forgotten. That's good to hear, but the wording of that APAR and previous experiences with TSM support made it look otherwise. Through the normal support channels, one encounters much resistance from IBM when a potential or suspected bug is involved; the phrase "works as designed" is sometimes being used much too lightly. By using the wording I did, I was barking up the wrong tree: the IBM people on this list are very helpful and very concerned with the quality of TSM. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
Re: TSM-client under FreeBSD?
On Friday 07 November 2003 14:12, Ewald Jenisch wrote: > Hi, > > I'd like to use the 5.x-TSM-client for Linux in order to back up a > FreeBSD-system. FreeBSD comes with Linux-compatiblity so the binaries > should be compatible/runable. > > When trying to install the required .rpms ("TIVsm-API.i386.rpm, > TIVsm-BA.i386.rpm) I end up with: > > bash-2.05b# rpm -i TIVsm-API.i386.rpm > error: failed dependencies: > /bin/sh is needed by TIVsm-API-5.2.0-0 > ld-linux.so.2 is needed by TIVsm-API-5.2.0-0 > libcrypt.so.1 is needed by TIVsm-API-5.2.0-0 > libcrypt.so.1(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 > libc.so.6 is needed by TIVsm-API-5.2.0-0 > libc.so.6(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 > libc.so.6(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 > libc.so.6(GLIBC_2.2) is needed by TIVsm-API-5.2.0-0 > libdl.so.2 is needed by TIVsm-API-5.2.0-0 > libdl.so.2(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 > libdl.so.2(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 > libm.so.6 is needed by TIVsm-API-5.2.0-0 > libm.so.6(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 > libpthread.so.0 is needed by TIVsm-API-5.2.0-0 > libpthread.so.0(GLIBC_2.0) is needed by TIVsm-API-5.2.0-0 > libpthread.so.0(GLIBC_2.1) is needed by TIVsm-API-5.2.0-0 > libpthread.so.0(GLIBC_2.2) is needed by TIVsm-API-5.2.0-0 > libstdc++-libc6.2-2.so.3 is needed by TIVsm-API-5.2.0-0 > bash-2.05b# > > So there are some libs missing on the target (FreeBSD) system. > > > Has anybody out there got the Linux-TSM client running under FreeBSD? - No, but you can ignore the depency's with --the rpm option nodeps. - Yes, my collague did. One tip : use virtual mount points. Stef -- [EMAIL PROTECTED] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.openprojects.net
Re: Include/exclude not working
Yes. You will get that for files that were backed up once, but are now excluded (or have been deleted from the drive). "expiring" doesn't mean the previous backup was necessarily deleted from the server end; it means that TSM has detected that the file is now excluded or deleted from the hard drive. The previous backup is now marked "inactive", and from this point will be managed based on your backup copy group values for "retextra" or "retonly". -Original Message- From: Lan Wu-Cavener [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2003 10:37 AM To: [EMAIL PROTECTED] Subject: Re: Include/exclude not working Yes, I tried to set up from client side as much as possible since server is in the remote location, the only communication is through email. Sometimes it is not easy to describe clearly what I wanted. But to make things simple, I have to ask server people to help. I did use a lot of exclude.dir with include option. My question is how to read log file. It seems everything is sent to server including the exclude.dir. In my log file I have entries like the following: 11/06/2003 15:56:16 Expiring-->0 \\machineName\c$\tsm_images_v52\System32\Redist\MS\System [Sent] Does this ( Expiring--> ) mean this is an excluded directory? Thank you very much for your help. Lan At 08:14 AM 11/6/2003 -0700, you wrote: >A second response to my post from a few moments ago: > >Why not simply run > >dsmc incremental g:\inetpub\ -subdir=yes > >Or create a schedule that backs up this directory only, as I described a >day or two ago? > >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. > > > > >Lan Wu-Cavener <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >11/06/2003 08:04 >Please respond to "ADSM: Dist Stor Manager" > > To: [EMAIL PROTECTED] > cc: > Subject:Re: Include/exclude not working > > >Thanks much, Andy! > >I am glad that I asked the question, although it is very stupid one. I did >read the user manual again. >It seems that the DOMAIN is for defining 1) drives, (I just assumed the >entries shown in my domain list window which mostly are directories could >be used as domain objects.) or 2) share names which could be used to a >directory (authentic shared one or not (cheating)). I do have a network >shared directory needs backup on the d drive of the machine where TSM >client resides. I will think this directory can be defined as share name. >Am I correct? My question is that is "net share inetpub=g:\inetpub" a >command line or I can put it into opt file? > >Lan > > >Lan Wu-Cavener >Dept. of Landscape Architecture >PennState Lan Wu-Cavener Dept. of Landscape Architecture
problems with OS/390 fixtest file
Anyone in the MVS world seen this before? I've ftp'd the 5.1.7.3 linklib and messages files from the IBM ftp site. I've transferred them to a pre-allocated data set on the mainframe with the recommended format, lrecl and block size (FB, 80, 3120). Yet, when I run the receive command to convert it from the xmit format to a link library I get the following message: INMR921I Received file appears not to be an Interactive Data Transmission Facilty file. The first record is:, INMR922I : ::INMR01 : : :&:: : :SNJMAS3:: : :K311552:: : :99:: : :99:: : :20030 and, in fact this file does look different from the one's we downloaded for 4.1.4.2. Any suggestions on what I'm doing wrong? I may try a different level fixtest just for drill. Thanks, -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: problems with OS/390 fixtest file
Did you use BINARY ? I just tried it and it worked fine. I use "SITE LRECL=80 RECFM=FB BLKSIZE=800 PRI=100 SEC=100" Jim Kirkman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 11/07/2003 03:49 PM Please respond to jim_kirkman To: [EMAIL PROTECTED] cc: Subject:problems with OS/390 fixtest file Anyone in the MVS world seen this before? I've ftp'd the 5.1.7.3 linklib and messages files from the IBM ftp site. I've transferred them to a pre-allocated data set on the mainframe with the recommended format, lrecl and block size (FB, 80, 3120). Yet, when I run the receive command to convert it from the xmit format to a link library I get the following message: INMR921I Received file appears not to be an Interactive Data Transmission Facilty file. The first record is:, INMR922I : ::INMR01 : : :&:: : :SNJMAS3:: : :K311552:: : :99:: : :99:: : :20030 and, in fact this file does look different from the one's we downloaded for 4.1.4.2. Any suggestions on what I'm doing wrong? I may try a different level fixtest just for drill. Thanks, -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: problems with OS/390 fixtest file
should have mentioned that, yes I did [EMAIL PROTECTED] wrote: > > >I've ftp'd the 5.1.7.3 linklib and messages files from the IBM ftp site. > > Jim - You didn't say whether you enforced a Binary transfer... > > Richard -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
SQL backup errors
B/A client 5.1.5.9 TDP for SQL 2.2.1 Windows 2000 SP4 / SQL Server 2000 TDP for SQL backup are failing with the following message: ACO5400E The Virtual Device Interface is not registered with the Common Object Model. I have never seen this one before. It sounds OS/SQL server related, but I haven't confirmed that yet. Any suggestions? Regards, Matt Adams Tivoli Storage Manager Team Deloitte This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Configuring Second TSM Server (to Share Library)
Hello, First of all, let me preface my post by saying that I am a TSM novice. I have a Solaris 9 server running TSM 5.2.1, which is physically attached to an L25, LTO tape library. This server is not using any storage pools. It is currently being used to back up a few UNIX servers each night, so neither the server, nor the library are being stressed. My team would now like to utilize the same tape library to perform backups of their desktop and notebook Windows 2000 /XP systems. They would not be backing up lage amounts of data, only their D:/Documents and Settings directory. I've got another unutilized UNIX server which I've loaded Solaris 9 and TSM Server 5.2.1, which I'd like to dedicate to these PC backups. This system is not physically connected to the library, but is on the same LAN. It also has a small disk array attached (2.1 GB x 12), which I plan to use as a storage pool. I'm not sure where to begin or what the most optimal configuration would be. Please help! Many thanks in advance! Angelo Proen EDS [EMAIL PROTECTED] 248-265-9753
Re: Configuring Second TSM Server (to Share Library)
If you cannot connect the 2nd Unix server to the L25 and it's drives, then you can setup the 2nd server to use "virtual volumes" on the first server. Refer to the TSM Administrator's Guide, Part 4, for information on how to do this. If your first server has excess capacity, you could just route the workstation backups to it, or define a 2nd TSM server image on it (answering at a different port number). There is documentation for this in the Quick Start guide. ..Paul At 05:31 PM 11/7/2003 -0500, Proen, Angelo G wrote: Hello, First of all, let me preface my post by saying that I am a TSM novice. I have a Solaris 9 server running TSM 5.2.1, which is physically attached to an L25, LTO tape library. This server is not using any storage pools. It is currently being used to back up a few UNIX servers each night, so neither the server, nor the library are being stressed. My team would now like to utilize the same tape library to perform backups of their desktop and notebook Windows 2000 /XP systems. They would not be backing up lage amounts of data, only their D:/Documents and Settings directory. I've got another unutilized UNIX server which I've loaded Solaris 9 and TSM Server 5.2.1, which I'd like to dedicate to these PC backups. This system is not physically connected to the library, but is on the same LAN. It also has a small disk array attached (2.1 GB x 12), which I plan to use as a storage pool. I'm not sure where to begin or what the most optimal configuration would be. Please help! Many thanks in advance! Angelo Proen EDS [EMAIL PROTECTED] 248-265-9753 -- Paul Zarnowski Ph: 607-255-4757 719 Rhodes Hall, Cornell UniversityFx: 607-255-8521 Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
TSM server on AIX 5.2.0 ML02 breaks TDP for Oracle (TDO) 2.2.1.0
Has anyone encountered this problem? If so, how did you resolve it? After upgrading the AIX level on which the TSM server runs from AIX 5.2.0 ML01 to ML02, a TDP for Oracle (TDO) version 2.2.1.0 client is now unable to do a full backup. After running for 4 or 5 hours the full backup fails on varing datasets. The TDO client is running on system with AIX 5.1.0 ML03 and TSM BA client 5.1.0.0. The error in the sbtio.log file is of the form that follows. However since some of the failed full backups did not generate this error in the sbtio.log file, this error may be caused by some other activity (like tdposync). SBT-108412 11/07/2003 02:23:57 remove2.cpp(237): sbtremove2(): Exit - wrong state, dsmHandle = 1, state = 2 The error reported by RMAN and Oracle's interpretation of the error is: > RMAN-00571: === > RMAN-00569: === ERROR MESSAGE STACK FOLLOWS === > RMAN-00571: === > RMAN-03007: retryable error occurred during execution of command: backup > RMAN-07004: unhandled exception during command execution on channel c1 > RMAN-10035: exception raised in RPC: ORA-19506: failed to create > sequential file, name="prod_backup_4578_f2f538v0_9_1", parms="" > ORA-27028: skgfqcre: sbtbackup returned error > ORA-19511: ANU0004E An unknown error has been detected. > RMAN-10031: ORA-19624 occurred during call to > DBMS_BACKUP_RESTORE.BACKUPPIECECREATE And this is Oracle's interpretation of that error: prod1 $ oerr ora 27028 27028, 0, "skgfqcre: sbtbackup returned error" // *Cause: sbtbackup returned an error. This happens when creating a backup // file during a backup operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor.