OK, I think I see what the problem is: we have two APARs that are related
to backing up system files when they are not on the C: drive: IC31758
andIC32636, both related to each other. I would expect to see a fix within
the next month or so...

On Windows 2000 and XP, SYSTEMOBJECT is part of the ALL-LOCAL domain. As a
short-term solution, you can set up a DOMAIN statement that lists all the
drives you want to back up, but excludes SYSTEMOBJECT.

Sorry I don't have a better, more immediate fix for you.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Steven Bridge <ccaasub AT UCL.AC DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/08/2002 08:47
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Problems with latest Windows client



Thanks for the rapid response Andy. The results of your
suggestions follow :

>approach. In your case, I would probably try something like this:
>
>1) Make a copy of your current dsm.opt file, then edit dsm.opt down to a
>very simple configuration, like this (use NOTEPAD, not the client
>preferences editor or setup wizard):
>
>   COMMMETHOD TCPIP
>   TCPSERVERADDRESS your.tsm.server.address
>   NODENAME yournodename
>   PASSWORDACCESS GENERATE
>
>That's it; nothing more, nothing less. Don't get fancy.   :-)

Done.

>
>2) From an OS command prompt, change into the directory where TSM is
>installed (where dsmc.exe is located). On most machines, the default is
>C:\Program Files\Tivoli\TSM\baclient. Depending on where you installed
>TSM, your configuration may differ.
>
>2) Run the command DSMC QUERY SESSION. If you can establish a session
with
>the TSM server, then your basic options file is configured correctly.
>
>3) Run this command:
>
>   DSMC S DSM.OPT
>
>Verify that the file backs up correctly.
>
>4) Now run this command:
>
>   DSMC RESTORE DSM.OPT C:\JUNK.TXT
>
>Verify that the file restores correctly. You can delete C:\JUNK.TXT, as
it
>isn't needed any more.
>
>Note that while seemingly trivial, steps 3 and 4 above are useful in
>validating at least basic function (you need to be able to walk before
you
>can run).

All OK ( although I: is the system disk on the system in question,
         so changed that ).

>
>5) Now try this command:
>
>   DSMC BACKUP SYSTEMOBJECT
>
>Does the command work? What does the output look like? If it works
>correctly, it should run for a few minutes, as it will back up all of the
>system files.

This runs but output from the constituent parts of the backup
intermingled so performed 'dsmc backup sysfiles' instead which produced
the following output :
-----------------------------------------------------------------------
Tivoli Storage Manager
Tivoli Storage Manager
*** Fixtest, Please see README file for more information ***
Command Line Backup Client Interface - Version 4, Release 2, Level 1.20
(C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved.

Node Name: BCCTEST-MS1
Session established with server ADSM: AIXRS/6000
  Server Version 4, Release 2, Level 1.7
  Server date/time: 03/08/2002 14:56:15 Last access: 03/08/2002 14:55:24

Backup System Object: 'System and Boot Files'.

Preparing System Object -> System and Boot Files
-----------------------------------------------------------------------
After about 30 secs it returns to the command prompt.
After about 30 secs it returns to the command prompt.
I saw similar for 'DSMC BACKUP SYSTEMOBJECT' but the 'Preparing System
Object'
line occurred 3 times.

Runnning the GUI and 'restore', you can see under 'system object',
Registry,
RSM,COM+DB, etc. but no sign of 'System and Boot Files'.
No errors in dsmerror.log.

>
>If the command fails or complains about something, try this command:
>
>   DSMC SHOW SYSTEMOBJECT
>
>This will show you the state of all the Windows 2000 system objects you
>have installed (such as registry, active directory, RSM, etc.). What does
>this output look like? Also, look at dsmerror.log: what is in that file?

This shows 'OK 0000' against 'System and Boot Files' and against
Registry, COM+DB, RSM and event Logs.

>
>The above steps should help get you started on understanding what is and
>is not working on your system. If you continue to have problems, you can
>post the results of the above steps to ADSM-L, and we'll see what we can
>see.

The machine in question is running Windows 200 Server and has
Metaframe XPe installed.

>
>Andy Raibeck
>IBM Software Group
>Tivoli Storage Manager Client Development

+----------------------------------------------------------------------+
 Steven Bridge     Systems Group, Information Systems, EISD
                          University College London
 email: s.bridge AT ucl.ac DOT uk                   tel: +44 (0)20 7679 2794