my personal blog about systemcenter

Archive for June, 2012

 

 

http://technet.microsoft.com/en-us/library/hh831414.aspx#BKMK_backup

Ease of file backup with CSVs

CSV features in Windows Server 2012 that help achieve a seamless backup experience for both backup applications and backup requestors include the following:

  • Support for parallel backups across CSV volumes and across cluster nodes

 

This post will cover the Parallel backup support , this is just one of the new features that just work Smile but is very very helpful

 

In Windows 2008 R2 it was not possible to run multiple backup jobs against a CSV volume if you didn’t have a supported hardware based VSS provider

 

Windows Server 2012 Hyper-V changes this and it is now possible to run jobs against the same CSV volume without a hardware based VSS provider

 

image

Create the protection group

image

 

By default Data Protection Manager will use the 3 VM’s limit

HKLMSoftwareMicrosoftMicrosoft Data Protection Manager2.0ConfigurationMaxAllowedParallelBackups

During testing I tried to change the MaxAllowedParallelBackup to higher than 3 without success need to explore that a bit more but 3 beats 1 every day of the week

 

Well that’s it actually instead of having to follow http://technet.microsoft.com/en-us/library/ff634192.aspx to get serializing to work for admins stuck without a supported hardware VSS provider it just works

Thank you Windows Server 2012

One of the new features in Windows Server 2012 Hyper-V Clustering is the support for Incremental backup of CSV volumes without going into redirected mode or having to read all data before changes to the Data Protection Manager server.

The changed block filter for Hyper-V was added in Data Protection Manager 2012 for stand alone hosts and help speed up backup of Hyper-V guests, with Windows Server 2012 we now have the same feature supporting clusters

 

http://technet.microsoft.com/en-us/library/hh831414.aspx#BKMK_backup

Ease of file backup with CSVs

CSV features in Windows Server 2012 that help achieve a seamless backup experience for both backup applications and backup requestors include the following:

  • Support for incremental backups

This post will cover the Incremental Backup support , this is just one of the new features that just work Smile but is very very helpful

 

image

First off to compare with a Windows 2008 R2 Cluster

 

image

CSV Volume going into redirected mode for the duration of the backup

image

There is a lot of disk activity as we are doing a rescan of the virtual machine to read changes

 

image

Windows Server 2012 Version

 

image

There is little to no disc activity

image

For this small test it was 2 Hyper-V guest doing close to nothing and about same data size

28-40 seconds for the Hyper-V 2012 backup and almost no additional load on the cluster

and about 5 times longer for the Windows 2008R2 Cluster with redirected mode and slow disk IO to follow.

Thank you Windows Server 2012 !

One of the new features in Windows Server 2012 Clustering is the Direct I/O mode for snapshots and backup , this will ensure that the CSV volume wont go into redirected mode , so even without the use of hardware VSS , data protection manager can backup the Hyper-V guests directly off the cluster without the performance impact of the CSV going into redirected mode.

 

http://technet.microsoft.com/en-us/library/hh831414.aspx#BKMK_backup

Ease of file backup with CSVs

CSV features in Windows Server 2012 that help achieve a seamless backup experience for both backup applications and backup requestors include the following:

  • Direct I/O mode for snapshot and backup operations

This post will cover the Direct I/O mode, this is just one of the new features that just work but is very very very helpful

image

Select the Hyper-V machine in the cluster that you want to protect

image

Create the protection group

 

image

And we can see the backup running

image

and our CSV volume is Online and not in redirected mode

Thank you Windows Server 2012 !

 

One of the great news features included in the box with Hyper-V and Windows Server 2012 is the ability to replica machines between systems that are only connected though IP , so no requirement for special shared storage

This free feature will be a game changer for many customers where SAN with replication is out of the question or where management will have a disaster recovery site without breaking their budgets

Creating full disaster recovery sites for FREE will be the feature everyone will embrace and ask where its been all their live.

Matthijs from Microsoft made a great post with detailed information about the powershell commands out so far for Hyper-V replica http://blogs.technet.com/b/matthts/archive/2012/04/02/managing-hyper-v-replica-from-powershell.aspx

 

This is done without Virtual Machine Manager integration so even shops wihout systemcenter can do this

 

 

 

image

If you are using a cluster as either the source or target you need to configure a new role from Failover Cluster Manager

 

 

 

image

Create Hyper-V Replica Broker , one is needed pr cluster

image

Give it a fitting name and ip address

image

Configure Replication for the Broker

image

image

For testing we allow connection though http and from all servers

image

Select the virtual machine you want to replicate , right client Replication Enable Replication

image

Select target Hyper-V host or Replica Broker on a different cluster

image

On the target we need to enable replication under Hyper-V manager and set authentication and port , the authentication and port type need to match the source

image

Select a default path for replica machines

 

image

image

Select what VHD files to replicate

image

If storage permits we can keep additional recovery points

 

 

image

image

Verify that initial replicate is complete

image

and to test a planned failover shutdown the machine and select planned failover

image

image

And the planned failover is complete , and the VMM is now running on the different host in the datacenter.

image

If the source and target is on different subnets we can inject a new ip address into the guest as it fails from one host to another keeping services up and running without any steps needed from IT straff