Unsolved
This post is more than 5 years old
46 Posts
0
865
September 12th, 2008 07:00
Disaster Recovery
Hi,
Next week we want to execute a disaster recovery test at a remote site. We have made backups of all our servers (DC's, MS Exchange, SQL, EmailXtender etc.) I've searched the documentation but couldn't find anything regarding this issue.
Is there a certain order we have to maintain while restoring the environment? E.g. first Exhange, second SQL, then EX.
Hope someone can answer my question.
Kind regards,
Duncan
Next week we want to execute a disaster recovery test at a remote site. We have made backups of all our servers (DC's, MS Exchange, SQL, EmailXtender etc.) I've searched the documentation but couldn't find anything regarding this issue.
Is there a certain order we have to maintain while restoring the environment? E.g. first Exhange, second SQL, then EX.
Hope someone can answer my question.
Kind regards,
Duncan
0 events found
No Events found!
RKatwal
2 Intern
•
600 Posts
0
September 15th, 2008 17:00
I do not think there is anything available from support or engineering of EX.
Professional services might have something for you but all services form professional services comes with a charge.
Regards,
Rajan
jacco_gijben
1 Message
1
September 22nd, 2008 04:00
I dind't find documentation on that either. But first you have to restore your DC and Exchange enviroment. After that you can restore SQL and EX, just restore. When the restore of the data, registry etc.. is done, you can start the SQL DB and after that your EX services.
Where do you store the .emx files? (EX, DX, Centera??)
Good luck with the tests!
Kind regards
Jacco
minfin
46 Posts
0
September 23rd, 2008 06:00
Last week we had the the disaster recovery tests, and everything went pretty smooth. We had some issues, but these were easily resolved.
Our .emx files are stored on a HP SAN, so the restore of these items was no problem.
We have modified the volume ID of the hard drive so that the license would work.
The mail applet was no longer available in Control Panel, this was resolved running fixmapi.exe from a command window.
Also we had restored the databases to a different SQL server, so we had to change a registry key and the ODBC settings.
Hope this helps other people who want to conduct a DR scenario.
Kind regards,
Duncan