[exx]

Hey,

I need to move our BES on ESX to our other site, which will take up to 10 hours to transfer. I was thinking we could shut down the original server, clone it and power the original back up until the clone is done transferring. Once the clone is transferred, shut down the original and power up the clone.

Would this cause any serious problems? Duplicate emails perhaps? In general this sounds like a bad idea, but I figure I'd throw it out there anyway incase it can help us avoid a full 10 hour outage.

Thanks!

[nobody7290]

I did this several times on the last weekend during my upgrade to 5.0

Did not experience major problems.
I had to re-actiavte all handhelds after I finallly got everything running, because of strange differences in the server view of the sync settings compared to what the handhelds displayed - server view: wireles sync off for PIM-sync, Device view: on (sychronisation did work, but, i thought its better not to ignore this).
This problem might be related to the switch to version 5 and not due to the switch back to a state several hours old.
But, if you have more then a few handhelds, better try it out before making the switch.

[TargetIT]

I could be wrong, but a restore of the current SQL database should fix a lot of that - is the dbase that large not to do that separately?

[stuwhite]

Yeah off the back of Target's post, OP why wouldn't you just build a new BES on the other site if moving the VM will take 10 hrs? Just create a new VM, install BES software then move the DB across. The DB is the heart of the BES, the rest is just an install you can do in 20 mins.

[exx]

Thanks for the suggestions. That's a good point about just building the new server and restoring the DB - I don't know why I didn't think of that when we're going to have to do that anyway since this move is temporary, losing my mind. Anyway, we've actually found a way to move the server in a fraction of the time (should take 1 hour) so problem solved, but I'll keep this in mind for next time.