Archive for April, 2010

MSCS Cluster VMs Migration to DR Site

April 23rd, 2010 | Category: vSphere

Another good story for sharing for those who going to clone MSCS nodes from one site to another. Below steps taken may not suitable for your cluster node migration process. However, the underlying concept as stated below most probably similar to most cluster storage migration practices.

Side Notes : If you are going to do MSCS cluster migration without involving new SAN, kindly refer to my earlier post on how to P2V MSCS Cluster Exchange here.

Scenario :
I have to clone 2x nodes MSCS cluster from HQ to DR site with different hardware setup (SAN). I may forgot something and caused my first migration failed yesterday. DataProtector & ASR backup as per Microsoft KB couldn’t help me much. Perhaps, I’m depending too much on DataProtector to handle critical backup operation for all cluster disks while ASR for the quorum disk and end-up, I restored the data without disk signature for all cluster LUNs and of course, my cluster services won’t start until I provide my cluster with valid disk signature. However with malicious test, effort & hard fought, I finally figured out a proper way on how I can accomplish my objective.

cluster resources error quorum error event viewer
Read more

1 comment

NFS Datastore Headache!

April 16th, 2010 | Category: VMware

I won’t say this is my great finding but, for the past few years I found out too many people had complaint the same issue I faced with ESX Datastore over NFS. While IP storage base (iscsi & nfs) become top choice for some of us who have little budget in the pocket, I’m still believing we should think twice before choosing NFS for the next ESX implementation.

Often we heard people had their NFS datastore become “inactive” and somehow won’t reconnect even though after NFS storage is back and available. The worse part is, sometime ESX reboot won’t change the situation and the only workaround I think most of us already knew is by removing NFS storage and add it back to the our ESX host. If it’s not your lucky day, you will not even able to remove your existing NFS datastore without remove first all your VMs from ESX inventory. Imagine if you have so many VMs need to be removed and add it back to your host manually after you successfully mounted your NFS datastore?. Read more

1 comment

Mail Server Backup

April 10th, 2010 | Category: Nox

Hosting a mail server at home can be done quite easily but is it good idea to keep all your important mails at your home? 3 years I’ve being hosting it from home and frankly speaking, 2 times I lost my mailbox because of my OS disk corrupted though I had everything run inside virtual machine and no proper backup was configured. I still remember for the past 3 years, my mail server has been configured as below :

  • Internet -> Mail server

Yeh, noob who also want to have own mail server (sendmail + squirrelmail) at home and do not know much about spams, filtering & etc. End up, my mail server became online mini market for viagra, sex toy & etc.

  • Internet -> Mail filter -> Mail Server (Less spam & but no backup)

Okay with new idea to protect what’s mine. Endian Firewall give no more mini market for spam but after one year, my Scalix mail server virtual disk corrupted, hell ya almost get heart attacked! Read more

No comments

Add / remove permission via vimsh

April 06th, 2010 | Category: Nox, vSphere

If you mistakenly lost administrator permission/role for root user, here how to correct it :

1) Create new user

$useradd -g admin -G users -s /bin/bash -d /home/usera -m usera

2) Assign Administrator Role to new user :
$vimsh -n -e “vimsvc/auth/entity_permission_add vim.Folder:ha-folder-root ‘usera’ false Admin true”

to remove it

$vimsh -n -e “vimsvc/auth/entity_permission_remove vim.Folder:ha-folder-root ‘usera’ false Admin true”

3) Verify Role for new user :

$vimsh -n -e “vimsvc/auth/role_permissions Admin” 

(vim.AuthorizationManager.Permission) [
(vim.AuthorizationManager.Permission) {
dynamicType = ,
entity = ‘vim.Folder:ha-folder-root’,
principal = “usera”,
group = false,
roleId = -1,
propagate = true,
}
4) Login to vi-client and modify your root permission

vi-client-> administration -> Roles Tab

p/s : Tested on ESX 3.5 U3
ariyossss

athlon_crazy 07/04/2010 12:16AM

update 1 : If you are totally no permission, please edit /etc/vmware/hostd/authorization.xml & make sure your roleID for root is “-1″

No comments