1. Sauvegarde en environnement virtualisé

2. Agenda
VMware
Hyper-V

3. VMware

4. VMware Virtualization Layer
Backup image VMware
Déduplication intra et inter VMs
Changed Block Tracking : réduction des temps de backup et de restauration
File-level recovery depuis le backup image
Restauration vers VM d’origine, VM existante ou nouvelle VM
Load balancing des Proxy Servers
Resource Pool
VMware Virtualization Layer
x86 Architecture
Stockage
Mount
Now let’s look at using Avamar to provide image-level backups, taking advantage of VMware’s vStorage API for Data Protection.
The vStorage API approach involves creating VMware snapshots of a virtual machine, presenting it to a proxy host—which can now be running in another virtual machine—and then backing up the VMDK file from the proxy. Companies like this approach because it moves the backup process away from the virtual machines where their applications are running, which avoids any performance impact to the application.
In this case, you would install the Avamar agent on the proxy host, treat it as the backup client, and run your backups from there to an Avamar Data Store. Because of VMware advancements, including the ability to run the proxy server in a virtual machine and to dynamically “hot-add” volumes to that proxy without physically moving data across the network, Avamar is able to back up large virtual machines in just minutes.
Something to think about when considering backup for Vblocks or other large virtual computing environments with hundreds of virtual machines to protect.
Avamar can load balance jobs across virtual proxy servers to assure that individual proxies are not overtaxed. Jobs can also be directed to available proxies to handle high-priority workloads. This approach helps drive down costs by having fewer proxies to manage.
Avamar can also leverage some new capabilities provided by VMware to only back up changed blocks. This lessens the backup processing that Avamar has to do, and speeds up the backups even further.
And Avamar’s architecture was designed to reconcile daily changed block backups into full instances for recovery. This is different from most backup applications that require at least a periodic full backup. This means Avamar can process the changed blocks identified by VMware into a new full recoverable image on an ongoing basis. As a result, recovery is much faster and more reliable.
One feature that companies really would like is the ability to do one backup, and have the option of a bare-metal restore OR a more granular file-level recovery. Taking advantage of its integrated file system, Avamar can provide this capability—and you don’t have to mount the VMDK in order to do it.
Finally, just as in physical environments, Avamar’s deduplicated replication of protected VMDK files allows for network-efficient disaster recovery—and importantly, great flexibility in how you can restore—either to the original virtual machine or to a new location.

5. Load Balancing via serveur Proxy universel
Cluster Vmware ESX
ESX SERVER 1
. . .
ESX SERVER N A B C D E F
Proxy VM
Proxy VM
VMware
vCenter Server
This example illustrates the power and performance of Avamar’s unique proxy server load balancing, which increases backup throughput. This is all automatic and transparent, simplifying the management of virtual machine backup.
Note to Presenter: Click now in Slide Show mode for animation.
As you can see, the backup process is assigned to the proxy VM that is least busy, which makes for a much faster backup. Decreased costs come from increased efficiencies of current virtual machine infrastructure.
= Données

6. Intégration avec le vCenter VMware
One of the great values of server virtualization is how much faster and easier it is to stand up a new server implementation. Virtual machines are easy to create, are portable, and can move from ESX host to ESX host automatically.
When new virtual servers can be created in an instant, with a point and a click, how can you assure they are associated with the right backup policy?
Avamar has taken the steps to integrate with VMware’s management tools—particularly vCenter Server—in order to make management of backup and recovery more effective.
With Avamar, you can access vCenter Server directly from the Avamar user interface. New virtual machines are automatically discovered and displayed, so that administrators can apply an appropriate backup policy. Then VMs can be sorted so that their current backup status can be assessed.
[Click] Administrators can see which virtual machines are backed up (either guest or image) and which ones are not well protected, and then they can make adjustments to correct.
Point de gestion unique pour toutes les options de sauvegarde VMware

7. Souplesse de restauration en mode image
NEW
Original
Existing
Restauration dans la VM d’origine
Restauration dans une VM existante
Restauration dans une nouvelle VM
Virtual Infrastructure
Note to Presenter: View in Slide Show mode for animation.
Avamar image-level backups leverage an architecture that includes a native metadata index for each backup instance. Unlike other backup software, which must create a metadata index during or after the backup is complete, Avamar’s native index provides end users with a granular view of image backup content, which can be used to perform file-level recovery without first requiring the image backup to be mounted. In addition, files can be restored to their original location or to an alternative location.

8. Restauration rapide des machines virtuelles
Changed block backup
Réduit les temps de sauvegarde
Changed block restore
Transfer t des delta blocks entre le backup set et la VM
Accélère les restaurations image
Restauration totale d’une VM en minutes vs. heures
CHANGED BLOCK TRACKING BACKUP
LAN-free
LAN/WAN VM
Image Proxy
CBT Blocks
Unique Blocks
STANDARD RESTORE
LAN-free
LAN/WAN VM
Image Proxy
Whole VM
Whole VM
CHANGED BLOCK TRACKING RESTORE
LAN-free
LAN/WAN VM
Image Proxy
With the latest release of Avamar, an even faster restore process has been developed. Leveraging Changed Block Tracking for backup, Avamar will restore VMware disk format (VMDK) files even faster. Let see how this works.
Note to Presenter: Click now in Slide Show mode for animation.
First a snapshot of the VMDK is presented to the virtual proxy server and VMware presents Avamar with a list of changed blocks. Next Avamar will break these changed blocks into variable length segments to determine which specific segments are unique and sending only those segments to the Avamar Data Store. Now let’s take a look at the standard restore process.
Prior to the Avamar 6.0 release, the recovery process simply restored either the full file (if in a Windows operating system) or the full VMDK image.
Now Avamar tracks the delta of changed blocks to speed the recovery process by restoring only the unique elements required to rebuild the file, folder, or VMDK requested—resulting in much faster restores.
CBT Blocks
CBT Blocks

9. Autres fonctionnalités
Granularité disque
Restauration thin provisionnée
Faster recovery is accomplished in numerous ways with Avamar including file-level from an image-level backup done in Linux or Windows, disk-level granularity and thin-provisioned restore. All of these mean a faster recovery since most end-users only need to restore a file or folder at most. There is no need to restore the entire VM.
Disk-level granularity allows you to minimize your backup times, reduce network traffic, and consume less storage by enabling backup and recover of only what is required. For example, a Windows VM may have a C:\ and D:\ drive but only the C:\ needs to be backed up. This feature allows a specific disk backup. On the restore side, if you backed up the whole VM and only lost a single drive you now have the ability to restore just that drive. On Linux you can also achieve greater efficiency by excluding a swap drive/partition.
Note to Presenter: Click now in Slide Show mode for animation.
Thin-provisioned recovery will reduce storage consumption. VMware allows virtual machine disks to be thin-provisioned. A thin provisioned disk only consumes physical capacity for the amount of space that is actually in use. For example, if a VM has a 200GB disk but only 50GB is in use, only 50GB is actually reserved for that VM. Avamar can now preserve the thin-provisioned state of the VM, thus using less disk space.

10. Instant Access . . . Virtual Infrastructure
2. La VM est “instantanément”
accédée en bootant
depuis le Datastore NFS
. . .
Virtual Infrastructure
1. Data Domain
est présenté comme
un Datastore VMware
via NFS
Storage
Memory
CPU
Consomme de ressources CPU et mémoire de l’ESX
3. La VM en cours d’exécution
est déplacée vers le stockage
de production par vMotion

11. Intégration d’Avamar dans NetWorker 8.1
Nouvelle Topologie
vSphere
vSphere Web Client
NetWorker Virtual Backup Appliance
Proxy Avamar
Serveur NetWorker
Avamar Virtual Edition
NetWorker v8.1
Virtual
Backup Appliance
Avamar 7 and NetWorker 8.1 will share the same fundamental dedup engine / technology implemented as a Virtual Backup Appliance to support Vmware backups and Recovery., meaning NW will benefit from teh same set of features that have been tocuh so far in this presentation, except for granular vmdk back.
There will be mino rworkflow differences, i.e. some backup management feature will have to be configured in the „Avamar“ VBA, while the „NetWorker“ VBA will be exposed to a vSphere administrator only and does not require access for the NetWorker administrator. The NetWorker administrator will only care and setup the infrastructure to successfulyl run Vmware backups and Recoveries (i.e. backup target, retention policy, number of copies/replicas, scheduling). NetWorker has no notion of any of the VMs that need to be backed up, this means in particular that no configuration of any VM as a client in NetWorker and no (VM) client name resolution will be required anymore.
There will be three non overlapping roles, a vSphere admin, who is responsible for assigning a VM to a backup policy ( we will touch on this a little bit later), a NetWorker backup admin, who will manage the backup infrastructure, i.e. the policy, and a (VM) client‘s system admin, who will run browser based recoveries.
This is a true cloud based approach, as the VM admin will deal with the content, but not where the content will be backed up to. The NW admin will not deal with the content all all, but just determine where to put it and how many copies to create.
The VM‘s system admin doesn‘t even know anything about how the content is protected, but has full control over file level recovery for Windows AND Linux.
NetWorker
Management
Console
Plugin Client Web vSphere

12. NetWorker 8.1 VMWare Next-Gen
Fonctionnalités :
Interface d’administration intégrée à vSphere
Interface web de restauration pour la restauration fichier
Sauvegarde / restauration en mode Change Block Tracking
Sauvegarde en mode Full Forever
Restauration incrémentales
Optimisé pour la sauvegarde sur le DataDomain
Sauvegarde possible sur du stockage local
Découverte automatique et protection des VMs basée sur des politiques définies par l’utilisateur
Sauvegarde assignée à la VM ou aux groupes de VMs
Coexiste avec la solution de sauvegarde actuelle
Sauvegarde directe vers bandes
vSphere
vSphere Web Client
NetWorker Virtual Backup Appliance
NetWorker Server
NMC

13. NetWorker 8.1 VMWare Next-Gen : Flux de données
Toute l’infrastructure est contrôlée via NetWorker
Sauvegarde via VBA vers DDBoost
Clonage possible ensuite de DDBoost vers un deuxième DD via CCR
Clonage possible ensuite vers bande physique
Restauration via l’interface Vsphere
Restauration image ou fichier
Restauration fichier possible depuis une interface web utilisateur
ProxyVM
Win VM
VMware ESXi & ESX
NetWorker
Linux VM
vSphere Web UI

14. NetWorker 8.1 Configuration du workflow VBA
Let‘s touch on how all the different bulding blocks come together. The vCenter will download the VBA from Powerlink or support.emc.com and deploy it in vCenter. It comes in .ova format. All values for proper network setup, like gateway, Ip address, network mask, name servers and host name, will have to be entered durign the pre-deployment phase.
You will boot your VBA after deployment and continue with additional configuration steps. The configuration will typically not take less than a minute and the basic workflow is next, next, next  [SPEAKERS: just advance from one to the next screenshot by hitting click or space]. NetWorker options have already been set and will just habe to be confirmed. Then you will set the timezone and change the VBA‘s password. Finally you will Finally you will register with vCenter and the NetWorker server. DEAL done. Configuration willbe finsihed that easily.
A final screen will come up and show that all services are running. Please note that there will be no CLI configuration steps required at all. Please note as well (on the right hand pane of this very screenshot) , that you can collect all log files from the VBA without having to know where those are located or manual intervention.
This is extremely easy and bullet proof.
VBA will reboot and set up the NetWorkler resources as well as runnign internal checks, as soon as all configuration steps have been compelted.
Though the VBA is based on Avamar, no Avamar knowledge will be required, though it wouldn‘t heart. VBA is under full control of NetWorker. Backups and Recovers can be run any time, as Avamar housekeeping will no longer block any operation.

15. Monitoring de la politique de sauvegarde VMware
NetWorker 8.1
Intégration Vmware – Vue de la NMC
Reporting
Monitoring de la politique de sauvegarde VMware
[1. screenshot] A NW VBA resource will be created, as part of the VBA‘s first reboot process, for each VBA. Please note that you may deploy as many VBAs as you want, all of which can be leveraged and managed by Networker.
Each VBA Networker resource will display status info of the VBA.
Pleas enote as well that you can right click on the VBA resource and navigate from here to the VBA configuration or the vSPhere Web Client. A NetWorke r can set up NMC with read permissions for a vSphere admin and thus provide help how to logon to the VBA / vSphere cweb client. Hence no need to remenber a URL.
[click twice]
One of the core enhancements in NW 8.1 is the (VBA) policy/workflow manager. Policies are private to VBAs, but can as well be shared amoung VBAs.
A Policy consists of a backup schedule and target at least. This is similar to a NetWorker group resource. However, you can creat edependencies in the policy manager, e.g. like creating an optional clone, as soon as the backup has finished. You may as well create multiple optional clonse, e.g. one to another DataDomain System and yet another to tape, i.e.e tape out is as easy as it always used to be in NetWorker.
The workflow does require a DataDomain System, just because the entire workflow is optimzed for backup to and recover from disk. Direct tape out is not supported, but supported as a clone process. The workflow is presented as a picture as well. This is extremly handy for complex workflows.
You can of course create as many clone copies, even with different retention policies, you may want. All NetWorker post-backup operations , like changing the retention policy, staging savesets and alike are supported.
A Vmware backup can be monitored in NMC just like „savegroup“ backups. However, clones and clone status will be included in the view. A policy, similarly to a savegrp, can be started from NMC as well. There is as well a nsrpolicy command to easily integrate with third party job management frameworks.
NetWorke rhas always been good on reporting and NetWorker 8.1 adds reporting for Vmware backups. This will enable you e.g. to review the dedup rate of your Vmware backups immediately.
VBA Policy Manager
Vue VBA

16. NetWorker 8.1 Intégration Vmware – vue du vCenter Monitoring
Reporting de l’état
Monitoring
Affectation des politiques
The backup policies that have been assigned to a particular VBA will show up in the VBA.
The vSphere admin will pick and chioose from those plocies and either assign individual VMs or a resource group to a policy.
A policy will be applied automatically to newly added VMs to a resource group automatically without the requirement for any further configuration steps. In other words, a VM willö be protected as soon as it has been deployed by the vSpehere admin. This is a major change to NetWorker 7.6.x and 8.0.x, as no configuration is required in NetWorker 8.1 at all.
Autoprotection can be implemented by assigning a policy to a vCenter, ESX host or cluster and, yet again, as soon as a VM will be added to any of those VM resources, the policy of which will be applied to the VMs.
Pretty slick, easy to use and bullet proof. Zero management for backup admin. Zero backup management for vSpehere admin. Those can focus on managing their Vcenter only !!
[click twice]
The VBA‘s status and the backup progress is presented to the Vsphere admin, thanks to the smart integratioin in vCenter, as well. There is no need for a Vsphere admin to become familiar with NMC …
The vSphere would as well run recovers for VMs from the Vsphere Web client GUI.
All recovery option already known from Avamar (i.e choice of datastore to recover to, selection of provisioning modell, recover to existing, new or renamed VM ) are supported.
Incremental restore, i.e. CBT image restore, is of course supported as well
Restauration
vCenter Backup UI Plugin

17. Client Web vSphere – Login
Let the Vmware administrators managing the backups & recoveries. The NetWorker version of the VBA would not show a backup server. The NetWorker Backup server is configured during the deployment phase of the VBA. The relationship is static, but can be reconfigured any time. It’s the Vsphere admin who configures the VBA.

18. Client Web vSphere – Backup Wizard

19. Client Web vSphere – Backup

20. Client Web vSphere – Restauration

21. Client Web vSphere – Wizard Restauration

22. Client Web vSphere – Rapports

23. Client Web vSphere – Configuration

24. Restauration fichiers Self-Service
Let the Vmware users managing their recoveries

25. Politiques Dynamiques/Container
Avamar example, Also exists in NetWorker 8.1, but with a different look and feel
Improve operations

26. NetWorker v8.1 vs Avamar v7 Fonctionnalité NetWorker Avamar
CBT backup et restore X
Incrémental forever
FLR – Windows et Linux
FLR Self-service
Backup vers Data Domain
Load balancing des proxys
Politiques Dynamiques
Instant access depuis Data Domain
Prévu fin d’année
Command Line Interface
Backup VMDK sélectif
Over time, all Avamar features will be introduced into NetWorker

27. Hyper-V

28. Completeness of Vision
Quick Market View
Gartner MQ for x86 Virtualization (June, 2012)
Completeness of Vision
Ability to Execute
VMware 
leaders
challengers
niche players
visionaries
 Microsoft
 Citrix
 Oracle
 RedHat
VMware: Best choice for automated and virtualized enterprises or private/hybrid cloud
Citrix: Suitable for enterprise customers adopting desktop virtualization
Microsoft: Viable alternative to VMware in midmarket and branch deployments. Hyper-V 3.0 and SCVMM 2012 narrowing functionality gaps
Oracle VM: Suitable for Tier1 Oracle workloads
Red Hat: Targeting customers with Linux instances that are under virtualized (35-45%) with built in KVM
I wanted to start with summarizing the virtualization landscape and setting the stage in terms of leaders and niche players.
[Review Gartner’s positioning.]
This is based on Gartner Magic Quadrant for x86 Virtualization released in June, At that time, it did not factor in Hyper-V 3.0 and SC VMM 2012, so Microsoft probably moved up a bit since.
I’ll cover this later on, but as you know, our investment has been about 85-90% Vmware, the rest MS and really nothing relative to the other players.

29. Virtualization Market
IDC Tracker – Q3 2012
26% Market Share for Hyper-V
InfoWorld April 2013 – Virtualization showdown: Microsoft Hyper-V 2012 vs. VMware vSphere 5.1
“Choosing between the two vendors should be relatively easy for the high-end and low-end customers. VMware still wins the big shops, and Microsoft is now the clear choice for the small guys. The fight over the middle has only just begun…”

30. Microsoft Cloud OS Vision
Public Cloud
Azure Virtual Machines
Windows Azure Services 1
Consistent
Platform
Windows Azure Services
Private Cloud
Service Providers
DEVELOPMENT
MANAGEMENT
DATA
IDENTITY
VIRTUALIZATION

31. Windows Server Management Marketing
Cloud OS Consistent Experiences
Customer
Service Provider
Windows Azure
Web Sites
Apps
Database
VMs
Service
Plans
Users
Provider Portal
Consumer Self-Service Portal
Web Sites
Apps
Database
VMs
Self Service Portal Moves On-Premises
Subscriber Self-Service Portal
Common Mgt. Experience
Service Management API
Service Management API
Worker
Role
Web
Sites VM
Role
SQL
Service
Bus
Caching
Other
Services
CDN.
Media,, etc.
Cloud-Enabled Services Move On-Premises
Web
Sites
VMs
SQL
Service
Bus
Future Services
R2 w/ Service Provider Foundation
Workload Portability
Consistent Dev. Experience
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
3/30/2017

32. EMC et Microsoft : une Alliance Unique
EMC et MS partagent la même vision sur l’importance de l’information
Un partenariat de plus de 16 ans, continuellement accru
Partenariat approfondi sur les produits comme sur les services
Partage de propriétés intellectuelles
EMC participe activement aux programmes Microsoft Technology Adopter Programs (TAPs) et Rapid Deployment Programs (RDP)
Déploiements mutuels internes des technologies de l’autre
Des milliers de clients communs
Revues trimestrielles par le management
22 fois élu Partner of the Year
consultants worldwide
Accord de support
Equipement dans les labs de Redmond
We often get asked why our alliance with Microsoft is unique. Our uniqueness really stems from the breadth of capabilities—across hardware, software, services and technology sharing—and the unique multi-level executive relationship we have with Microsoft. This is combined with the fact that EMC and Microsoft have aligned directions and solution sets. Microsoft’s march to the enterprise has quickly turned them into a software platform company, and one that is counted on for mission-critical applications. Their platform is also driving the lion’s share of information growth within our customers. These new technologies are the exciting next step. The fact that EMC’s data center experience, and focus on information infrastructure helps answer the challenges that Microsoft customers encounter as they move in this direction is one of the main reasons for EMC’s strong alliance with Microsoft.
The rest of these areas we are about to discuss may not be unique on it’s own right, but the combination and depth of work that EMC and Microsoft work on in each of them truly separates us from the pack of Microsoft partners.
EMC and Microsoft have a very specific, worldwide, customer-centric go-to-market alliance. This means that the two companies manage, at a corporate level, dedicated resources—both in terms of money and people—focused on developing, proposing and deploying joint solutions. Executives across multiple areas of our business meet regularly to discuss the progress of technology, business, and solution initiatives. This includes a detailed quarterly business review that occurs at an executive level.
As many Microsoft partners do, EMC deploys Microsoft technology across our business for messaging and desktops among other areas. Often more interesting, is whether Microsoft puts the same faith in their partners technology. And Microsoft has placed significant investments in EMC technology to drive core areas of their business. Microsoft uses EMC hardware, software, and our services capabilities within its own IT environment.
Lastly—and admittedly hard to specifically qualify—is that EMC and Microsoft have a large amount of synergies relative to addressing joint customer needs. EMC’s vast experience with mission-critical computing lines up with the increasing customer interest in leveraging Microsoft technology for these areas of their business. Our solutions are built to ensure the infrastructure is ready for those demands.
Key facts to highlight:
EMC has Proven deployment experience that speeds implementation and minimizes risk
Deep virtualization expertise
Hundreds of thousands of Exchange 2007 users migrated
We participate in Exchange 2010 TAP and Microsoft Rapid Deployment Program (RDP) Participant
Talent
Thought leaders with elite Microsoft certifications provide in-depth expertise and insight
Worldwide consultants certified as MCPs, MVPs, Rangers/Masters, and Certified Architects
Over 75% of program managers are certified PMPs
Microsoft Relationship
Comprehensive alliance leverages the leadership and innovation of both organizations
Global System Integrator, Global Alliance Partner, Worldwide ISV
Microsoft Gold Certified Partner with 16 competencies
21-time Partner of the Year winner; FASTforward Enterprise Search Innovation Award

33. Top Reasons Why EMC Backup is the Best Choice for Microsoft

34. Points clés de la protection Hyper-V
Image Based Backup & Recovery
Pour serveurs Hyper-V Stand-Alone, Hyper-V over CSV, Hyper-V over SMB-3
Protection sans agents
Déduplication des données à la source
Client Direct avec Data Domain Boost
Proxy Backup pour Hyper-V over CSV élimine la charge du backup
Hyper-V Granular Level Recoveries (GLR) : restauration de fichiers en quelques secondes
Facile à utiliser et à gérer via des Configuration Wizards faciles d’emploi
Avamar users can leverage any combination of the Hyper-V backup methods, with or without deduplication, to craft a backup environment to suit their needs and recovery time and recovery point objective (RTO/RPO) requirements.
No matter where your stage of adoption of Hyper-V, Avamar can provide an appropriate solution to help you best manage protection and recovery.
Avamar can help speed backup and provide offerings to protect the entire enterprise, from the data center to the remote office. And by combining capabilities into a single solution, Avamar helps simplify the number and complexity of tools that are necessary to learn and use for backup and recovery.

35. Support d’Hyper-V 2012 Performances accrues
Proxy backup pour Clusters Hyper-V over CSV
Elimination de la redirection d’I/O
Backups parallèles de serveurs Hyper-V
Support de DD Boost over FC (NetWorker seulement)
Meilleur support d’Hyper-V over SMB-3
Management simple
Wizard de configuration client
Exclusion de VMs du backup (Avamar seulement)
In Guest backup Copy (pas de troncature de Log) ou Full
Bénéfices
Backups plus rapides
Pas d’impact sur les serveurs Hyper-V durant le backup
Configuration et gestion simplifiées
Souplesse opérationnelle accrue
Support de tous les workloads Hyper-V
In the Avamar 7 release, we add support for Hyper-V 2012 to our existing Hyper-V 2008 support. For both Hyper-V 2008 R2 and Hyper-V 2012, Avamar now supports backup proxies for clustered shared volumes. These proxies (one per CSV) can be backup specific servers added to the CSV cluster or lightly loaded Hyper-V servers in the CSV cluster. The CSV Proxy can backup all of the Hyper-V servers in the cluster for impact free backups. Another capability is concurrent backups. In Avamar 6.1 and with Hyper-V 2008 R2, if a 4-node Hyper-V over CSV cluster was backed up, each Hyper-V server was backed up sequentially. The new Hyper-V 2012 over CSV Proxy support can backup all Hyper-V servers in the CSV cluster simultaneously.
Hyper-V I/O Redirection Eliminated for Backup
In a Hyper-V 2008 R2 implementation, when a backup was started for one server in a Hyper-V over CSV cluster, all of the other Hyper-V servers in the cluster went into I/O redirection mode. This meant for the life of the backup, all of these other Hyper-V servers had to send their I/O write requests to the Hyper-V server being backed up, slowing their write I/O performance. This re-direction now eliminated in Hyper-V 2012 backups with Avamar.
In-Guest VSS Options: Copy or Full Backup
With Avamar 6.1 and Hyper-V 2008 R2, when a VM was backed up, inside the guest a VSS full backup was performed, resulting in application log truncation. For Hyper-V 2012 Avamar now gives the user an option of full or copy. VSS Copy selection will not truncate in-guest application logs, so this helps customers that want to run VM image backups and in-guest application backups, with log truncation controlled in-guest.
Exclude VM’s from Backup
Administrators can backup ‘ALL’ VMs in a Hyper-V over CSV cluster or stand-alone Hyper-V server and simply exclude certain VMs in an exclude list. This is much easier and faster to configure than having to add each VM to the policy.
The Client Configuration Wizard makes setup even easier.
So what does all mean to your customers? A long list of benefits including faster backups, no impact to Hyper-V servers during the backup, simplified configuration and management, increased operational flexibility and the support for all Hyper-V workloads. Just as Hyper-V 2012 provides advanced capabilities to handle more robust environments, so does Avamar 7.

36. Serveur Windows Hyper-V
Image Backup Hyper-V
Protection Hyper-V complète
Protection de l’OS, du System State, des Data Volumes et de la Configuration Database Hyper-V
Les Backups Image des Guests Hyper-V offrent à la fois une protection DR et granulaire
Supporte tous les Operating Systems Guest Hyper-V
Windows Server 2012/2008R2/2008, Windows Server 2003, Windows 8/7, Windows Vista, XP, SUSE Linux, Red Hat Linux, CentOS ( pas de restauration granulaire pour Linux)
Tire parti du Writer VSS Hyper-V
Quiesces l’OS Windows et les applications dans les guests pour une consistance Os et applicative
Nombreuses options de backup Hyper-V
Support des serveurs Hyper-V standalones
Federated Hyper-V Cluster Shared Volume CSV Backup
Backups multi-streams vers Data Domain via DD Boost ou vers du disque simple (AFTD)
NetWorker
Avamar
Avamar provides complete protection for Microsoft Hyper-V servers. This protection includes protection for the physical Hyper-V server itself including the base Windows operating system, OS system state, all data volumes and also Hyper-V configuration files.
For virtual machines (VM’s) located on the Hyper-V server, Avamar completes a single image level backup for virtual machines, and this single backup can be used for image level recoveries along with granular level recoveries of files within the VM. This image level backup support leverages the Hyper-V VSS Writer for OS and application consistency within each guest. Avamar supports all of the VM guest level operating systems that Microsoft supports with Hyper-V.
A unique part of the Avamar Hyper-V VM image level protection is there is no requirement for in-guest Avamar software. This reduces complexity for customers in maintaining Avamar software within each VM.
The Avamar Hyper-V support is flexible enough to meet any customers Hyper-V deployments. There is full support for stand-alone Hyper-V servers and also Hyper-V servers in a cluster using Cluster Shared Volumes (CSV’s). Support for Hyper-V clusters is ‘federated’, in that backup schedules are set-up for the entire Hyper-V cluster and Avamar will automatically find VM’s wherever they are located.
Avamar Hyper-V backups to Avamar DataStores or Data Domain Systems leverage multi-streaming, allowing multiple VM’s to be backed up simultaniously. This provides very high speed backups for large scale Hyper-V deployments.
Virtual Machines
APP OS
APP OS
APP OS
Serveur Windows Hyper-V
Serveur physique

37. Backups Hyper-V fédérés
Federated Hyper-V CSV backup met en œuvre le load-balancing pour accélérer la sauvegarde
Entièrement automatisé
Sauvegarde des VMs ordonnancée depuis le cluster CSV
Supporte la migration des VMs de/vers différents nœuds Hyper-V CSV
Souplesse d’ordonnancement des backups CSV
Backup de toutes les VMs du cluster CSV
Backup des VMs individuelles
Avamar provides federated data protection for Hyper-V servers in a cluster using Cluster Shared Volumes (CSV’s). This allows customers to set-up backup schedules for the entire Hyper-V cluster and Avamar will automatically find VMs wherever they are located and then complete the backup.
Here is an example. A customer has a Hyper-V Cluster with two Hyper-V physical servers in the cluster. Lets call these Hyper-V servers HV1 and HV2. Within the cluster are multiple virtual machines which can be live migrated from Hyper-V server HV1 and HV2 by the customer for operational or disaster recovery purposes. In this scenario, a customer would set-up federated backups for the Hyper-V cluster, not individual Hyper-V servers in the cluster. This makes Hyper-V backup and recovery independent of the physical location of any given VM. VM1 could be located on Hyper-V server HV1 on Monday, migrated to Hyper-V server HV2 on Tuesday, and Avamar will automatically find it each data and protect it via a common data protection schedule.

38. Hyper-V over CSV avec Proxy Node Backup (Hyper-V 2008)
Solution actuelle :
Backup “On Host”
Redirection des I/O (écriture)
Backups séquentiels
NetWorker
Backup
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
Backup
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
Backup
Backup
VM1 Files
VM2 Files
Cluster Node #1
Cluster Node #2
Cluster Node #3
Cluster Node #4
Clustered Shared
Volumes
Backup
Hyper-V over CSV with Proxy Node Backup is a new feature in upcoming Avamar and NetWorker releases. With this new support a physical proxy can be assigned to support backup and restore of all of the Hyper-V Servers in the CSV cluster. These proxies (one per CSV) can be backup specific servers added to the CSV cluster or lightly loaded Hyper-V servers in the CSV cluster. The CSV Proxy can backup all of the Hyper-V servers in the cluster for impact free backups. Another nice change here is parallel backups. In prior releases, if a 4-node Hyper-V over CSV cluster was backed up, each Hyper-V server was backed up sequentially. The new Hyper-V 2012 over CSV Proxy support can backup all Hyper-V servers in the CSV cluster simultaneously
Avamar and NetWorker provide Federated Hyper-V CSV Backup data protection for Hyper-V servers in a cluster using Cluster Shared Volumes (CSV’s). The Avamar Plug-in for Hyper-V VSS supports failover clusters through a federated architecture that manages backup and restore across the Hyper-V cluster. The federated architecture provides failover resiliency for Hyper-V highly available virtual machines by determining the physical cluster node where a virtual machine is running at the time of a backup or recovery operation. This allows customers to set-up backup schedules for the entire Hyper-V cluster and Avamar will automatically find VM’s wherever they are located.
Here is an example. A customer has a Hyper-V Cluster with two Hyper-V physical servers in the cluster. Lets call these Hyper-V servers HV1 and HV2. Within the cluster are multiple virtual machines which can be live migrated from Hyper-V server HV1 and HV2 by the customer for operational or disaster recovery purposes. In this scenario, a customer would set-up Federated Hyper-V CSV Backup for the Hyper-V cluster, not individual Hyper-V servers in the cluster. This makes Hyper-V backup and recovery independent of the physical location of any given VM. VM1 could be located on Hyper-V server HV1 on Monday, migrated to Hyper-V server HV2 on Tuesday, and Avamar will automatically find it each data and protect it via a common data protection schedule.
Hyper-V I/O Redirection Eliminated for Backup
This is one we ‘get for free’ from Microsoft in Hyper-V With Hyper-V 2008 R2, when backup was started for one server in a Hyper-V over CSV cluster, all of the other Hyper-V servers in the cluster went into I/O redirection mode. This meant for the life of the backup, all of these other Hyper-V servers had to send their I/O write requests to the Hyper-V server being backed up, slowing their write I/O performance. This is now eliminated in Hyper-V 2012
Backup
Backup
Backup
Hyper-V over CSV

39. Hyper-V over CSV avec Proxy Node Backup (Hyper-V 2012)
Avamar
NetWorker
Solution NW 8.1 :
Proxy Backup
Backups parallèles
Elimination de la redirection des I/O
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
VM1
Virtual Machines
VM2
VMM
VM3
Virtual Machine Manager
Backup
VM1 Files
VM2 Files
Cluster Node #1
Cluster Node #2
Cluster Node #3
Cluster Node #4
Hyper-V over CSV with Proxy Node Backup is a new feature in upcoming NetWorker release. With this new support a physical proxy can be assigned to support backup and restore of all of the Hyper-V Servers in the CSV cluster. These proxies (one per CSV) can be backup specific servers added to the CSV cluster or lightly loaded Hyper-V servers in the CSV cluster. The CSV Proxy can backup all of the Hyper-V servers in the cluster for impact free backups. Another nice change here is parallel backups. In prior releases, if a 4-node Hyper-V over CSV cluster was backed up, each Hyper-V server was backed up sequentially. The new Hyper-V 2012 over CSV Proxy support can backup all Hyper-V servers in the CSV cluster simultaneously
NetWorker provide Federated Hyper-V CSV Backup data protection for Hyper-V servers in a cluster using Cluster Shared Volumes (CSV’s). The neetowrker Plug-in for Hyper-V VSS supports failover clusters through a federated architecture that manages backup and restore across the Hyper-V cluster. The federated architecture provides failover resiliency for Hyper-V highly available virtual machines by determining the physical cluster node where a virtual machine is running at the time of a backup or recovery operation. This allows customers to set-up backup schedules for the entire Hyper-V cluster and Avamar will automatically find VM’s wherever they are located.
Here is an example. A customer has a Hyper-V Cluster with two Hyper-V physical servers in the cluster. Lets call these Hyper-V servers HV1 and HV2. Within the cluster are multiple virtual machines which can be live migrated from Hyper-V server HV1 and HV2 by the customer for operational or disaster recovery purposes. In this scenario, a customer would set-up Federated Hyper-V CSV Backup for the Hyper-V cluster, not individual Hyper-V servers in the cluster. This makes Hyper-V backup and recovery independent of the physical location of any given VM. VM1 could be located on Hyper-V server HV1 on Monday, migrated to Hyper-V server HV2 on Tuesday, and Avamar will automatically find it each data and protect it via a common data protection schedule.
Hyper-V I/O Redirection Eliminated for Backup
This is one we ‘get for free’ from Microsoft in Hyper-V With Hyper-V 2008 R2, when backup was started for one server in a Hyper-V over CSV cluster, all of the other Hyper-V servers in the cluster went into I/O redirection mode. This meant for the life of the backup, all of these other Hyper-V servers had to send their I/O write requests to the Hyper-V server being backed up, slowing their write I/O performance. This is now eliminated in Hyper-V 2012
Clustered Shared
Volumes
Proxy
Backup
Hyper-V over CSV

40. Restaurations image Hyper-V
Souplesse de restauration des images Hyper-V
Restauration dans la VM d’origine à l’emplacement d’origine
Restauration dans la VM d’origine à un nouvel emplacement
Restauration dans un serveur Hyper-V différent
Restauration Initial Store
Restauration des fichier de configuration Hyper-V uniquement
NetWorker
Avamar
The Avamar Hyper-V VSS Plug-in provides the ability to recovery complete virtual machines to the same Hyper-V server, an alternate Hyper-V server, or just recover the virtual machine files to allow the user to manually provision a VM. In the case of a DR recovery of the complete Hyper-V Server, Avamar can also recover the Hyper-V Server configuration database files.
Virtual Machines
APP OS
APP OS
APP OS
Windows Server Hyper-V
Physical
Server

41. Restauration granulaires Hyper-V (GLR)
Proxy de restauration granulaire Hyper-V (GLR)
Monte rapidement les backups image Hyper-V depuis les savesets pour restaurer répertoires et fichiers au niveau guest
Avamar supports Granular Level Recoveries (GLR) from VM image level backups. With Hyper-V GLR, users can select a VM within the Avamar MCGUI and virtually mount this VM to a Windows Hyper-V GLR Proxy. Once virtually mounted, a process which takes seconds, users have the ability to browse directories and files within the VM for granular recoveries. All while the VM image is still resident within an Avamar DataStore or Data Domain System in a highly deduplicated state.
Note that Hyper-V GLR is only supported for Windows OS file system formats (FAT/FAT32/NTFS)

42. Backup des applications critiques
Les agents/modules assurent la consistance applicative
Application-specific agent within each VM ensures consistent state for hot backup
Deduplicates within and across virtual machines
Reduces resource contention and speeds backups
Provides file-level restore for Windows, Linux, and Solaris
No charge for agents
Many companies today continue to choose to backup VMware at the guest level. The main advantages of this approach, as we’ve said, is its simplicity and familiarity. This approach is great for file-level backup and recovery.
In this scenario, the Avamar agent is installed inside the virtual machine. When the backup runs, data is reduced within the virtual machine, and only new unique segments are moved and stored. The key benefit is that because it eliminates the backup bottleneck caused by contention for shared resources, Avamar really helps companies optimize consolidation ratios and get the most out of their VMware investment.
Another benefit is that because operating system- or application-specific agents run in the virtual machine, application consistency can be guaranteed.
And Avamar agents are free. You are only charged for the deduplicated capacity that you consume, so you can deploy agents as you like, which is great for virtual environments where virtual machines tend to come and go very quickly.
APP OS
VM1
APP OS
VM2
APP OS
VM3
APP OS
VM4
APP OS
VM5
APP OS
VM6
APP OS
VM7
APP OS
VM8
Infrastructure virtualisée

43. Consistance applicative –Hyper-V
Windows Server 2012/2008 R2 R2 Hyper-V OS
Crash Consistent
File-System Consistent
Application Consistent
Windows 2012
Oui
Windows 2008 R2
Windows 2008
Windows 2003
Windows 2000
Non
Windows 7, 8
Windows Vista
Windows XP
Other OS’s
This chart shows the levels of VM in-guest application consistency supported by the different flavors of Windows client and server operating systems. The bottom line is if the latest Windows OS is used, OS and application consistency in-guest is supported using Hyper-V VM image level backups.

44. NMM/Hyper-V : Matrice de support
Version NMM
Version Hyper-V supportée
Feature Hyper-V supportée
NMM v2.3
Stand-alone
Windows Server 2008 & R2
Backup
Restore
Directed Restore
NMM v2.4
+ Windows Server 2008 R2 CSV
+ GLR Restore
+ CSV
+ Federated Backup & Restore
NMM v2.4 SP1
+ Windows Server 2012 stand-alone & CSV
NMM v3.0
+ Optimized
Federated backup for CSV
+ SMB 3.0
+ Config Wizard

45. Look and Feel Hyper-V

46. Look and Feel Hyper-V (suite)

47. Look and Feel Hyper-V (suite)

48. Terminologie sauvegarde Hyper-V
PSOL (Preferred Server Order List)
Nouvelle fonctionnalité similaire au DAGs Exchange
Sélection du nœud du Cluster où sera fait le backup
VSS Copy/Full Backup
Copy Backup : pas de troncature des logs
Full Backup : troncature des logs
 Introduit avec Windows 2008

49. Backup Hyper-V Sélection de Saveset

50. Wizard de configuration du client

51. Options de restauration
Restauration depuis un nœud du cluster
« Directed » Recovery depuis une VM
Granular Recovery

52. Granular Level Recovery Hyper-V
Permet la restauration de fichiers et répertoires spécifiques ainsi que les applications
Similaire à une restauration d’un backup à froid SQL

53. Processus de restauration GLR
Sélection du client

54. Processus de restauration GLR Montage d’image VHD

55. Processus de restauration GLR Chargement de la partition

56. Processus de restauration GLR (Select, Start, Monitor)

57. Processus de restauration GLR
Vérification de la restauration de fichier

58. Roadmap Hyper-V 2011 2012 2013 2014 2015 2016 Released Planned Content
In Planning
NW 8.1/NMM 3.0 (Q3’13)
Performance: Proxy backup for Hyper-V over CSV Clusters, I/O redirection eliminated, Parallel Hyper-V Server backups, DD Boost over FC support, Client Direct to Disk
Broader Support: Hyper-V over SMB-3
Flexible Operation: In Guest backup type of Copy (No Log Truncation) or Full Backup
Simple to Use: Client Cfg Wizard
NW 8.0/NMM 2.4 (Q2’12)
Hyper-V Federated Backup
Client Direct to Data Domain via DD Boost
Hyper-V Granular Level Recovery (GLR)
NMM 2.2 (2008)
Hyper-V 2008
Hyper-V Image Backup/Recovery
NW Spaten/NMM 3.1 (Q2’14)
Performance: Multiple Backup Proxies, Partial Writer Support
Flexible Operation: Exclude VM from Backup
NW 8.0 SP1/ NMM 2.4 SP1 (Q4’12)
Hyper-V 2012
NMM 2.3 (Q2’11)
Hyper-V 2008 R2
2011
2012
2013
2014
2015
2016
NW 8.1 SP1/ NMM 3.0 SP1 (Q4’13)
Hyper-V 2012 R2
Future (Q1’15)
Hyper-V vNext Support
Hyper-V Virtual Edition (DDVE)
Management: SCVMM Integration - Recovery
Performance: Hyper-V Block Based Backup, Multiple Virtual Proxies
Future (Q2’15)
Management: SCVMM Integration – Backup Policies
Performance: Hyper-V Changed Block Restore, Hyper-V Instant Access
Usability: Hyper-V Self-Serve Web UI for end users, Recovery UI support, Application GLR from VM Backup