ADSM-L

Re: Backing Up Windows 2000 SysFiles

2000-12-28 11:47:58
Subject: Re: Backing Up Windows 2000 SysFiles
From: Len Boyle <SNOLEN AT VM.SAS DOT COM>
Date: Thu, 28 Dec 2000 11:43:29 EST
In article <C12569C3.0055B840.00 AT nlangwa3.nbg.sdv.spb DOT de>, Markus 
Stegmeier
<markus.stegmeier AT SPB DOT DE> says:
>
>Hello there,
>
>does anybody know, who to backup Windows 2000 Sysfiles. On our new Testserver
>the backup systemobjects fails with a user abort "ANS1074I". It seems the
p
>backu
>sysfiles found no sysfiles.... why?
>
>Best regards.
>
>Markus Stegmeier

Hello Markus
This appears to be a new and improved bug with the 412 client.
I assume that IBM/Tivoli will have a fixtest out soon for this problem
as they have had the problem  for a week and normally they are pretty
quick with a patch. But I also assume that holiday schedules are slowing
things down a little bit.
/len

Item IC29182





  APAR Identifier ...... IC29182      Last Changed ........ 00/12/21
  TSM 4.1.2 WINDOWS CLIENTS FAILS INCREMENTAL WITH DR. WATSON.
  APPEARS TO BE OCCURING ON BACKUP OF SYSTEM OBJECTS.

  Symptom ...... AB ABEND             Status ........... OPEN
  Severity ................... 2      Date Closed .........
  Component .......... 5698TSMCL      Duplicate of ........
  Reported Release ......... 41W      Fixed Release ............
  Component Name TIVOLI STR MGR       Special Notice
  Current Target Date ..01/04/21      Flags
  SCP ................... UNIX
  Platform ............ UNIX

  Status Detail: Not Available

  PE PTF List:

  PTF List:


  Parent APAR:
  Child APAR list:


  ERROR DESCRIPTION:
  The TSM 4.1.2 Windows client may fail with a Dr. Watson during
  an incremental backup. The problem appears to be occuring when
  the client is backing up the system objects. The failure also
  appears only to occur when a full filesystem backup exists for
  the give node. The original failure reported by the customer
  showed up as a popup window titled Application Error with the
  following text:
  The insruction at "0x780142c1" referenced memory at "0x0052ffb6"
  The memory could not be "read".
  The customer also reported an occurance of the failure with
  an access violation (0xc0000005) Address: 0x780142c1 in the
  Application Error popup window.
  THe reporting customer was running NT 4.0 sp6a
  Recreate attempts in house have resulted in other exception
  numbers being reported.
  The problem only seems to appear on the command line client. The
  GUI seems to work just fine. Additional testing on other Windows
  machines have not resulted in the failure on a regular basis.
  Initial Impact: High


  LOCAL FIX:
  Using a new nodename to obtain a new full backup appears to
  work.

-------------------------------------------------------------------------
Leonard Boyle                               snolen AT vm.sas DOT com
Leonard Boyle                               snolen AT vm.sas DOT com
SAS Institute Inc.                          ussas4hs@ibmmail
Room RB448                                  len.boyle AT sas DOT com
1 SAS Campus Drive                          (919) 531-6241
Cary NC 27513
<Prev in Thread] Current Thread [Next in Thread>