Run the replace-profile subcommand on a server that was originally set up with a server profile to replace its configuration with a new profile. The tool applies a specified server profile to an existing server while preserving its data, topology configuration, and replication configuration.

While manage-profile replace-profile is running, the existing server is stopped and moved to a temporary directory that the --tempServerDirectory argument can specify. A fresh, new server is subsequently installed and set up with the new profile. The final server is left running if it was running before the command was started, and remains stopped if it was stopped.

Run manage-profile replace-profile from a second unzipped server install package on the same host as the existing server, similar to the update tool. Use the --serverRoot argument to specify the root of the existing server that will have its profile replaced.

If files have been added or modified in the server root since the most recent manage-profile setup or manage-profile replace-profile was run, they are included in the final server with the replaced profile. Otherwise, files specifically added from the server-root directory of the previous server profile are absent from the final server with the replaced profile. If errors occur during the subcommand, such as the new profile having an invalid setup-arguments.txt file, the existing server returns to its original state from before manage-profile replace-profile was run.

The --skipValidation option which skips the validation step when running on an offline server

Note:

When you run the manage-profile replace-profile tool with an SDK extension included in the new profile, the tool invokes the setup command.

The manage-profile replace-profile tool can update the server version when needed. It can also directly apply configuration changes when there are no other changes in the new profile. This is a shorter process when making small changes to dsconfig.