Overinstall: same installation directory, hosts, and portsOverinstall: same installation directory, hosts, and portsSide-by-side: new installation directory, same hosts and portsCross-host: new hosts, same ports. The installation directory can have the same or a new value.Command Central syntax:Not applicable to Platform Manager.Argument or Option | Description |
stackName | Required. The name of the stack to use to migrate the product installations. |
migration.type={overinstall|sidebyside|crosshost} | Required. The type of migration to run when upgrading the product installations. Valid values: overinstallsidebysidecrosshost |
[-i input-parameters-file.properties] | Optional. The properties file that contains the required and optional properties, for which you should specify values during migration. |
[param1=value1 param2=value2 ...] | Optional. Include the required and optional properties, for which you should specify values during migration, as arguments in the command. |
[migration.reuse.templates={true|false}] | Optional. After a failed migration attempt, you can include this argument in the command when you next attempt to migrate with the same stack. Indicates whether to use the generated templates from the last failed migration run in the next run. Valid values: true - reuses the generated templatesfalse (default) - does not reuse the generated templates |
[migration.dry.run={true|false}] | Optional. Indicates whether Command Central should try a dry run of the upgrade. In the dry run, Command Central generates templates, validates the templates and the migration properties, but does not apply the templates on the target nodes. You can review the results of the dry-run job and check the templates before the actual migration run. Valid values: true - generate and validate the templates, but do not apply themfalse - (default) - generate, validate, and apply the templatesWhen you do not include the argument, Command Central does not try a dry run. For information about how Command Central validates a template, see
Validating a Composite Template. |
[options] | Optional. The command allows all options supported by the Command Line Interface. For a description of the options, see
Common Options. |
To obtain the required and optional properties for migration, run the sagcc list stacks migrate properties command. You can also use the Stacks > Upgrade Stack web user interface to export the properties for an existing stack into a properties file to use as input file for the stacks migrate command.You must specify the migration properties either as arguments in the command, or in an input file. You can also include both [param1=value1 param2=value2 ...] and [-i <input-parameters-file>.properties] in the same command. The values specified in the arguments will override the values of the parameters specified in the properties file.If a migration attempt fails, run the sagcc list stacks migrate status command to check the migration status of the stack. The command output also indicates whether any templates were generated during the failed attempt.When running the stacks migrate command, the command processes the fixes property as follows:fixes=ALL By default, installs all the latest fixes for the respective layer, which are available in the specified fix repository for the products in the target installations.fixes= If you leave the value empty, the command does not install fixes on the target installation.fixes=[fixName1[_version], fixId2, ...,fixIdN] If you include this argument, the command installs only the fixes listed in the argument. To retrieve a list of fix names or fix IDs, run
sagcc list repository fixes content.