ADSM-L

[no subject]

2015-10-04 17:51:03
We are using the Exchange Agent and had a problem the other day were we had
a tape drive go bad during a backup and any subsequent backups received the
RC=1. The EXCSCHED.LOG showed "waiting on ADSM Server....." for the last
attempt at a backup.  The only way we "cleared" the indication that a backup
was still running was to reboot the Exchange Server.   

***********************************************************
Also...FYI...this is an earlier incident where we saw the "waiting on ADSM
Server" and it did correct the problem...
        -----Original Message-----
        From:   Del Hoobler [SMTP:hoobler AT US.IBM DOT COM]
<mailto:[SMTP:hoobler AT US.IBM DOT COM]>  <mailto:[SMTP:hoobler AT US.IBM DOT 
COM]
<mailto:[SMTP:hoobler AT US.IBM DOT COM]> >
        Sent:   Wednesday, September 09, 1998 7:53 AM
        To:     ADSM-L AT VM.MARIST DOT EDU <mailto:ADSM-L AT VM.MARIST DOT 
EDU> 
        Subject:        Re: ADSM Connect Agent For Exchange

        Scott,

        This is a Microsoft Exchange Server bug.
        It is most prevalent on single CPU machines but may occur on
multi-CPU machines also.
        Microsoft has found the bug and has written a fix.
        The fix is available as a "HOTFIX" from Microsoft.  Any of our
customers experiencing this hang, will have to call Microsoft Technical
support to obtain the fix.  Here are the Microsoft Bug numbers that the
customers should refer to:
                Bug x5:66198 is for Exchange 5.5
                Bug x5:66942 is for Exchange 5.0
                Bug x5:66943 is for Exchange 4.0

        You can call Microsoft to obtain the fixes since they are not yet
available in a service pack.
        Until you obtain the fix from Microsoft...  there is a possible
workaround that you can try.  When using the Exchange Agent command-line
client, specify the following option on the command line:
                /BUFFERS:1
        If, after applying the Microsoft fix, you still
        experience the problem, let us know.

        Thanks.

        -------------------------
        Del Hoobler
        IBM ADSM Agent Development
        hoobler AT us.ibm DOT com <mailto:hoobler AT us.ibm DOT com> 

        ====================================================================
                >> We have been using the Connect agent for a while now with
success.
                >> Recently, we installed the agent on a new server and were
backing up
                >> successfully until the following occurred last week.  Has
anyone else
                >> seen this problem?  Any ideas?
                >>
                >> Thanks,
                >> Scott

        The current date is: Fri 09/04/1998
        Enter the new date: (mm-dd-yy) The current time is:  0:08:15.44
        Enter the new time:
        ADSTAR Distributed Storage Manager
        ADSMConnect Agent for Microsoft Exchange Server Command Line
Interface - Version 1, Release 1, Level 0.0 © Copyright IBM Corporation
1998. All rights reserved.
        ***FIXTEST - Version 1.1.0.0 "A"
        ADSM API Version 3, Release 1, Level 3
        ADSM Nodename: PTLEXI03

        License file exists and contains valid license data.
        Starting a backup to the ADSM server...
                Exchange Server : PTLEXI03
                Database : Information Store
                Backup Type : Full

        Logging on to the ADSM server...
            1,(1/2 full)> Wrote  61619 bytes, total: 61619    2,(1/2 full)>
        Wrote  65536 bytes, total: 127155    3,(1/2 full)> Wrote  65536
bytes,
        total: 192691    4,(1/2 full)> Wrote  65536 bytes, total: 258227
        5,(1/2 full)> Wrote  65536 bytes, total: 323763    6,(1/2 full)>
Wrote
        65536 bytes, total: 389299    7,(1/2 full)> Wrote  65536 bytes,
total:
        454835    8,(1/2 full)> Wrote  65536 bytes, total: 520371    9,(1/2
        full)> Wrote  65536 bytes, total: 585907   10,(1/2 full)> Wrote
65536
        bytes, total: 651443
        (((  I deleted lines 11 through 270...you can probably guess what
was there!! )))  271,(0/2 full)> Wrote  65536 bytes, total: 17637979
272,(0/2 full)> Wrote  65536 bytes, total: 17703515 Waiting for Exchange
server..................
        Waiting for Exchange
server..................................................................
        
........................................................................
        
........................................................................
****************************************************************************
*******************************************

        -----Original Message-----
        From:   Salvatore Greco [SMTP:salvo AT REAPER DOT ORG]
        Sent:   Tuesday, November 03, 1998 8:33 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: Exchange Agent backup question

        Hi Dell,

        I have viewed the "activity log" for the Exchange agent (taken from
the
        example in the manual).

        On Tue, 3 Nov 1998, Del Hoobler wrote:

        |Also, if the EXCHFULL.CMD file starts the backup with the
        |"START EXCDSMC /BACKUP:is,full  ...etc...etc" then the
        |backup could still be running.  You should be able to check
        |this by doing a "query session" on the ADSM server to see
        |if the session for the backup is still running.
        |The Exchange server will not allow two backups to be running
        |at the same time for the same database.

        Here is a copy of the parts that start the Exchange Agent backup:

        c:\win32app\ibm\adsm\agentexc\excdsmc /backup:dir,full
        /logfile:c:\win32app\ibm\adsm\agentexc\excsfull.log >
%exc_dir%\excshed.log

        c:\win32app\ibm\adsm\agentexc\excdsmc /backup:is,full
        /logfile:c:\win32app\ibm\adsm\agentexc\excsfull.log >
%exc_dir%\excshed.log

        On a `query ses' it responds that there is no other session running
other than
        my admin session.

        Any ideas ?



        -- Salvatore Greco | salvo AT reaper DOT org | http://salvo.reaper.org

<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=