Quick observation. Look at the two commands...
dsmftm -log D:\tsmdata\server1\extrareclogspace
dsmserv extend log extrareeclogspace
The name of the log changes from 'extrareclogspace' to
'extrareeclogspace'.
There is an additional 'e' in the extend command. Please verify your
command syntax, I will cross my fingers and we'll hope it works!
Good Luck!
John G. Talafous
Berbee Information Networks
john.talafous AT berbee DOT com
http://www.berbee.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David McClelland
Sent: Tuesday, August 23, 2005 11:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] server 5.1.9.0 rec log problem - multiple servers?
Importance: High
Alex,
Be more explicit in your dsmserv extend log command - give the full
path, e.g.
>>> dsmserv extend log d:\tsmdata\server1\extrareclogspace 800
at the moment, it's looking for it in your PWD, not where you defined it
in the first place.
Take onboard Wanda's note about breaking the 13GB log size too - good
luck, let us know how you get on.
Rgds,
David McClelland
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Alexander Lazarevich
Sent: Tuesday, August 23, 2005 10:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] server 5.1.9.0 rec log problem - multiple servers?
TSM 5.1.9.0 server on win2K server. I've got a very confusing problem,
and our server is totally dead at the moment so I'm in a bit of an
emergency.
We've been running TSM 5.1.6.5 for 2-3 years, I recently (8 months ago)
upgraded to 5.1.9.0, no problems. Last night, we ran out a tapes, and
therefor the automatic backup of the database couldn't happen, and
therefor the rec log filled up to maximum, and the server died and
cannot restart until I increase the size of the log. Easy enough, I've
had to do this before, but the standard commands are not working:
dsmftm -log D:\tsmdata\server1\extrareclogspace 8000 that works fine,
create/formats the new volume, but then:
dsmserv extend log extrareclogspace 8000, dies with:
C:\Program Files\tivoli\tsm\server1>dsmserv extend log extrareeclogspace
8000 ANR0900I Processing options file c:\program
files\tivoli\tsm\server1\dsmserv.opt
ANR7800I DSMSERV generated at 10:06:54 on Mar 18 2004.
Tivoli Storage Manager for Windows
Version 5, Release 1, Level 9.0
Licensed Materials - Property of IBM
5698-ISE (C) Copyright IBM Corporation 1999,2002. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR0200I Recovery log assigned capacity is 12000 megabytes.
ANR0201I Database assigned capacity is 32000 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR9969E Unable to open volume C:\PROGRAM
FILES\TIVOLI\TSM\SERVER1\EXTRAREECLOGSPACE.
The most likely reason is that another TSM server is running and has the
volume allocated.
ANR9999D admstart.c(3483): ThreadId<23> Error 31 from lvmAddVol.
ANR7835I The server thread 1 (tid 1448) terminated in response to server
shutdown.
ANR7835I The server thread 22 (tid 1548) terminated in response to
server shutdown.
ANR7835I The server thread 23 (tid 1096) terminated in response to
server shutdown.
ANR0991I Server shutdown complete.
The problem is, we don't run two servers. We've got one server, that's
all we've ever had, that's all we want. And this brings me back to
something I've noticed since I first installed the server, which I
thought was
normal:
In C:\Program Files\tivoli\tsm\ there are two server folders. a "server"
and a "server1". In the "server" folder that's where most of the
executables live, like dsmserv.exe and dsmsvc.exe. In "server1" folder
there are .opt .log and .bat files, among others. But definately, it
seems that the guts of the server live in "server" folder.
However, the TSM management console window lists "TSM Server1" as the
real server, it doesn't even see "Server". Whenever I have to deal with
the MMC window, which I try to avoid at all costs, it only ever lists
Server1, never just Server. As far as I remember, Server and Server1
have always both existed from when I first setup TSM 5.1.6.5 and it
seemed wierd to me, but everything worked, so I thought Server1 and
Server were somehow intertwinned, but they were basically the same
server. Maybe that is wrong, and only now is the problem showing itself.
Anyone have an idea? Again, we are down 100% until I can increase the
reclog size.
Thanks in advance,
Alex
--------------------------------------------------------
If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to
this e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------
|
