- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem - General
- >
- Best config for backup throughput?
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2009 04:14 AM
03-16-2009 04:14 AM
Best config for backup throughput?
I've gone through the VC Cookbook and know that setting up a team with TLB will give maximum *outbound* throughput but I'd like to optimise throughput for the backup server, currently backing up from FC-AL to FATA drives on an EVA4000 (via VC-FC).
I'm not looking to achieve anything earth-shattering, I just know the current setup is somewhat sub-optimal as, for a start, they've only configured one NIC as a backup NIC and disabled the 4th NIC (?!?). So, given that there's no redundancy configured for the backup network anyway, I was wondering if it was worth trying to go for SLB networking.
Only half of the VC-Enet ports have been cabled up as well - this is a historical environment I've recently come into, having previously set up a VMWare infrastructure on similar kit (480's rather than 460's).
Any suggestions/pointers appreciated...
Paul
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2009 06:58 AM
03-16-2009 06:58 AM
Re: Best config for backup throughput?
What do the 4 NICs do?
All teamed as one?
Backup NIC?
Cluster heartbeat NIC?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2009 07:25 AM
03-16-2009 07:25 AM
Re: Best config for backup throughput?
On the backup server it's just a pair of teamed NICs for the LAN, a single backup NIC and a disabled NIC (hence my thoughts of teaming backup NIC in best way for throughput).
The VNet it's connecected to is also configured as a sincle VNet with ports from two VC-Enet modules assigned to it (so active/standby) which further reduces throughput possibilities as I understand it.
We do have clusters as well which are in a config of Teamed pair (Public) single NIC (private) Single NIC (backup). Increasing outbound speeds from this backup network wouldn't be worthwhile without increasing inbound throughput to the backup server so I'm not worried about these ATM. Multiple servers (with single NICs) backing up to a single server with teamed (inbound) NICs would be an improvement in itself.
Thanks for prompt response.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2009 09:12 AM
03-16-2009 09:12 AM
Re: Best config for backup throughput?
Is the backup server backing up just the blades or is there a lot of other clients external to the blade enclosure to backup?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2009 11:58 AM
03-16-2009 11:58 AM
Re: Best config for backup throughput?
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP