ADSM-L

Re: [ADSM-L] Restoring a "Renamed Exchange TDP" Backup

2008-02-27 07:45:04
Subject: Re: [ADSM-L] Restoring a "Renamed Exchange TDP" Backup
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 27 Feb 2008 07:44:25 -0500
The change that you made should not be causing the
"ACN5241E The Microsoft Exchange Information Store is currently not
running."
message. ACN5241E means that DP/Exchange tried to contact the local
Exchange Server (or the cluster Exchange server if you are using
/EXCSERVER=server-name)
and was not able to communicate with it.
I have seen cases where CDOEXM (Exchange Admin API that DP/Exchange
uses on Exchange 2003 servers) and the Exchange Server quit communicating.
Sometimes this requires a recycle of the Exchange services and in some
other cases, it requires a re-register of the CDOEXM DLL.
    http://www-1.ibm.com/support/docview.wss?uid=swg21163079
If these suggestions do not resolve the problem, please call IBM support,
they can get a trace and find out exactly what is going wrong.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/26/2008
12:45:14 PM:

> Got a fun one, maybe someone has ran in to.  We've been performing Daily
> Full Exchange Backups with a Indefinite Retention... We finally received
> word we can put the Exchange backups on a 35 Day Retention but must
> preserve all existing backups.
>
> 1) Renamed Existing Exchange TDP Client Names in TSM from Exchange to
> Exchangele.lgl
>
> 2) Copied the Excisting Exchange Domain to a New Domain Called
> Exchange.lgl - as it has the Nolimits for retention.
>
> 3)We then updated the exchange.lgl dom=exchange.lgl - So now we have the
> Lgl Backup data segregated
>
> 4)Updated exiting Exchnage Dom,ain to do a 35 Day Retention
>
> 5)Re-registed the orginal Exchange Node Names to the Original 35 Day
> Retemtikon Domain
>
> So far So good the Exchange Admin can pull up via TDP GUI and see the
> Old backup data with the Exchange.lgl name, but when he tries to restore
> to his Recovery Stggroup he gets an error ACN5241E The MS Exchange
> Information Store is currently not Running.
>
> What appears to be happening is that Exchange is expecting the restore
> for \\exchange\stggroup1 while we are trying to restore
> \\exchange.lgl\stggroup.
>
> So we fakes out TSM with the Node Name but now Exchange needs to faked
> out or somethin.... Has antone run in to a similar situaltion?

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