Re: [ADSM-L] TDP for Exchange 2007 scenario
2009-12-16 09:17:52
Hi Grigori,
The tdpexc.cfg file exists and is configured.....I don´t think the problem lies
in it......this is more like an architectural issue I believe......it´s not
clear to me where I should install the TDP agent......considering the 3
machines scenario: 1 front end with the Exchange 2007 Server and 2 cluster
nodes where the Exchange DBs reside.....
Mario
________________________________
From: Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Wed, December 16, 2009 11:54:49 AM
Subject: Re: TDP for Exchange 2007 scenario
I think you should lok for file tdpexc.cfg or make it from appropriate smp file.
________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Mario
Behring [mariobehring AT YAHOO DOT COM]
Sent: Wednesday, December 16, 2009 4:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDP for Exchange 2007 scenario
Hi list,
I have the following scenario and I am having a hard time making TDP for
Exchange work....
1- Microsoft Exchange 2007 binaries installed in one machine, as afront end
machine.
2- Microsoft Exchange 2007 Database Agents installed on 2 other machines
running MCSC (Microsoft Cluster Server).
3- Microsoft Exchange 2007 Databases exists on this 2 MCSC nodes.
I´ve installed TDP for Exch on both nodes and I am getting the error below when
verifying my installation:
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 5, Release 5, Level 1.0
(C) Copyright IBM Corporation 1998, 2008. All rights reserved.
ACN5051I The configuration file cannot be found, using default settings.
ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has
been pruned successfully.
Querying Exchange Server to gather storage group information, please wait...
ACN5237E Unable to communicate with the Microsoft Exchange Server.
On the dsm.opt file, the NODENAME parameter is pointing to the virtual server
name on the MSCS, as recommended by the TDP for Exchange Installation Guide...
I did TDP for Exchange installations in MSCS environments before, with Exchange
2003....and everything was fine. This 2007 scenario is different though....it
uses a 3rd machine, like a frontend.....only the Exchange Databases are on the
cluster nodes....
________________________________
I´ve tried installing the TDP on the frontend machine also, which is a
standalone machine and it is where the Exchange Server binaries are
installed....and I got the following error:
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 5, Release 5, Level 1.0
(C) Copyright IBM Corporation 1998, 2008. All rights reserved.
ACN5051I The configuration file cannot be found, using default settings.
ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has
been pruned successfully.
=========================================================================
Unable to obtain the Microsoft Exchange version running on your system.
Microsoft Exchange 2003 is being assumed. Unexpected results may occur.
=========================================================================
Querying Exchange Server to gather storage group information, please wait...
ACN5241E The Microsoft Exchange Information Store is currently not running.
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc /excserv=exfront1 query exchange
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 5, Release 5, Level 1.0
(C) Copyright IBM Corporation 1998, 2008. All rights reserved.
ACN0102E Invalid command: /excserv=exfront1
________________________________
Is there any methodology to install TDP on this scenario?
Any help is appreciated.
Mario
Please consider the environment before printing this Email.
"This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are not the
named recipient(s), please delete this email after notifying the sender
immediately. BKME cannot guarantee the integrity of this communication and
accepts no liability for any damage caused by this email or its attachments due
to viruses, any other defects, interception or unauthorized modification. The
information, views, opinions and comments of this message are those of the
individual and not necessarily endorsed by BKME."
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [ADSM-L] TDP for Exchange 2007 scenario, (continued)
- [ADSM-L] TDP SQL connection error, Mario Behring
- Re: [ADSM-L] TDP SQL connection error, Mark Yakushev
- Re: [ADSM-L] TDP SQL connection error, Del Hoobler
- Re: [ADSM-L] TDP SQL connection error, Sanju Chacko
- Re: [ADSM-L] TDP SQL connection error, Schaub, Steve
- Re: [ADSM-L] TDP for Exchange 2007 scenario, Grigori Solonovitch
- Re: [ADSM-L] TDP for Exchange 2007 scenario,
Mario Behring <=
- [ADSM-L] Data Protection for Domino, Elek Kurucsó
- Re: [ADSM-L] Data Protection for Domino, Del Hoobler
- Re: [ADSM-L] Data Protection for Domino, Grigori Solonovitch
- Re: [ADSM-L] TDP for Exchange 2007 scenario, Del Hoobler
- Re: [ADSM-L] TSM 5.3.4 Policy problem, William ZHANG
- Re: [ADSM-L] TSM 5.3.4 Policy problem, Skylar Thompson
- Re: [ADSM-L] TSM 5.3.4 Policy problem, William ZHANG
- Re: [ADSM-L] TSM 5.3.4 Policy problem, Skylar Thompson
- Re: [ADSM-L] TSM 5.3.4 Policy problem, Carol Trible
- Re: [ADSM-L] TSM 5.3.4 Policy problem, William ZHANG
|
|
|