Issue is due the third-party jetdr I/O filter module which is blocking and failing the snapshot task during the prepare phase. Snapshot can fail for a multi-disk VM if the backup appliance does not have enough resources (e.g., attempting to back up too many VMs/disks concurrently). As result, some disks of the affected VM may not be snapshotted. In such a case, JetStream DR restores/returns to a pre-snapshot state for already snapshotted disks.
Virtual machine Logs: /vmfs/volumes/[datastore-name]/[vm-name]/vmware.log
below errors indicates the issue with the third-party jetdr module
2025-02-06T03:23:49.631Z Er(02):vmx - DISKLIB-LIB_CREATE :DiskLib_NotifySnapshotPrepare: FiltLib failed to noilify snapshot prepare: Operation completes asynchronously
2025-02-06T03:23:49.651Z In(05):vmx - DISKLIB-CBT: ChangeTrackerESX_CreateMirror: Created mirror node /vmfs/devices/<vm/****-cbtmirror.
2025-02-06T03:23:49.666Z In(05):vmx - SNAPSHOT: SnapshotPrepareTakeDoneCB: Failed to prepare filter.
2025-02-06T03:23:49.752Z In(05):vmx - SNAPSHOT: SnapshotPrepareTakeDoneCB: Prepare phase complete (Operation failed,
2025-02-06T03:23:49.752Z In(05):vmx - SnapshotVMXPrepareTakeDoneCB: Prepare phase failed: Operation failed (5).
025-02-06T03:23:49.560Z In(05) vmx - DISKLIB-CBT :ChangeTrackerESX_CreateMirror: Created mirror node /vmfs/devices/svm/3f2c8886-371b1c3b-cbtmirror.
2025-02-06T03:23:49.570Z In(05) vmx -I>FLTR_MAIN: FioCbkSnapshot(1824): VMIOF_SNAPSHOT_PREPARE entered for VM.vmdk, opMode=2.
2025-02-06T03:23:49.570Z Wa(03) vmx -I>FLTR_MAIN: FioCbkSnapshot(1945): Unable to take snapshot of VM_1.vmdk as protection start is not completed yet.
025-02-06T03:23:49.570Z In(05) vmx - FiltLib: jetdr: Notification completed with error: "Operation failed" (1).
2025-02-06T03:23:49.570Z In(05) vmx -FiltLib: jetdr: filter failed notification processing: "Operation failed" (1).
Snapshot may fail due to insufficient resource, so wait for a while before attempting to take the snapshot again and then retake the snapshot.
If the above operation fails It is recommended to involve the third-party (Jetstream) vendor to further investigate the issue.
JetStream software installed on each ESXi host configured for JetStream DR. The host driver intercepts the vSphere VMs I/O and sends the replication data to the DRVA. The IO filters also monitor relevant events, such as vMotion, Storage vMotion, snapshots, etc.