Frequently Asked Questions (FAQs)

After listing details such as the version, subnet, and security policy of the OS / middleware to be installed and defining the server design contents from clients, we will build the cloud / server based on the design contents.

After the initial construction of the cloud / server construction is completed, we will give you a set of login information and setting information for the cloud / server.

> Cloud/Server system designing.

> Subnets, security group design.

> Virtual hosts configurations.

> Server parameter configurations.

> Server machine or instance setup.

> Login user accounts and credential configurations.

> Backup configuration and policy creation.

> OS/Middleware/Module installations and configurations.

> IP Restrictions and security control.

> Monitoring configurations.

> Cost and payment setup, configurations.

Our work operated by engineers 24 hours a day, 365 days a year to provide system run, maintenance, monitoring, and technical support. In the event of sudden irregularities, we can quickly troubleshoot them.

In addition, we can analyze the daily operation status and trends of your cloud/server and advise you on possible future problems which will help you avoid operational problems and improve your system stableness.

If you have any requests for operation, maintenance, or monitoring items not listed above, please contact us. The minimum usage period for this service is three months.

Unlimited support for cloud/server operations, maintenance, and monitoring. We provide support via email, phone, and chat 24 hours a day, 365 days a year.

Yes, we are good at designing, building, operating, and maintaining servers and clouds for web services and large-scale systems, so we can design, build, operate, and maintain servers for dozens or hundreds of servers.

Of course, we can also provide services for the smallest number of servers, even if it is just one server.

Cloud Server

■Security

• The hardware infrastructure (server/network) is redundant as a standard feature and this will make very few service interruptions due to hardware failure.

■Operational aspects

• You can immediately build, add, or upgrade the number of servers without choosing the location of the servers.

• Server scale-out can be adjusted for high-load access.

■Cost

• The majority of clouds charge for the amount of data transferred on a pay-as-you-go basis, so monthly costs will fluctuate.

• The monthly service fee fluctuates depending on the monthly exchange rate of AWS, GCP, Azure, Alibaba Cloud and etc.

■Advantages

• Easy to add resources.

• Even if the server configuration is minimal at the time of cloud deployment, the specifications can be increased after the service is launched.

■Disadvantages

• Since the hardware infrastructure and configuration is a black box, it is difficult to determine the cause and evaluate the performance in the event of a failure caused by the hardware.

• Since the amount of data transfer is charged on a pay-as-you-go basis, there is a possibility that the cost of monthly service fees will increase.

※Overall evaluation※

• For services such as social games, e-commerce sites, and digital contents, where the load on the server changes rapidly, the cloud is suitable because it can respond quickly to adding resources and scaling out.

• In terms of cloud reliability, most cloud services are regularly audited by an internationally recognized auditing organization every year to provide assurance on security, privacy, and compliance controls.

Physical Server

■Security

• The location of the server is clear because the location where the data is stored is in the physical environment.

■Operational aspects

• The hardware resources such as servers, firewalls, and load balancers can be occupied by a single company.The system can be easily customized to meet your company's requirements.

■Cost

• The initial installation cost is high, but the monthly cost is fixed in many cases so the monthly cost management is stable.

• However, there are indirect and invisible costs such as infrastructure maintenance man-hours, data center rack costs, electricity costs, and hardware manufacturer maintenance updates.

■Advantages

• No influence from other users' systems, since the system is occupied by one company.

• The performance of machines and resources, such as CPU and memory, is clear.

■Disadvantages

• Risk of server shutdown due to physical hardware failure.

• Difficult to upgrade hardware resource specifications.

• It takes time for system sizing and estimation when initially installing hardware.

※Overall evaluation※

• The hardware resources can be used to the maximum extent. When developing mission-critical systems that are not connected to the external Internet physical servers are more stable and maintain higher performance than cloud computing.

• In addition, some studies have shown that the performance results of physical servers are three times higher than those of cloud computing.

BEYOND does not provide support for on-premise server construction and operation, nor does it provide on-site support.

Web services such as social games, e-commerce sites, and digital contents that require speed and flexibility and are directly linked to sales, or companies that want to concentrate on content development and management. If your company does not have a server administrator, this may be the right choice for you.

In addition, many companies with such issues tend to outsource to vendors that specialize in cloud/server construction, operation and maintenance, such as Beyond.

We use and manage our own Zabbix - an enterprise monitoring software - instance. It is used as standard for operation, maintenance and monitoring of the cloud/server, so there is no need to build a separate server for Zabbix. Datadog can also be used according to customer requirements.

Yes, we can migrate your server data from on-premise, physical server or legacy system environment to cloud environment. However, server data migration requires a separate server data migration fee.

• In the case of taking over a cloud/server that has already been built or a system that is already in operation

We can provide operation, maintenance, and monitoring services within 5 to 7 business days after the service is ordered.

• When designing and building a new cloud/server

Operation, maintenance, and monitoring will be available in 10 to 15 business days after the service is ordered.

In each of these cases, we will provide you with the server parameter sheet (configuration information) after the server monitoring configuration is completed.

The above delivery time is a guide. Depending on the system configuration and situation, the schedule and delivery date may vary. Please contact us for the detailed schedule and delivery date.

Yes, we provide technical advice on parameter tuning as well as design, construction, and support using OSS, such as LAMP environment.

Yes, if a highly urgent vulnerability is found, we will perform a security update after coordinating the schedule with the customer.

※This will be done by using package management tools such as yum.

We can provide the best cloud/server environment for your needs, regardless of whether it is a foreign or domestic cloud/server.

We can also provide multi-cloud configuration and operation.

For more details, please click below.

Full List

Yes, if we have an environment where we can connect remotely via SSH or RDP port, we can operate and maintain and monitor.

However, please note that the items for operation and maintenance / monitoring may be limited depending on the specifications of the current system environment.

Yes, it is possible to carry out operations and maintenance / monitoring work by taking over the customer's own infrastructure environment such as a running cloud system or VPS / hosting server from the customer as it is.

In that case, install and set up the monitoring tool (Zabbix) specified by our company, investigate the current infrastructure setting status, and if there is a setting content that seems to be a problem, set the parameter to improve the infrastructure operation. Perform resetting and tuning.

We are sorry that Beyond does not carry out on-site work by constructing and rushing on-premises environment within the customer's company. Our main business is construction, operation, maintenance, monitoring, and migration of remote cloud server environments.

Yes, since we are in the operation and maintenance and monitoring of the cloud / server for 24 hours a day, 365 days a year, telephone technical support is available early morning and late night. Of course, we also provide technical support by email and chat.

Yes, we will provide hearing and advice on customer service / application specifications, security requirements, budget feelings, etc., and define requirements for prerequisites for infrastructure.

However, please note that we do not meet with requirement definitions and create requirement definition documents, which involve frequent visits.

Yes, we have various domains and SSL certificates. Of course, we also accept work and renewal of SSL certificate installation on cloud / server.

Yes, Beyond uses Apache JMeter to create and execute a test plan scenario file (jmx file) by the customer or Beyond, and will work and support load testing assuming the load of the production environment.

1. Definition of assumed load and performance targets

2. Load test design (throughput target, etc.)

3. Create scenario for load test

4. Load test environment construction

5. Perform load test

6. Review and investigation of load test

7. Creation of load test result data

- If the target is not reached, repeat the following process until the target is achieved.

1. Check and correct load test design

2. Check and correct program implementation, server settings and database design.

3. Retest

* This service requires a separate load test work fee. Please ask for details.

When migrating from the current server to the cloud, select a new cloud / server to install, identify bottlenecks and risks during data migration, and synchronize the database and content data, system downtime, DNS switching Finalize the work process and schedule until the work and operation confirmation.

- Beyond work

1. Hearing and definition

2. Investigation of current server environment * Connection information to the current server is required.

3. Adjust schedule for data migration

4. Design and construction of new server environment for data migration (machine setup, OS / middleware installation, etc.)

5. First data migration from current server to new server (full data import)

6. First operation check of service system

7. Data migration from the current server to the new server 2nd time (differential data import) * Maintenance of site suspension is required.

8. Service system operation check 2nd time

9. DNS server record switching / direction change * or implemented by customer.

10. Create a new server parameter sheet

- Customer work

1. Adjust data transfer schedule

2. Apply for a new server

3. Program modification and version upgrade work of the current service / system

*Please respond if necessary.

4. Create a maintenance page * Since the site will be stopped, please prepare as necessary.

5. DNS server record switching / direction change * or Beyond.

6. Service system operation check

7. Removal and cancellation of the current server

===

* The above server migration / migration work process is an example. The method of server migration changes depending on the customer's system environment, so we will respond according to the customer's request.

* This service requires a separate server data migration work fee.

* Please ask for details.

Yes, we can design, build, and provide technical support for CI/CD and DevOPS pipelines using tools such as Jenkins, CircleCI, Ansible, and Terraform.

Unfortunately, we do not build on-premise (physical) servers. We accept cloud computing, VPS, hosting, and other server environments that allow remote operation.