[VMware] Recovering from the configured recovery point objective (RPO) is lower than what the host can support error

客戶反應一台VDP 6.x在測試還原一台機器後,開機還原測試機無法開機,

error message :

Recovering from the configured recovery point objective (RPO) is lower than what the host can support error

這大多是VDP backup source VM曾是或正是VMware Replication 抄寫過!

Solution#1 (效率快,原廠提供方式)

step01. backup VDP restore VM 該機器 .vmx

step02. vi /vmfs/volumes/{storage}/VM/VM.vmx

step03. 將以下的註解不用及存檔
————–未修改前——————

hbr_filter.configGen = “"
hbr_filter.rpo = “"
hbr_filter.destination = “"
hbr_filter.port = “0″
hbr_filter.gid = “"
hbr_filter.protocol = “"
hbr_filter.quiesce = “true"
hbr_filter.opp = “true"
hbr_filter.pause = “true"
scsi0:0.hbr_filter.rdid = “"
scsi0:0.hbr_filter.persistent = “"
——————————————–

>>
————–已修改後——————

#hbr_filter.configGen = “"
#hbr_filter.rpo = “"
#hbr_filter.destination = “"
#hbr_filter.port = “0″
#hbr_filter.gid = “"
#hbr_filter.protocol = “"
#hbr_filter.quiesce = “true"
#hbr_filter.opp = “true"
#hbr_filter.pause = “true"
#scsi0:0.hbr_filter.rdid = “"
#scsi0:0.hbr_filter.persistent = “"
——————————————–

step04.
vim-cmd vmsvc/getallvms | grep -i to find the vmid  // 最前面的數字即是 vmid

step05.
vim-cmd vmsvc/reload  {vmid}  // 重新載入該VM config

step06.
try Power-On VDP restore VM

Done & Enjoy ^O^

solution#2 (厚功)

step01.砍掉無法開機VDP restore VM

step02.重新source VM reconfig vSphere Replication

step03.

Recovery settings 裡的Point in time instances
(V) Enable
Keep {x} instances per day for the last {y} days (24total)

Done.

 


Reference:

1.Recovering from the configured recovery point objective (RPO) is lower than what the host can support error. (2123433)

[VMware] ESXi 5.5 upgrade to 6.0U2 DependencyError issue

今日作ESXi 5.5U2 upgrade to ESXi 6.0U2 使用ESXi CLI update happen some issue , messages as below

[DependencyError]
 VIB VMware_bootbank_esx-base_6.0.0-2.34.3620759 requires vsan >= 6.0.0-2.34, but the requirement cannot be satisfied within the ImageProfile.
 VIB VMware_bootbank_esx-base_6.0.0-2.34.3620759 requires vsan << 6.0.0-2.35, but the requirement cannot be satisfied within the ImageProfile.
 Please refer to the log file for more details.

solution for ESXi CLI

step1.
# esxcli software sources profile list -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip
display profile information 記得下它

Name                                                                                        Vendor    Acceptance Level
————————————————————————    ———-   ————————
Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1     Cisco      PartnerSupported

step2.

# esxcli software profile update -p Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1 -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip

step3.
# esxcli software vib install -n esx-base -n vsan -n vsanhealth -d /path/Vmware-ESXi-6.0.0-3620759-Custom-Cisco-6.0.2.1-Bundle.zip

step4.
Reboot apply new esxi version

後記:
若是用vSphere Update Manager (VUM) 或是 放置ISO方式(pre-boot)是不會有以上產牛相依性這類狀況唷!!


Reference :

VMware KB 2144595 ( Dealing with vSAN VIB issues in ESXi 6.0 Update 2 and later releases )

Windows Server 2008 設定 共用磁碟 安全性(Security) 或 擁有者(Owner) 會發生"無法列舉容器中的物件。拒絕存取。"

客戶反應他們NetApp 移轉到另一台同型號,請我們initialize 另一台FAS-series也設定好cifs shares ,
測試目錄設定安全性(Security) 或變更擁有者(Take owner) 會發生錯誤訊息 " 無法列舉容器中的物件。拒絕存取 "

(前提:該使用者非Domain Admins Groups member)
他們發現若是replication過去的volume分享出來無論是作變更安全性或是擁有者都很正常 !
若在另一台新機作變更安全性或是擁有者卻有錯誤訊息 " 無法列舉容器中的物件。拒絕存取 “但還是有套用成功只是都會有錯誤訊息。

最後查證後只要是NetApp 新建volume後cifs shares出來空的目錄就會如此,但若新建後放些檔案及目錄則為正常,原來是微軟 KB972299 Bug搞的鬼。

Microsoft原廠KB 972299說明可以忽略此一錯誤無patch ….Orz


Reference:

Microsoft KB972299

Windows 2012 R2 Core版本 切換回 Full GUI

在一次偶然安裝了Windows Server 2012 R2 IIS想重新安裝再IIS remove重開機發現GUI版變為了 Core版(純指令模式),但有方法可以再度變回GUI版本.

step1. 若已有PowerShell請忽略此步驟
press “Ctrl + Alt + Delete" 呼叫 Task Manager(工作管理員) > 執行 > 輸入 ‘cmd.exe’

step2.
c:> dism.exe /online /enable-feature /featurename:MicrosoftWindowsPowerShellRoot
c:> dism.exe /online /enable-feature /featurename:MicrosoftWindowsPowerShell /all

step3.
c:> powershell.exe // path c:WindowsSystem32WindowsPowerShell

step4.
PS c:> Install-WindowsFeature Server-Gui-Shell,Server-Gui-Mgmt-Infra -restart

PS c:> Add-WindowsFeature Server-Gui-Shell,Server-Gui-Mgmt-Infra -restart

done.

**若之前沒安裝過可能需要光碟方式**
c:> mkdir c:mnt

c:> dism /get-imageinfo /ImageFile:d:sourcesinstall.wim // check wimfile determine the correct index for the OS (mine was 4 )

c:> dism /mount-wim /wimfile:d:sourcesinstall.wim /index:4 /mountdir:c:mount /readonly

c:> powershell.exe

ps c:> install-windowsfeature server-gui-mgmt-infra,server-gui-shell –restart –source c:mountwindowswinsxs

c:> dism /unmount-wim /mountdir:c:mnt // umount source

c:> rmdir c:mnt

**Remove/Uninstall Full GUI**
Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra -restart

Remove-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra -restart

**GUI方式變為Core版操作**

Roles and Features > Features > User Interfaces and Infrastructure

**Core呼叫操作**
SConfig.exe

[VMware] VMware Workstation error "cannot change network to bridged : there are no un-bridged host networ adapters."

今日workstation因主機更新無預警自動重開機套用新的updates

再開啟lab virtual machine發現網路不通才注意到右下角虛擬網卡處於灰階 !

設定"Virtual Netowrk Editor" 點擊 Bridge會出現 " Cannot change network to bridged: There are no un-bridged host network adapters"

Solution :

step1. ncpa.cpl

step2. 開啟bridge NIC

step3. Properties > install > Service > VMware Bridge Protocol

done.


Reference:

1. Workstation fails to bridge adapter with the error: Cannot change network to bridged: There are no un-bridged host network adapters (2005168)

2. http://it-life.wyx-ccy.com/2016/02/vmware-virtual-network-editor.html

[VMware] vCenter unable to load resource module from /vsphere-client/VDP2/locales/VDP-zh_TW.swf

近日在vCenter 6.0U2 操作客戶反應登入vSphere Web Client 會有錯誤,類似之前寫過一篇

VMware vCenter unable to load resource module from /monitoring-ui/locales/zh-tw.swf"

此次是針對vSphere Data Protection plug-in 中文部份,測試了

https://vCS-IP:9443/vsphere-client/?locale=en_US (英文版) > OK
https://vCS-IP:9443/vsphere-client/?locale=de_DE (德文版) > OK
https://vCS-IP:9443/vsphere-client/?locale=ko_KR (韓文版) > OK
https://vCS-IP:9443/vsphere-client/?locale=ja_JP   (日文版) > OK
皆沒問題!

QQ .. 偏偏就咱們中文繁文(VDP-zh_TW.swf) 有問題…

login vSphere Web Client error message
———————————————————————-
發生內部錯誤 – Unable to load resource module from /vsphere-client/VDP2/locales/VDP-zh_TW.swf

建議重新載入用戶端,以清除此錯誤殘留的任何問題。
按一下[是]以重新載入 vSphere Web Client ?
顥示錯誤堆疊…
Workaround:

1.
search “C:\Program Files\VMware\vCenter Server\WebClient\server\work\deployer\s\global\158\vdr-ui-war-6.1.2.war\locales

search “C:\Program Files\VMware\vCenter Server\WebClient\server\work\deployer\s\global"

找關鍵字"VDP-*.swf"  > 開啟檔案位置(I) > 跳到存在這VDP-*.swf位置

2.拿 VDP-zh_CN.swf 複製一份,並變更檔名為 VDP-zh_TW.swf (無需重啟vSphere Web Client  service)

done.

Windows 8 or Windows 10 How to auto login

solution#1

step01. Win + R

step02. netplwiz

step03. 必須輸入使用者名稱和密碼,才能使用這台電腦(E)


solution#2

step01. regedit.exe

step02. HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

step03. add ‘字串值’ ( DefaultPassword ) , 輸入DefaultUserName密碼在裡頭

step04. AutoAdminLogon 把 0 改為 1


Reference:

1. http://www.intowindows.com/how-to-automatically-login-in-windows-10/

2. http://pcsupport.about.com/od/windows-8/fl/auto-logon-windows-8.htm

[VMware] vSphere Web Client connect vSphere Data Protection 6.1.2 hangs or Freezes ?

客戶 vCenter server 5.5 upgrade to 6.0U2 ,因在vCenter 6.0U2已不支援使用原先備份vSphere Data Protection 5.8 Advanced , 建議除了使用Migrate(註1) 較費功夫,因此,客戶決定重新安裝!

重新安裝後發生在點擊 connect 居然會 hang (freeze)不動,

check / procedure list
====================

1. dns server , A / PTR record ( /etc/resolv.conf  ,  /etc/hosts)

2. networking ip / gateway

3. vdp service ( https://vdp:8543/vdp-configure)

3. restart web management service ( emwebapp.sh –stop && emwebapp.sh –start )

4. un-register / re-register vCenter into plug-in ( httos://vcenter/mob & https://vdp:8543/vdp-configure )

以上都作但無效,加上VMware SR Support 提供都回覆很慢,最後看到國外論壇討論到若 vdp 6.1.2 or 6.1.x安裝到

vSphere Standard Switch 是可以 –> 自己實測過確實客戶這邊改到 vSS是 OK ,看來vDP 和 vDS (vSphere Distributed Switch) 有關,找尋到前天才發佈 VMwre KB 2145686

雖此篇講述vSphere Data Protection 6.1.2 搭配 vCS / vCSA 5.5 , 6.0 加上有 network vDS環境才會,但
我實測在 vDP 6.0.x 6.1.x皆會發生 hang (freezes) state

~Solution~
vSphere Data Protection 及 vCenter Server / vCenter Server Appliance需安裝此 KB 2145686 hotfix即解決這個問題。

# 再次證明我之前經驗 VMware Infrastructure support engineer 服務及解決能力真的是讓人 OOXX , 替他們想或許他們電話接不完來不及理我 QQ

(註1) vSphere Data Protection Migrate > https://kb.vmware.com/kb/2127665


Reference:
1. Deploying the vSphere Data Protection 6.1.2 plug-in fails with the error: Type ‘com.vmware.vim.binding.vim.dvs.PortConnection’ not found (2145686)

https://kb.vmware.com/kb/2145686

[VMware] How to use vSphere Data Protection 5.5 ~ 6.x non use DNS

以往在安裝VDP按照官方就是一定要DNS A / PTR record ,但其實在 vSphere Data Protection v5.5 ~ 6.x其實可以騙過它自己也是可以正常佈署VDP的唷 !

~solution~

step1. deploy vSphere Data Protection Appliance (在此DNS指向自己vdp本身 " 127.0.0.1 " )

step2. power-on it

step3. 在設定 https://vdp-ip:8543/vdp-configure之前先進入console

step4. confirm  /etc/resolv.conf , information as below
—————————————————————
nameserver    127.0.0.1
—————————————————————

step5. vi /etc/hosts   // 加入自己vSphere Data Protection & vCenter server record
—————————————————————
192.168.1.100     vdp.com.tw              vdp
192.168.1.20       vcenter.com.tw        vcenter
—————————————————————

step5. vi /etc/dnsmasq.conf    //加入一筆 server=vdp-ip
—————————————————————
server=192.168.1.100
—————————————————————

step6. # chkconfig dnsmasq on    // 常駐開機 dnsmasq service

step7. # /sbin/service dnsmasq start   // 啟用 dnsmasq service

step8. verify dns self is fine
verify A record
—————————————————————
# nslookup vdp.com.tw
Server : 127.0.0.1
Address: 127.0.0.1#53
Name: vdp.com.tw
Address: 192.168.1.100

verify PTR record

—————————————————————
# nslookup 192.168.1.100
Server : 127.0.0.1
Address: 127.0.0.1#53
100.1.168.192.in-addr.arpa          name = vdp.com.tw

done. enjoy vdp world ^O^


Reference:

1. http://www.virtuallyghetto.com/2013/11/how-to-evaluate-vsphere-data-protection.html

[VMware] vSphere Replication error “unable to configure replication for virtual machine ‘xx’ because group ‘xx’ cannot be created

在幫客戶測試vSphere Replication 多次後因都用同一台VM,操作發生如下訊息

" unable to configure replication for virtual machine ‘xx’ because group ‘xx’ cannot be created.

another virtual machine ‘xx’ that has the same instance UUID ‘xxxxxxxxxxxxxxxxxx’ already exists on protection site ‘DR_VR"

查明Google大神

如果您有兩個站台,且已重新安裝 vSphere Replication Management Server 應用裝置或重設其資料庫,則設定複寫會失敗。
問題
其他站台包含有關舊應用裝置和資料庫的資訊,並且可阻止您設定新複寫。可能會顯示以下錯誤訊息:
無法設定虛擬機器的複寫 VM_name 因為無法建立 group_name 群組。
擁有相同執行個體 UUID instance_UUID 的另一個虛擬機器 configured_VM_name}’ 已存在於保護站台 source_site_name 上。

解決方案
1 在其他站台上重新安裝 VRMS,或重設其資料庫。
2 連線站台,並登錄任何其他 vSphere Replication Server 應用裝置。
3 從目標資料存放區資料夾移除存留的任何暫存 hbr* 檔案。
4 設定所有複寫,同時重複使用現有複本 .vmdk 檔案做為複寫種子。

因為我的案例屬新建的因此直接採取"重設其資料庫"

> login https://VRMS:5480
> Configuration > Reset Embedded Database


Reference:

https://pubs.vmware.com/vsphere-replication-60/index.jsp?topic=%2Fcom.vmware.vsphere.replication-admin.doc%2FGUID-06A0C28D-4854-4B2E-A91D-98EF2FD3AB22.html