KeyValueStoreReplica.FullCopyMode Enum
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Specifies the behavior to use when building new secondary replicas (full copy).
public enum KeyValueStoreReplica.FullCopyModetype KeyValueStoreReplica.FullCopyMode = Public Enum KeyValueStoreReplica.FullCopyMode- Inheritance
-
KeyValueStoreReplica.FullCopyMode
Fields
| Name | Value | Description |
|---|---|---|
| Default | 0 | The full copy mode specified in the cluster manifest will be used. |
| Physical | 1 | Full copies will be performed by taking a backup of the primary replica database and sending the physical database files to secondary replicas for restoration. This is the recommended and default mode. |
| Logical | 2 | Full copies will be performed by reading all database contents and sending them to secondary replicas for replay against their own databases. Since this mode requires opening a long-running transaction on the primary for the duration of the build, it's only recommended for small databases or services with low write activity. This mode enables changing database parameters that are normally fixed after initialization such as DatabasePageSizeInKB and LogFileSizeInKB. |
| Rebuild | 3 | Full copies will be performed as a physical copy, but with an additional step of replaying all database contents in primary index order to a new database on the secondary. This mode also enables changing database parameters that are normally fixed after initialization, but will take longer than either physical or logical build due to the extra replay step. After replay, the final data layout is optimal since insertion occurred in primary index order. Currently not supported in Linux. |
