Monday, January 15, 2018

Azure–Upsize VM while Maintaining VHD

Upsizing a VM which is in the same family will be easy to perform.  However, what happens if I want to upsize the VM to another category/family ?

I’m going to share the steps.

Scenario :

A VM (DC) that is in the size of Standard A1.  I’ll need to upgrade to size to Standard A1 V2.  Need to maintain the information.

In the steps I’ve created a text document and place it in the desktop of the old VM before I upsize the VM, just to show that the data is still intact.

image

Before changing the VM size.

image

The above shows the VM size

image

The above shows the VM (BK-TRN-DC01) in the resource group name rg_bkhoo_training

image

Take note of the VH VHD.  This info is needed later.

Also take note of the Network Card attach to the VM.


The Process.

image

Firstly, stop the VM just like the shown above.  The VM is stopping. 

image

Once the VM has stopped, then delete the particular VM.

image

As you can see, even though the VM has been deleted, the VHD is still intact in the storage.

image

Create a new VM with the same OS in the Resource Group that you have deleted the VM

image

Now I created a new VM.  In my example I name it as BK-TRN-DC01-A.

image

Now the VM, I select the size of A1_V2 Standard.

image

In the Settings panel, key in to the same settings as the same previous VM that was deleted earlier, then click OK

Revise the Summary, then click OK.

Once the VM is created, then click on the Virtual machine to review the size.  It’s shown as follow

image

Ensure the VM is shutdown down.

Azure Storage Explorer

Next is to launch the Azure Storage Explorer and connect to the Azure Account .

image

Take note that we’re going to remove the new VHD that has been created, and attach the previous VM VHD into the new VM.

image

Firstly, select the the new VM VHD, right-click and select Break Lease.

image

Click Yes to break the lease

image

Before the deletion, copy down the name of the new VM VHD.

Select the new VM VHD, then right-click, choose Delete the new VM VHD in the Azure Storage Explorer.

image

Select Yes to confirm the deletion

image

Right-click on the previous VM VHD and select Rename. Rename the VHD to the name that was noted earlier.

image

The end result in the Azure Storage Explorer is displayed as above for my example.

Attaching back previous Network.

The next things before firing up the VM, is to attach back the previous VM Network.  It contains the previous IP address, with it’s profile.  This is very important.

Take note the VM must be shutdown in order to perform the action

Select Virtual machine networking.

image

Select Attach Network Interface.

image

Select the previous VM network interface and click OK.

image

Next is to detach the the network interface when the new VM was created.

Select the new VM interface in the tab. Then at the top click Detach network interface.

image

Click OK to confirm.

image

Take note of the previous Private VM IP has been attached to the new VM.

image

Now can Start the VM.

RDP into the VM

image

Take note that the new VM hostname is the old VM hostname.  This is because is using the previous VHD. 

Also take note of the IP address.  It’s the previous VM IP address. 

Hope the steps has helped you on how to migrate your VMs from one size to another (from different category) without much of hassles.  The method also can be use to migrate the VMs from classic to the new Azure Portal.


keywords : Azure migration, azure up size, azure family, azure migration of different family, virtualization, azure sizing.

Wednesday, January 10, 2018

Azure Storage Explorer–Release 0.9.3

The Microsoft Azure Storage Explorer was release in December 2017.

Can download from the link  here

image

keywords : Azure Storage Explorer, storage, azure, cloud storage

Monday, March 13, 2017

SCDPM 2016 Storage Setup – Modern Backup Storage

In the System Center Data Protection Manager 2016 (SCDPM 2016), there’s improvement of which type of data to be stored into specific LUN.  I have in the sample are 2 LUNs from NetApps presented the volume to SCDPM 2016 for the Storage Pool.

By configuring this, I’ll have it as Application-aware backup for my SCDPM 2016

In the predecessors (SCDPM 2010, SCDPM 2012), the whole storage pool is mixed together with SQL,VM Backups etc.

However in the SCDPM I can have something like this :

 image

In order to have the above, I’ll share the steps of how it was done.

Once the LUN is presented to the SCDPM 2016, open up the Disk Manager.  I’m going to use Disk 4 and add into the Storage Pool.  This LUN I’m going to use it for SQL type of backups.  This Disk 4 LUN storage was presented from NetApps.  In the later steps I use a friendly name to distinguish in the Storage Pool.

image

I’m going create it as a New Simple Volume (Right-click – Select New Simple Volume)

image

In the Welcome to the New Simple Volume Wizard, click Next.

image

In the Specify Volume Size, click Next (selection to use entire volume for this backup)

In the Assign Drive Letter or Path display, click the Assign the following drive letter, select letter, then click Next

SNAGHTML63274d

In the Format Partition display, click Do not format this volume, then click Next.

image

In the Completing the New Simple Volume Wizard, click Finish

(Below is just a sample)

image

It will something like a sample below in the Disk Management, once the above activity has completed carry out.

image

Switch back to SCDPM 2016 console.

Click ManagementDisk Storage – then click Add at the ribbon menu.

image

In the Add Disk Storage display, click the Add button. 

image

A warning is displayed, click Yes  to continue

image

Once selected and added, key in a friendly name (as mentioned earlier in this blog) to distinguish.  Click OK.

image

Double click on the DPM Management Shell to launch the specific PowerShell commands for SCDPM (Note that this is different set of commands from the normal Windows PowerShell)

Once the DPM Management PowerShell is launch type the following :

$vol = Get-DPMDiskStorage –Volumes

$vol

image

In the next command key, this is going to change the particular pool for Application-aware backup as shown below :

Update-DPMDiskStorage –Volume $vol[3] –FriendlyName “SQL-NetApps” – DataSourceType SQL

Note : Change the ones in Pink in the above syntax  The rest of it stays.

image

DatasourceType supported are :

  • Client
  • SQL
  • SharePoint
  • Exchange
  • SystemProtection
  • HyperV
  • VMWare
  • Other
  • All

Remember to use a unique Volume number.  Usually my Practice is using Disk # – 1  (Disk Number minus 1, refer to the Disk Management)

image

Once the Update-DPMDiskDiskStorage shell command is done, navigate back to your DPM ConsoleManagementDisk Storage to see the Preferred Datasource Types has been changed

image

When the Protection Group is created, you can then select the appropriate storage for the kind of backup.  With this Workload Aware Storage, it will help to reduce storage costs.  

Hope this helps.

keywords : Application-aware backup, SCDPM 2016, System Center Data Protection Manager 2016, modern backup storage

Wednesday, March 8, 2017

Network Connection Folder Empty

Recently I had an issue with Server not displaying the Network Adapters.

 image

I checked and ping and it was okay.  But when I did a Failover Cluster Validation, it displayed error cause it couldn’t find the network.

The following are the steps that was carried out to have it resolve

  • Open regedit .
  • Drill to the following in the registry

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network

  • On the right-panel look for Config.  Delete the key.

    image
  • No worries.  When delete this key, it’s just removing the configuration cache.
  • Restart the server or just reopen the Control PanelNetwork, it will display once again.

    SNAGHTMLc1d9bb

keywords : Network Connection missing, network not display, network connections folder is empty, not showing network adapter list

Monday, February 27, 2017

How to remove “Unsupported Cluster Configuration” in SCVMM 2012

Recently I had a incident in one of the end user’s environment. 

The scenario is as follow :
The storage LUNs where the Virtual Machines resides had several Hard Disks failed.  There were not enough hotspare disks assigned to it.  The only way is to replace the faulty Hard Disks in the storage and then reconfigure it again.

Once it was done, the LUN was presented back to the Hosts and Failover Cluster recognize the LUN and then VMs were configured.

However, in the System Center Virtual Machine Manager (SCVMM 2012) has an issue.  It contained two identical records.  One is displayed as Running and another as Unsupported Cluster Configuration

image

Steps Taken

  • Ensure the VM is running in the Cluster
  • Launch the Virtual Machine Manager Command Shell in the Server that is running the SCVMM 2012
    (right-click run as administrator)
    image
  • Key in the command as follow in the VMM Command Shell that was launched :

    Get-SCVirtualMachine | where { $_.Name -EQ "Duplicate-ComputerName"} | fl name, status


    Note : Replace the Pink with your computer name that you want to remove from the SCVMM.   Remember the rest of the commands stay, including the quotes.
  •  It will display something like the screen below :

    SNAGHTMLb479c8
  • Next is to execute the command to  remove from the SCVMM database
    Get-SCVirtualMachine | where { $_.Name -EQ "Duplicate-ComputerName"} | Remove-SCVirtualMachine –Force

    Note : Replace the Pink with the computer name that you want to remove from the SCVMM.  The rest of the commands stays inclusive the quotes.  This is going to remove from the SCVMM DB but not removing the VM.  Remember the VM needs to be up and running.
  • In the SCVMM, the record will be removed and you need to do a refresh to once again get the information from the Cluster. 
    Right click on the Cluster in the VMM and click refresh

    image

After the SCVMM has completed the job (getting the information from the Cluster), the Unsupported Cluster Configuration is no longer in the record.  The one that is healthy is displayed in the cluster information.

A thank you to Aidan Finn and Law.

keywords : error 2604, unsupported cluster configuration, system center virtual machine manager, scvmm hyper-v, duplicate computer name in scvmm 2012, how to remove computer from scvmm