Upload
scott-sharp
View
398
Download
6
Embed Size (px)
DESCRIPTION
Now that you've implemented server virtualization in your small community bank, what should you do next.
Citation preview
Virtualization What’s Next
Now that you've virtualized you Core, Image, and Domain Systems;
• Types of Backups– Remote?– Local?
• Paravirtualization?• System Requirements?• Benefits & Drawbacks
What’s Next?
Types of Backups
• Local; best for file recovery over multiple days– Tape– Disk-NAS Replication– NAS-NAS Replication
• Remote; best for whole system disaster recovery– System-System replication– File Replication – Virtual Drive Replication (bit level)
Specifics – PC-Core
New Configuration w\ Linux• Two Drives – System & Archive\Backup• System Drive = System• Archive\Backup (all replicated to
backup):– Archive Reports (COLD) Storage– 10 day backup files (tape rotation)– Monthly/Yearly backup
• Virtualization requires in-depth system knowledge (RHCA/RHCE)
Specifics - CheckImage
• Non-Archived files replicated daily– Quick rebuild of recent data
• Other Data Archive to DVD & Yearly Databases
• Databases manually moved
yearly; due to size• Requires Para-Virtualization
– Physical DVD-Burner attached to Virtual Machine
• Bandwidth Intensive for bit-level replication used in virtualization (5-20Mbps required)
System Requirements - Typical
• Core/Image/Domain virtualized on single Hypervisor w\ NAS; Local & Remote– 2 Hypervisor, 2 Large NAS’s– Decreased Hardware Cost– Increased Software Cost– Single point of Failure for all– Disk Access (speed) Issues– More negatives over single
systems than positive
System Requirements - Recommended• Recommended – Core/Image/Domain
virtualized on dual Hypervisor w\ dual NAS; Local & Remote– 2 Hypervisor, 2 Large NAS; Local– 1 Hypervisor, 1 Large NAS; Remote– Fast Recovery– Same Hardware Cost– Increased Software Cost– Increased Complexity– Disk Access (speed) Issues– More negatives over single systems than
positive
System Requirements - Advanced
• Core/Image/Domain virtualized on dual Hypervisor w\ dual NAS; Local & Remote; with Failover– 2 Hypervisor, 2 Large NAS; Local
• 1 Additional VM Manager\Replicator– 1 Hypervisor, 1 Large NAS; Remote– Immediate Recovery– Increased Hardware Cost– Increased Software Cost– Increased Complexity– Disk Access (speed) Issues
Benefits & Drawbacks of Virtualizationat the System Level• Faster Local Recovery w\ Failover• Large file changes = Large amount of
data replication• Increased Cost• Decreased System Speed• Increased Complexity
Virtualization Recommendations
• Cost Benefit Analysis• Implement In-house for 10+ Systems• Outsource <10• Fully Implement!• Fully Document & Test!• Dedicated IT Staff or Qualified
Outsourced• Patch Management