Re: Backing Up Exchange Using A Privete Network
- From: "John Fullbright" <fjohn@donotspamenetappdotcom>
- Date: Tue, 24 Jul 2007 19:51:54 -0700
"so that It can be utilized to run Microsoft Exchange backups from disk to
tape during operation hours"
Unless you properly sized your storage to handle the extra IOPS during peak
operations, your strategy is flawed. You'll create more problems than you
will solve. I'd expect to see you run out of version store as well,
compounding the performance problems created by the extra backup IOPS during
peak hours. I'd recommend snapshot backups with a technology that does not
"copy on write" if you want frequent backups during peak opeating hours
without a large performance impact. If you're an IBM shop, look at the N
series SAN.
"Tony Negron" <TonyNegron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F1B7622-8C85-454C-AE02-263649AF628B@xxxxxxxxxxxxxxxx
Recently we got a backup library and Tivoli that will be use to backup our
application and resources. One strategic I want to implement is a private
network (10. Network), so that It can be utilized to run Microsoft
Exchange
backups from disk to tape during operation hours.
What I'm planning to do is to add an additional network card (NIC) to each
of the Exchange servers and configure them with 10.XXX.XXX.XXX Network IP
information; of course, I will configure a switch independently from the
production network. Now, my question is; when I configure the additional
NIC,
should I configure the default gateway or not? Basically we are not going
to
rout anything. Also, does this backup strategic supported or is acceptable
for Microsoft Exchange 2003? And last, would you recommend another
solution?
Thanks
.
- Prev by Date: Re: Security groups versus Distribution lists
- Next by Date: Still looking for method to remove X400 addresses
- Previous by thread: Re: Backing Up Exchange Using A Privete Network
- Next by thread: Incoming Winmail.dat Problems
- Index(es):
Relevant Pages
|
