Vizioncore backup Architecture & Best Practice
13
Vizioncore backup Architecture & Best Practice Simon Poulton Senior SE – ANZ [email protected] March 2010
description
Vizioncore backup Architecture & Best Practice. Simon Poulton Senior SE – ANZ [email protected]. March 2010. Agenda. Backup 2.0 – What is it?! Architecture – LAN-based vs LAN Free ESX vs ESXi and considerations Additional notes on LAN Free backup. - PowerPoint PPT Presentation
Transcript of Vizioncore backup Architecture & Best Practice
Agenda
• Backup 2.0 – What is it?!
• Architecture – LAN-based vs LAN Free
• ESX vs ESXi and considerations
• Additional notes on LAN Free backup
2
B2.0: Simply Better Data Protection
ESX Network backups
To Backup Repository
ESX Host
Nic 0
Storage Connections (Ethernet or FC)
vCentervRanger Pro
4.2
Service Console
Mmgt Connection
vRanger Pro uses the SC
connection for Network transport
backups
Compressed
vStorage API for data protection ESXi Network backups
ESXi Host
Nic 0
Storage Connections
(Ethernet or FC)
vCenter vRanger Pro 4.2
Uncompressed
Mmgt Connection
vStorage API uses this
connection for Network transport backups
Compressed To Backup Repository
vRanger Pro Architecture for LAN free backups
SAN Storage
Lun 0 Lun 1 Lun 2
Fibre Channel Switch
ESXHost
ESXHost
vRanger Pro Architecture for LAN free backups
SAN Storage
Lun 0 Lun 1 Lun 2
Fibre Channel Switch
vRangerServer
ESXHost
ESXHost
vRanger Pro Architecture for LAN free backups
vRangerServer
ESXHost
ESXHost
The storage is presented to both the ESX hosts and the vRanger Pro server.
iSCSI Switch(s)
SAN Storage
Lun 0 Lun 1 Lun 2
vRanger Pro Architecture for LAN free backups
ESXHost
ESXHost
The storage is presented to both the ESX hosts and the vRanger server.
FC / iSCSI Switch(s)
SAN Storage
Lun 0 Lun 1 Lun 2
vRanger Server
Read Only Access
vRanger Pro Architecture for LAN free backups using a FC SAN
Nic0
HBA2
HBA1
vRanger Pro (Proxy)
Prod Network – to vCenter
Shared Storage (VMs)
To Backup Repository
SAN Storage
Lun 0 Lun 1 Lun 2
SAN Storage
Lun 10 Lun 11 Lun 12
Architectural Choices
Architecture Direct to Target - LAN Proxy Based – LAN Proxy-Based – LAN Free
Advantages Simultaneous backups easily accommodated and scaled (direct to target & control via ESX/LUN/Application maxima)
Easily scaled at target side via adding additional CIFS targets
Simple to install and enable, no SAN expertise req’d
ESXi Support leveraging vStorage APIs
No pressure on LAN/SC/Management network
Easy if existing methodology has been VCB/vStorage API
Leverage SAN investment
Considerations Changes required to SC Mem/CPU reservation for injected run-time agent
Additional load on SC/Management console
ESXi Not supported
Proxy a potential bottle neck (multiple proxies possible)
Requires traffic on Management LAN
Proxy a potential bottle neck (multiple proxies possible – only 1 per group of LUNs)
All LUNs can only be backed up via a single proxy, creating a potential bottleneck
Configuration on SAN required, non-trivial without in-house storage expertise
11
Requirements for LAN free backups
• vRanger Pro 4.2 installed on a physical proxy server• One proxy per set of VMFS luns• VMFS luns zoned so vRanger Pro can see and read them• VCB application is no longer used• Works with ESX 3.0.2 - ESX 4 (vSphere)• ESX 4 hosts require minimum “Essentials” license to use the
vStorage API.• DISABLE AUTOMOUNT!!!! DO NOT WRITE DISK SIGNATURES!!!
