asked on
Exchange 2007 Standard Database Move
We have an Exchange 2007 Standard installation running on Server 2003 R2 which is running like an absolute bag of cr**, therefore I have built a new Exchange 2007 Standard installation on Server 2008 R2 and given it the resources it needs, everything is up and running and I can move users manually from old databases to the new databases on new server without issue, it's just that the time it's taking is too long for the amount of mailboxes we have.
My question is, if I choose to move the entire database as a whole rather than individual mailboxes, do the naming conventions for the new storage groups and databases have to match the old naming conventions?
For example:-
Old Config
Storage Group 1 > Mailbox_Database 1.edb
New Config
First Storage Group > Mailbox Database.edb
Is this OK?
The databases are huge in size, around 250 GB, hence the reason I'm carrying out this entire process as I'll eventually spread the load more efficiently. I'm also aware of the default limits set @ 250 GB for the database to dismount, I can get around that with a registry change temporarily.
My question is, if I choose to move the entire database as a whole rather than individual mailboxes, do the naming conventions for the new storage groups and databases have to match the old naming conventions?
For example:-
Old Config
Storage Group 1 > Mailbox_Database 1.edb
New Config
First Storage Group > Mailbox Database.edb
Is this OK?
The databases are huge in size, around 250 GB, hence the reason I'm carrying out this entire process as I'll eventually spread the load more efficiently. I'm also aware of the default limits set @ 250 GB for the database to dismount, I can get around that with a registry change temporarily.
ExchangeInstallation
Last Comment
Peter Jones
ASKER
Do you want copy over whole storage from old server to new one and connect it (mount) in Exchange ?- Yes, from old server to new server
You not supposed to play with Exchange 2007 anymore this days.- That is a matter of opinion, not fact. Exchange 2007 Standard is currently in extended support by Microsoft until 04/10/2017. Therefore the product is still valid.
- I haven't mentioned anything about Outlook 2016? I'm fully aware of client-side compatibility, hence the reason I haven't included this in my question.
New Office 2016 is not compatible with old Exchange.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I don't think you can mount old database and use it on new server.
You should mount it and perform users migration to new database
It's called Dial Tone Recovery on an Exchange 2007 Server
You can try this article
https://technet.microsoft.com/en-us/library/bb310773%28v=exchg.80%29.aspx
I know you did not mentioned Outlook 2016 and I also know that support for Exchange 2007 is extended, but very soon you can face this problems specially that extension will expire in one month.
You should mount it and perform users migration to new database
It's called Dial Tone Recovery on an Exchange 2007 Server
You can try this article
https://technet.microsoft.com/en-us/library/bb310773%28v=exchg.80%29.aspx
I know you did not mentioned Outlook 2016 and I also know that support for Exchange 2007 is extended, but very soon you can face this problems specially that extension will expire in one month.
ASKER
It turns out that it is possible to migrate an Exchange 2007 database to a new Exchange 2007 installation running on a new Windows Server platform:-
1.) Create new storage groups on new Exchange installation
2.) Create new mailbox databases on new Exchange installation with exactly the same naming convention as old databases. Also, allow database to be overwritten via a restore and remove database limits to allow overwrite
3.) Check database integrity using ESEUTIL /MH. If database is in "Clean Shutdown" state then migrate database to new location. If database is in "Dirty Shutdown" state then further work is required to replay transaction logs using ESEUTIL or "Exchange Aware" backup to commit logs
4.) Move databases to new specified location. Check for integrity again using ESEUTIL /MH just to be sure.
5.) Mount database on new Exchange installation
6.) Run Powershell command to point mailboxes to new configuration "Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch '(SystemAttendantMailbox|E
7.) Add required OWA configuration to be accessed externally (FQDN)
Source = https://technet.microsoft.com/en-us/library/aa998340(v=exchg.80).aspx
1.) Create new storage groups on new Exchange installation
2.) Create new mailbox databases on new Exchange installation with exactly the same naming convention as old databases. Also, allow database to be overwritten via a restore and remove database limits to allow overwrite
3.) Check database integrity using ESEUTIL /MH. If database is in "Clean Shutdown" state then migrate database to new location. If database is in "Dirty Shutdown" state then further work is required to replay transaction logs using ESEUTIL or "Exchange Aware" backup to commit logs
4.) Move databases to new specified location. Check for integrity again using ESEUTIL /MH just to be sure.
5.) Mount database on new Exchange installation
6.) Run Powershell command to point mailboxes to new configuration "Get-Mailbox -Database <SourceDatabase> |where {$_.ObjectClass -NotMatch '(SystemAttendantMailbox|E
7.) Add required OWA configuration to be accessed externally (FQDN)
Source = https://technet.microsoft.com/en-us/library/aa998340(v=exchg.80).aspx
Do you want copy over whole storage from old server to new one and connect it (mount) in Exchange ? )
You not supposed to play with Exchange 2007 anymore this days.
New Office 2016 is not compatible with old Exchange.