Virtualization.

Virtualization

Definisi Virtualisasi
Virtualization berasal dari kata Virtual atau Maya yang menerangkan sebuah teknik menciptakan sesuatu yang maya dari sesuatu yang konkrit. Teknik ini telah diterapkan sejak jaman mainframe dan dan terus terus berkembang berkembang sampai sampai diterapkan diterapkan pada pada cloud cloud computing sebagai satu feature yang sangat penting. Walaupun tentunya penerapan teknik virtualisasi ini berbeda.

Sejarah Virtualisasi Pada jaman mainframe computing atau “Host-Terminal” system, teknik virtualisasi ini sudah diterapkan pada sistem memory. Dengan teknik ini jumlah memory seakan disulap menjadi berlipat ganda dari jumlah memory secara fisik yang sesungguhnya. Bayangkan saja sistem PDP-11 sebuah minicomputer yang hanya mempunyai memory sebesar 64 KB memory saja bisa dirubah sehingga mempunyai kemampuan untuk melayani puluhan users. Coba bandingkan saja saja dengan dengan komputer komputer PCPC yang yang umum umum kita kita pakai pakai,, memorynya memorynya saja saja sudah sudah 22 GB tetapi hanya melayani 1 user saja. Prinsip cukup sederhana, dengan bantuan hard disk dan kenyataan bahwa eksekusi setiap program dari user adalah satu instruksi setiap saatnya, maka hanya sebagian program saja yang diangkut ke memory pada setiap saat dan sisanya mendekam di harddisk yang baru diangkut ke memory sampai dibutuhkan atau eksekusi program tersebut tiba pada instruksi yang dikandungnya. Prinsip manfaat yang kita peroleh dari teknik virtualisasi ini adalah meningkatnya kemampuan jumlah user yang bisa dilayani secara bersamaan

Sejarah Virtualisasi …
Lalu berkembang sebuah teknik irtualisasi yang mensimulasi sebuah hardware atau PC secara software misalnya Virtual PC. Virtual PC ini berfungsi sama persis seperti sebuah komputer lengkap dengan operating systemnya dan siap dipergunakan user sebagaimana sebuah PC beneran layaknya. Untuk mempergunakan virtual pc ini maka user harus menjalankan software cpc yang yang telah telah diciptakannya itu karena karena virtual pc ini hanyalah merupakan sebuah file saja. Jadi dengan mempergunakan sebuah PC kita bisa menciptakan virtual pc bermacam-macam seolah kita mempunyai beberapa PC dalm arti sesungguhnya. Salah satu tujuan penggunaannya adalah untuk testing software sehingga apabila ada terjadi masalah atau virus sekalipun maka PC benerannya tidak akan kena imbasnya karena segala yang terjadi hanya di dalam virtual pc itu sendiri. Penanggulangannya semudah menghapus sebuah file dan menciptakan virtual pc yang baru.

Manfaat Virtualisasi Tujuan lain dari virtualisasi adalah untuk memaksimalkan pemanfaatan sebuah fasilitas infrastructure seperti processor, network, dan communication channel. Tanpa disadari bahwa processor lebih banyak nganggurnya daripada sibuk bekerja. Pada waktu anda melakukan pekerjaan mengetik dengan Microsoft word sebenarnya processor tidaklah begitu banyak dipergunakan. Apalagi kalau kita bicara printer tentunya tidak mungkin atau jarang kita melakukan printing dengan printer itu. Jadi lebih banyak nganggurnya daripada dipakai. Kenyataan inilah yang menyadarkan dunia bisnis untuk mengirit biaya, misalnya biaya biaya media media telekomunikasi telekomunikasi.. Seandainya Seandainya dulu dulu menyediakan menyediakan 11 jalur jalur untuk untuk 11 departemen, sekarang tidak lagi tetapi mungkin cukup hanya 2 jalur dan dishare dengan teknik virtualisasi oleh semua departemen. Hebatnya teknik virtualisasi ini adalah bahwa pihak user tidak mengetahui kenyataan ini dan merasa atau mengetahui bahwa mereka memiliki 1 jalur sendiri yang tidak dipakai bersama2 dengan pihak lainnya.

Manfaat Virtualisasi …
Bisa meningkatkan UTILITY atau pemanfaatan infrastructure mencapai 100% atau semaksimalnya. Bisa menciptakan imunisasi atau security dimana 1 user tidak bisa mengganggu atau merusak user lainnya karena mereka masing masing terselubung dalam 1 virtual machine. Bisa memberikan elastisitas atau ketidakterbatasan infrastructure kepada setiap user. Bisa menciptakan virtual machine atau virtual desktop yang sesuai dengan spesifikasi prosesor, memory, harddisk, dsb yang dibutuhkan oleh user. Sehingga user cukup pakai sebuah IPAD saja untuk mengoperasikan sebuah virtual super desktop atau komputer secanggih apapun karena semua proses dilakukan di cloud host/server dan IPAD itu hanya berfungsi sebagai kepanjangan monitor dan keyboard saja.

Key Properties of Virtual Machines
Partitioning Run multiple operating systems on one physical machine Divide system resources between virtual machines The hypervisor (ESX Server and ESX Server 3i) then partitions a server into multiple virtual machines. VMs are basically just files and can be treated like files. This gives VMs amazing properties that then enable a much broader set of capabilities beyond just running many VMs on one server, not possible in the physical world. These properties: Partitioning: With ESX Server you are able to run many different OS-es on the same machine Isolation: These VMs running on a physical machine are independent and unaware of each other. Infecting one doesn’t mean affecting all the others. Encapsulation: Since the entire OS + app is packaged up into a set of files – manipulation of VMs becomes very much simpler than their physical counterparts Hardware independence: Virtual machines can be created on any x86 hardware and moved to any other x86 hardware; in many cases live

Partitioning Run multiple operating systems on one physical machine Divide system resources between virtual machines Isolation Fault and security isolation at the hardware level Advanced resource controls preserve performance

Partitioning Run multiple operating systems on one physical machine Divide system resources between virtual machines Isolation Fault and security isolation at the hardware level Advanced resource controls preserve performance Encapsulation Entire state of the virtual machine can be saved to files Move and copy virtual machines as easily as moving and copying files

Partitioning Run multiple operating systems on one physical machine Divide system resources between virtual machines Isolation Fault and security isolation at the hardware level Advanced resource controls preserve performance Encapsulation Entire state of the virtual machine can be saved to files Move and copy virtual machines as easily as moving and copying files Hardware-Independence Provision or migrate any virtual machine to any similar or different physical server

Software virtualization Technology Platform
Emulation Instruction-set/pure emulation : 8086 emulator on IA-32 OS-API emulation : wine Hosted virtualization VMWare ESX server, User Mode Linux Para-virtualization Xen, Denali Container based virtualization Linux Vserver, Solaris Zones, BSD Jails, FreeVPs, OpenVz ACML – AMD Core Math Library IMKL – Intel Math kernel Library ESSL – Engineering Scientific Subroutine Library GOTO – Blas Library

Emulation or simulation
the virtual machine simulates the complete hardware, allowing an unmodified "guest" OS for a completely different CPU to be run. This approach has long been used to enable the creation of software for new processors before they were physically available. Examples include Bochs, PearPC, PPC version of Virtual PC, QEMU without acceleration, and the Hercules emulator. Emulation is implemented using a variety of techniques, from state machines to the use of dynamic recompilation on a full virtualization platform.

Hosted Virtualization
form of full virtualization where the hypervisor runs on top of a host OS

Paravirtualization the virtual machine does not necessarily simulate hardware, but instead (or in addition) offers a special API that can only be used by modifying the "guest" OS. This system call to the hypervisor is called a "hypercall" in Xen, Parallels Workstation and Enomalism; it is implemented via a DIAG ("diagnose") hardware instruction in IBM's CMS under VM (which was the origin of the term hypervisor). Examples include VMware ESX Server, Win4Lin 9x, and z/VM.

Para-virtualization (Type 1) Hosted-virtualization (Type 2)
Platform Virtualization Para-virtualization (Type 1) Hosted-virtualization (Type 2) ACML – AMD Core Math Library IMKL – Intel Math kernel Library ESSL – Engineering Scientific Subroutine Library GOTO – Blas Library

Hypervisor Hypervisors are currently classified in two types:
Type 1 hypervisor (or Type 1 virtual machine monitor) is software that runs directly on a given hardware platform (as an operating system control program). A "guest" operating system thus runs at the second level above the hardware. The classic type 1 hypervisor was CP/CMS, developed at IBM in the 1960s, ancestor of IBM's current z/VM. More recent examples are Xen, VMware's ESX Server, and Sun's Hypervisor (released in 2005). Type 2 hypervisor (or Type 2 virtual machine monitor) is software that runs within an operating system environment. A "guest" operating system thus runs at the third level above the hardware. Examples include VMware server and Microsoft Virtual Server.

This is the preferred technology for running Linux servers as it is the fastest approach. OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as CT, VEs or VPSs). Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files.

Resource Virtualization
The basic concept of platform virtualization, was later extended to the virtualization of specific system resources, such as storage volumes, name spaces, and network resources.

Resource aggregation, spanning, or concatenation combines individual components into larger resources or resource pools. For example: RAID and volume managers combine many disks into one large logical disk. Storage Virtualization refers to the process of completely abstracting logical storage from physical storage, and is commonly used in SANs. The physical storage resources are aggregated into storage pools, from which the logical storage is created. Multiple independent storage devices, which may be scattered over a network, appear to the user as a single, location-independent, monolithic storage device, which can be managed centrally. Channel bonding and network equipment use multiple links combined to work as though they offered a single, higher-bandwidth link. Virtual Private Network (VPN), Network Address Translation (NAT), and similar networking technologies create a virtualized network namespace within or across network subnets. Multiprocessor and multi-core computer systems often present what appears as a single, fast processor.

Computer clusters, grid computing, and virtual servers use the above techniques to combine multiple discrete computers into larger metacomputers. Partitioning is the splitting of a single resource (usually large), such as disk space or network bandwidth, into a number of smaller, more easily utilized resources of the same type. This is sometimes also called "zoning," especially in storage networks. Encapsulation is the hiding of resource complexity by the creation of a simplified interface. For example, CPUs often incorporate cache memory or pipelines to improve performance, but these elements are not reflected in their virtualized external interface. Similar virtualized interfaces hiding complex implementations are found in disk drives, modems, routers, and many other "smart" devices.

Linux-related virtualization projects
Type License Bochs Emulation LGPL QEMU LGPL/GPL VMware Full virtualization Proprietary z/VM Xen Paravirtualization GPL UML Linux-VServer Operating system-level virtualization OpenVZ

Virtualization Examples
Server consolidation - Virtual machines are used to consolidate many physical servers into fewer servers, which in turn host virtual machines. Each physical server is reflected as a virtual machine "guest" residing on a virtual machine host system. This is also known as Physical-to-Virtual or 'P2V' transformation.

Disaster recovery - Virtual machines can be used as "hot standby" environments for physical production servers. This changes the classical "backup-and-restore" philosophy, by providing backup images that can "boot" into live virtual machines, capable of taking over workload for a production server experiencing an outage.

Testing and training - Hardware virtualization can give root access to a virtual machine. This can be very useful such as in kernel development and operating system courses.

Portable applications - The Microsoft Windows platform has a well-known issue involving the creation of portable applications, needed (for example) when running an application from a removable drive, without installing it on the system's main disk drive. This is a particular issue with USB drives. Virtualization can be used to encapsulate the application with a redirection layer that stores temporary files, Windows Registry entries, and other state information in the application's installation directory – and not within the system's permanent file system. See portable applications for further details. It is unclear whether such implementations are currently available.

Portable workspaces - Recent technologies have used virtualization to create portable workspaces on devices like iPods and USB memory sticks. These products include: Application Level – Thinstall – which is a driver-less solution for running "Thinstalled" applications directly from removable storage without system changes or needing Admin rights OS-level – MojoPac, Ceedo, and U3 – which allows end users to install some applications onto a storage device for use on another PC. Machine-level – moka5 and LivePC – which delivers an operating system with a full software suite, including isolation and security protections.

73% of VMware customers have implemented VMotion in production
VMware VMotion 73% of VMware customers have implemented VMotion in production Live migration of virtual machines Zero downtime Starting with mobility, VMware’s VMotion permits the live migration of virtual machines from one physical server to another, with zero downtime. The key is, users see no service interruption. From their perspective, and from the VM’s perspective, NOTHING has happened. But behind the scenes, the application is now running on a completely different server. Key Points: One of our most popular products Move VMs between ESX servers with ZERO downtime End users don’t see any service interruption Neither users nor the application / VM know it’s been moved Example use case (of many!): Financial application at end of month that requires additional resources. Supported on Fibre Channel and iSCSI SAN and NAS

67% of VMware customers use DRS in production
VMware DRS 67% of VMware customers use DRS in production Business Demand Dynamic and intelligent allocation of hardware resources Ensure optimal alignment between business and IT VMotion thus provides the foundation for VMware Distributed Resource Scheduler or DRS. DRS analyzes a cluster of ESX hosts to determine virtual machine resource needs and priorities and migrates VMs as necessary to optimally load balance the system. Thus, a financial application used for closing out the books might need computing capacity just one day a month. DRS will recognize the increase in demand, and reassign other workloads to ensure resource requirements are met. Again, users are not impacted or even aware of any of this. From a business perspective, IT can now ask business partners to specifically assign priorities and service levels to specific applications, and allow the infrastructure itself to meet those service levels. Key points Leverages VMotion but adds intelligent, policy-based automation Admin sets VM resource commitments based on business partner requirements DRS determines if VM is getting resource it needs at any point in time Moves VMs around between physical servers to load balance and meet resource commitments Example use case (of many!) Rehash financial application, but focus on automation No longer need to overbuy hardware VMware® Distributed Resource Scheduler (DRS) dynamically allocates and balances computing capacity across a collection of hardware resources aggregated into logical resource pools. VMware DRS continuously monitors utilization across resource pools and intelligently allocates available resources among the virtual machines based on pre-defined rules that reflect business needs and changing priorities. When a virtual machine experiences an increased load, VMware DRS automatically allocates additional resources by redistributing virtual machines among the physical servers within the network. VMware DRS allows IT organizations to: Prioritize resources to the highest value applications in order to align resources with business goals. Optimize hardware utilization automatically and continuously to respond to changing conditions. Provide dedicated (virtual) infrastructure to business units while giving central IT complete control over hardware. Conduct zero-downtime server maintenance How does VMware DRS work? VMware DRS dynamically allocates and balances computing capacity across collections of hardware resources aggregated into logical resource pools. VMware DRS continuously monitors utilization across the resource pools and intelligently allocates available resources among virtual machines. VMware DRS allows users to define the rules and policies how virtual machines share resources and how these resources are prioritized among multiple virtual machines. When a virtual machine experiences increased load, VMware DRS first evaluates its priority against the established resource allocation rules and policies, and if justified, allocates additional resource. .Additional resources are allocated to the virtual machine by either migrating it to another server with more available resources or by making more “space” for it on the same server by migrating other virtual machines to different servers.. VMware DRS can be configured to operate in automatic or manual mode. In automatic mode, it migrates virtual machines to the most appropriate physical servers. The live migration of the virtual machines to the different physical server is executed completely transparent to end-users though VMware VMotion. In manual mode, VMware DRS provides a recommendation for optimal placement of virtual machines, and leaves it to the system administrator to decide whether to make the change. Flexible hierarchical organization of resource pools allows administrators to match available IT resources to the needs of the business organization. Individual business units can receive dedicated IT resources while still benefiting from the efficiency of resource pooling. Robust access privileges make it possible to delegate routine infrastructure tasks for a business unit resource pool to a business unit administrator. VMware DRS optimizes IT environments to align resources with business goals while ensuring flexibility and efficient utilization of hardware resources. How Is VMware DRS Used in the Enterprise? Align IT resources with business priorities. Define rules and policies how resources are prioritized among virtual machines. VMware DRS dynamically and intelligently allocates IT resources to the highest priority virtual machines to ensure optimal alignment between business and IT. Guarantee IT autonomy and service levels to business organizations. Provide dedicated IT infrastructure to business units while still profiting from higher hardware utilization through resource pooling. Dramatically increase system administrator productivity. Enable a single system administrator to monitor and effectively manage a large pool of infrastructure resources. Automate hardware maintenance. Place a physical server in maintenance mode and VMware DRS will automatically migrate all virtual machines to other physical servers, allowing server maintenance with zero downtime. What is it? Dynamic balancing of computing resources across resource pools Intelligent resource allocation based on pre-defined rules Customer Impact Align IT resources with business priorities Operational simplicity; dramatically increase system administrator productivity Add hardware dynamically to avoid over-provisioning to peak load Automate hardware maintenance Resource Pool

Ensure High availability with VMware HA
VMware HA automatically restarts virtual machines when a physical server fails X Resource Pool So that helps you deal with planned downtime. How about unplanned downtime? Well, the first line of defense is VMware High Availability, or HA. HA detects when a physical ESX server fails or stops responding. <click> It then automatically restarts those virtual machines on other servers. To be clear, this is analogous to a re-boot. I’m not claiming 100% up time, but services are restarted within minutes. As an example, I was talking to a customer the other day running desktop Operating systems (XP) on a set of servers. One entire rack lost electric power in the data center. HA automatically restarted the XP instances on other servers and no one even noticed until the next day when they walked by the racks. Users never even filed a ticket. Key points: If a physical machine fails, HA automatically restarts all of the VMs on other hosts Can work with DRS to ensure intelligent placement Minimize downtime and service disruption Simple and low cost What is VMware HA? VMware® High Availability (HA) provides easy to use, cost effective high availability for applications running in virtual machines. In the event of server failure, affected virtual machines are automatically restarted on other production servers with spare capacity. VMware HA allows IT organizations to: Minimize downtime and IT service disruption while eliminating the need for dedicated stand-by hardware and installation of additional software. Provide uniform high availability across the entire virtualized IT environment without the cost and complexity of failover solutions tied to either operating systems or specific applications. How Is VMware HA Used in the Enterprise? VMware HA allows companies to provide high availability to any application running in a virtual machine. With VMware HA IT organizations can: Protect applications with no other failover option. Provide cost-effective high availability for any application running in a virtual machine. High availability solutions are often relatively complex and expensive, and typically reserved for mission critical applications. VMware HA provides a cost-effective high availability solution that makes high availability possible for software applications that were formerly left unprotected. Establish consistent “first line of defense” for an entire IT environment. Unlike other high availability solutions that are operating system or software application specific, VMware HA represents a consistent, easy to manage high availability solution for the entire IT environment. VMware HA provides basic failover for any application with minimum cost and management overhead. How Does VMware HA Work? VMware HA continuously monitors all servers in a resource pool and detects server failures. An agent placed on each server maintains a “heartbeat” with the other servers in the resource pool and a loss of “heartbeat” initiates the restart process of all affected virtual machines on other servers. VMware HA ensures that sufficient resources are available in the resource pool at all times to be able to restart virtual machines on different physical servers in the event of server failure. Restart of virtual machines is made possible by the Virtual Machine File System (VMFS) clustered file system which gives multiple ESX Server instances read-write access to the same virtual machine files, concurrently. VMware HA is easily configured for a resource pool through VirtualCenter. What is it? Automatic restart of virtual machines in case of server failure Customer Impact Cost effective high availability for all applications No need for dedicated stand-by hardware None of the cost and complexity of clustering

Distributed Power Management
Minimize power consumption while guaranteeing service levels Consolidates workloads onto fewer servers when the cluster needs fewer resources Places unneeded servers in standby mode Brings servers back online as workload needs increase Business Demand Power Off Most servers consume 50% of their peak power requirement even when idle. Distributed Power Management helps you really manage your power bill without compromising on resource availability to virtual machines Put host in stand-by mode if: total demand + reserve <= total capacity minus host capacity Availability: Later this quarter (December). Available bundled with DRS. Experimental: VMware has a very high quality bar and we often release 1.0 products as “experimental” to get real world feedback MORE DETAIL FOR INTERESTED CUSTOMERS: Users can define: Reserve capacity to always be available Time for which load history can be monitored before the power off decision is made. Time for which load history can be monitored before the power on decision is made. Power on will also be triggered when there aren’t enough resources available to power-on a VM or when more spare capacity needed for HA. Stand-by mode means the host is powered off (S5). There are sub-modes to standby mode: When a recommendation to go into standby is accepted, the host immediately enters standby/entering mode. In this mode the machine is still powered on and may still have some VMs running on it. They must be migrated off, and no new VMs can be started/migrated on the host. When the host is evacuated, it can be powered off (standby/off) At some later point, if a recommendation to leave standby mode is accepted, the machine is powered up and begins to boot (standby/leaving). No VMs can be migrated on it until it's fully up. Automation options: Automation level Automatic – DPM makes power on/off recommendations and executes them Manual – DPM makes power on/off recommendations and admin chooses whether or not to execute them Off – DPM is disabled Automation level defined on per-cluster & per-host basis Advanced options for tuning load parameters Manual power off/on of hosts Requirements and considerations: Running Virtual Center with DRS VMotion compatible cluster Shared storage Compatible processor architectures VMkernel/VMotion network Hosts with Wake on LAN NICs with Wake on LAN Configure these as the VMotion NICs Test Wake on LAN prior to using DPM in production Manually power off and then power on each host using VC UI Resource Pool

VirtualCenter Components
VirtualCenter Management Server – Minimum one management server license required to manage individual ESX Server instances – Analogous to IBM Director server VirtualCenter Management Server VirtualCenter Consoles VirtualCenter Agent ESX Server SMP VMotion [ GOAL OF SLIDE: GET PEOPLE THINKING ABOUT THE ACTUAL DEPLOYMENT AND WHAT GOES WHERE ] The Key Components of a VirtualCenter Deployment are: 1. VirtualCenter Management Server: the service that delivers the centralized monitoring and management 2. Management Client: A Windows-based client that is the UI 3. ESX Servers: where the virtual machines run. The Management Server maintains licenses for the total number of ESX Server CPUs under management. 4. Management licenses: managed by the VirtualCenter Management servers. Keeps track of how many ESX Server CPUs can be managed. 5. VMotion licenses: also managed by the Management server. Keeps track of which ESX Server CPUs can use VMotion 6. Database: keeps the management information and provisioning templates 7. SAN: Stores the virtual machine disks and data Of these, of course, most are already present in your company – ideally, you’re just adding the management server and clients – possibly with additional ESX servers. VirtualCenter VMotion – required on every ESX Server instance on which VMotion is intended to be used Requires VC Agent License VirtualCenter Agent – this is the management agent required for every ESX Server instance being managed by VirtualCenter – Analogous to IBM Director agent

VirtualCenter Capabilities
Virtual Machine and Server Management 1 Provisioning 2 7 Programmatic Interfaces Centralized Management Security and Access Control 6 Migration 3 For background: The key tool for this is VirtualCenter. This is your single pane of glass view to your ESX servers and Virtual Machines. It provides the functions for activating VMotion, setting up DRS & HA, and monitoring system performance. It also provides fine-grain access controls allowing you to assign specific roles and privileges to your various administrators and partners. For example, the application team might have privileges to administer VM’s or set priorities within a resource pool, but not be allowed to configure ESX servers. But focusing just on the provisioning capabilities, VirtualCenter allows you manage “templates” or golden images of virtual machines that can be preconfigured with all of your typical security settings and services. When a new “server” is required for an application, you can deploy it instantly from the template. Similarly, you can clone an existing, running VM. This is helpful when you want to test a patch, for example, before applying it to the production copy of the VM. Centralized management capabilities allow to organize, monitor, and configure the entire environment through a single interface resulting in lower operating costs. Rapid provisioning with deployment wizard and virtual machine templates reduces the time and effort for creating and deploying virtual machines to a few mouse clicks. Performance monitoring capabilities, including utilization graphs of CPU, memory, Disk I/O, and Network I/O provide the detail needed to analyze the performance of physical servers, and the virtual machines they are running. Operational automation through task scheduling and alerting improves responsiveness to business needs and prioritizes actions needing the most urgent attention. Secure access control, robust permissions mechanisms, and integration with Microsoft® Active Directory guarantee authorized access to the environment and its virtual machines. Responsibilities can be delegated to tiers of system administrators. Resource optimization through performance monitoring, multi-server resource pools, and dynamic workload balancing delivers the highest virtual machine to physical server ratio while improving service levels to software applications. Automated data center-wide resource optimization with VMware DRS aligns available resources with pre-defined business priorities while streamlining labor and resource intensive operations across disparate hardware, operating system, and software applications. Migration of live virtual machines across entirely separate physical servers with VMware VMotion makes the maintenance of IT environments non-disruptive. High Availability provided by VMware HA enables broad-based, cost-effective application failover of hardware and operating systems. Programmatic interfaces through the VMware Infrastructure SDK. Provide Web Services APIs to access the functionality and data provided through the graphical user interfaces, and enable integration third party systems management products as well as extension of the core functionality. System Monitoring 5 Resource Management 4 What's new

Introducing VMware Site Recovery Manager
Site Recovery Manager leverages VMware Infrastructure to transform disaster recovery Simplifies and automates disaster recovery workflows: Setup, testing, failover, failback Provides central management of recovery plans from VirtualCenter Turns manual recovery processes into automated recovery plans Simplifies integration with 3rd-party storage replication Availability: Q1 of next year Pricing: Not announced. Will not be a part of VI3. Will be a separate product like Lab Manager. Provides a central point of management for disaster recovery plans Plug-in to VMware VirtualCenter Manage recovery plans for virtual machines managed by VirtualCenter Enables pre-programming of disaster recovery plans Map resources between production and recovery sites Program steps of recovery process Automates key disaster recovery workflows Automate tests of recovery process Automate failover in disaster scenarios Simplify failback to primary datacenter

Replication with VMware: Array-Based Replication
DR SITE PRIMARY Site Failure WAN or Dark Fiber Array-Based Replication (SRDF, SnapMirror, etc.) NOTE to presenter : slide is automatically animated – click one click and test before you use. Host-based (earlier slide) can be used when performance SLA’s are moderate For demanding performance requirements and lowest RTO/RPO applications, consider off-host replication via storage array or storage network-based replication. We will be discussing array based replication technology here – where the replication load is now being handled by the storage processors within the storage arrays on the primary and DR sites (connected by dark-fiber or a WAN) Array-based replication allows you to easily replicate entire virtual machines simply by replicating the storage disks on which they reside—virtual machines are just like any other files residing on a disk Example array-based replication vendors include – EMC (SRD)F, NetApp (SnapMirror), IBM (FlashCopy), HP Target VMFS Source VMFS SLA’s = High

Virtualization.

Presentasi serupa

Presentasi berjudul: "Virtualization."— Transcript presentasi:

Presentasi serupa

Tentang proyek

Tanggapan

Masuk

Otorisasi melalui jaringan sosial:

Virtualization.

Presentasi serupa

Presentasi berjudul: "Virtualization."— Transcript presentasi:

Presentasi serupa

Tentang proyek

Tanggapan