Interesting issue. You certainly should be able to accomplish this but not having all the information on the environment makes it hard to truly understand what you are seeing.

You have repopulated the indexes and can see them fine? Can you give us the steps you used to do this? Also- it may not be ideal but you could do a redirected recover of the whole thing to and RSG and then grab what you need from a higher level?

-Steve

Hi the index are already populated. I have rescanned the tape with the datastore.

I have running the client from the Legato Server and selected the old server and old datastore but i recive this error

sadn(1241): Organization or AdminGroup Invalid

sadn(1204): The AD search for the Exchange Server FIERA-BCK did not return any rows of information.

If run the client from new exchange there isn't the datastore.

Hi is possible extract the db without client for exchange?

If i recover only edb and add to a datastore or extract with third part software ??

Thanks

Hello,

First, it is not possible to extract or recover the Exchange EDB files
(or logs even) with using the Module for Exchange if they were backed up online using Module for Exchange

Second, there are some limitations when it comes to restoring old Exchange data that was backed up on original Exchange server1 
to new target Exchange server2

Most limitations are by design with respect to Exchange.

For example, server2 -- the target of the restore -- must be running the

same operating system version (Windows version and service packs)

same Exchange version and service packs

As the original source server1 exchange server1 that was backed up.

To recover an Exchange database on new Exchange server server2,
the following conditions must be met: 

the target  Exchange Storage group and database names must match exactly  as original

the target Exchange server must be configured with the same
organization name and administrative group name as the original
Exchange server.

(If the original server is still online in the same domain)
Then additionally the new Exchange server  

  ** must be in a different Active Directory forest than the original Exchange server. **

Some are limitations with respect to networker.

The client file index for server1 must be populated with meta data for  the desired
save set.  That can be accomplished with nsrck -L7 or by running scanner -i on the data tape volume.

The client resource of server1 must have *@* to give access of original client index to any other client.

The new Exchange server must have
,  same Networker client or higher
,  same Networker module for Exchange or higher
as the original Exchange server.

== Assumptions: 
** so far the assumption is that the new Exchange server is installed on the
same Active directory forest and domain as the original Exchange server. 

sadn(1241): Organization or AdminGroup Invalid

sadn(1204): The AD search for the Exchange Server FIERA-BCK did not return any rows of information.

===
From the threads above the error seems that one of the Exchange servers (it seems the new Exchange server)
FIERA-BCK  either does not exist in active directory  (which is strange if it was installed correctly in this domain)

OR it has been installed with a non-similar Organization Name or Administrative Group in
comparison to the original server.  This will prevent the success of the restore. 
The requirements for Exchange restore must be met first.

See the comments above about requirements to restore to new Exchange server.

** If this does not make sense I might suggest some reading from Microsoft Technet
on Exchange 2003 backup  and restore concepts. 
Also from Powerlink,  the Administration Guide for Networker Module for Exchange would be useful.   Some useful chapters are the

Recovering data from backups
and
Disaster Recovery.

Hope that helps a little.