looking for advice/recommendations/thoughts on whether I should purchase and deploy a barracuda 300 spam appliance and then put the 3 Exchang roles on a single box (Mail, CAS, HT) or whether I should split out the roles so Mailbox is separate and put the Exchange spam filtering on the CAS/HT server? I need to make this decision quick and I really want to get some feedback from some experienced users. Thanks alot.
no one have any thoughts to share on this scenario? I'd really like to get some good recommendations before I have to make this decision in the next few days. Thanks.
300 users..currently have 125GB total of database size for a total of 4 databases. currently doing spam filtering on 2003 with Exchange...all on the same box.
How many years of service will I get out of the barracuda before it needs to be upgraded?
Posts: 6
Joined: 25.Jun.2001
From: Lombard, IL
Status: offline
I have a barracuda 300 running with Exchange 2007 with the all 3 major rolls installed. It seams to run fine. I had it running on my Exchange 2003 with no issues. If you pay for the maintence which includes updates and warranty for like $900 a year it will pretty much last for ever they cover the whole unit if it dies. Mine has beening running 2 years with out a glitch, support has been fine. After you get it set it pretty much does everything its self. All I really do now is add domains to the white list and install the firmware updates. I would tell more people to buy it. Very easy to set up. You will be up and running in like 30 mins. It will take longer to mount in the rack than to setup.
The only draw back is the users can only check what is in the Spam filter @ the office.
Howie, I was wondering what you did for the Barracuda. I just got around to decommissioning my Exchange 2003 server. As soon as that completed my email from the Barracuda stopped flowing. I did set the Barracuda to point to the new IP address of the new (Exchange 2007) server. The Barracuda test email will work, however no email that goes to the Barracuda will then flow into the Exchange 2007.
I am not using Edge transport, it is a stand-alone server for a small office. I have tried setting the anonymous user access in the cmdlet, but that also did not work. Any suggestions?
Thanks. Oh, first time poster here, so sorry if I missed the obvious. If I did, swing away with the clue bat, just put me in the right direction.
did mail flow normally to the Exchange 2007 before you installed the cuda?
On the Basic -> Administration tab you have obviously run test, did you look at the details, did all 9 tests pass? On the Status tab, does it look like mail is stacking up in the cuda's queue? Have you configured your Domains on the cuda?
Yes, the email did flow fine. The flow was from the barracuda to the exchange 2003 and then the exchange 2007. Once the exchange 2003 left the path everything halted. The email continued into the barracuda but would not go into the exchange 2007.
I found finally I had to run another commandlet to allow the barracuda to send mail into the excahnge 2007. Once I did that, everything was/is fine.
Yes, the email did flow fine. The flow was from the barracuda to the exchange 2003 and then the exchange 2007. Once the exchange 2003 left the path everything halted. The email continued into the barracuda but would not go into the exchange 2007.
I found finally I had to run another commandlet to allow the barracuda to send mail into the excahnge 2007. Once I did that, everything was/is fine.
Thanks.
Can you share what teh commandlet was? I'll be up against the same issue shortly.
Actually, I cannot recall exactly what I did. Unfortunately I flopped into panic mode when the email stopped and began googling and flailing for answers. I know I did spend a fair amount of time here and on this site http://www.petri.co.il/exchange.htm reviewing what I could.
I think that I had to tweak the settings for "Anonymous Relay" properties. Specifically I think I had to add the IP address of the Barracuda as the "Remote IP Address" and to tell the Exchange server to specifically use it's own "Local IP Address". It seems to me when the Exchange 2003 was there, I did not have to specifically set the IP address of the Exchange 2003 server because as a domain system they already knew about each other and the flow was expected. At least that is my newbie to Exchange 2007 observation.
Sorry for being so late to the game on this. I bet you already figured this out by now. My apologies for missing this reply for so long.