Pages

Search This Blog

Monday, December 23, 2013

Convert System Into VHDX Format–Disk2VHD v2.0

 

Disk2VHD is a great tool to convert physical to virtual machine in vhd format. Recently they have released v2.0 to support vhdx as well.

Just download the utilities and run on source machine. When executed, it will create one virtual disk (vhd or vhdx format) on each disk.

VHD Format

With “Uncheck use vhdx” option. It will convert the disk to vhd format

image

VHDX Format

With “Use VHDX option” checked. It will convert into vhdx format

image

To download, please visit Windows SysInternal:- http://technet.microsoft.com/en-us/sysinternals/ee656415

Wednesday, December 18, 2013

Free ebook:- System Center Family

 

While browsing and looking for book which I’m going to read during up coming holiday break, I have found a link which consist of a lot of System Center 2012 R2 ebook. These ebook is provided free by Microsoft.

image

If you’re interested, please feel free to download PDF, ePub or Mobi format from Microsoft Press link as listed below

image

Tuesday, December 3, 2013

Starwind HA Products - 2013 Year End Sale

 

image

Black friday and Cyber Monday just over, but Starwind just offered a year end sale. Some words from them:-

Only one month left until the New Year, and we are having a massive Farewell to 2013 Countdown here at StarWind!
Buy any StarWind iSCSI SAN & NAS edition or StarWind Native SAN for Hyper-V edition by the end of the year and get BIG discounts off list price!*

With the countdown discounts melting down with every passing week, you can SAVE BIG if you ACT NOW!

30% Discount Countdown to 2014!

Contact us and take advantage of our special offer now!

Latest news about Starwind:-

StarWind iSCSI SAN & NAS, has been named the first runner-up in two categories: Virtualization Management Product of the Year and Storage Virtualization Product of the Year at the SVC Awards 2013. Our Press release is here: http://www.starwindsoftware.com/news/112

Review PHD Virtual : PHD Virtual Backup for Hyper-V

 

With Windows Server 2012 R2 Hyper-V recently launched to public, we are constantly looking at backup solutions in the market. This review covers a great new product due for release in mid December, PHD Virtual Backup for Hyper-V (http://www.phdvirtual.com/). This product is powerful, easy to use and best of all, it is FREE.

You can get the this free product on www.phdvirtual.com

clip_image001

PHD Virtual Backup is used worldwide for the backup and recovery of virtual environments, leading the way in fault tolerant, high performance, scalable and efficient data protection of virtual machines. The product has traditionally supported VMWare and Citrix XenServer hypervisors. This new release extends this support to Hyper-V (Windows Server 2012).

Multi –Hypervisor support on a single solution

Testing of the product was done on its BETA software. General availability is scheduled on December 18, 2013.

Here is our review from beginning of the testing in our test lab environment.

Installation Process

No installation on the product. Use the wizard below. Just define few VM configuration and click to deploy the VBA (Virtual Backup Appliance). It was super easy! You can use execute it once you have installed PHD Virtual Hyper-V Services on each Hyper-V Machine and deploy multiple roles.

clip_image002

Management - Web Based Interface

Once a VBA has deployed, you can manage it by using browser. You are not required to install any console.

The product is currently limited to support Mozilla Firefox and Google Chrome browsers. Internet Explorer is not supported during our time of testing. Hopefully, PHD Virtual will add support on Internet Explorer in a future release.

On 1st login, the system will display a simple help on the page to guide a customer through the navigation. This helps you to understand and use the system immediately without need to spend more time on documentation. Very cool!

clip_image004

On front page, you will be welcome by a dashboard page. The dashboard that provides an “at-a-glance” overview of the current state of your environment and you can configure and manage the data protection for all of your Hyper-V hosts in a single pane of glass.

Agentless data protection

Before we start to protect, we need to define a VBA on each Hyper-V Host into this the portal. For protection, you do not need to install any agent on the Hyper-V Host or Virtual Machine. PHD Virtual technologies is using image based backup.

You need to deploy correct Virtual Backup Appliance role. Let have a look on the each role.

The 1st VBA includes a Presentation (P) role which provides a web based interface. You can configure and manage your installation. Only 1 Presentation appliance is necessary per installation.

The next role is Management (M) role. Each Hyper-V host or they called it Environment, is required on each Hyper-V Host. It will perform inventory and other hypervisor specific tasks and manages the work of the engine appliance.

The last role is Engine (E) which provides the actual backup processing and sends data to their configured backup data stores.

You can combine multiple roles into a single virtual appliance. To better understand it, I’ve drawn a picture on the appliance that you should deploy.

clip_image006

Once the correct appliance roles has been deployed, you can manage it using a virtual appliance which consists of Presentation (P)-1st appliance.

clip_image008

The system is using Virtual Image Backup concept to perform backup of the complete image of the VM, its configuration and virtual disk data. The major processing will be on the virtual appliance rather than installing agents in each guest. This makes deployment and maintenance simple, as well as follows best practices for virtualization data protection.

Backup Virtual disks run on SMB shares

clip_image010

Once an appliance has deployed (M & E role), next step is create an empty virtual fixed disk of a Backup Data Store to store the backup data. The backup virtual disk can run on a dedicated SMB share rather than on dedicated Hyper-V Host. We do recommend that you leverage on these capabilities to store the backup virtual disk on a dedicated SMB share to protect the backup data. Thanks to Hyper-V and File Server Product Group which makes the “Hyper-V over SMB” concept a reality. As a result, PHD Virtual is able to add SMB share support in their PHD Virtual Backup for Hyper-V product.

image

Support more than 2 TB per virtual disk

Starting with Windows Server 2012 Hyper-V, the hypervisor introduces a new virtual disk format called vhdx. Now we can provision a larger backup data store and no longer limit to 2TB per disk.

During our testing on Windows Server 2012 R2 Hyper-V, we found out that we can add a new virtual disk into the running Virtual Backup Appliance pre-installed with Ubuntu 12.04.

Then go to Portal and add a new Disk Storage to Virtual Backup Appliance.

Compression

You can define any storage option such as compression or storage threshold as well before add a disk storage.

image

Backup - Deduplication

Let move on to check out the backup options. When you start to create a backup job, the system will provide few backup mode options:

clip_image015

The recommended mode is “Virtual Full” which provides users with built in global deduplication across all data on the entire backup target. With this feature, we do not need to write duplicate data to the backup data store using incremental backup.

What do we gain? Faster of backup, reduced backup time & storage space! With compression enabled on the virtual storage disk, we achieve thin backup over time as well.

Well, if you don’t like Virtual Backup mode, you can opt for Full/Incremental backup which allows you to transfer the full or incremental backup data to any deduplication appliance available in the market or a tape library.

clip_image016

Sometimes we do need to protect a VM and do not want the backup to be overwritten by retention. With PHD Virtual we can pin that particular VM to protect it. Once pin, the backup data will retain and will not be removed by retention policy.

clip_image017

clip_image018

Granular Backup Per-VM Options

On each VM, you can define its own backup storage store as well as retention range. This is much better when compared to System Center Data Protection Manager, which puts everything into storage pool and one the same retention range in a backup job.

clip_image020

Occasionally, I get a requirement from a customer who would like to put a specific VM into a dedicated backup storage disk and configure a different retention range. PHD Virtual helped us easily achieve this.

Restoration- File Level Recovery

Now that we have configured the backup job and review the options, let move on to the most important part: Restoration. There is no point of backing up the VM without the abilities of restoration.

Our first test is file level recovery. We would like to restore a file inside a VM without restoring the entire virtual disk. We have configured a native SQL Backup to backup the SQL Database and configured PHD Virtual to backup the VM.

clip_image022

We then executed FLR option and waited for the system to map the backup VM data and provide the CIFS.

clip_image024

Then use the given CIFS and use Windows Explorer to access the backup data and restore an individual file. You can even connect to the SQL database using SQL Management Studio and recover specific SQL objects, if needed.

The Next test is Restoration- for the Entire VM. PHD Virtual has make the recovery of existing VM simpler. To overwrite existing VM, just click Rollback.

clip_image026

We can rollback any VM to a selected VM based on our backup date and time. Do be careful when using this option, as it will replace the entire production VM. PHD did add some protection by including a snapshot on the VM prior to recovering the data. This is a great feature and useful especially when you’ve got a corrupted VM and would like to recover from backup immediately.

To recover to alternate location without interrupting the existing production VM, you can define not to connect to Network, change another VM name, path or disk location or map it to the alternate virtual switch.

clip_image027

clip_image029

Useful Jobs

The next review is to monitor the progress of backup and restoration. PHD Virtual included this in the Jobs view.

clip_image031

I Found “Pause Job” to temporary halt an active job. This comes in handy especially when you urgently need to halt the backup job and allow the recovery job to go first.

clip_image032

While waiting, we can drill down to see the progress of action rather than seeing the progress bar and guess what is the system doing in the background. The Figure above depicted the action of attaching disk, attached status and rolling back status.

Advanced Reporting

Next, the dashboard, gives us a quick view of protection risk and trends as well as alerts with drill in options for each object. You can view the daily change rate for your storage as well.

clip_image034

Besides than dashboard, you can go to Report View to generate more reports such as protection summary, protected VMs, unprotected VMs, backup history and storage details. Each report provides a quick summary chart and details data as well. You can set to export the report to either PDF or CSV format. On each backup job, you can send status report by email as well.

clip_image036

Our conclusions for PHD Virtual Backup for Hyper-V.:

Pros:-

  • Excellent product for a virtual backup appliance running on top of Microsoft Windows Server 2012 R2 Hyper-V Host. Bonus: I never expected such a good performing Linux backup appliance on Hyper-V!
  • Ease of management using web interface
  • Agentless
  • Virtual Backup disk on SMB Shares
  • Ability to add more than 2TB virtual disk for virtual backup storage
  • Compression
  • De-Duplication
  • Ability to set backup storage & retention per VM
  • Lock VM and prevent from remove by retention period.
  • Able to Perform Item Level Recovery
  • Pause Jobs
  • Included with Dashboard and Reporting
  • It’s a FREE* Hyper-V backup solution that delivers backup to the same industry level as Veeam and Symantec! (There is a purchase option for support)·

Cons:-

  • No Internet Explorer support during our testing

Do check out their website:- http://www.phdvirtual.com/ to evaluate their product in more details.

Monday, December 2, 2013

Designing Converged Network for Windows Server 2012 R2 Hyper-V

 

I just got a several machine to setup Windows Server 2012 R2 Hyper-V. Nothing special except the specification of the machine is quite huge.

1

The machine has a specification of

  • Intel Xeon 2.7 Ghz – 32 logical processor (a bit closer to have 64 vcpu in a virtual machine. Too bad, I only can assign up to 32 vcpu)
  • 384 GB of Memory
  • 8 NIC X 20 GbE. Total up 160 GbE of network throughput.

2

So the design of the NIC should not follow like non-converged network which we use to do. In normal rack mounted server, we often have multiple of 1GbE of NIC card. When you do Hyper-V Cluster, you will end up minimum of 8 NIC depend on your environment.

ConvergedNetwork

Figure 1: Non-converged network

Do we do converged network on 1 GbE NIC? Well, we seldom do that as 1Gb is not a lot of throughput. We probably will laugh when someone design such as way when using 1 GbE.

“ So when do we start to look at Converged Network?”

Converged network is a new feature in Windows Server 2012 which allow the creation of virtual network adapter in the parent partition. You should look on converged network when you have 10 GbE NIC. It make more sense to split the traffic rather than wasted on 10GbE. Just imagine that you configure

  • 10 GbE for Private
  • 10 GbE for Live Migration

Then it is going to be a waste. So let split it up the traffic by using Converged Network which available on Windows Server 2012 or Windows Server 2012 R2 using either Windows Powershell or Virtual Machine Manager 2012 or 2012 R2. You cannot do converged network by using Hyper-V Manager snap-in.

Option 1 Design

Option1

Teaming 2 X 20 GbE

  • Management
  • Live Migration
  • Cluster
  • Backup

MPIO 2 X 20GbE

  • Storage

Teaming 4 X 20 GbE

  • Hyper-V Virtual Switch for Virtual machine workload

Option 1 design in such a way to isolate the management traffic, storage traffic and VM Guest traffic.

Option 2 Design

Option 2

Teaming 3 X 20 GbE

  • Management
  • Live Migration
  • Cluster
  • Backup
  • Storage

Teaming 5 X 20 GbE

  • Hyper-V Virtual Switch for Virtual machine workload

Option 2 design in such a way to combine management and storage traffic and isolate VM Guest traffic.

Option 3 design

option 3

Teaming 8 X 20 GbE

  • Management
  • Live Migration
  • Cluster
  • Backup
  • Storage
  • Hyper-V Virtual Switch for Virtual machine workload

Option 3 design in such a way to combine multiple traffic into a team and split it to different virtual network.

The question right now, which design is correct and suitable?

There are so many design other than above three designs.

Myself, still prefer Option 1 design. Thanks to Aidan Finn and David Lachari ( my peer MVP Virtual machine) on their opinion about converged network.

There's no one right design.  That's the cool thing with this Converged Network.