How long does it take to create a physical server?
A Linux physical server is generally created within 30 minutes. This includes configuring hardware resources, installing the operating system, and configuring the network.
It takes about 1 to 2 hours to create a Windows-based physical server.
To quickly deploy physical servers with the same configuration in batches, you can create a physical server using a private image to reduce service deployment time.
What should I do if I can't find my physical server resources in the console?
If you cannot find your purchased physical server resources in the console, please follow these steps:
l Check the selected region: Check that the region you currently select matches the region where the physical server you purchased resides. Physical server resources are region specific and you must switch to the correct region to check the resources you purchased. Usually, the currently selected region is displayed at the top or to the left of the console page, and you can check and switch to the correct region.
l Check the selected project: If your physical server resources are purchased under a specific project, make sure that the project you currently select matches the project specified at the time of purchase.
l View permissions: Ensure that you have sufficient permissions to view physical server resources. In some cases, resources may be restricted to a specific user or a user group.
If you still cannot find your physical server resources in the preceding steps, we recommend that you create a ticket and ask the customer service to help you further diagnose and resolve the problem to ensure that you can correctly access and manage your physical server resources.
Can I transfer the physical server to another account?
You cannot directly transfer the physical server to another account.
To transfer the physical server to another account, you can follow these instructions:
1. Set the physical server to transfer as a private image: Locate the physical server to transfer in the management console and select the option to make it a private image.
2. Share a private image with another account: Once you have successfully created a private image, you can share the image with another account. By sharing an image, another account can access and use the image to create a physical server.
3. Another account uses the shared private image to create a physical server: In another account, the shared private image is used to create a physical server.
4. Unsubscribe from the original physical server: After the physical server is transferred, you can unsubscribe from the original physical server to avoid duplicate charges.
Is it normal for the name of a physical server to be suffixed with "novalocal"?
Normal.
When a physical server is created, the name of a Linux-based physical server is determined by the user-defined name injected by Cloud-init. In some cases, the name of a physical server to query may be suffixed with ".novalocal" and not be suffixed with ".novalocal" in other cases. This is because different distributions and operating systems have differences in how Cloud-init is implemented. This can lead to differences in how server names are displayed. Therefore, a server name suffixed with ".novalocal" is normal and does not affect the normal operation of physical servers.
How do I monitor physical server metrics?
You can use the Cloud Eye service to monitor the metrics of physical servers. The following shows the methods to monitor physical servers:
1. View monitoring metrics on the physical server monitoring tab: The Agent plug-in has been installed on the public images provided by eSurfing Cloud. After a physical server is created using a public image, you can quickly view the physical server metrics, including CPU usage, memory usage, disk space, and network traffic, on the physical server monitoring tab.
2. Manage monitoring metrics on the Cloud Eye dashboard: You can view monitoring metrics of physical servers in the Cloud Eye console or using APIs. You can monitor metric values in real time and receive alert notifications based on set thresholds.