SRM Test Failover takes long time to complete the step 'Create writable storage snapshot'
search cancel

SRM Test Failover takes long time to complete the step 'Create writable storage snapshot'

book

Article ID: 403665

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

An administrator observes SRM Test Failover taking longer time to complete the step 'Create writable storage snapshot'


Environment

VMware Site Recovery Manager 8.X
VMware Site Recovery Manager 9.X

Cause

When VM is powered-off and the VM is set CBT enabled in the reconfigure VM task, it might take long time as CBT initialization needs to retrieve the allocated blocks.

hostd.1: 2025-06-19T15:02:17.587Z Db(167) Hostd[2100351]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/67b654c9-8619d1d5-a68b-6c92cf1e47a0/xxxx/vrTestImage/xxxx.vmx opID=d6b3a604-c099-4885-8907-c1c126244cfd-test:e34f:98bc:f71f:4efa:ed48-ca-01-3b-037f sid=52c287d2 user=vpxuser:VSPHERE.ASCEND\SRM-fb720ed5-d38d-443b-9f1c-ba8e2dda24e6] Adjusting tracking state for disk /vmfs/volumes/67b654c9-8619d1d5-a68b-6c92cf1e47a0/xxxx/vrTestImage/hbrimagedisk.RDID-a851180f-13b9-458f-a4ee-8bc874e35926.vmdk to state enabled

 

Resolution

Retrieving the allocated blocks takes much time if the disk is huge / there are many fragments of allocation / the storage is slow. It's common that it takes 10+ mins to initialize CBT.