Rolling Back a Migrated Instance
You can rollback a migrated instance to OS Management, if required.
- Rollback Considerations
-
- OS Management periodically removes instances that haven't checked in with the service. If you rollback a migrated instance after an extended period of time, the instance might register with OS Management as a new instance. Its prior configuration, including attached software sources, group assignments and scheduled jobs, isn't restored.
- After a rollback and before you retry the migration to OS Management Hub, you must remove the
osmh-agent-unregister
file. See Instance was previously unregistered.
Using the Migration Assistant
Use the osms-to-osmh rollback managed-instance
command and required parameters to return a migrated instance to OS Management.
For example:
osms-to-osmh rollback managed-instance --managed-instance-id ocid
The following is sample output:
$ osms-to-osmh rollback managed-instance --managed-instance-id ocid1.instance.oc1..<unique_ID>
Rolling back instance: ocid1.instance.oc1..<unique_ID> to OSMS
Checking de-registration progress...
Instance de-registration still in progress. Retrying in 20 seconds...
Instance successfully de-registered from OSMH
Enabling OS Management Service Agent
Disabling OS Management Hub Agent
Registering instance with OS Management Service...
Instance rolled back to OSMS successfully
Usage
osms-to-osmh rollback managed-instance --managed-instance-id ocid [ --help]
Option Details
Parameter | Description |
---|---|
--managed-instance-id ocid |
Returns the managed instance to OS Management. For ocid, specify the OCID assigned to the managed instance. |
--help |
Displays help information about the migration assistant command, such as the available options and the supported values for each option. |