How Do I Choose When the System Asks Whether to Disable the Google Services Detected on My Source Server on the Google Cloud?
Description
When I started the Agent on the Linux source server running on the Google Cloud, the system asked me whether to disable the detected Google services.
Background
Some Google services depend on Google Cloud. After the source server is migrated to Huawei Cloud, Google services cannot run properly. As a result, after the migration, the target server may fail to be launched or other services may fail to be started. Before the migration, read Description of Disabling Google Services and make evaluations based on service requirements.
![](https://support.huaweicloud.com/intl/en-us/sms_faq/public_sys-resources/note_3.0-en-us.png)
- Disabling these services does not affect the source server. It only affects the configuration of startup services on the target server.
- If your services depend on these Google services, contact Huawei Cloud technical support before the migration.
- If you choose to disable these Google services, enter y. During the target server configuration, the Agent will disable these services on the target server.
- If you choose not to disable these Google services, enter n and change the value of disableplatformservice to False in the .../SMS-Agent/agent/config/g-property.cfg file in the SMS-Agent installation directory. After the migration, all service settings are retained, and the target server or some services may fail to be started.
Description of Disabling Google Services
- Servers with startup services in the /etc/systemd/system directory, such as those running Ubuntu, CentOS 8, or CentOS 9
If you choose to disable the Google services, the Agent will only delete the soft links related to these services in the /etc/systemd/system directory. The service files pointed by the soft links are not affected.
![](https://support.huaweicloud.com/intl/en-us/sms_faq/public_sys-resources/note_3.0-en-us.png)
Deleting the soft links of a service prevents the service from starting automatically at startup but does not affect the actual files of the service.
- Servers with startup services in the /etc/init directory, such as those running CentOS 6
If you choose to disable the Google services, the Agent will check the configuration files whose names start with google in the /etc/init directory, move these configuration files to /etc/backup_googleconf, and compress the folder into package google_conf_bak.tar.gz for backup.
Agent Installation and Startup FAQs
- How Do I Download and Install the Agent on Source Servers?
- What Can I Do If I Fail to Download the Agent Installation File?
- How Do I Verify the Integrity of the Agent Installation File?
- Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?
- How Do I Configure Certificate Verification in the SMS-Agent Configuration File?
- Where Can I Find the Agent Run Logs?
- Why Is My Target Server Locked During the Migration?
- How Do I Unlock a Target Server Manually?
- How Do I Resolve Error "The application cannot be started due to incorrect parallel configuration" When I Start the Agent?
- Why Does the Agent Not Start the First Time I Launch It?
- Why Does the Windows Agent Executable Not Run When I Double-Click It?
- How Do I Fix Error "INTERNAL ERROR: cannot create temporary directory!" When I Start the Agent?
- How Do I Troubleshoot Failures of Pasting the AK/SK Pair When I Start the Agent (Python 2)?
- How Do I Resolve Error "utf-8 codec can't decode byte 0xce in position0: invalid continuation byte" When I Start the Agent?
- How Do I Restart the Agent?
- How Do I Fix Agent Startup Failures Due to Insufficient Space in /tmp on a Linux Source Server?
- How Do I Fix Error "Failed to start sms agent! 'disks'" When I Start the Agent on a Linux Source Server?
- How Do I Fix Error "Failed to obtain information about disk X" When I Start the Agent on a Linux Source Server?
- How Do I Choose When the System Asks Whether to Disable the Google Services Detected on My Source Server on the Google Cloud?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore