Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*update\s+server\s+roles\s*$/: 7 ]

Total 7 documents matching your query.

1. update server roles (score: 1)
Author: BEYERS Kurt <Kurt.BEYERS AT VRT DOT BE>
Date: Fri, 6 Oct 2006 11:10:34 +0200
Hello, In the output of a server definition in TSM (TSM server 5.3.2.4, TSM BA client 5.3.2 and STA 5.3.2.1), multiple roles are defined: q server SERVER f=d Server Name: SERVER Comm. Method: TCPIP H
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00089.html (13,427 bytes)

2. Re: update server roles (score: 1)
Author: Matthew Warren <Matthew.Warren AT DIGICA DOT COM>
Date: Fri, 6 Oct 2006 14:18:14 +0100
I could be missing something, but I cant off the top of my head understand(remember?) why TSM1 is communicating to TSM2 to update a storage agent/server definition at all? Even though TSM1 is a libra
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00090.html (17,014 bytes)

3. Re: update server roles (score: 1)
Author: BEYERS Kurt <Kurt.BEYERS AT VRT DOT BE>
Date: Fri, 6 Oct 2006 16:28:04 +0200
Matt, The server name of the Linux STA is the same on both TSM servers, although they are listening on different TCP/IP ports of course. Indeed when the STA to TSM1 is started, it ends up talking to
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00093.html (18,431 bytes)

4. Re: update server roles (score: 1)
Author: Matthew Warren <Matthew.Warren AT DIGICA DOT COM>
Date: Fri, 6 Oct 2006 15:56:27 +0100
By this; Do you mean the data? If so, as I understand it, TSM1 will have the PATH definitions for the storage agent which tie drive names to /dev entries on the client. You would have the drives in t
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00094.html (20,819 bytes)

5. Re: update server roles (score: 1)
Author: Matthew Warren <Matthew.Warren AT DIGICA DOT COM>
Date: Fri, 6 Oct 2006 16:38:04 +0100
Apologies. It actually works opposite to how I thought; When the Tivoli Storage Manager server (data manager server) is also the library manager for the devices where data is stored by the storage ag
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00095.html (21,362 bytes)

6. Re: update server roles (score: 1)
Author: BEYERS Kurt <Kurt.BEYERS AT VRT DOT BE>
Date: Fri, 6 Oct 2006 20:06:02 +0200
Matt, I guess the problem description was not yet complete. The desired setup is as follows Each TSM server has it's own library (LIB1 for TSM1 and LIB2 for TSM2): The backups taken by the STA1 on th
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00101.html (22,270 bytes)

7. Re: update server roles (score: 1)
Author: Matthew Warren <Matthew.Warren AT DIGICA DOT COM>
Date: Mon, 9 Oct 2006 10:09:19 +0100
Hi, Ah, I didn't realise TSM1 had a LIB1. For some reason though, I had got stuck on the idea that storage agents don't go direct to libraries, they go through the library client, which is wrong. Alt
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2006-10/msg00116.html (25,099 bytes)


This search system is powered by Namazu