Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Force stop vSphere Replication on vSAN datastore and retain existing VMDKs/Seeds for the Virtual machine (58550)

Last Updated: 6/30/2023Categories: TroubleshootingTotal Views: 12305Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

vSphere -Replication for a virtual machine is broken  The destination vm folder is located on a vSAN datastore.

The Admin would like to stop/re-configure replication using existing seeds / vmdks to avoid a full sync to the destination vSAN datastore .

Purpose

Traditional method using the VMFS  datastore was to rename the folder at the destination VMFS datastore and then force stop replication , re-name the folder back to original and replicate the VM using existing Seeds

We Cannot Re-Name the folders on the destination vSANdatastore (Object Store file system) since the VM folder name is symlink to namespace object UUID .

To safely force stop vsphere Replication and reconfigure replication once again , this KB covers the steps  to re-replicate the VM using existing seeds to a vSAN datastore on the destination.

Cause

Vsphere Replication is in error state for a VM replicating to a vSAN datastore

Replication is in a RPO violation state . Force resync is failing for the VM running on vSAN datastore

RDID vdisk on the destination folder is corrupted , force re-configure and other attempts did not help sync up the VM .

Re-sync replication to the target vSAN datastore gets stuck at full sync for very long time and never progresses .

Impact / Risks

If this procedure was not followed in correct order , the customer will lose the existing VMDK at the target site and a full sync to a new VMDK/Object  is needed to get the replication back to OK status.

The steps mentioned in the article should be executed by experts only. In case of doubts please open support ticket with VMware GSS with details of the environment.

Resolution

Please follow the below steps carefully and make sure every step is documented and noted .

Note down the path / namespace object for the vm-folder where the data is being replicated to from the source virtual machine  and the files and object in that folder .

SSH to any of the hosts on the destination site/cluster which has access to the VM-namespace folder and view the list of files available .

[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c] cd Test-vr-rep
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734] ls -la
total 792608
drwxr-xr-t    1 root     root          2940 Sep 18 05:42 .
drwxr-xr-x    1 root     root           512 Sep 18 05:53 ..
-rw-------    1 root     root             0 Sep 18 04:25 .207ea05b-d5d7-dd9c-1a66-005056b8688c.lck
-rw-------    1 root     root             0 Sep 18 05:42 .2b90a05b-cbd0-7a1c-610b-005056b82734.lck
-rw-------    1 root     root             0 Sep 18 04:25 .337ea05b-aaf4-ae0b-073c-005056b8688c.lck
-r--------    1 root     root       1441792 Sep 18 04:06 .fbb.sf
-r--------    1 root     root     267026432 Sep 18 04:06 .fdc.sf
-r--------    1 root     root       1179648 Sep 18 04:06 .pb2.sf
-r--------    1 root     root     268435456 Sep 18 04:06 .pbc.sf
-r--------    1 root     root     262733824 Sep 18 04:06 .sbc.sf
drwx------    1 root     root           280 Sep 18 04:06 .sdd.sf
-r--------    1 root     root       4194304 Sep 18 04:06 .vh.sf
-rw-------    1 root     root           521 Sep 18 04:27 Test-vr-rep.vmdk
-rw-------    1 root     root          8684 Sep 18 04:32 hbrcfg.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.10.nvram.14
-rw-------    1 root     root          3151 Sep 18 04:32 hbrcfg.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.10.vmx.13
-rw-------    1 root     root          8684 Sep 18 04:27 hbrcfg.GID-cf9f2410-3997-47d0-8033-333de72398c6.9.nvram.12
-rw-------    1 root     root          3153 Sep 18 04:27 hbrcfg.GID-cf9f2410-3997-47d0-8033-333de72398c6.9.vmx.11
-rw-------    1 root     root           339 Sep 18 05:42 hbrdisk.RDID-b968fb4a-13c7-415c-a43d-8ef040fc1051.31.124727821486618.vmdk
-rw-------    1 root     root           339 Sep 18 04:27 hbrdisk.RDID-e219e8d8-b7a7-4ee0-8311-2ebba2323659.15.255651935167219.vmdk
-rw-------    1 root     root          3064 Sep 18 05:42 hbrgrp.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.txt
-rw-------    1 root     root          3064 Sep 18 04:27 hbrgrp.GID-cf9f2410-3997-47d0-8033-333de72398c6.txt

Create a new Folder (namespace)by browsing vSAN datastore (GUI) or by command line as Below :

[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c] /usr/lib/vmware/osfs/bin/osfs-mkdir Dummy-Folder
0194a05b-5c07-0c48-c4f8-005056b82734
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c] cd 0194a05b-5c07-0c48-c4f8-005056b82734
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734]

Move all the content in the original folder to the new Test/Dummy folder , here in this example , Original folder "Test-vr-rep" (/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734) to Dummy-Folder (/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734) . Please Double check and Confirm that there are no vmdk descriptors leftover on the source folder before moving to the next step .

[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734] mv * /vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734/
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734] cd /vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734/
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734] ls -la
total 792608
drwxr-xr-t 1 root root 2520 Sep 18 06:49 .
drwxr-xr-x 1 root root 512 Sep 18 06:50 ..
-r-------- 1 root root 1441792 Sep 18 05:58 .fbb.sf
-r-------- 1 root root 267026432 Sep 18 05:58 .fdc.sf
-r-------- 1 root root 1179648 Sep 18 05:58 .pb2.sf
-r-------- 1 root root 268435456 Sep 18 05:58 .pbc.sf
-r-------- 1 root root 262733824 Sep 18 05:58 .sbc.sf
drwx------ 1 root root 280 Sep 18 05:58 .sdd.sf
-r-------- 1 root root 4194304 Sep 18 05:58 .vh.sf
-rw------- 1 root root 521 Sep 18 04:27 Test-vr-rep.vmdk
-rw------- 1 root root 8684 Sep 18 04:32 hbrcfg.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.10.nvram.14
-rw------- 1 root root 3151 Sep 18 04:32 hbrcfg.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.10.vmx.13
-rw------- 1 root root 8684 Sep 18 04:27 hbrcfg.GID-cf9f2410-3997-47d0-8033-333de72398c6.9.nvram.12
-rw------- 1 root root 3153 Sep 18 04:27 hbrcfg.GID-cf9f2410-3997-47d0-8033-333de72398c6.9.vmx.11
-rw------- 1 root root 339 Sep 18 05:42 hbrdisk.RDID-b968fb4a-13c7-415c-a43d-8ef040fc1051.31.124727821486618.vmdk
-rw------- 1 root root 339 Sep 18 04:27 hbrdisk.RDID-e219e8d8-b7a7-4ee0-8311-2ebba2323659.15.255651935167219.vmdk
-rw------- 1 root root 3064 Sep 18 05:42 hbrgrp.GID-2e816e27-c516-4761-bec4-6e7ec5e576b6.txt
-rw------- 1 root root 3064 Sep 18 04:27 hbrgrp.GID-cf9f2410-3997-47d0-8033-333de72398c6.txt
[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/0194a05b-5c07-0c48-c4f8-005056b82734]

**NOTE ORIGINAL FOLDER WILL STILL CONTAIN lck files , which can be ignored :

[root@zh4:] cd /vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/Test-vr-rep

[root@zh4:/vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734] ls -la
total 790528
drwxr-xr-t    1 root     root          1680 Sep 18 06:49 .
drwxr-xr-x    1 root     root           512 Sep 18 06:51 ..
-rw-------    1 root     root             0 Sep 18 04:25 .207ea05b-d5d7-dd9c-1a66-005056b8688c.lck
-rw-------    1 root     root             0 Sep 18 05:42 .2b90a05b-cbd0-7a1c-610b-005056b82734.lck
-rw-------    1 root     root             0 Sep 18 04:25 .337ea05b-aaf4-ae0b-073c-005056b8688c.lck
-r--------    1 root     root       1441792 Sep 18 04:06 .fbb.sf
-r--------    1 root     root     267026432 Sep 18 04:06 .fdc.sf
-r--------    1 root     root       1179648 Sep 18 04:06 .pb2.sf
-r--------    1 root     root     268435456 Sep 18 04:06 .pbc.sf
-r--------    1 root     root     262733824 Sep 18 04:06 .sbc.sf
drwx------    1 root     root           280 Sep 18 04:06 .sdd.sf
-r--------    1 root     root       4194304 Sep 18 04:06 .vh.sf

Head back to webclient , and execute FORCE Stop Replication for the virtual machine in question from both Source VCenter (Outgoing Replication) and Destination VC (Incoming Replication) .  Please  note that the VC will still try to delete the vmdk on the destination (Original folder) and fail the task at this stage .

Copy the vmdk files (all the base disks) back to the source folder and leave the rest on the dummy-folder

cp Test-vr-rep.vmdk /vmfs/volumes/vsan:5221428b209bc448-116434ddeaf3473c/c579a05b-4d12-f70f-df1c-005056b82734/

​Complete Re-Configure Replication task , from the source VM and use existing seed at the destination , Replication using existing VMDK should finish successfully .

Workaround

N/A

Related Information

https://docs.vmware.com/en/vSphere-Replication/6.0/com.vmware.vsphere.replication-admin.doc/GUID-C7CD1006-7E2F-42B3-A3EC-429F365140E1.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Diagnóstico de implantação lenta de modelos ou clones no vCenter Server (1004002)

KB
•
vSphere Replication 管理服务器中出现一般错误 (55020)

KB
•
在 vRealize Operations Manager 6.x 及高级版本中，分析服务在多节点群集上启动失败 (2149200)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Replication

VMware vSphere

VMware vSAN

Related Versions:

VMware vSphere Replication 8.x

VMware vSphere Replication 6.x

VMware vSphere Replication 6.5.x

VMware vSphere Replication 6.0.x

VMware vSAN 6.x

VMware vSAN 6.7.x

VMware vSAN 6.6.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant