Hey guys.
We have four TSM servers (long story, don't ask) across two sites,
setup with one as a config manager, the other three all subscribing to
the config pushed out by the manager. For various DR reasons, we're
wanting to do data exports from those four servers to a fifth server,
located at a completely different site to any of the four main servers.
These exports are for a limited subset of the servers being backed up,
and there's no easy way to separate them from the not-to-be-exported
hosts in terms of policy domains, storage pools, etc. At the moment,
the intent is to use the "export node" command to push the data across
directly to the fifth TSM server.
I've defined the server links and the requisite administrators. I've
also -- by way of experimentation as much as anything else -- set up
the fifth server to subscribe to the same config pushed to the other
servers. I'm now finding that, whenever I try to export a server
directly to this fifth server, I get a bunch of error messages in the
logs. Some of them are relatively spurious[1]; others, however, are of
concern[2].
I've had similar problems previously, which were rectified by changing
the version of the TSM server software running on each host to match
(they're all running version 5, release 2, level 3.2 now). I'm pretty
sure these problems only started after I made the fifth server a
managed server, rather than being mostly independent.
So. Questions.
* Can a server to which data is being exported directly over the
network be managed, or must it be completely independent?
* If it can be managed, how can the spurious errors about managed
objects be suppressed?
* If it can only be managed for certain config items, what are the
restrictions on what can and cannot be managed?
* If it _can't_ be managed, I'm curious to know why not. (This one
doesn't really matter beyond satisfying my curiosity :)
* Presumably, there is no problem with making the server link
information for the importing server managed -- that the issue is
purely with making the importing server managed by one of the exporting
servers?
Having managed profiles would make a number of things a lot easier, but
if I have to live without them, so be it. Also, if there are any trips
or traps that would be useful to know, I'd greatly appreciate knowing
them. :)
If there are any details that need to be disclosed for this one to be
tracked down, let me know; I'm well aware that the above is rather
vague, but it's hard to know when you're just setting out what might be
relevant and what might not be.
Thanks for any and all advice you can give,
Stuart.
[1] For example:
01/25/2005 11:14:45 ANR0646I IMPORT (from Server TSM1): DEFINE
CLIENTOPT:
AM Command cannot be executed - option set NW is a
managed
object. (PROCESS: 27)
01/25/2005 11:14:45 ANR0730E IMPORT (from Server TSM1): Internal
error from
AM command 'DEFINE CLIENTOPT NW INCLEXCL "exclude
sys:\vol$log.err" FORCE=Yes SEQNUMBER=11'.
(PROCESS: 27)
01/25/2005 11:14:45 ANR3229E DEFINE CLIENTOPT: Command cannot be
executed -
AM option set NW is a managed object. (SESSION:
4560,
PROCESS: 27)
[2] Prime case in point:
01/25/2005 11:14:45 ANR0730E IMPORT (from Server TSM1): Internal
error from
AM command 'REGISTER NODE SOMENODENAME XXXX
DOMAIN=NW_PD
CONTACT=" " COMPRESSION=CLIENT ARCHDELETE=YES
BACKDELETE
=NO URL="SOMENODENAME.its.monash.edu.au:2002"
CLOPTSET="
NW" FILEAGGR=YES AUTOFSRENAME=NO
VALIDATEPROTOCOL=NO
DATAWRITEPATH=ANY DATAREADPATH=ANY
SESSIONINIT=CLIENTORS
ERVER TYPE=CLIENT'. (PROCESS: 27)
01/25/2005 11:14:45 ANR0728E IMPORT (from Server TSM1): Processing
terminated
AM abnormally - internal error. (PROCESS: 27)
01/25/2005 11:14:45 ANR0620I IMPORT (from Server TSM1): Copied 0
domain(s).
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0621I IMPORT (from Server TSM1): Copied 0
policy sets.
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0622I IMPORT (from Server TSM1): Copied 0
management
AM classes. (PROCESS: 27)
01/25/2005 11:14:45 ANR0623I IMPORT (from Server TSM1): Copied 0 copy
groups.
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0624I IMPORT (from Server TSM1): Copied 0
schedules.
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0625I IMPORT (from Server TSM1): Copied 0
administrato
AM rs. (PROCESS: 27)
01/25/2005 11:14:45 ANR0891I IMPORT (from Server TSM1): Copied 0
optionset
AM definitions. (PROCESS: 27)
01/25/2005 11:14:45 ANR0626I IMPORT (from Server TSM1): Copied 0 node
AM definitions. (PROCESS: 27)
01/25/2005 11:14:45 ANR0627I IMPORT (from Server TSM1): Copied 0 file
spaces 0
AM archive files, 0 backup files, and 0 space
managed files.
(PROCESS: 27)
01/25/2005 11:14:45 ANR0628I IMPORT (from Server TSM1): Used 0
volume(s).
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0629I IMPORT (from Server TSM1): Copied 22
bytes of
AM data. (PROCESS: 27)
01/25/2005 11:14:45 ANR0634I IMPORT (from Server TSM1): Detected 18
errors.
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0611I IMPORT (from Server TSM1) started by
EXPORT as
AM process 27 has ended. (PROCESS: 27)
01/25/2005 11:14:45 ANR0988I Process 27 for IMPORT (from Server TSM1)
running
AM in the BACKGROUND processed 22 bytes with a
completion
state of FAILURE at 11:14:45 AM. (PROCESS: 27)
01/25/2005 11:14:45 ANR0440W Protocol error on session 4559 for node
EXPORT
AM (Solaris 8/9 ) - invalid verb header received.
(PROCESS:
27)
01/25/2005 11:14:45 ANR3174E Communication error with managed server
EXPORT.
AM (PROCESS: 27)
01/25/2005 11:14:45 ANR0484W Session 4559 for node EXPORT (Solaris
8/9 )
AM terminated - protocol violation detected.
(PROCESS: 27)
|
