No, the Enterprise version of Veeam.
Sent from my iPhone
On 16 Feb 2012, at 22:21, "Eric" mailto:seag...@gmail.com>>
wrote:
Steve,
Do you mean we'd have to purchase the Enterprise version of Exchange to
leverage the Veeam backup/restore feature?
Thanks,
Eric
On Thu, Feb 16, 2012 at 12:56 PM
Steve,
Do you mean we'd have to purchase the Enterprise version of Exchange to
leverage the Veeam backup/restore feature?
Thanks,
Eric
On Thu, Feb 16, 2012 at 12:56 PM, Steve Goodman wrote:
> +1 on Veeam, it is a pretty good solution. Only caveat with it when it
> comes to Exchange is that yo
Yes we have, but there is an internal app that requires a local copy
unfortunately. We tested a hosted solution but it wouldn't work with the
app.
Thanks,
Eric
On Thu, Feb 16, 2012 at 1:33 PM, Adm wrote:
> Have you considered cloud based Exchange instead of setting up a
> complicated, expensiv
Have you considered cloud based Exchange instead of setting up a
complicated, expensive solution for 100-200 people?
Just wondering
On Thu, Feb 16, 2012 at 1:03 PM, Eric wrote:
> Thanks for the feedback. I am looking at a backup solution as well as
> planning for a disaster using something like
I looked at Veeam, but apparently it doesn't backup servers that aren't
virtual. testing the new version of Backup Exec. Has greatly improved
On Thu, Feb 16, 2012 at 2:56 PM, Steve Goodman wrote:
> +1 on Veeam, it is a pretty good solution. Only caveat with it when it
> comes to Exchange
+1 on Veeam, it is a pretty good solution. Only caveat with it when it comes to
Exchange is that you require Enterprise licencing for Exchange backup/restore,
and a restore will fire up a copy of the VM to then extract the Mailbox data
from it. There are of course a lot of traditional solutions
Thanks for the great info! Will look into Veeam as well!
Eric
On Thu, Feb 16, 2012 at 10:20 AM, Paul Hutchings
wrote:
> For Hyper-V/VMware specific backups, Veeam always seems to get a ton of
> good press as it will also do replication between locations/servers without
> the need for shared sto
For Hyper-V/VMware specific backups, Veeam always seems to get a ton of good
press as it will also do replication between locations/servers without the need
for shared storage.
I haven't ever used it, but I don't seem to see/hear much negative about it so
I'd definitely consider it.
If you're
Take a look at Veeam, has some nifty Exchange hooks for backup/restore.
From: Eric [mailto:seag...@gmail.com]
Sent: Thursday, February 16, 2012 12:03 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange 2010 Hardware & Backups
Thanks for the feedback. I am looking at a backup solution as well a
Thanks for the feedback. I am looking at a backup solution as well as
planning for a disaster using something like Symantecs utility which
performs an image of the system that can be recovered on another Hyper-V or
VMware host. I have never used a tool like this for Exchange so thought
I'd get a
FOr 100 to 200 users gut reaction is that's absolutely fine. The Mailbox
Sizing Spreadsheet will help but you're not likely be taxing any half-decent
RAID.
I'd probably increase the RAM because it's a cheap win.
Backup? I'm not sure if you're asking just for Exchange or in general. You
can
We have around 6000 active mailboxes (2GB) and 23,000 small (20MB) alumni
mailboxes.
All Exchange 2010 is on VMware 4.1i backed by NetApp storage.
Prod is 4 machines, 2x4 CPU's and 96GB RAM. On that we have 4 mailbox hosts
with 48GB RAM and 4 CAS/HT nodes with 12GB RAM.
DR are the same physica
Below are the configs of a totally default "Client " receive
connector.
Anyone with a mailbox is allowed to use the connector (that is the "Permissions
Group" tab).
On the "Authentication tab, if you want to support plaintext authentication,
then uncheck the box after "Offer Basic authenticati
The mail attribute also has to be changed to reflect the new primary SMTP
address.
From: Haritwal, Dhiraj [mailto:dhiraj.harit...@ap.sony.com]
Sent: Thursday, February 16, 2012 1:08 AM
To: MS-Exchange Admin Issues
Subject: Set Secondary smtp Address as Primary SMTP Address in Exchange 2003
Hi,
Either way you do it, the HTs will be intelligent enough to work it out. We
changed our inbound to 2010 quite early on (using a smarthost that accepts mail
from the internet). Again, the efficiencies of routing the mail should be your
concern I think - if you don't mind an extra hop from 2010 >
Excellent, that makes perfect sense. One last though just came to mind. Inbound.
Current flow is through a spam filter then to the 2007 HUB. I will need the 07
HUB to forward to the 2010 HUB for the '10 Mailboxesis there a connector
for that or is it smart enough to figure that out? I also
Right. Remember for that to happen, you'll need to add your 2010 HT to the Send
Connector. Essentially, your Send Connector will stay the same, so you can
control which HT server(s) handle outbound mail by adding/removing them from
the Source Server.
It was more efficient for us to add the 2010
Finally working on migrating 2007 to '10. Current setup is a single CAS/HUB and
two mailbox servers all 2007. There is no edge. Incoming hits a spam appliance
that feeds the hub. Outgoing is done with the hub. OWA is published through an
ISA 2006. Seems pretty straightforward, put up a new CAS
18 matches
Mail list logo
