Perhaps someone put these into a client option set?
Q NODE nodename F=D
Look for optionset:
If it's non=blank, then you need to investigate the contents of the optionset,
that's where your conflict is coming from.
If that is not revealing, from the client machine:
start the command line
This just happed, had been working for months. If I use ./dsmc q fi
I get nada, hangs! Will guarantee a reboot of linux will fix it.
Also no other locations is there another tsm log file
Tim
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
If I can remember well, try with, regardless the path:
exclude.backup *:\...\*.mdf
exclude.backup *:\...\*.ldf
exclude.backup *:\...\*.ndf
2015-02-06 13:09 GMT-06:00 Kinder, Kevin P kevin.p.kin...@wv.gov:
TSM Client 6.3.2.2
Windows Server 2003 R2 64bit
I have the following include\exclude
Hello Tim,
Any dsmc command is openning a connexion with the server (dsmc q se, dsmc q
fi...), but dsmc help doesn't. You may give it a try.
Also, TSM 6.1.0 is worth an update to a fixed version, don't you think ?
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
- Mail original
When debugging include-exclude specs, don’t look first at your client options
file: do ‘dsmc q inclexcl’, which will both evaluate the specs and look for
server-side contributors and intrinsic OS contributors - which may have
interactions with what you coded on the client. And always issue that
I would have told you the same thing about the reboot! My experience with V6
clients on Win2K3 it's not necessary; and even if it asks for a reboot, usually
any issues only affect the GUI (because of DLLs), not the scheduler/cmd line.
So I'm just flailing here.
Another thing I'd look for is
Hi Kevin,
Is Microsoft SQL Server running? Something in the back of my mind is
telling me that the .mdf and .ldf files are automatically excluded by the
client if SQL Server is running; in which case, the hard-coded excludes
would be redundant.
Regards,
- Andy
TSM Client 6.3.2.2
Windows Server 2003 R2 64bit
I have the following include\exclude statements:
EXCLUDE E:\Interfaces\NLXjobs\WV_NLXjobs.xml
EXCLUDE E:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.mdf
EXCLUDE E:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\*.ldf
EXCLUDE E:\Microsoft SQL
First, thanks to all who have responded. Second, ICYMI...
Now through 27 February you can take a quick survey to tell us what you
think about the TSM wiki.
Why? We want to improve the wiki and to improve, we need your help. If you
can give us 2 minutes (only 120 seconds!), we can make some
Perhaps try adding some traceflags to your dsm.opt/dsm.sys, and/or try
tracing it at the RHEL level with strace. One or both may shed light on
where it's getting stuck.
IIRC, I've seen some odd client hangs (and other weird client failures) when
there was a stuck/wedged/borked filesystem mount.
Thanks for the reply Wanda. We don't use option sets, but I checked to make
sure, it is blank.
No apparent conflicts when running q inclecxl, which I had done.
This dsm.opt worked in the past on this server, and the problem only started
when I upgraded the client version. I am guessing
Oh, that is weird.
If they only show up once in q inclexcl, you shouldn't be getting that error.
Perchance is there a reboot pending since you did the upgrade? (she asked,
grasping for straws...)
Wanda Prather
TSM Consultant
ICF International Enterprise and Cybersecurity Systems Division
Thanks again Wanda. That will be my next step.
As a bit of background, this was all part of a process to move from our TSM
installation on z/OS to a new one on an AIX server. Hated to do that, but since
IBM dropped development and upgrades in the z/OS arena, we had no choice. So,
in going
Or perhaps... could it have something to do with this flash alert I
received in my inbox today?
http://www-01.ibm.com/support/docview.wss?uid=swg21696086myns=swgtivmynp=OCSSGSG7mync=Ecm_sp=swgtiv-_-OCSSGSG7-_-E
Abstract
RHEL 6.6 contains a kernel defect, which can cause Tivoli Storage Manager
How are you starting it? With service ? Did you search for multiple
copies of dsmsched/error.log? It might be updating a different one from
what you are looking at?
On Fri, Feb 6, 2015 at 8:32 AM, Tim Brown tbr...@cenhud.com wrote:
Last line in dsmsched.log
02/06/2015 08:03:48 ANS2820E An
Last line in dsmsched.log
02/06/2015 08:03:48 ANS2820E An interrupt has occurred. The current operation
will end and the
client will shut down.
I was able to kill the process but whenever I restart the scheduler, the
process starts but dsmsched.log and or dsmerror.log arent refreshed.
I even
From my experience, this likely has nothing to do with the TSM server, but
rather either configuration issues with the client or permissions on the
dsmerror.log, or its location.
Start with a simple command like ‘dsmc q fi’, as an ordinary user and then
root, to see if there are issues with
We have been fighting this kernel problem for a while but as far as we know
it only effects the server and sql calls to DB2, not a client. We are
waiting for an official RedHat patch. The latest kernel update that just
came out addresses 3-semaphore related problems but none directly list the
18 matches
Mail list logo
