If an administrator clones a Microsoft SQL Server database by using the “Latest Time” option...

NDB Time Machine protects Microsoft SQL Server databases through application-consistent snapshots and a continuous sequence of transaction-log backups captured by Log Catch-up operations. When the latest protected time is selected, NDB uses the appropriate snapshot as the baseline and applies the required transaction logs through the most recent available recovery point. This produces a transactionally consistent clone rather than a crash-consistent VM copy. NDB does not need to leave the source database in read-only mode, and Volume Shadow Copy Service alone cannot provide the transaction-log replay required for granular point-in-time cloning. “Latest Time” means the latest point covered by the valid Time Machine snapshot and log chain, not an unprotected wall-clock instant after the last log capture. Nutanix’s Database Log Backup Management documentation explains that Log Catch-up captures database transaction logs for point-in-time cloning.