Thanks but all required services are in the list.... The problem is that even though they are in the list they don't start not automatically when replistor starts.

We have set replistore to manual fail over and this all works in our test labs.

The symptom you are describing is by design.

The Alias has a services tab. In that tab, you must list which Exchange services you would like RepliStor to control. If no services are listed here, the Alias will not start any of the Exchange services. Make sure you add all Exchange services, including SMTP.

The exch2k.dll does NOT control the Exchagne services. It makes the necessary updates to Active Directory.

If you are using the "Manual Activation on Target" option, this means that during a failover, the Alias will move to the Target machine, but will not activate. that means no scripts, DNS changes, or services will be controlled at that point. It is up to the admin to activate the alias to get that functionality to start.

This feature was added to give admin's the ability to control the Alias instead of being automated.

6.1 SP2

Are you seeing any errors in the Event Logs of the Windows box?

Do the services not start on the Sopurce machine when the Alias is activated?
Or do they not start on the Target after a Manual failover?

So you do not see any issues in your test environment?

No errors in the even log - just replistor started.

When Replistore starts it doesn't activate the alias.- don't know why

I would try upgrading to 6.2. I know it resolves a lot of bug issues and there were some Alias ones included in it.

I have not seen any bugs related to the Alias not activating on the Source after a reboot. If you are only seeing it in your production environment and not your test environment, it may be localized.

What version of ReplIStor is installed by the way?

Use the following procedure to enable debug logs in RepliStor. Perhaps it will reveal more information than what we are being shown.

How to enable debug logs in RepliStor

Open the Windows registry and browse to the following key.

HKLM/Software/Legato/RespliStor/

Add a new value with the following settings.

Name: Enable Debug Log
Type: Reg_DWORD
Value: 1 (1 is the same for binary, hex, or decimal)

Close the RepliStor Client (GUI or Console) and then restart just the RepliStor Server service. Open the RepliStor Client and confirm that debug logs are now enabled by right-clicking on the message window at the bottom of the attached server screen where Debug now shows up as an option to view.

Note: All messages are saved in the msg.rdf log file in the data directory regardless of whether they are being displayed in the message window of the attached server. It is not recommended to leave debug logs enabled once troubleshooting has been completed. Additionally the max message log count should be increased from 1000 (default) to a higher number to ensure that the greater number of messages do not overwrite possibly other important messages in the log.

Thanks, we found what triggers it.
There is a bug in Replistor that when do NOT have the DNS alias change disable is doesn't start Exchange.... Enable and it works....

EMC are looking into it.