I believe the command to which you are referring is refenced at the following
URL: http://www.storage.ibm.com/software/adsm/adagent.htm#ExchangeNT
Below is the an excerpt from this WEB page............
=============================================================================
Exchange Server:
Development has recently discovered an incompatibility between an ADSM V3
Server and an ADSMConnect Agent for Microsoft Exchange Server product or
try and buy. When attempting to store multiple files whose total size
exceeds 4 GB within a single transaction the server will fail the
transaction. As a temporary work
around, execute the following command either from the server console
command line or from an Administrative
Command Line client:
update node node_name fileag=no
IMPORTANT! The above command should ONLY be used for MS Exchange Agent nodes.
This incompatibility will be fixed in ADSM Server PTF 3.1.1.3. This server
PTF will be available for download from our ADSM fixes Web page.
When the PTF becomes available, please install it and then perform the
following command either from the server console command line or from an
Administrative
Command Line client:
update node node_name fileag=yes
IMPORTANT! The above command MUST be executed in order to ensure optimal
storing of objects onto the ADSM server.
===========================================================================
======
At 10:01 AM 7/9/98 -0400, you wrote:
>I was getting this error on my Exchange databases using the Exchange
>connect Agent, but it had nothing to do with a mount request. I was able
>to see that the error occurred at about the same point in the database
>each time, around 4GB. Apparently version 3 has a problem with file
>aggregation and files over 4GB in size (this is what support told me).
>Support gave me a secret, undocumented command to turn file aggregation
>off on that node (that I promised not to divulge or abuse), and it now
>backs up just fine. But this message strikes me as one that could pop
>up for a variety of reasons.
>
>Perhaps someone from IBM would like to jump in here.....
>
>> -----Original Message-----
>> From: McAllister, Andrew [SMTP:McAllisterA AT UMSYSTEM DOT EDU]
>> Sent: Thursday, July 09, 1998 9:26 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: Server Detected System Error...ANS1301E
>>
>> Here's what our cron script returns after a failed backup with the
>> ANS1301E system error:
>> We get the file backed up about 2, maybe 3, times a week (we try every
>> night). I know very little about ADSM so this output may not be
>> useful,
>> but...
>>
>> When we get the ANS1301E the backup ends and all other data is not
>> backed up. The backup succeeds if the ADSM server has been restarted
>> recently.
>>
>> Notice the file size (5 gig). Anyone having this problem on smaller
>> files?
>>
>> Andy
>>
>> See cron output below.
>>
>> ---------- start of cron script output ----------
>> ADSM backup on xxxxxx at Tue Jul 7 02:00:00 CDT 1998
>> Node Name: xxxxxx.xxxxxxx.xxx
>> ADSTAR Distributed Storage Manager
>> Command Line Backup Client Interface - Version 3, Release 1, Level 0.1
>> (C) Copyright IBM Corporation, 1990, 1997, All Rights Reserved.
>>
>> Session established with server ADSM1: AIX-RS/6000
>> Server Version 3, Release 1, Level 1.3
>> Server date/time: 07/07/1998 02:00:14 Last access: 07/06/1998
>> 09:46:11
>>
>>
>> Incremental backup of volume '/'
>> ANS1898I ***** Processed 500 files *****
>> ANS1898I ***** Processed 1,000 files *****
>> ANS1898I ***** Processed 1,500 files *****
>> ANS1898I ***** Processed 2,000 files *****
>> Normal File--> 3,012 /.sh_history [Sent]
>> Normal File--> 60,633 /dsmerror.log [Sent]
>> Special File--> 0 /dev/error [Sent]
>> snip
>> ...thousands of files backed up successfully...
>> snip
>> Incremental backup of volume '/u03'
>> Normal File--> 5,493,062,874 /u03/umdba/export/expdat.dmp.Z **
>> Unsuccessful **
>> ANS1114I Waiting for mount of offline media.
>> Retry # 1 Normal File--> 5,493,062,874
>> /u03/umdba/export/expdat.dmp.Z ** Unsuccessful **
>> ANS1301E Server detected system error
>>
>>
>> Total number of objects inspected: 65,784
>> Total number of objects backed up: 2,271
>> Total number of objects updated: 0
>> Total number of objects rebound: 0
>> Total number of objects deleted: 9
>> Total number of objects failed: 0
>> Total number of bytes transferred: 2.04 GB
>> Data transfer time: 373.05 sec
>> Network data transfer rate: 5,746.56 KB/sec
>> Aggregate data transfer rate: 2,397.65 KB/sec
>> Objects compressed by: 0%
>> Elapsed processing time: 00:14:54
>> ---------- ..end of cron script output ----------
>>
>> > -----Original Message-----
>> > From: Dwight Cook [mailto:decook AT AMOCO DOT COM]
>> snip
>> > What was in the surrounding activity log?
>> >
>> > Backups running?
>> > DB backup ?
>> > expiration ?
>> > etc...?
>> >
>> snip
>
>
|
