ADSM-L

FW: TDP for MS Exchange 5.1.5

2005-10-10 09:36:49
Subject: FW: TDP for MS Exchange 5.1.5
From: "Jones, Kelli" <JonesK AT CHESTERFIELD DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 10 Oct 2005 09:36:29 -0400
Below is the dsm.opt for for the tdp agent.  I think maybe the problem
is that our network group used the default dsm.opt and didn't bind it to
the actual management class set up for the agent? 

DSMOPT:
*======================================================================*
*                                                                      *
* IBM Tivoli Storage Manager for Mail                                  *
*                                                                      *
* Data Protection for Microsoft Exchange Server                        *
*                                                                      *
* Sample Options File                                                  *
*                                                                      *
*======================================================================*

NODename          KING_AGNT
CLUSTERnode       no
COMPRESSIon       Off
PASSWORDAccess    Generate

*======================================================================*
* TCP/IP                                                               *
*======================================================================*
COMMMethod        TCPip
TCPPort           1500
TCPServeraddress  172.24.10.20
TCPWindowSize          2048
TCPBuffSize            128

*======================================================================*
* Named Pipes                                                          *
*======================================================================*
*COMMMethod         NAMEdpipe
NAMedpipename      \\.\pipe\tsmpipe

*======================================================================*
* LAN Free                                                             *
*======================================================================*
*ENABLELANFREE YES

*======================================================================*
*                                                                      *
* - Scheduling Options                                                 *
*                                                                      *
*   The default scheduling mode is the client polling method.          *
*   To use server prompted scheduling, you must be sure to use a tcp   *
*   client port different than the one used by the regular backup      *
*   client.                                                            *
*                                                                      *
*======================================================================*
SCHEDMODE             Polling
*SCHEDLOGRetention     14
*SCHEDMODE             Prompted
*TCPCLIENTADDRESS      yy.yy.yy.yy
*TCPCLIENTPORT         1502

*======================================================================*
* Include/Exclude Processing                                           *
*                                                                      *
*   First, read the documentation about INCLUDE/EXCLUDE processing     *
*   included in the base TSM backup-archive client documentation.      *
*   There are specific instructions that are needed for Tivoli Data    *
*   Protection for Microsoft Exchange Server - V2.  Please refer to    *
*   Chapter 2 in the Installation and User's Guide for more            *
*   information.                                                       *
*                                                                      *
*   NOTE:                                                              *
*     Server names and storage group names are case sensitive.         *
*======================================================================*
*======================================================================*
*   The following include statement assigns all backup objects of      *
*   a particular storage group to the management class ExcMgmtClass.   *
*======================================================================*
*INCLUDE "SERVER_NAME\A Storage Group\...\*" ExcMgmtClass

*======================================================================*
*   The following exclude statement excludes a particular storage      *
*   group from backup.                                                 *
*======================================================================*
*EXCLUDE "SERVER_NAME\A Storage Group\...\*"

COPYGROUP SAMPLE:

Policy        Policy        Mgmt          Copy          Versions
Versions       Retain      Retain
Domain        Set Name      Class         Group             Data
Data        Extra        Only
Name                        Name          Name            Exists
Deleted     Versions     Version
---------     ---------     ---------     ---------     --------
--------     --------     -------
KINGPD        ACTIVE        KINGMC        STANDARD             5
2     No Limit          90
KINGPD        ACTIVE        KING_AGN-     STANDARD            90
2     No Limit          90
                             TMC

KINGPD        KINGPS        KINGMC        STANDARD             5
2     No Limit          90
KINGPD        KINGPS        KING_AGN-     STANDARD            90
2     No Limit          90
                             TMC

-----Original Message-----
From: Richard Sims [mailto:rbs AT bu DOT edu] 
Sent: Saturday, October 08, 2005 7:00 AM
To: Jones, Kelli
Subject: Re: TDP for MS Exchange 5.1.5


Kelli - Your posting doesn't give us any sense of what you actually did.

Review pages 16 and 17 of the 5.1.5 TDP manual, and see if your
arrangement complies with what the manual advises.

Re-post with technical details if necessary.

    Richard Sims

On Oct 7, 2005, at 5:02 PM, Jones, Kelli wrote:

> TSM 5.2.6.0 Server
> AIX 5.2 OS
>
> We discovered that we have not been retaining the 90 versions we had 
> specified for our exchange backups.  We are using a separate
> management
> class/copygroup for the agent and the server node.  It seems that
> instead of using the copygroup parms we had configured for the agent,
> the parms for the server node are being used.  It appears that
> everything is set properly on the server end.  Does anyone have any
> ideas on where I could check?
>
> Thanks,
> Kelli
> Chesterfield County VA
>

<Prev in Thread] Current Thread [Next in Thread>