We just ran into a problem when backing up sysfiles when system files -
ntldr, boot.ini etc are on a drive other than C: drive. See apar below.
Search for a drwatsn32.log file to see if this is your problem.
APAR= IC32636 SER= IN INCORROUT
DR. WATSON IS WITNESSED WHEN BACKING UP SYSFILES IF SYSTEM FILES NTLDR,
BOOT.INI, ETC. ARE ON A DRIVE OTHER THAN C:
STAT= CLOSED PER FESN0907344- CTID= SJ0291 ISEV= 1
SB02/01/17 RC02/01/18 CL02/01/24 PD SEV= 1
PE= TYPE= F
RCOMP= 5698TSMCL TIVOLI STR MGR RREL= R42W
FCOMP= 5698TSMCL TIVOLI STR MGR PFREL= F999 TREL= T
ACTION= SEC/INT= DUP/
USPTF= PDPTF= DUPS 0
DW02/01/17 RT02/01/18 SC FT RE
PT UP LP PV02/01/24 AP
EN FL LC02/01/24 RU02/01/24 OT
CT FR TD TYPE OF SOLUTION=
PROJECTED CLOSE CODE= CUST INST LVL/SU= 42W
FAILING MODULE: DSMC FAILING LVL/SU= 42W
SYSROUTE OF: RET APAR= PS= S
STATUS DETAIL= RELIEF AVAILABLE=
SCP: UNIX PLATFORM: UNIX
HIPER SYMPTOMS:
DATALOSS/N SYSTEMOUTAGE/N FUNCTIONLOSS/N
PERFORMANCE/N PERVASIVE/N
XSYSTEM/N
SPEC/ATTN/N
SYSRES= SYSIN= SYSOUT= CPU= RE-IPL=
OPTYPE= SPECIAL ACTIVITY= REGRESSION=
PRE-SCREEN NO.= RSCP= RS42W
ERROR DESCRIPTION:
When performing a backup of the sysfiles a Dr. Watson is
witnessed:
if using the Scheduler:
FAULT ->004482ff 8b590c mov ebx,[ecx+0xc] ds:0083d5d2=0
if using the GUI:
FAULT ->004c7c1f 8b590c mov ebx,[ecx+0xc] ds:0083d5d2=?
if using the CommandLine Client:
FAULT ->0044620f 8b590c mov ebx,[ecx+0xc] ds:0083d5d2=?
The Dr. Watson is witnessed if the sysfiles are requested for backup
directly or as part of the systemobject. The problem has been seen on NT and
on NT Citrix Metaframe. For the NT machine drive D: was the boot drive when
this problem was witnessed. For the Citrix machines the C: is changed to a
drive suchas
M: or O: during the citrix installation.
LOCAL FIX:
Can use the SUBST command to remap the C: drive as the location that
contains the system files.
SUBST C: M:
.
Ensure that the system boot files are on C:
"ntldr", "boot.ini", "ntbootdd.sys","ntdetect.com","arcldr.exe",
"arcsetup.exe"
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: Win NT/2k/XP *
****************************************************************
* PROBLEM DESCRIPTION: DR. WATSON IS WITNESSED WHEN BACKING *
* UP SYSFILES IF SYSTEM FILESNTLDR, *
* BOOT.INI, ETC. ARE ON A DRIVE OTHER *
* THAN C: *
****************************************************************
* RECOMMENDATION: *
****************************************************************
DR. WATSON IS WITNESSED WHEN BACKING
UP SYSFILES IF SYSTEM FILESNTLDR,
BOOT.INI, ETC. ARE ON A DRIVE OTHER
THAN C:
PROBLEM CONCLUSION:
The source of the problem was fixed by IC31758. This is an additional fix to
the main fix from defect 30954 for IC31758. TEMPORARY FIX:
COMMENTS:
MODULES/MACROS: DSMC DSM DSMSVC
SRLS: NONE
RTN CODES:
APPLICABLE COMPONENT LEVEL/SU:
R42W PSY UP
CIRCUMVENTION:
MESSAGE TO SUBMITTER:
CUST NAME= ALLEGHENY ENERGY SERVICE CORP CUST NO= 0138405
STREET= PROB NO= 48559,111
CITY= LICENSE=
ZIP=
CUST REP= Mark Basenback PHONE= 724 830 5389
BO NAME= NCMD PITTSBURGH CENTRAL AREA =AR# 04
IBM BLDG. 4 ALLEGHENY CENTER B.O. NO=B SP7
PITTSBURGH, PA. COUNTRY=C 000
X 15212 AST CT= IP CT= 2
WONG, CHRISTOPHER K. / 56041 Y B 999 AR# 99 C 000
PANG, KATHY / 86156 Y B 344 AR# 02 C 000
TRACKING:
CREATED CR02/01/17 CRSJ0291 INCIDENT TRANSFER 1743
RECEIPT RT02/01/18 RTSJ0291 1048
RECEIVED RC02/01/18 RCSJ0291 1048
ASSIGN AS02/01/18 ASSJ0291 999999 UQ2 1048
ASSIGN AS02/01/18 ASSJ0291 MINSK 1050
EDIT SB02/01/18 SB109714 INTERESTED PARTY PAGE 2 1523
ASSIGN AS02/01/21 ASSJ0291 MINSK/BELYAVSKY 0253
EDIT SB02/01/23 SB974547 INTERESTED PARTY PAGE 2 1426
CLOSED CL02/01/24 CLSJ0291 PER 0543
-----Original Message-----
From: Steven Bridge [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 08, 2002 9:47 AM
To: [EMAIL PROTECTED]
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
*** 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.
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: [EMAIL PROTECTED] tel: +44 (0)20 7679 2794
