Conference cookie::archive_backup

453.0. "NT backups appears to loop." by CX3PST::BSS::SAUL () Tue May 06 1997 13:34

Hi again,

I have a customer attempting to backup a complete drive from a AXP 4.0 NT
system.  She gets about 10 minutes into it before it appears to start looping. 
On the VMS side she says there is lots of Buffered I/O but no Direct I/O.  On
the NT side she gets:

ABSgtar.exe - Application Error

The exception unknown softeware exception (0xc0000008) occoured in the 
application at location ox77f4e9ac

Click on OK to terminate the application


I'm having her check her quotas for the TCP protocol.  This is the customer
using multinet.  Thanks for any pointers.

Ted

********************************************************************************

The save command looks as follows:

Save Request
    Name            - NT_TEST_4
    Version         - 12
    UID             - F467AFC1-C54A-11D0-B0B4-564D53313020   
    Movement Type     - SELECTIVE_ARCHIVE 
    Data Object Set
        Sequence Option    - SEQUENTIAL
        Commit Option - KEEP_PARTIAL
        Node Name - AXPNTSA
        Include Spec - C:\
        Exclude Spec - \PERFMON\
        Object Type Name - WINDOWS_NT_FILES_GTAR
        Agent Qualifiers - 
        Data Safety Options - CRC_VERIFICATION
        Compression Options - None
        Source File System Options - FILE_HOT_BACKUP, FILE_IGNORE_WRITERS
        Span Filesystem Options - SPAN FILESYSTEMS
        Symbolic Links Option - LINKS_ONLY
        Object Date Options - None
        Selection Options - None
        Restore Options - RETAIN_EXISTING_VERSIONS 
        Date Identifier - NONE
        Low Limit Date - 17-NOV-1858 00:00:00.00
        High Limit Date - 17-NOV-1858 00:00:00.00
    Owner     - VMS10::WONG
    Access Right - VMS10::WONG
        Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
    Media Management Info
        Storage Class Name - OMT_BACKUPS
        Media Type - None
        Device Name - None
        Start Time - NOW
        Schedule Interval - ONE_TIME_ONLY
        Explicit Interval -  
        Special Day On - None
        Special Day Off - None
        Execution Envir - OMT_BACKUPS_ENV
        Storage Class retention value used.
        Original Object Action - NO_CHANGE
    Restart Interval - 17-NOV-1858 00:00:00.00
    Wait Flag - NO
    Prologue Command - None
    Epilogue Command - None

*******************************************************************************

The tail of the log file:

THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9383--:8673 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9382--:8672 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9383--:8673 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9384--:8674 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9384--:8674 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9385--:8675 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9385--:8675 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9386--:8676 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9386--:8676 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9387--:8677 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9387--:8677 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9388--:8678 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9389--:8679 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9388--:8678 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9389--:8679 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9390--:8680 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9391--:8681 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9390--:8680 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9392--:8682 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9391--:8681 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9392--:8682 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9393--:8683 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9393--:8683 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9394--:8684 
THREAD #1:  %ABS-I- Packet Size: 10240 delay : -114 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9394--:8684 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9395--:8685 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9396--:8686 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9395--:8685 
THREAD #1:  %ABS-I-Disk:528 OutOfSeqPacket:9396--:8686 
THREAD #1:  %ABS-I- Id: 512 Packet error status: 8428request for: 10240 bytes 
THREAD #1:  %SYSTEM-F-LINKDISCON, network partner disconnected logical link 
THREAD #1:  %ABS-I- Packet Size: 32 delay : -114 
THREAD #1:  %ABS-I- Socket Shutdown phase 2 
THREAD #1:  %ABS-I Socket:512 Bytes processed:8.89549e+07 
THREAD #1:  %ABS-I-Shutdown Phase 1 
THREAD #1:  %ABS-I- Socket Shutdown phase 2 
THREAD #1:  %ABS-I Socket:512 Bytes processed:8.89549e+07 
THREAD #1:  %ABS-I-Shutdown Phase 1 
THREAD #1:  %ABS-I- Socket Shutdown phase 2 
THREAD #1:  %ABS-I Socket:544 Bytes processed:130109 
THREAD #1:  %ABS-I-Shutdown Phase 1 
THREAD #1:  %%Status 1 
THREAD #1:  %ABS-I- Socket Shutdown phase 2 
THREAD #1:  %ABS-I Socket:512 Bytes processed:131 
THREAD #1:  %ABS-I-Shutdown Phase 1 
THREAD #1:  %ABS-I-Disk: Shudown Phase 2 
THREAD #1:  %ABS-I-Disk:528 BusyQue Length:0 
THREAD #1:  %ABS-I-Disk:528BytesReceived:88954880 
THREAD #1:  %ABS-I-Disk:528 Total Bytes Processed:8.89549e+07 
THREAD #1:  %ABS-I-Shutdown Phase 1 
THREAD #1:  %ABS --UBS SUCCESS-- Gtar status may vary 
THREAD #1:  $  
THREAD #1:  Normal successful completion 
THREAD #1:   
COORDINATOR:  Completed with failure status
COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failure status
COORDINATOR:     %%Status 1
COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failure status
COORDINATOR:     Line = 1463, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
COORDINATOR:  Final status is Completed with failure status
%SYSTEM-F-OPINCOMPL, operation is incomplete
  ABS          job terminated at  5-MAY-1997 15:09:32.38

  Accounting information:
  Buffered I/O count:            4440         Peak working set size:  11776
  Direct I/O count:              4721         Peak page file size:    66720
  Page faults:                   1029         Mounted volumes:            0
  Charged CPU time:           0 00:01:33.76   Elapsed time:     0 00:15:01.47

********************************************************************************
The NT Event Log:


Event Detail
Event ID: 112
Source: ABSClient

Description:
The ABSClient service completed Save/Restore request.
Request completed with status 1073807364.

Note that other times the status has been 1073741816.

Any ideas on this???

    
    Ted,
    
    The customer is using multinet.  We are not able to provide support
    for it, until we claim official multinet support in the future.
    
    Masami
    
    

Ted,

Sorry that I haven't responded before now, partly because of other
problems being worked and partly because I have absolutely no ideas
on what this problem might be.

I don't want to make a statement that it is a problem with multinet
but since that is an unknown variable in this case it might be.

I'm going to try and determine the location in the code, based on the
map where the access violation may have occurred.  This may take
awhile however.

Lyle

Anything you can will be helpful.  This is a fairly large Mission Critical
customer and would be a nice site to have it running.  They are a good mix of
NT, Unix and VMS.

I've reproduced the customers access violation on an NT V4.0 ALPHA
system here.  I am looking at the problem.

Lyle

It appears that we have a bad image in the NT Alpha distribution for
ABSgtar.exe.  We have been able to reproduce this problem from the
distribution, but not from a rebuilt image or a debug image to try
and determine the problem.

The best thing to do at this point is to open an IPMT case and we
can get a new image to this customer.

Lyle

Ok, will do...probably Monday.