BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 04-13-2009, 09:53 AM   #1 (permalink)
New Member
 
Join Date: Mar 2007
Model: 8700
Carrier: 8700
Posts: 9
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Set up of 2nd BES server

Please Login to Remove!

Hi,

I am planning to set up a 2nd BES server for Exchange 2003. Currently we have one BES server (window 2003) set up with remote Database on another windows 2003 server. For the current BES server we are using the BESadmin id. I need some advise on the BESadmin id that I should use for my 2nd BES server.

1. Can I use the same BESadmin id for this new BES server as well or
I must use a separate BESadmin id?

2. If I would to use the remote BES Database on the same SQL server as my first BES server. Would that cause any issue to the first BES server database?




Any thought?


Thanks,
K K
Offline  
Old 04-13-2009, 10:08 AM   #2 (permalink)
BlackBerry Elite
 
knottyrope's Avatar
 
Join Date: Jan 2008
Location: Massachusetts
Model: Z30
OS: 10.2.1
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 6,570
Post Thanks: 256
Thanked 262 Times in 248 Posts
Default

Use the same login and the same database.

Then you can move users between the two BES servers with ease.

Just call the new BES server instance with a different name.
__________________
irony : many old timer posters have de-evolved into the trolls they once fought
I am on http://supportforums.blackberry.com
BES 10 running sweet for my Z30, Z10 and Q10
Offline  
Old 04-13-2009, 12:55 PM   #3 (permalink)
Knows Where the Search Button Is
 
Join Date: Apr 2005
Model: 8700
Carrier: cingular
Posts: 32
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I would say yes to using the same database, because that is what gives you the ability to move users between servers without reprovisioning, but regarding the use of the same besadmin account, this can be tricky. The need for a second BES server probably indicates it will be in a different geographic location? If the second BES server will be located in the same location as the first, then efficiency dictates you should use the same database and besadmin account. If the new BES server is going to be in a different location, and the users and their mailboxes that will be on this server are in that same separate location, you should create a new besadmin account and make sure it's mailbox is located on the mail server collocated with the BES. This gives you fault tolerance to some degree. You will still be able to administer both servers using the same console and besadmin account.
Offline  
Old 04-14-2009, 06:31 AM   #4 (permalink)
Feeling Blue, Bigly ;->
 
stuwhite's Avatar
 
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by cartwfh View Post
I would say yes to using the same database, because that is what gives you the ability to move users between servers without reprovisioning, but regarding the use of the same besadmin account, this can be tricky. The need for a second BES server probably indicates it will be in a different geographic location? If the second BES server will be located in the same location as the first, then efficiency dictates you should use the same database and besadmin account. If the new BES server is going to be in a different location, and the users and their mailboxes that will be on this server are in that same separate location, you should create a new besadmin account and make sure it's mailbox is located on the mail server collocated with the BES. This gives you fault tolerance to some degree. You will still be able to administer both servers using the same console and besadmin account.
On what evidence do you base these statements and in what way can it be tricky? I have (and know of many) multiple BESs across the world and use a single besadmin account for them all. I understand the fault tollerance point but see that as the only reason you would do this. Some supporting info please....
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
Offline  
Old 04-14-2009, 11:30 AM   #5 (permalink)
Knows Where the Search Button Is
 
Join Date: Apr 2005
Model: 8700
Carrier: cingular
Posts: 32
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Primarily this issue surrounds power outages or mail server availability in general. One besadmin account responsible for multiple Bes servers in multiple locations means that when the mailbox for that service is unavailable, NONE of the BES servers using that account can forward email (Hence the single point of failure). While administratively, this configuration is efficient, the continued deployment of servers this way will at some point bite you in the proverbial @ss.

The second issue would involve Wan traffic. Depending on your overall network architecture, the process of reading from the Besadmin mailbox then forwarding of the resulting traffic over the WAN out to the internet (If internet traffic is all funneled out through one portal) can cause a lot of back and forth that is resolved with separate BES service accounts on mail servers collocated with the BES server.

A specific example is as follows: a company has three offices and in each location they have an exchange server with about 75 users per site. Bes server should be

A. collocated in each of those locations with the exchange server so no mailbox reads occur across WAN connections.
B. the BES service accounts for each location should be based on the local exchange server.
c. the database should be one large shared (SQL?) database to allow free movement of users between servers when needed.
D. each site should have local internet access to avoid down connections as an additional enterprise wide point of failure.

If the database is unavailable, the bes servers can continue working under the right conditions for up to 4 days... more than enough time to get a database restored or rebuilt.
Offline  
Old 04-15-2009, 04:39 AM   #6 (permalink)
Feeling Blue, Bigly ;->
 
stuwhite's Avatar
 
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yeah I understand the single point of failure and tech concepts. I was looking for some supporting evidence mainly for the comment that "efficiency dictates you should use the same database and besadmin account". Our WAN doesn't suffer at all from using a single besadmin account and while what you say regading WAN traffic reduction using a second account is of course true, it may not be relevant if the WAN can cope.

I just think it's important that the OP understands here that having a second besadmin account for a second BES is totally a personal choice based on your setup (as it was for you) and not a requirement, as I believe your wording in your first post made it sound. It might be a good idea for certain setups but it's certainly not something I would say you "should" do, it's something you "could" do.
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
Offline  
Old 04-15-2009, 11:24 AM   #7 (permalink)
New Member
 
Join Date: Mar 2007
Model: 8700
Carrier: 8700
Posts: 9
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi guys, thank you all for the feedback and suggestion. Eventually I would prefer to set the 2nd BES server as a development server. Hence I dont prefer to mess it with the same SQL database. So if it is alrgiht to use the same BES admin id for my 2nd BES server and it wont cause any trouble to my existing BES server..I will go for it and as for the Remote SQL database I will choose a new database but reside in the same SQL server.


My main concern now is by having 2 BES database in the same SQL server. Would that cause any problem. How to ensure that they are indepent to each other?


Thanks again guys

Ken
Offline  
Old 04-15-2009, 12:24 PM   #8 (permalink)
BlackBerry Elite
 
knottyrope's Avatar
 
Join Date: Jan 2008
Location: Massachusetts
Model: Z30
OS: 10.2.1
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 6,570
Post Thanks: 256
Thanked 262 Times in 248 Posts
Default

you can setup a second SQL instance and will knot require a reboot on SQL 2005 to make it.

This will seperate the DB nicely.
__________________
irony : many old timer posters have de-evolved into the trolls they once fought
I am on http://supportforums.blackberry.com
BES 10 running sweet for my Z30, Z10 and Q10
Offline  
Old 04-15-2009, 01:39 PM   #9 (permalink)
Knows Where the Search Button Is
 
Join Date: Apr 2005
Model: 8700
Carrier: cingular
Posts: 32
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Stu,

I take it your network has never had a WAN outage from power blinks? Or a mail server needing to be rebooted because some poorly written service agent or corrupt virus DAT file causes the box to have to temporarily be taken offline? While none of these things are scary items for techies, they are annoyances when they happen to users. All it takes is the right VP or high level manager to be unable to "connect' for the simple step of splitting the accounts to look like something that should have been done in the initial engineering phases. most companies that pay the cost to implement BES servers are companies trying to grow using this form of technology to stay connected. That blackberry does not eat up a lot of WAN throughput when you only have 100 users is shortsighted...... 50 users on an exchange server in a remote location from where the BES resides can consume almost 2 GBs of WAN data throughput in a 24 hour period; that has to be considered.
Offline  
Old 04-15-2009, 02:24 PM   #10 (permalink)
BlackBerry Elite
 
knottyrope's Avatar
 
Join Date: Jan 2008
Location: Massachusetts
Model: Z30
OS: 10.2.1
PIN: t of blood has been taken
Carrier: AT&T-US with I dee ten tee errors
Posts: 6,570
Post Thanks: 256
Thanked 262 Times in 248 Posts
Default

I would invest in a UPS and a better version of antivirus.

Knot sure about the splitting, since all is in one house now.
But maybe some day.
__________________
irony : many old timer posters have de-evolved into the trolls they once fought
I am on http://supportforums.blackberry.com
BES 10 running sweet for my Z30, Z10 and Q10
Offline  
Old 04-15-2009, 05:00 PM   #11 (permalink)
Feeling Blue, Bigly ;->
 
stuwhite's Avatar
 
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by cartwfh View Post
Stu,

I take it your network has never had a WAN outage from power blinks?
Err, no. We pay someone a lot of money to ensure that can't happen.

Quote:
Originally Posted by cartwfh View Post
Or a mail server needing to be rebooted because some poorly written service agent or corrupt virus DAT file causes the box to have to temporarily be taken offline?
Nope, I would be out of a job if that could happen in our org.

Quote:
Originally Posted by cartwfh View Post
While none of these things are scary items for techies, they are annoyances when they happen to users. All it takes is the right VP or high level manager to be unable to "connect' for the simple step of splitting the accounts to look like something that should have been done in the initial engineering phases. most companies that pay the cost to implement BES servers are companies trying to grow using this form of technology to stay connected.
I don't disagree with DR and contingency planning but RIM are very good at pointing out what you should do (not so good at what you shouldn't!) and I don't recall them ever suggesting or recommending split accounts for this sceanrio. We aim for best practise based on vendor guidelines and while something might look practical and logical, we generally have to take the vendor line, even if that might not be the logical choice. That's why I asked for docs and evidence in my first post, as if RIM are saying somewhere that this is the best thing for our setup, I will have no issues getting it approved. Maybe it's something I have missed, so would genuinely like some hard RIM docs if they are available.

Quote:
Originally Posted by cartwfh View Post
That blackberry does not eat up a lot of WAN throughput when you only have 100 users is shortsighted...... 50 users on an exchange server in a remote location from where the BES resides can consume almost 2 GBs of WAN data throughput in a 24 hour period; that has to be considered.
Our internal and external network guys just don't have an issue with the traffic shipped because of the BES. Again they are paid a lot to ensure speed and efficiency globally, and would be the first to grab me if I was causing an issue with this setup. I do take your points but I just don't know of anyone else using two accounts and do know of many with a global setup like this (others with two production besadmin accounts pls speak up if you are out there, I really am interested to see evidence of others seeing a benefit from this). Like I said before it might be efficient on paper but if it's not the best practise being performed by the Pros and blessed by the vendor, I wouldn't be able to go near it.
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.