Here's some info that might help you.
************************************************************************
IBM ADSMConnect Agent for Microsoft Exchange Server
Version 1 Release 1 Level 0.0B
README.FTP
(c) Copyright IBM Corporation, 1999
****************************************************************************
**
* Fixtest 1B, IC22589: A new command has been written for the
* command line that will allow the deletion
* of Exchange backup objects based on how old
* a backup object is. This command can be
* scheduled to provide automatic deletion of
* backup objects.
*
* This fixtest also includes a change to correct a
* situation where a read error during a backup may
* not be properly handled and can lead to a hang.
*
* Additional Information : This software has not been fully system
* tested with the Fixtest code.
****************************************************************************
**
****************************************************************************
**
IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT!
****************************************************************************
**
Fixtext 1B - The following describes the new command and its
syntax and any messages that have been added.
EXCDSMC /ADSMAUTODELETE
-----------------------
Use this command to delete Exchange database backup objects from ADSM
storage based on how old a backup object is. This command works on
objects
backed up from the local server only.
Syntax
------
>>-EXCDSMC----------------------------------------------------->
>----/ADSMAUTODELete:--dbtype---------------------------------->
>----/IFOLDer:--n---------------------------------------------->
>----+-----------------------+---+----------------------+------>
'-/ADSMNODe:--nodename--' '-/ADSMPWD:--password--'
>----+-------------------------------------+------------------->
| .--dsm.opt--------. |
'-/ADSMOPTFile:--+-optionsfile.opt-+--'
>----+-----------------------------+--------------------------><
| .-excdsm.log--. |
'-/LOGFile:--+-logfilename-+--'
Parameters
----------
/ADSMAUTODELete:dbtype
dbtype refers to the type of Exchange database to delete. This
parameter can be:
DIR Exchange Directory Database
IS Exchange Information Store Database
You may run this command against all types of Exchange databases
by using the '*'.
/IFOLDer:n
n represents the number of days for which database backup objects
are to be kept. Database backups that are older than "today - n"
will be deleted. n must be an integer in the range from 0 to 9999.
If n is 0, then all backup objects for the specified database
will be deleted. This parameter MUST be specified.
Note: If a full or copy backup object is deleted, then any
subsequent
incremental and differential backup objects associated with
that
backup are deleted.
/ADSMNODe:nodename
nodename refers to the ADSM node name the Exchange Agent uses to
logon
to the ADSM server. You can also store the node name in the options
file. The command line parameter overrides the value in the options
file.
Note: /ADSMNODe cannot be used if Generate Password is in effect.
The nodename must be specified in the options file.
Generate Password is specified by either checking the
Generate Password check box while modifying your options
file using the Exchange Agent options editor, or by adding
the PASSWORDACCESS GENERATE option to your options file.
/ADSMPWD:password
password refers to the ADSM password the Exchange Agent uses to logon
to the ADSM server. If Generate Password is in effect, then the
password need not be provided here because the one stored in the
registry is used. If you do specify the password on the command
line when Generate Password is in effect, then the command line
value is ignored unless the password for this node has not yet
been stored in the registry. In that case, the specified password
is the one that is stored in the registry and used for the current
command execution.
If Generate Password is not in effect and a password value is
specified in the options file, the value specified on the command
line overrides the value in the options file.
Note: Storing the password in the options file is not recommended.
If Generate Password is not in effect, and a password value is not
specified in the options file or on the command line, then you are
prompted for a password.
Generate Password is specified by either checking the Generate
Password check box while modifying your options file using the
Exchange Agent options editor, or by adding the
PASSWORDACCESS GENERATE option to your options file.
/ADSMOPTFile:optionsfile.opt
optionsfile.opt refers to the ADSM options file to use. This is
similar to selecting an ADSM server from the server list in the GUI.
The options file name must have an extension of .opt. If the
specified name does not end with the .opt extension, the extension
is appended to the name when determining the actual options file
name.
The file name can include a fully qualified path name. If no path
is specified, it is assumed that the file is in the agent's
installation directory.
The default is dsm.opt.
/LOGFile:logfilename
logfilename identifies the name to be used for the activity log
generated by the Exchange Agent. The log file name is used only for
this command run, and does not update the default log file that
is stored in the registry. If the specified file does not exist,
it is created. If it does exist, new log entries are appended to
the file. The file name can include a fully-qualified path.
However, if no path is specified, the file is written to the
directory where the Exchange Agent is installed. The Exchange Agent
does not prune this file. You should periodically prune this log
file to keep it from getting too large.
You cannot turn logging off. If this option is not specified, log
records are written to the default log file. The default log
file is excdsm.log.
Examples
--------
This example deletes all of the database objects that are older
than 4 days.
excdsmc /adsmautodelete:* /ifolder:4
ADSTAR Distributed Storage Manager
ADSMConnect Agent for Microsoft Exchange Server
Command Line Interface - Version 1, Release 1, Level 0.0
(C) Copyright IBM Corporation 1998. All rights reserved.
***FIXTEST - Version 1.1.0.0B
ADSM API Version 3, Release 1, Level 3
ADSM Nodename: deniseexc
License file exists and contains valid license data.
Logging on to the ADSM server...
Attempting to delete backup object(s) from ADSM...
Database Name : *
Retention Days : 4
List of Databases and Objects Deleted
-------------------------------------
Database: DIR, Object Name : 19990221154547.FULL
Database: DIR, Object Name : 19990221160147.INCR
Database: DIR, Object Name : 19990221170435.COPY
Database: IS, Object Name : 19990221154559.FULL
Database: IS, Object Name : 19990221160223.INCR
Database: IS, Object Name : 19990221170520.COPY
Results: 6 backup object(s) of 54 examined were deleted.
Messages
--------
There has been a new message added. The following details the message.
Message : The /IFOLDer option needs to be specified when issuing
the /ADSMAUTODELete command.
Explanation : This option needs to be entered for the /ADSMAUTODELete
command.
System Action: Processing ends.
User Response: Re-enter the command specifying the /IFOLDer option.
****************************************************************************
**
IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT! IMPORTANT!
****************************************************************************
**
Installation instructions:
-------------------------
- Download the IC22589B.EXE file in "binary" format.
- Download the IC22589B.EXE file in "binary" format.
- Run the IC22589B.EXE file. It is a self-extracting install file.
> -----Original Message-----
> From: Roland Bender [SMTP:BENDERR AT ING.BOEHRINGER-INGELHEIM DOT COM]
> Sent: Friday, April 23, 1999 2:06 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: AW: ADSM and MS Exchange
>
> We face some problems with backing up Exchange Servers.
>
> It seems that ADSM ignores the parameters in the option file.
> I think the connectin agent has a bug!
> I would like ADSM to keep 6 versions but it runs and runs (could be the
> 20th version of the backup.)
>
> Has anyone face a similiar problem?
>
> Have a nice weekend
>
> Yours,
>
> Roland
>
> > -----Ursprungliche Nachricht-----
> > Von: Pita, Gene [SMTP:PitaG AT NABISCO DOT COM]
> > Gesendet am: Freitag, 23. April 1999 18:44
> > An: ADSM-L AT VM.MARIST DOT EDU
> > Betreff: Re: ADSM and MS Exchange
> >
> > Hi Wes,
> >
> > How are you getting those fabulous numbers? If I can get at least 8 to
> 10
> > Gig an hour I'd be happy as a clam.
> >
> > Do you have a separate network for backing up?
> >
> > How many MS Exchange servers are you backing up?
> >
> > If you're backing up multiple Exchange servers, are they all done at the
> > same time?
> >
> > Thanks.
> >
> > --Gene
> >
> > > -----Original Message-----
> > > From: Wes Lewison [SMTP:WesLewison AT WINN-DIXIE DOT COM]
> > > Sent: Friday, April 23, 1999 10:37 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: ADSM and MS Exchange
> > >
> > > Well I can definitely answer some of these questions...
> > >
> > > Our Config: (for exchange)
> > > IBM PC Server 325 (handles all SQL and EXCH)
> > > ADSM for NT 3.1.2.13
> > > 256meg of RAM
> > > 100mb Ethernet (ADSM)
> > > 18gig disk pool (Exchange only)
> > >
> > > 4 Exchange Servers:
> > > IBM Netfinity 5500
> > > Dual 450's
> > > 896meg of RAM
> > > 155mb ATM
> > > 50gig Exchange storage space provided by an EMC disk array
> > >
> > >
> > > 1. Excellent quality, backups are always flawless and rather
> > speedy.
> > > (11-12gig an hour)
> > > 2. Restoring a exchange database that is 14gig to a recovery
> server
> > > takes approx. 1 hour 5 min.
> > > 3. The backup and restore GUI is extremely easy to use, the
> > Exchange
> > > admin learned it in under 2 min.
> > > 4. Configuration is somewhat clunky... more steps than setting
> up
> > > the
> > > regular client, but the same is true for SQL agent's that we use also
> > > 5. No experience, sorry.
> > >
> > > As far as I know exchange itself doesn't allow restore of signal
> > > mailboxes..
> > >
> > > We have had to restore to a different server, and export the mailbox
> out
> > > to
> > > a pst file and then import it into the production servers
> > >
> > > I don't think logging method matters if you do full backups every
> > night...
> > > which we do, but we have our servers set to normal logging. (and have
> > > tested incrementals this way, and found no problems)
> > >
> > > Please feel free to email me if you would like more information on our
> > > setup.
> > > WesLewison AT winn-dixie DOT com <mailto:WesLewison AT winn-dixie DOT com>
> > >
> > > -----Original Message-----
> > > From: Gerard Diep [mailto:Gerard.Diep AT PEDICO DOT DE]
> > > Sent: Thursday, April 22, 1999 5:28 PM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: ADSM and MS Exchange
> > >
> > > Dear Collegues!
> > >
> > >
> > > As we haven4t found ADSM Newsgroups in Germany we may ask you, if
> > someone
> > > of
> > > you has experience in using the actual version of ADSM exchange agents
> > as
> > > main Backup& Restore and Disaster&Recovery strategy in your MS
> Exchange
> > > environment.
> > > Can someone tell me about:
> > > Backup&Restore
> > > 1. Quality of Backup&Restore of MS Exchange Server via ADSM,
> online
> > > Database
> > > Backup
> > > 2. Performance of Backup&Restore of 10-12 GB Exchange Databases
> > > 3. Handling of Backup&Restore GUI
> > > 4. Configuration "smartness"
> > > 5. Experience in ADSM Backup for Exchange in a Storage Area
> Network
> > > environment
> > > Brick Level Backup&Restore
> > > Does ADSM in the actual Version support brick level Backup&Restore of
> > > Exchange. Can we restore single mail or public Folders? Can we restore
> > > single connectors?
> > >
> > > Disaster Recovery
> > > Does someone have experience about Disaster & Recvorey experience?
> > > Is that possible to restore Exchange Databases with or with no
> circular
> > > logging?
> > >
> > >
> > >
> > > Many thanks for your hints
> > > Gerard Diep
> > > mailto:Gerard.Diep AT PEDICO DOT DE
|
