Results 1 to 12 of 12
-
05-21-2007, 10:17 AM #1
Dual Server Install on one physical server
Hi there, I need to install a second instance of TSM Server on an already existing, up and running TSM Server. Do I simply click the install package? (It's on Win2k3) and choose another server name, or is there a recommended way to do this?
Many thanks
-
05-21-2007, 12:45 PM #2Senior Member
- Join Date
- Nov 2005
- Location
- LU Germany
- Posts
- 1,066
- Thanks
- 0
- Thanked 1 Time in 1 Post
If you absolutely want to, you can do it manually, but "create another TSM server instance" or whatever its called in the installation wizard will be much simpler.
PJ
-
05-21-2007, 12:52 PM #3Moderator
- Join Date
- Dec 2003
- Location
- Czech Republic
- Posts
- 2,056
- Thanks
- 2
- Thanked 59 Times in 58 Posts
Hi,
use TSM Management Console, under "Tivoli Storage Manager" locate the server and after right click select "Add a new TSM server ..."
no need to run installer again
Harry
-
05-22-2007, 04:31 AM #4
Thanks for the help guys, I've installed the server, gave it a name, it's up and running, I've made the entries in dsm.sys so that I can log into it.... and it logs me into "Server 1" rather than "Server 2". I'm guessing it get this from the I.P. address entry in dsm.sys. The I.P. is always going to be the same, as it's obviously referencing the physical windows server, but how do I log into the individual server instances? I can run commands on it from the management console, but I want to log in on a remote unix box, using putty, as I do for all the other servers, as in:-
dsmadmc -server=drserver
... and it's not playing..
Thanks
-
05-22-2007, 05:03 AM #5Moderator
- Join Date
- Dec 2003
- Location
- Czech Republic
- Posts
- 2,056
- Thanks
- 2
- Thanked 59 Times in 58 Posts
Hi,
dsmadmc -tcpserveraddress=server2.whatever.com -tcpport=xyz
xyz is from dsmserv.opt of server2
Hope it helps
Harry
-
05-22-2007, 05:40 AM #6
dsmadmc -tcpserveraddress=server2.domain.co.uk -tcpport="c:\program files\tivoli\tsm\server2\dsmserv.opt"
This returns command line parameter is not valid?
Thanks
-
05-22-2007, 05:57 AM #7Moderator
- Join Date
- Dec 2003
- Location
- Czech Republic
- Posts
- 2,056
- Thanks
- 2
- Thanked 59 Times in 58 Posts
Hi,
sorry, was not clear enough ..... not the PATH to the dsmserv2.opt ... the port NUMBER you can find in that file
By default first server listens on 1500, second on 1501 etc ....
So try 1501 first and if it does not help, then look into the file for the port number
Hope it helps
Harry
-
05-22-2007, 07:32 AM #8Moderator
- Join Date
- Nov 2005
- Location
- Victoria, Australia
- Posts
- 537
- Thanks
- 0
- Thanked 0 Times in 0 Posts
-
05-22-2007, 07:40 AM #9
Using the management console command line, I can access the new server, a q status shows:-
tcp port number: 1501
...so that's ok.
I think my problem is that the TSM Server on the Unix box I use to access all my TSM Servers via putty is at Version 5.2.2, and it does not recognise the paramters. How else will I get putty to access this server for command line usage as I prefer to do? Windoze "cmd" is of no use, and I'd rather not use the management console command prompt....
Thanks for the help
-
05-22-2007, 08:06 AM #10Moderator
- Join Date
- Nov 2005
- Location
- Victoria, Australia
- Posts
- 537
- Thanks
- 0
- Thanked 0 Times in 0 Posts
Hang about... Both of your servers are trying to access port 1501?
When running multiple servers in a UNIX environment (surely windows is the same) you would usually make something like hops of 100 for your ports...
Now because 1500 is the default, I would be considering having neither server use that. Also have you defined a tcpadminport?
-
05-22-2007, 09:45 AM #11
Just the second DR Server is set to 1501, the first is 1500.
I could do all the config. via the Management Console command line, but would prefrer the freedom putty offers.
-
05-24-2007, 01:32 AM #12Member
- Join Date
- May 2004
- Location
- Victoria, Australia
- Posts
- 165
- Thanks
- 3
- Thanked 0 Times in 0 Posts
It doesn't matter what OS the TSM server is running on, but once you have multiple server instances running, the only differentiation is the TCP port. 1500 default (server1), 1501 for (server2) etc. specified in the server options file.
You can run dsmadmc from any machine on any operating system to administer the server instances, as long as you've custom installed the TSM client and selected Administrative Command Line Interface'. You also should do this on the server even if you aren't going to backup the server as such, just so you can schedule jobs against itself etc and have access to this interface.
On a windows client for example, after I installed the extra's and was able to administer the first server, I then copied the default dsm.opt to dsm.server2.opt. Then edited the dsm.server2.opt and changed the 'tcpport 1500' option to 'tcpport 1600' (in my case).
Now you can run 'dsmadmc -optfile=dsm.server2.opt -id=admin -pa=admin' to access and administer the new server instance from anywhere.


Reply With Quote
