Conference cookie::archive_backup

455.0. "%CMA-F-EXCCOP,SYSTEM-F-ACCVIO from WNT backups" by ATZIS1::KARTNER_M (HOUSTON, we have a problem) Wed May 14 1997 11:14

    Hi!
    
    Is there a known problem with INCREMENTAL BACKUPS of NT clients ?
    The save requests at the customer site that run FULL BACKUPS work
    fine but all incremental tries result in an accvio
    
    %CMA-F-EXCCOP, exception raised; VMS condition code follows
    -SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=0000000
    0, PC=805AD290, PS=0000001B
    No Exception Information blocks currently exist.
    No Exception Information blocks currently exist.
    THREAD #1:  EXCEPTION: `([, module = $��, line = 6678048
    THREAD #1:  Unexpected exeception in Data Mover
    THREAD #1:
    COORDINATOR:  Completed with failure status
    
    Following the complete logfile. The used storage class works with
    the full WNT backups so there should be no problem from MDMS. 
    

Executing ABS LOGIN.COM
Completed execution of ABS LOGIN.COM
"@abs_system:coordinator.com 905F8A6E-CB74-11D0-B45E-574241435331" Executing, output follows :
------------------------------------------------------
---------------------------------------------------------------
Starting New Request at 13-MAY-1997 09:38:13.16
   Name:   TSY87_INC_SR
   UID:    905F8A6E-CB74-11D0-B45E-574241435331   

COORDINATOR:  Attempting to allocate volume set AMD707...
COORDINATOR:  Mounting volume set member: AMD707 RVN 1
COORDINATOR:     (Selected drive WBACS1$MKD300:)
%MOUNT-I-MOUNTED, AMD707 mounted on _WBACS1$MKD300:
COORDINATOR:  Skipping WBACS1$MKD300: to End of Tape...
THREAD #1:  Agent information has been altered 
THREAD #1:  Facility ABS:  ABS_AGENT_INFO_ALTERED, Agent information has been altered 
THREAD #1:     Line = 326, File = RESD$:[SRC]CHECKSUM_AGENT.C;1 
THREAD #1:  Facility ABS:  ABS_AGENT_CHECKSUM_ERROR, Error checksumming agent information 
THREAD #1:     File: ABS$TEMPLATES:NT_GTAR-1.PARSE_TEMPLATE 
THREAD #1:   

Operation #1 starting at 13-MAY-1997 09:39:41.98

   Data Movement Type:    INCREMENTAL_SAVE
   Incremental Level:     Level 1 Operation

   Object Set:
      Object Type:        WINDOWS NT FILES GTAR
      Include List:       C:\
      Exclude List:       

   Archive Information:
      Storage Class Name: TSY87_SC
      Saveset Location:   AMD707
      Saveset Name:       13MAY19970938132.

   Execution Environment:
      Name:               NT_ENV
      Number of retries:  0
      Retry Interval:     0 minute(s)


THREAD #1:  $  
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC=805AD290, PS=0000001B
No Exception Information blocks currently exist.
No Exception Information blocks currently exist.
THREAD #1:  EXCEPTION: `([, module = ��, line = 6678048 
THREAD #1:  Unexpected exeception in Data Mover 
THREAD #1:   
COORDINATOR:  Completed with failure status
COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failure status
COORDINATOR:     EXCEPTION: `([, module = ��, line = 6678048
COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failure status
COORDINATOR:     Line = 1463, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
COORDINATOR:  Dismounting volume set member: AMD707 RVN 1
COORDINATOR:  Final status is Completed with failure status
%SYSTEM-F-OPINCOMPL, operation is incomplete
  ABS          job terminated at 13-MAY-1997 09:39:53.41

  Accounting information:
  Buffered I/O count:             641         Peak working set size:  11536
  Direct I/O count:               201         Peak page file size:    65984
  Page faults:                   1059         Mounted volumes:            2
  Charged CPU time:           0 00:00:00.50   Elapsed time:     0 00:02:03.71
    

    
    The problems was formally submitted to ABS engineering as an IPMT case.
    Case number CFS 51244.  Since Engineering is obligated to submit formal
    responses and updates to the IPMT cases, we will not be responding to
    this notesfile entry.  Please communicate further through the mechanism
    of IPMT.  It will not leave engineering any choice of how to handle the
    problem when it is submitted as an PMT.

    One thing to note is that you will probably find the response time of 
    IPMT case much slower than communicating through the notesfile. It goes
    through several IPMT processing layers and with the time difference
    between Europe and Colorado, one round of communication takes AT LEAST
    one day through IPMT.

    Thanks,
    Masami

     

     

    
    Hi,
    
    Someone from the U.S. corrected me that one day minumum turn around time 
    of IPMT case does not apply to the U.S. sites due to smaller time 
    differences in time zones.
                 
                 Masami