As I mentioned the majority of my Windows 2000 servers have TSM Client
V5.1 and have had no problems with backing up 'domain all-local'. Then
we started installing V5.2.2 on Windows 2003 and started seeing the
'RC=12 error message'. We scrubbed that version and started installing
with V5.2.2.10. We occasionally see this 'RC=12' problem failed back
ups even using V5.2.2.10.
I was working with IBM Support on these issues and this is the solution
that was generated from them:
"The problem documented in the Apar IC38377 is generated by the TSM
Client, then upgrading the TSM Server does not fix the problem, it is
fixed if the current Client is upgraded to v5.2.2.10.
To split the backups you should modify in the dsm.opt file, the line:
Domain All-Local
changing it to:
Domain C: D:
With this change, the current scheduled task will perform the backup of
all the information on the C and D disks but not the OS files.
Then you can create a command file (for example OSfiles.cmd) in the
directory Baclient, with the instructions to backup the System State,
System Services and the ASR files:
dsmc backup systemstate
dsmc backup systemservices
dsmc backup asr
And also a new scheduled task in the TSM Server must be created to run
the command file OSfiles.cmd, this schedule will use ACTION=COMMAND and
OBJECTS=OSfiles (<-- or the name you chose for the cmd file).
Melinda Cooper
Senior Information Center Analyst
Work - 425.783.4467
Pager - 425.438.5981
-----Original Message-----
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 20, 2004 8:16 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Client V5.2.2.10 for Windows 2000/2003
Hi Melinda,
Can you provide more information about the problem? The dsminfo.txt file
created by the "dsmc query systeminfo" command would be helpful (make
sure
you use the same dsm.opt file as your scheduler uses). You can attach
dsminfo.txt in a response. Also, check the server activity log to see
what
messages are issued therein at the time this problem occurs. What are
these messages?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 07/20/2004
07:59:54:
> This has been very frustrating for us since when you review the log
> files it says that the system objects and files have successfully been
> backed up.
>
> This is the error code:
> ANS1026E Session rejected: Communications protocol error.
> Explanation: Communications protocol error. An unexpected
communications
> message was received by the client.
> System Action: ADSM canceled the current operation.
> User Response: Verify that your communication path is functioning
> properly. If the problem continues, have your service representative
> check for a possible program error.
>
> So at this point I don't know if it's in the dsm.opt file for with the
> Unix server that has the TSM software.
