Exports the cloned DFS Replication database and volume configuration settings.
PowerShell · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft DFSR reference: Exports the cloned DFS Replication database and volume configuration settings. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Export-DfsrClone. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / DFSR · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-AllowClobber
Indicates that the cmdlet overwrites an existing exported database and XML configuration file. By default, if a file exists in the specified path, the operation halts. After you export the DFS Replication database, but before you perform the import clone operation, you must populate the downstream server with the contents of the replicated folder.
-Confirm
Prompts you for confirmation before running the cmdlet.
-Force
Forces the command to run without asking for user confirmation. Use this parameter for scripted cloning.
-Path
Specifies a folder path to which to write the exported DFS Replication files dfsr.db.clone and config.xml. The folder path must exist. The path must be a local volume and not a mapped drive or a UNC path. If you do not specify this parameter, the cmdlet uses the current working directory. After you export the DFS Replication files, but before you perform the import clone operation, you must populate the downstream server with the contents of the replicated folder.
-Validation
Specifies the verbosity level of checks performed by the DFS Replication service against the replicated content set files and folders for comparison to the populated data on the destination clone during import. Acceptable values for this parameter are: - None (0) No validation is performed on the files, all files and folders are assumed to exist, and the administrator must have populated the files and folders without errors, or allowing any changes to the file structures on upstream and downstream servers. This is the fastest but most optimistic mode. - Basic (1) Simple comparisons are performed for every file and folder using the size, modified time-date stamp, and hash of the ACL. Any added, missing or differing files or folders are replicated inbound and any inconsistent local copies on the downstream are moved to the \\Dfsrprivate\ConflictAndDeleted folder or to the \\DfsrPrivate\PreExisting folder. This mode is a good balance of performance and optimism. - Full (2) DFS Replication hash computation is performed for every file and folder. Any missing or differing files or folders are replicated inbound and any inconsistent local copies on the downstream are moved to the \\Dfsrprivate\ConflictAndDeleted folder or to the \\DfsrPrivate\PreExisting folder. This is the slowest but most accurate mode.
-Volume (required)
Specifies a drive letter or mount point path that contains the database to export for that volume's replicated content folders, in order to perform cloning. If there are multiple replicated folders hosted on that volume, they all use the same DFS Replication database and they all clone. After you export the DFS Replication database, but before you perform the import clone operation, you must populate the downstream server with the contents of the replicated folder.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the DFSR module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
This example demonstrates exporting the DFS Replication database clone and then uses Get-DfsrCloneState to periodically retrieve state until the replication completes. The first command uses the Export-DfsrClone cmdlet to start the export process. You must open another Windows PowerShell console or hit CTRL+C to exit the Export-DfsrClone cmdlet. The cloning continues on the server even if the cmdlet stops running. The second command uses the Get-DfsrCloneState cmdlet to check the state of the export process. The output appears after the command. The third command uses the Get-DfsrCloneState cmdlet to check the state of the export process. The output indicates that the export completed successfully. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.