What Are the Important Statements of SMS?
- Source server data collection
After the Agent is started on a source server, it will report source server details to SMS. This information will only be used to check the feasibility of a migration. For details about what information will be collected from the source server, see What Information Does SMS Collect About Source Servers? If you use SMS, you agree that SMS collects the information.
- License invalidity
After OSs, applications, and files on source servers are migrated to target servers, the SIDs and MAC addresses of the servers will change. This means that some OS or application licenses may become invalid. SMS is not responsible for this type of issue.
- Target server disk formatting
During a migration, disks on the target server are formatted and re-partitioned based on the source disk settings. Any existing data on the target server will be lost. Before the migration, make sure you have backed up any data on the target server that you need to save and ensure that the disks can be formatted. SMS is not responsible for any data losses incurred.
- If your target servers on the cloud platform cannot be started after the migration is complete, the cloud platform can provide technical support to help you solve the problem, but does not promise that the all possible problems can be resolved.
There are many possible reasons that a target server may be unable to start, for example:
- The source server cannot be restarted.
- The source server has a non-standard OS configuration.
- The source server has drivers or software that are incompatible with the cloud platform.
- To ensure compatibility with the cloud platform, SMS modifies the system configurations of target servers. For details, see What Are the Differences Between Target and Source Servers After the Migration? SMS can ensure data consistency before and after the migration but cannot ensure that your services run properly after the migration. You need to modify related service configurations thereafter.