LINUX | Export NFS for VMware datastore

vi /etc/exports (add line)
/path/to/share 10.123.123.123(rw,sync,no_root_squash) ->ESX IP

exportfs -> verify actual shares on NFS server
exportfs -r -> reexport online all shares on NFS server after modif. /etc/exports

vSphere Replication Appliance Solution user detail certificate is invalid

Solution user detail’ certificate is invalid – certificateException java.security.cert.CertificateExpiredException: NotAfter: Sat Aug 20 16:36:39 CEST 2022

Resolution:

VMware resize vmdk LVM without adding new, primary partition (primary partition MBR limit to 4)

1. fdisk /dev/sda
p
q

2. Extend the VMDK in vCenter

3. fdisk /dev/sda
p
q

4. If no extra space:
echo ‘1’ > /sys/class/scsi_disk/0\:0\:0\:0/device/rescan

5. fdisk /dev/sda
p
q
There is free space

6. Delete partition
d
4
n
p
4
<enter>
<enter>
t
4
8e

p
w -> write partition!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.

7. partprobe -s

8. Extend
pvresize /dev/sda4
vgdisplay
lvdisplay
df -h
lvextend -L +100%FREE /dev/VGroot/LV01
lvdisplay
df -h
resize2fs /dev/VGroot/LV01 or fsadm resize /dev/VGroot/LV01
df -h

Disable CBT without poweroff VM by Avamar

admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:03 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:18:06 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:08 PM CEST

 

 

 
admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –disablecbt –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:33 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –disablecbt –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————– ———————————–
Jul 30, 2019 4:18:35 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250
Disabling CBT for : XXXXXXXXXXXXXXXXXXXXXX

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:38 PM CEST

 

 

 

 

admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:45 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:18:48 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : false
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:50 PM CEST

 

 

 
admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –enablecbt –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:22:13 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –enablecbt –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:22:18 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:22:21 PM CEST

VMware vCenter Server 5.5.0 (Windows, MSSQL) migrate upgrade to VMware vCenter 6.0 U3 Appliance (Linux, PostgreSQL)

source:
VMware vCenter Server 5.5.0 (Windows 2012R2, MSSQL 2012 Express), 12GB RAM

target:
VMware vCenter 6.0 U3 Appliance (Linux, PostgreSQL), 16 GB RAM

 

Error:

• Firstboot script execution error
• This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request
• /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log
• install.ciscommon.internal.error
• This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: VR Management (by VMware, Inc.) on http://vcenter:80/|https://appliancevr:8043 VMware vSphere Update Manager Extension on https://vcenter:8084/vci/sdk vCenter Operations Manager (by VMware, Inc.) on https://new_vcenter/vcops-vsphere/viClientConfig.xml

 

 

on logs:

csd.txt :
[2018-05-23 15:28:44] [INFO] Web Socket Server [50100] Terminated With no error code
[2018-05-23 15:28:44] [INFO] CSD Server Exited.
[2018-05-23 15:28:44] [INFO] Lookup: stop called…
[2018-05-23 15:28:44] [INFO] Lifetime: join…
[2018-05-23 15:28:47] [INFO] Lifetime Timer stopped.
[2018-05-23 15:28:47] [INFO] Lifetime: Exited.
[2018-05-23 15:28:47] [INFO] Lookup: Exited.
[2018-05-23 15:28:47] [INFO] ~MigrationApi
[2018-05-23 15:28:47] [INFO] Process exiting.

vcsa_0001.txt:
2018-05-23 14:47:23.065316 CIP Service [VCSA INFO] nfc.vmGetFile: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5509″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”cQk5-Fj2d-VuiB-e1PL”,”result”:”{\n \”status\”: \”error\”, \n \”info\”: [], \n \”question\”: null, \n \”progress_message\”: {\n \”args\”: [\n \”VMware Postgres\”\n ], \n \”id\”: \”install.ciscommon.component.starting\”, \n \”localized\”: \”Starting VMware Postgres…\”, \n \”translatable\”: \”Starting %(0)s…\”\n }, \n \”warning\”: [], \n \”error\”: {\n \”resolution\”: {\n \”id\”: \”install.default.failure.resolution\”, \n \”localized\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\“, \n \”translatable\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\”\n }, \n \”detail\”: [\n {\n \”args\”: [\n \”see /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\”\n ], \n \”id\”: \”install.ciscommon.internal.error\”, \n \”localized\”: \”Encountered an internal error.\\n\\nsee /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\“, \n \”translatable\”: \”Encountered an internal error.\\n\\n%(0)s\”\n }\n ], \n \”componentKey\”: \”vpostgres\”, \n \”problemId\”: null\n }, \n \”progress\”: 48\n}”,”isFinal”:”true”}
2018-05-23 14:47:23.068319 Progress Page: [VCSA ERROR] – First Boot error
2018-05-23 14:47:28.784075 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:47:30.187195 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”true”}
2018-05-23 14:47:30.191199 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:10.911286 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:12.316936 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:12.320941 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:53.037021 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:54.440281 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:54.443297 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:49:38.771027 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”false”,”item”:[“{\”data\”:\”\”}”]}
2018-05-23 14:49:39.573271 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 14:49:39.577275 Progress Page: [USER INFO] Support bundle created successfully – {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 15:14:49.825467 Progress Footer: Closing the installation wizard

 

what to check:

1. Check DNS, forward and reverse resolution
2. Check NTP server, try to sync time
3. Plug-in not compatible is better to unregister/uninstall:  how to.
   I uninstalled: Update Manager, Operations Manager, UCS Plugin, VR Plugin
4. In our environment Replication Appliance was incompatible with new version of vCenter. I stopped all replication jobs, unregistered Appliance (how to). Stopped VR Appliance.
5. Check the database size…

 

Resolution:

In my situation, 8GB database (MSSQL) on Win2012R2 with 12GB RAM (small vCenter, 1000VM), was migrated to the same, small vCenter on Linux (1000 VM), with 16 GB RAM.

… it was to small.
I modified: vCenter Server to 32GB RAM,
on migration step I choose Large vCenter (32GB RAM) to create large vCenter Appliance

Success :)

ps. after this, I downsized RAM to 16GB :)

 

 

RESULT:

 

 

DPM cannot continue protection for VMware

Problem:

Type: Consistency check Status: Failed Description: DPM cannot continue protection for VMware <vm_name> on <vCenter_server/ESX host IP>  (ID 30184) More information End time: 2018-03-12 23:48:37 Start time: 2018-03-12 23:48:37 Time elapsed: 00:00:00 Data transferred: 0 MB Cluster node – Source details: <vm_name> Protection group: Protection Group 1 Items scanned: 0 Items fixed: 0

 

Resolution 1:

Problem with VM *.vmx file.

• Delete vmx and recreate VM
  or
• create new VM and bind hdd from old VM.

 

Resolution 2:

• check if there is not snapshot on VM! :)