My company is looking to add a second bes server to our network. The current one is out in cali we are in wi so we have problems with the bes having connection issues with all the peoples mailboxes in wi. So thats why we are adding another local bes. I was wondering that if we do a backup of the current database on the 1 out in cali if we can restore it here and use it for our database and then just remove the duplicate users. Will this work with out having to put people through enterprise activation again? I just am trying to make sure that we can do this with the least user impact. Also i'm not the one that had setup the other one. So i'm sure that theres some problems with it being in a child domain instead of us the parent. I appreciate any replys thanks.


Cavy

what is the database? MSDE or SQL? If SQL, what is the latency between current database and new bes server? You can connect to current database as long as latency is not too high. I have servers with latency between them close to 200ms and all is good. Now, there should not be any latency between BES and exchange if possible less then 35ms.
Child domain is irelevant...

We have been having problems with our mpls that our times are normally around 70-140ms to cali but sometimes they screem way up there this is the reason for implementing another server with database. Its a sql database.

Well if connection is not reliable then just create separate BES with separate SQL /msde db on your site. Try though connecting both to a same and see if it works. If it does not then do copying of db and removing old/first BES from second DB. You should then remove users/ second BES from old/first db.

Depending how many users you are adding to a new server from old one it might be easier to remove them from old and re-activate them on new.

we are going to be moving about 80 or 90 users and want to try and do it without them having to reactivate.

Then connect new server to a same db.
Move users from server A to B.
Backup DB on site A and restore to SQL DB site B.
Remove BES server B from SQL DB in site A.
Stop services on BES B.
On Server B, change DB to from SQL A to a SQL B.
Restart BES server B.
Remove BES server A from SQL server DB on site B.

That should do it.

Thanks man i'm going to try that once i get everything ready to go.

as someone with 2 BES domains (and over 7000 devices) I would highly reccommend against it. you will create more problems than you solve by doing it.

1. add a new BES server in WI an connect it to SQL in CA.
2. move users from old server to new server.
3. ...
4. profit.

let BES worry about latency to SQL, it should not cause message delivery delays as Exchange is local to BES, and it will save you many administrative problems. (users activated on 2 bes domains, devices on both domains, moving users from one domain to another requires re-activation) and then there is reporting from 2 domains instead of 1, maintaining 2 sets of IT policies, etc etc etc..

rich

But were moving users off the other one on to this one. Not keeping everyone on both.

Start here ... are you going from full blown sql or msde? ... all you really want to do is move sql, and then do a knife-edge cutover ... or you could do a phased migration.

I agree but he is saying that connection between two sites are not reliable and that there might be disconnection between them. Other then that I have couple of dozen BES servers all over tyhe country and they are all connected to a same SQL. Some of them with high latency but reliable link between. No problem so far.

hmmm... I don't think you've read his initial post carefully...

I did ... why wouldn't the proposed methods I suggested work? Please explain.

I beleive they have two exchange servers on two locations and latency is an issue. So they want to add second bes to it. I agree that the best would be to have one DB and connect both to it. But they have issue with connectivity of tweo sites so I guess they have no choice but have two BES connected to their own DB on each site. Or maybe I misunderstood it..

I read it as Exchange in WI and BES in CA ...

... Hence the need for posters to post as much detail as possible. Thanks for the input fadmin

Hdawq, now when I read it again hmmm .. you might be right. I guess took it for granted that first BES would be always placed where their exchange is but it might not be in his case, you are right.
So Cavy, unless you have two exchange servers on two sites, you might be better off with HDawg advice...

... and follow fadmin's advice if the other scenario.

Yes we have exchange servers in both locations.

Cavy,
I'd still suggest to stick with one DB and 2 BES as long as there is a link in between sites as latency between BES and SQL is not big deal. If you see that connection drops for a long time between them then from that point on you follow my instructions to split BB domains to two.

In addition, make sure you have the DataBase Notification System correctly setup