09-28-2010 02:59 AM
Hi,
i am tasked with installing our new EV9 environment. After the EV9 server is working, we want to migrate the mailboxes from EV8 to EV9 and then migrate the mailboxes from Exchange 2007 to Exchange 2010.
I prepared the server and also installed Enterprise Vault already. I started the Configuration Wizard which asked me about the DatabaseServerName.
Question: The first time, i inserted the DatabaseServerName from the Server where the EV8 Database resides. I clicked "Next" and got something similar like "something is wrong with the database, repairing EV9" and after that the connection from the EV8 to my EVDirectory Database vanished. Pretty uncool, was seeing me restoring the database already.. After chanceling the wizard and restarting the EV8 Services two times the connection did reappear.
Do i need to put in a new DatabaseServer? Or is there a way to configure EV8 and EV9 on the same SQL Server (without data loss obviously).
I fear to restart the configuration Wizard :(
I dont have much knowledge about SQL..
Anything else i should consider?
greetings
Solved! Go to Solution.
09-28-2010 04:54 AM
Hello vmds,
In short, you wrekced your install of EV8. When you installed EV9, and pointed it to use the ev8 database, it probably upgraded the database, or did some other funky stuff.
The only way to get this repaired is to restore a backup from the databases (yes all of them), from the point BEFORE installing the EV9 server.
Before doing so, you need to uninstall the ev9 server, make sure no ev9 services are running.
When databases are restored, you might want to keep all tasks in report-mode, and run EVSVR to verify integrity of the restored databases.
Doing an inplace upgrade of the 8 machines now will probably create more problems than it will resolve.
sorry to bring the bad news.
09-28-2010 03:37 AM
You cannot have different versions of EV within the same directory. To do your plan above you would need a 3rd party tool to migrate from one directory to another. Otherwise you could do a Data only DR to fail the old server to the new server, this is covered n the admin guide
09-28-2010 03:51 AM
Yeah, the way you are trying to this will not work. As Marvin said you can do the data only recovery but first you would upgrade your current EV server to EV 9 and then fail over to the new hardware. That would serve to migrate all your EV archives to the new server.
You might want to consult a professional to help you work through the process if you are not sure how to do it.
09-28-2010 04:54 AM
Hello vmds,
In short, you wrekced your install of EV8. When you installed EV9, and pointed it to use the ev8 database, it probably upgraded the database, or did some other funky stuff.
The only way to get this repaired is to restore a backup from the databases (yes all of them), from the point BEFORE installing the EV9 server.
Before doing so, you need to uninstall the ev9 server, make sure no ev9 services are running.
When databases are restored, you might want to keep all tasks in report-mode, and run EVSVR to verify integrity of the restored databases.
Doing an inplace upgrade of the 8 machines now will probably create more problems than it will resolve.
sorry to bring the bad news.
09-28-2010 04:55 AM
Sadly, i still have problems with the Database now.
After the restart of the EV Services i was able to reconnect my EV8 to the Directory Database. I am able to recall items. Now, at 12:00, the Sync task did run producing a lot of errors in the eventlog:
09-28-2010 05:22 AM
Would i need to restore the Vault Partition Database too? Or Only the EnterpriseVaultMonitoring, Audit and Directory Database?
If i have to restore the Vault Database, whats with the items on the EV Server itself? (Vault Store Partition on the File System).
What happens to the items that got archived last night?
The EV9 services are deactivated already.
Want to add:
A small warning message at the configuration wizard that gives a hint like "Database on Server detected - do you -really- want to overwrite?" would be much appreciated :(
//Edit:
I would like to try the following:
According tp page 351 of the Admin Guide:
a) Stop the EV Services
b) restore the Directory Database
c) start the Directory Service
d) run EVSVR
c) run Tasks in report mode for a week
09-28-2010 06:30 AM
If you're lucky, the only database being attempted to be upgraded is the directory database. Personally, if ev8 starts without problems, no events, having tasks run in reportmode for a day (24 hours) should be enough.
You might want to call support to be sure.
09-28-2010 06:45 AM
EV8 starts without problems except of
09-30-2010 03:16 AM
Restoring the Directory Database solved the issue. Tasks in report mode running fine not generating any errors.
Noticed what i did wrong there (still, a little notification in the configuration wizard would be much appreciated!) and we are planning the update process different now.
Thanks for the help
09-30-2010 03:21 AM
Hello vmds,
Glad to see that you are ok now.
Good luck with the upgrade