Hello,
just look at the example init script /etc/init.d/skeleton.
Copy it to /etc/init.d/tsm_sched
Edit it (you only need the start and stop section) it's really
easy...
And then use chkconfig tsm_shed on to activate it. Then the
script
will
Hi,
Debbie Bassler schrieb:
Our TSM server, 5.1, is on an AIX OS, 4.3.3. Does anyone know of a log
containing information about the tape drives? One of our drives has been
inaccessible since 3:20 this morning. I'd like to write a script to page
me when this happens, but, I don't know if there
Hoi Roark,
If you cannot affort to upgrade to 5.3.x, you can also use more tapepools.
So you can make a tapepool for very small nodes, with collocation off, so it
still uses less tapes and a tapepool for the big nodes with collocation on.
If neccesary, you can make more tapepools, but remember,
Hello,
I wonder what this error mean and why I get it? After googling for
GetBootPath and QueryDosDevice() but with no luck. I have found similar
questions on list but no answers. Do anyone have any idea what this is?
29-08-2005 20:06:19 GetBootPath: error on QueryDosDevice() for C:\,
rc = 998
Hi,
Just one thing to add. If the command line isn't your friend, tools like
tsmmanager can help you a lot. Just checkout the website (and look at
the pricing) and download the demo.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hi Mark!
Actually, the vacuum in a 3590 drive isn't used for pulling in the
cartridges, it's used for pulling the tape against the head.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Debbie Bassler [mailto:[EMAIL PROTECTED]
Sent: Monday, August 29, 2005
Hi Hendrik!
Windows return code 998 means:
998 Invalid access to memory location. ERROR_NOACCESS
However, that probably still doesn't tell you much... I would open a PMR in
your case.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Henrik
True ;-)
I use Operational Reporting and Access with a bunch of advanced selects (on
imported tables) to monitor and the command admin client to enter the
commands... that's cheaper... more Dutch ;-)
Regards,
Maurice
- Original Message -
From: Bos, Karel [EMAIL PROTECTED]
To:
Hi Hendrik,
I see that use version 5.1.6.6 client.
Did you installed the right version? You cannot use this version without the
base version 5.1.6 installed first.
You don't get any error when you install it, but it can give very strange
problems when using.
Same for the server: first 5.1.0.0,
Thanks.
I would appreciate the script - please send.
Volker Maibaum
[EMAIL PROTECTED]
BERSPAECHER.COM To
Sent by: ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor
One thing to watch our for is that not all of TSM gets installed into
/usr/tivoli/tsm/server directory
structure (on AIX . . . don't know about other os's). A quick list of the
files in the TSM v5.3
filesets showed bits/pieces installed in /etc and /usr/lib.
Rick
Ok, got SNMP running @ the OS, dsmsnmp is running and connects to os
SNMP.
I've enabled all SNMP events in TSM,
Dsmserv.opt
COMMmethod SNMP
SNMPSUBAGENT HOST 127.0.0.1 COMM public timeout 600
SNMPSUBAGENTHOST 127.0.0.1
SNMPMESSAGECATEGORY SEVERITY
Then did the following on TSM
BEGIN
Hi Maurice,
As far I remember it is 5.1.5 that i base level for 5.1.9 server.
And is that true, that I really need to install base level before I
apply a patch on a client?
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Maurice van 't
Hi Eric,
Thanks, and it sounds strange, I didnt find anything in Eventviewer either.
The problem only occured during scheduled backup. A restart of TSM scheduler
made the problem go away. So I´m temporarily happy...
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager
Yes, sorry...
5.1.5 was a baselevel also... That was a very strange releasenumber I
think it should be 5.2... but hey, my meaning is that 5.3 should be 6.1... i
don't understand the versions completely
But normaly the full versions are x.x.0.0 for servers and x.x.x.0 for
clients.
Thanks to all of you..
With a weekend of reading and some experimentation, I believe that the
problems have been overcome. I might still have lots of questions, but you
all have been very helpful.
Roark
Maurice van 't
Loo
[EMAIL PROTECTED]
No problem and I agree.
I have never read anything about the client base level requirement
before installing a patch on a Windos client.
Where did you find that information?
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Maurice van 't
With ALL events enabled, ANY admin command you send to TSM (like a Q DB)
will be logged in the event log, and therefore should be sent to your
SNMP receiver.
I have always had to stop and restart TSM AFTER you get dsmsnmp talking
for the msg forwarding to work.
Then in your TSM actlog you should
It's in the readme
- Original Message -
From: Henrik Wahlstedt [EMAIL PROTECTED]
To: ADSM-L@VM.MARIST.EDU
Sent: Tuesday, August 30, 2005 4:26 PM
Subject: [ADSM-L] Upgrade strategy - was GetBootPath: error on
QueryDosDevice()
No problem and I agree.
I have never read anything about
hi all,
after upgrading from 5.2.4 to 5.3.1
i get
tsm: TSM03disa ses
Message number 2553 not available for language /USR/LIB/NLS/MSG/EN_US/
and other similar messages !
did i forget something ?
thanks
its on AIX 5.2 ml4 p640 model
thanks
goran
Goran - From my notes in ADSM QuickFacts:
Message number not available for language EN_US
These errors are generally seen when the TSM messages filesets
are not
at the same level as the TSM Server. As a result, certain
messages do
not exist in the message repository and
We are going to be doing a Migrate Install from 5.1.9 to 5.3.1, to
facilitate the use of LTO-3 drives/tapes (Overland Neo 4100). Our host is
Windows 2000 Server, SP4, and all other updates, are installed. We
currently have a single LTO-2 (Overland Neo 4100) library attached to the
host. Current
Hi Goran,
This might help - double-check with `lslpp -l tivoli.tsm*` or similar
that your tivoli.tsm.msg message filesets are all at the same/correct
level and not still at the old level...
David
goc [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
30/08/2005 15:46
== On Tue, 30 Aug 2005 11:04:06 -0400, Nancy Jarin [EMAIL PROTECTED] said:
Hi Allen. I have received an update from the TSM development.
They agree that LDAP can be used to authenticate users. At the present time,
the embedded ISC that is installed and configured as part of the TSM
Thanks Wanda! I'm now seeing adsm SNMP output!!! I also reduced the
logging.
Thanks again for your help!!!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Prather, Wanda
Sent: Tuesday, August 30, 2005 9:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject:
Hendrik,
Is this the Windows client machine part of a cluster?
Are C: or E: on external disk?
Matt Thomas
Storage Technical Delivery Team
Service Lines (Projects)
IT Project Delivery
Group IT
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Loon,
Hi Matt,
It isn´t a cluster and both disks are internal (DAS).
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas,
Matthew
Sent: 30. august 2005 16:18
To: ADSM-L@VM.MARIST.EDU
Subject: Re: GetBootPath: error on QueryDosDevice()
Hum...
Exactly where? I havent had time to set my brain to TSM mode after three
weeks of vacation. But as far as I remember I
never had any problems what so ever installing a patch, witout
installing 5.x.y.0 first.
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintena
Another disk operations group is using IBM TotalStorage DS6000 Storage
Manager 5.0.5.281 and needed to remove it from the Win2003 server. After
doing the removal the backup group found that the backups failed that
evening. Turns out that the TSM 5.3 client, web client, scheduler and
journal
All of a sudden, lots of my Domino TDP node passwords are expiring.
Considering that:
1. I am running with PASSWORDACCESS GENERATE and there is a TSM.PWD file
in the approriate domdsmc directory
2, The server password EXPIRATION is 90-days and these systems have not
been running that long
3.
Out of order..
== On Thu, 25 Aug 2005 14:03:20 -0400, Tae Kim [EMAIL PROTECTED] said:
3. Less experienced Admins might do something funky to the directory or
files that TSM instance is running off of.
Not to be too brutal here, but anyone whom you fear will
rm -rf /usr/tivoli/tsm/server
Thanks!
I actually found out that there were some minor problems with TSM ver
5.3.1.0 but were fixed in 5.3.1.1
Here's the email that was posted to this group on 04/08/05 by a TSM
representative:
APAR IC45703 resolves an issue where ACSLS libraries are unable to mount
scratch volumes. ACLSL
32 matches
Mail list logo
