Skip to main content

Independent disks in a Virtual machine

When we add a new disk in  a VM hosted in Vmware ESXi, we can choose whether the disk should be Independent or not. If we choose the disk to be independent, it is not included in snapshots. If you browse the datastore after taking a snapshot of the machine, you will not see any delta disks related to the independent disks. There are two types of independent disks:

Persistant: The data written to the disk is retained after we powercycle the machine. It is like any normal disk that we add to a machine, only difference is that we cannot return to a point in time for data in that disk

Non-persistant: Data is deleted when we powercycle the VM. I have tried it on a Windows VM and the disk is listed as unallocated space each time I powercycle the VM, thereby deleting all data saved in it. I had to initialize the disk from the disk management console and format it  as a drive before using it again. Interestingly, if we restart the windows OS the disk and the data that it contains is retained.This could be because when we restart the OS, the VM power state is not changed. It will still be ON

Note: While taking snapshot of VMs with independent disks, make sure that the option 'Snapshot the Vitual machine's memory' is not selected. If this option is selected, snapshot operation will fail with an error "cannot take memory snapshot, since the virtual machine is configured with independent disks"

This is because snapshots are used to revert to a point-in-time state of the VM, and the persistant attribute of disks prevent it from doing so. The solution is to deselect the options to snapshot the VM memory,quiesce option or to ensure that the disks are not of type 'independent'

Reference:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007532

Comments

Popular posts from this blog

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Use Diskpart to make drives online

Issue: In disk management, disk is shown as missing or Offline in Windows Resolution: The disks can be made online by using diskpart utility - Open a command prompt->type diskpart -Inorder to list the disks in the system type: list disk -Note down the number of the disk that you want to make online -Select that disk to operate upon, For eg:, if the disk number is 1, type: Select disk 1 -Now that particular disk will be selected as teh active disk. If you type "list disk" command once more, you can see a * symbol on the left side of the selected disk -Inorder to make the selected disk online type : online disk - If the disk is made online, you will get a message that the operation is completed successfully

Kubernetes best practices in Azure: AKS name space isolation and AAD integration

Once you have decided to run your workloads in AKS service in Azure, there are certain best practices to be followed during design and implementation. In this blog we will discuss two of these recommended practices and the practical aspects of their implementation- Azure AD integration and name space isolation While AAD helps to authenticate users to your AKS cluster using the existing users and groups in your Azure AD, name space isolation provides logical isolation of resources used by them. It is useful in multi tenant scenarios where the same cluster is being used by different teams/departments to run their workloads. It is also useful in running say a dev, test and QA environment for organization in the same cluster. Combining AAD integration with name spaces allow users to login to their namespace using their Azure AD credentials AAD integration with AKS : The following Microsoft document will get you started  with AAD integration of AKS cluster.: https://docs.microsof