Using the Export-Finalize with a SQL Server VDB

Export Finalize is the controlled cut over step that ensures data integrity between Incremental VDB and physical database. It completes an in-progress incremental export of a SQL Server Incremental VDB and applies any remaining backups from the VDB to the physical database, so they are identical and later brings the exported physical database online for user access. Finally, the Incremental VDB and the associated workers are deleted from the engine.

Currently, the Incremental V2P is supported only via API/CLI. So, the following sections explain the procedure to complete these stages using CLI.

Procedure

Log in to CLI and navigate to database.
Select the Incremental VDB associated with Incremental export (physical) database:
Copy
```
select <incremental_vdb>
```
Finalize export to open physical database:
Copy
```
exportFinalize
```
Commit the configuration to execute the job:
Copy
```
commit
```

This operation will abort when pending, unapplied backups exceed the allowed threshold (default limit: 5). To customise this behaviour, Delphix provides following parameters:

Parameter	Description
`maxAllowedBackupsPendingRestore` (integer, default limit 5)	Upper limit of incremental backups still not restored to the physical database that is tolerated before exportFinalize starts.
`force` (boolean, default false)	Set true to ignore maxAllowedBackupsPendingRestore.

Parameter

Description

maxAllowedBackupsPendingRestore

(integer, default limit 5)

Upper limit of incremental backups still not restored to the physical database that is tolerated before exportFinalize starts.

force

(boolean, default false)

Set true to ignore maxAllowedBackupsPendingRestore.

Best Practices

Execute exportFinalize once the backlog (pending incremental backups) between the Incremental VDB and the physical database is within your target threshold; monitor applied vs. pending changes to select a low‑gap window. To know more about the available container runtime attributes, refer to the Monitoring incremental V2P status section.
Adjust maxAllowedBackupsPendingRestore to prevent accidental exportFinalize operation before your target threshold.
Quiesce write activity during finalize to limit new log generation and ensure a faster, smoother completion.
Use force=true only when backlog unexpectedly spikes; otherwise let safeguards prevent long finalize durations.