Exchange 2007 SCR question

Ok,
I just had a question about Exchange 2007 Standby Continuous replication....I want to enable SCR but when i give the command

Restore-StorageGroupCopy vmmbx1\vmmbx1-sg2 -StandbyMachine Scrtarget -force

Now, the above command requires the source Exchange Server to be dismounted (or disconnected from network) to work; will not work otherwise  ... I was under the impression that in case of failure I only need to give the following command

Get-Mailbox -Database vmmbx1 ... | where ... | move-mailbox

But now I think I need to give all the commands starting from


1. Restore-StorageGroupCopystatus
2. Use Eseutil utility
3. Move storagegroup path and movedatabase path
4. Setmailboxdatabase and mount and finally the get-mailbox-cmdlet ...

So Am I doing all these steps 1-4 in case of failure (because I certainly cant give restore-storagegroupcopystatus command) as long as the primary exchange doesnt go down ... So thats the confusion ... Do I give all 4 commands or just the last command of get-mailbox-cmdlet ...

Sorry if i cant make it clear, let me know in case anything is unclear !
nabeel92Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

debuggerauCommented:
you shouldn't need to dismount the database, especially since it should be down for SCR to be enabled...

Here is a real life example:
http://technet.microsoft.com/en-us/library/bb738150.aspx

Are you clustered? or do you have single standby unit?
0
nabeel92Author Commented:
single standby unit ...

exactly right, i wont need to dismount the database since the server will be down ... But what I wanted to know was only when my Primary Exchange server dies, then I need to give all those commands (mentioned in steps 1 - 4) in my post above .... I thought that I only needed to give the last command i.e. get-mailbox-cmdlet ...  but it turns out that I have to give all those commands, right ?
0
debuggerauCommented:
err, no..

in a cluster, the database is replicated, so not needed, however a standby unit is not, so recover database or database portability is required.

Essentially, what your doing is just updating the Schema and DNS to point the service to the new server...

So, if you use Mailbox recovery, the eseutil shouldnt be needed as the service replays the log files from the SCR commands redirect.

0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

nabeel92Author Commented:
Ok,

and whats the recommendation on which method of SCR to use

Database Portability or RecoverServer method ???

I used the database portability method in my testing ...

thanks for ur help !
0
debuggerauCommented:
both are ok, just depends on your requirements.

If you using Database portability, you should move, then, and only if dirty, use eseutil to recover.
http://technet.microsoft.com/en-us/library/bb738132.aspx
0
nabeel92Author Commented:
hmmm....ok..i read the link above...typical example of database portability method...

but in my case, am suspecting the primary exchange server itself to go down ... i mean database portability would still work in that scenario, right ?
0
debuggerauCommented:
since the database is not stored on that machine itself, the idea is that you could enable a standby server to take over that service and use that database..

However, you are right with the recovery option on eseutil as if the outage caused a corruption, you would need to repair before starting the service..

0
nabeel92Author Commented:
sorry, i just got confused with ur answer ...
my query was simply whether database portability would be a good enough option to use even if the server (primary exchange) would be dead ? or should I use recover server option instead ?
0
debuggerauCommented:
the server recovery option existed previously(albeit, only back into that server..), and I hope you never need to use it, however database portability is an additional feature that allows the database to be portable and can be recovered into another organization (if required).

http://technet.microsoft.com/en-us/library/bb124275.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nabeel92Author Commented:
The reason being that I never got a straightforward answer to my straigh forward question ..... rather
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.