Veeam a company who is leading backup software vendor for hyper visors released their latest version (6.5) which supports Windows Server 2012. One of the key advantage of this product is you’re getting Backup and replication solution in one package. So if you’re planning to have a disaster recovery solution for your virtualize infrastructure this is an ideal solution.
Some of the new features in 6.5 for Windows Server 2012 are,
- Built-in compression and deduplication – This will allows you to backup large VHD files with reduce cost in storage infrastructure. Thanks to the compression technology and bandwidth throttling you have the capability to limit the resource usage.
- Advanced monitoring, reporting and capacity planning – With upgrade to their Veeam Backup Management Suite you’ll have deep visibility of your backup jobs. (In my view I would say this is something advance for large data centers heavily depend on Veeam)
- Support for Windows Server 2012 Hyper-V – Fully supporting for Windows 2012 plus can leverage on CSV v2 (Cluster Shared Volumes) and SMB 3.0
You can get a free edition of Veeam 6.5 as well.
It’s been a while I post anything to the blog due to the new life challenges I faced Anyway now I’m back and started the practice along with ITPro community session regarding the above subject. You can find the relevant slide deck in Slide share (http://www.slideshare.net/susanthasilva1/windows-server-2012-failover-clustering-improvements)
Looking back at the history and compare the clustering technology starting from Windows NT 4.0 Microsoft has done significant improvements on the technology. Instead of calling high availability now we try to achieve contiounsly availability (Thanks to storage, network improvements) for the mission critical apps through Windows clustering in Windows Server 2012. Apart from that now we have the capability to monitor the clustered services and applications inside the VM’s proactively. In case of a failure of these services we can restart or move to another node (pretty impressive feature where normally SCOM used to do this but now freely integrated with clustering)
Failover clusters also provide Cluster Shared Volume (CSV) (improved)functionality that provides a consistent, distributed namespace that clustered roles can use to access shared storage from all nodes. Apart from that the utilization of scale-out-fileserver and SMB 3.0 are some new add ins to improve the clustering experience and expandability apart from typical SAN environment.
Another new improvements is Cluster Aware Updating (CAU) which describes about the updating the cluster nodes with little intervention from Cluster administration. (Very much welcome feature if you’re handling large clusters)
To have this feature you need to add the particular role to the cluster nodes first. Once it carried out you’ll see the option in the Tools menu in Server Manager.
Once you open the cluster MMC you can select the “Cluster aware Update” option which will open you another menu,
This menu will help you to verify the nodes met the required settings to eligible under CAU.
Another welcome improvements in the Cluster Shared Volumes (CSV). In 2008 R2 we have the CSV option but limited to use in HYPER-V scenarios only. With Windows 2012 we can extend this to file servers as well. Combine with Scale-out-fileserver scenario we can have HYPER-V cluster in affordable cost as well. In a nutshell CSVs allow multiple nodes in the cluster to simultaneously access the same NTFS file system without imposing hardware, file type, or directory structure restrictions. As shown in the following figure, with CSVs, multiple clustered virtual machines can use the same LUN and still live migrate or quick migrate from node to node independently. Think CSV as a file system which is referred as CSVFS these days
Honestly there are too many information which cannot be written in one article like this. But you can refer to the TechNet article which describe all the new improvements in Windows 2012 Failover clustering (http://technet.microsoft.com/en-us/library/hh831414.aspx#CommunityContent)