metered VPS

metered VPS

 

 

For several years, Secure Online Desktop offers Cloud servers and cloud services not only on hardware resources physically located in Italy, but also through customized custom projects abroad.

We are pleased to announce that thanks to an update of our web interface, it is now possible for a customer / partner to independently select the Datacenter according to the desired location by selecting from a list of 62 Datacenter in 25 countries around the world.

The Cloud Server that can be deployed across all of our Datacenter is the so-called VPS metered, ie Virtual Private Server whose cost is measured based on the time consuming of hardware resources, unlike classic VPS or SuperCloud, you can actually create a server for a few hours or for a few days, paying only for the time of use. In this sense, VPS metered are much cheaper than the so-called flat servers whose cost is constant and therefore does not vary within the billing period.

For those who fit the VPS metered?

Metered VPS are ideal under the following conditions:

   ♦ Limited use

      For demo, development and testing servers in periods of less than one month.

   ♦ The need for hardware resources outside of Italy

      For projects where you need to deploy resumes in different locations, for example: Multi-site projects, multi-pop, disaster recovery, offsite backup, etc.

   ♦ Better performance

      VPS metered can be created in one or more of the following Datacenter, for each Datacenter there is a score showing its relative performance, relative to the others. The score is between 1 and 100, the higher the score will be the performance of that Datacenter.

 

metered VPS Pro Tier and Dev Tier

There are currently two plans for metered VPS (soon the Enterprise plan will also be released), let’s see the difference macros together:

   ♦ Pro Tier

      It is necessary to select this type of Datacenter for server in production where it is necessary to ensure an adequate level of reliability and performance. This level ensures all the parameters required for a 100% uptime such as the presence of professional UPSs, high reliability resources, enterprise-wide components, etc.

   ♦ Dev Tier

      This level, much cheaper, is suitable for test or demo servers that are not in a production environment where high reliability is not required.

 

For those who are not fit for VPS metered?

Metered VPS are NOT ideal under the following conditions:

   ♦ Need to have flat costs

      By its very nature, the consumption and the relative costs of the metered servers vary according to use so they are not really ideal where it is absolutely necessary to have fixed costs.

   ♦ Need to have Italian resources

    The metered servers are deployed on 62 worldwide Datacenters, if a customer needs (for policy, internal regulations, etc) to have only hardware resources on Italian national territory then he should not choose this type of server unless the two Italians Datacenter in the list.

   ♦ Need to have IPv6 addresses

      IPv6 addresses are not yet supported by this type of server.

   ♦ Need to have internal network

      Internal networks (private LAN, VLANs, secondary LANs) are not yet supported by this type of server.

   ♦ Need to have the Cloud customization

      Customizations are not yet supported by this type of server.

 

In all the above cases, you need to navigate to Cloud Servers or SuperClouds.

 

USEFUL LINKS:

METERED VPS

 

Contact us

 

vps

vps

A virtual server (Cloud server) or VPS (Virtual Private Server) is a full-fledged server with its own operating system and well-defined hardware features only that unlike a classic server it shares physical resources with other virtual machines in this way multiple VPS can run simultaneously on the same server (hypervisor).

This virtualization technique allows significant cost savings and an optimization of hardware resources as it is possible to run multiple operating systems on the same hardware.

VPS – Advantages / Disadvantages

Advantages:

 

   ♦ Migration: It is possible to “move” (migrate) a VPS from one server (hypervisor) to another (even without interruption of service).

Example: You have created a server  on a hypervisor in Italy and you want to move it to a server in America. With a VPS, as long as the Cloud Provider has another Datacenter in America, this can be done quickly.

   ♦ Scalability: It is the possibility of increasing or decreasing the hardware resources (CPU, RAM, Disk, etc) without rebuilding the VPS and in some cases without restarting it in full transparency to users who use the services provided.
Example: A VPS of 2 cores, 1 GB of RAM and 20 GB of disk has been created but after a few months we realize that the RAM memory is insufficient for the services provided and it is necessary to increase it. With a VPS it is very easy to solve this problem, just increase the RAM from the configuration panel and the new configuration will be applied (in the case of linux systems without the need to reboot).

   ♦ Autoscaling: It is the possibility to increase or decrease the resources (scaling) automatically according to well defined hardware policies. This technique is extremely valid in cases of load peaks.
Example: A VPS has been created with 2 cores, 1 GB of RAM and 20 GB but in some periods of the year due to the high user access these resources are not sufficient, then in this case it is possible to configure these policies:

a) If the CPU is at 90% for more than 1h then the CPU of a core increases every 30min for a maximum of 6 cores and then if the CPU is less than 10% for more than 1h decrease the CPU of a core every 30 min up to a minimum of 2 cores.

b) If the RAM is 99% for more than 1h then increase the RAM of 1Gb every 30min for a maximum of 32Gb and then if the RAM is less than 50% for more than 1h decrease the RAM of a core every 30 min until at a minimum of 1Gb.

   ♦ Low cost: by comparing the cost of a VPS to that of a fiscal server like hardware resources, the cost of a VPS is much lower, especially considering that some cost items are already included in the VPS fee. :
a) Energy consumption;

b) Internet band;

c) Cost of public IP addresses;

d) Costs related to housing (cooling, surveillance, etc);

e) Firewall;

f) Technical assistance.

Disavantages:

   ♦ Shared resources: Depending on the configurations and characteristics of the Cloud Provider, some hardware resources, such as the CPU, could be shared so performance may be lower than a physical server. This condition is not always true as it is possible to request a 100% allocation on all hardware resources to your Cloud Provider.

Limits:

 

   ♦ OS Virtualization: Not all operating systems and platforms can be virtualized (Eg AS400, Apple OS).
   ♦ Band: Although this is not an inherent problem of virtualization itself there could be latency differences in the Internet connection between a physical server in the company and a VPS if users are predominantly within the company and if the company has not an adequate Internet line.
Example: A physical server in the customer’s DMZ is accessed by its LAN users via a 10Gb line, if the server is virtualized and becomes a VPS at a Cloud provider, access to it is transmitted via the client’s Internet line which may be more slow.

 

False myths:

   ♦ A VPS does not have the same performance as a physical server: By allocating 100% of the physical resources and correctly dimensioning a VPS the latter has nothing to envy to a physical server from a performance point of view.
   ♦ A VPS is less secure than a physical server: A VPS can have the same degree of security as a physical server because it is possible to adopt the same security measures (Firewall, Antivirus, Hardening, VPN) applicable to a Fiscal server.

Contact us

 

Useful links:

IaaS | Cloud | Infrastructure as a Service

Alternative to the NAS

Demo Cloud Servers

Free Microsoft Windows licenses

New templates for Cloud Server

Docs

server cloud

server cloud

A cloud server or VPS (Virtual Private Server) is a fully-fledged server with its own operating system and well-defined hardware features only that unlike a classic server it shares physical resources with other virtual machines in this way more VPS can be run simultaneously on the same server (hypervisor).

This virtualization technique allows significant cost savings and an optimization of hardware resources as it is possible to run multiple operating systems on the same hardware.

 

Server Cloud – Pros cons

Pros:

 

   ♦ Migration: It is possible to “move” (migrate) a VPS from one server (hypervisor) to another (even without interruption of service).

Example: You have created a VPS on a hypervisor in Italy and you want to move it to a server in America. With a VPS, as long as the Cloud Provider has another Datacenter in America, this can be done quickly.

   ♦ Scalability: It is the possibility of increasing or decreasing the hardware resources (CPU, RAM, Disk, etc) without rebuilding the VPS and in some cases without restarting it in full transparency to users who use the services provided.
Example: A VPS of 2 cores, 1 GB of RAM and 20 GB of disk has been created but after a few months we realize that the RAM memory is insufficient for the services provided and it is necessary to increase it. With a VPS it is very easy to solve this problem, just increase the RAM from the configuration panel and the new configuration will be applied (in the case of linux systems without the need to reboot).

   ♦ Autoscaling: It is the possibility to increase or decrease the resources (scaling) automatically according to well defined hardware policies. This technique is extremely valid in cases of load peaks.
Example: A VPS has been created with 2 cores, 1 GB of RAM and 20 GB but in some periods of the year due to the high user access these resources are not sufficient, then in this case it is possible to configure these policies:

a) If the CPU is at 90% for more than 1h then the CPU of a core increases every 30min for a maximum of 6 cores and then if the CPU is less than 10% for more than 1h decrease the CPU of a core every 30 min up to a minimum of 2 cores.

b) If the RAM is 99% for more than 1h then increase the RAM of 1Gb every 30min for a maximum of 32Gb and then if the RAM is less than 50% for more than 1h decrease the RAM of a core every 30 min until at a minimum of 1Gb.

   ♦ Low cost: by comparing the cost of a VPS to that of a fiscal server like hardware resources, the cost of a VPS is much lower, especially considering that some cost items are already included in the VPS fee. :
   a) Energy consumption;  

   b) Internet band;

   c) Cost of public IP addresses;

   d) Costs related to housing (cooling, surveillance, etc); 

   e) Firewall;

   f) Technical assistance.

Cons:

   ♦ Shared resources: Depending on the configurations and characteristics of the Cloud Provider, some hardware resources, such as the CPU, could be shared so performance may be lower than a physical server. This condition is not always true as it is possible to request a 100% allocation on all hardware resources to your Cloud Provider.

Server Cloud – Limits:

  1. ♦ OS Virtualization: Not all operating systems and platforms can be virtualized (Eg AS400, Apple OS).
  2. ♦ Band: Although this is not an inherent problem of virtualization itself there could be latency differences in the Internet connection between a physical server in the company and a VPS if users are predominantly within the company and if the company has not an adequate Internet line.
    Example: A physical server in the customer’s DMZ is accessed by its LAN users via a 10Gb line, if the server is virtualized and becomes a VPS at a Cloud provider, access to it is transmitted via the client’s Internet line which may be more slow.

Server Cloud – False myths:

  1. ♦ A VPS does not have the same performance as a physical server: By allocating 100% of the physical resources and correctly dimensioning a VPS the latter has nothing to envy to a physical server from a performance point of view.
  2. ♦ A VPS is less secure than a physical server: A VPS can have the same degree of security as a physical server because it is possible to adopt the same security measures (Firewall, Antivirus, Hardening, VPN) applicable to a Fiscal server.

Check out the Cloud Server

Contact us

Useful links:

IaaS | Cloud | Infrastructure as a Service

Let’s Encrypt Free Certificates for all Webhosting users

Alternative to the NAS

CloudFlare free Plesk extension for Webhosting users

Demo Cloud Servers

Free Microsoft Windows licenses

New templates for VPS

VPS

Docs

How to have your computer network under control

VPS Metered – Cloud location

ownCloud

Home

virtual server

A virtual server or virtual private server (VPS) is a fully-fledged server with its own operating system and well-defined hardware features only that unlike a classic server it shares physical resources with other virtual machines in this way more VPS can be run simultaneously on the same server (hypervisor).

This virtualization technique allows significant cost savings and an optimization of hardware resources as it is possible to run multiple operating systems on the same hardware.

 

Virtual server – Pros/Cons

Pros:

   ♦ Migration: It is possible to “move” (migrate) a VPS from one server (hypervisor) to another (even without interruption of service).

Example: You have created a VPS on a hypervisor in Italy and you want to move it to a server in America. With a VPS, as long as the Cloud Provider has another Datacenter in America, this can be done quickly.

   ♦ Scalability: It is the possibility of increasing or decreasing the hardware resources (CPU, RAM, Disk, etc) without rebuilding the VPS and in some cases without restarting it in full transparency to users who use the services provided.
Example: A VPS of 2 cores, 1 GB of RAM and 20 GB of disk has been created but after a few months we realize that the RAM memory is insufficient for the services provided and it is necessary to increase it. With a VPS it is very easy to solve this problem, just increase the RAM from the configuration panel and the new configuration will be applied (in the case of linux systems without the need to reboot).

   ♦ Autoscaling: It is the possibility to increase or decrease the resources (scaling) automatically according to well defined hardware policies. This technique is extremely valid in cases of load peaks.
Example: A VPS has been created with 2 cores, 1 GB of RAM and 20 GB but in some periods of the year due to the high user access these resources are not sufficient, then in this case it is possible to configure these policies:

a) If the CPU is at 90% for more than 1h then the CPU of a core increases every 30min for a maximum of 6 cores and then if the CPU is less than 10% for more than 1h decrease the CPU of a core every 30 min up to a minimum of 2 cores.

b) If the RAM is 99% for more than 1h then increase the RAM of 1Gb every 30min for a maximum of 32Gb and then if the RAM is less than 50% for more than 1h decrease the RAM of a core every 30 min until at a minimum of 1Gb.

   ♦ Low cost: by comparing the cost of a VPS to that of a fiscal server like hardware resources, the cost of a VPS is much lower, especially considering that some cost items are already included in the VPS fee. :
   a) Energy consumption;  

   b) Internet band;

   c) Cost of public IP addresses;

   d) Costs related to housing (cooling, surveillance, etc); 

   e) Firewall;

   f) Technical assistance.

Cons:

   ♦ Shared resources: Depending on the configurations and characteristics of the Cloud Provider, some hardware resources, such as the CPU, could be shared so performance may be lower than a physical server. This condition is not always true as it is possible to request a 100% allocation on all hardware resources to your Cloud Provider.

Virtual server – Limits:

  1. ♦ OS Virtualization: Not all operating systems and platforms can be virtualized (Eg AS400, Apple OS).
  2. ♦ Band: Although this is not an inherent problem of virtualization itself there could be latency differences in the Internet connection between a physical server in the company and a VPS if users are predominantly within the company and if the company has not an adequate Internet line.
    Example: A physical server in the customer’s DMZ is accessed by its LAN users via a 10Gb line, if the server is virtualized and becomes a VPS at a Cloud provider, access to it is transmitted via the client’s Internet line which may be more slow.

Virtual server – False myths

    1. ♦ A VPS does not have the same performance as a physical server: By allocating 100% of the physical resources and correctly dimensioning a VPS the latter has nothing to envy to a physical server from a performance point of view.
    2. ♦ A VPS is less secure than a physical server: A VPS can have the same degree of security as a physical server because it is possible to adopt the same security measures (Firewall, Antivirus, Hardening, VPN) applicable to a Fiscal server.

    Check out the Cloud Server

 

Contact us

Useful links:

VPS Metered – Cloud location

IaaS | Cloud | Infrastructure as a Service

Demo Cloud Servers

Server Cloud

VPS

Alternative to the NAS

New templates for VPS

Free Microsoft Windows licenses

Let’s Encrypt Free Certificates for all Webhosting users

CloudFlare free Plesk extension for Webhosting users

autoscaling

Autoscaling

https://cloud.secure-od.com/cart/iaas-public-cloud—load-balancer/&step=0

7 GOOD REASONS TO CHOOSE THE AUTOSCALING OPTION

 

1. The hard disk or one of the server’s hard disks is full

   ◊ WITHOUT Autoscaling: Services crash and users of applications running on the disk receive a disservice image of the company and risk users do not return.
   ◊ WITH Autoscaling: The disks are resized according to the new disk occupation.

2. The processor (CPU) goes into saturation (100% use)

   ◊ WITHOUT Autoscaling: Web applications respond slowly or time-outfollowing degradation and / or disservice to the user.
   ◊ WITH Autoscaling: The system adds the necessary CPUs.

3. The RAM memory goes into saturation (occupied 2Gb on 2Gb, occupied 6Gb on 6Gb …)

   ◊ WITHOUT: Web applications respond slowly or time-outfollowing degradation and / or disservice to the user. *
   ◊ WITH: The system adds RAM memory.

4. Increased network traffic (client delivers 100Mbps on a 100Mb network card)

   ◊ WITHOUT: What is called the “bottleneck” takes place, ie the system is not able to serve new users.
   ◊ CON: The system resizes the bandwidth.

5. Server oversizing

   ◊ WITHOUT: the user buys a client that is oversized compared to his needs as a result pays for features he does not use.
   ◊ CON: The system reduces resources in order to adapt to the real needs of the user, considerably reducing costs.

6. Installation times

   ◊ WITHOUT: In the face of a change, the user must re-install the entire platform on a larger system.
   ◊ CON: It is not necessary to re-install the software or the platform because the system resizes itself automatically.

7. Autoscaling vs scaling

Autoscaling does everything that a scaling system does, that is, it allows the user to vary them

hardware features, but it does this automatically, reducing management costs and increasing end-user satisfaction.

* In technical terms it is said that the operating system swapped.
Swapping means saving to the hard disk all the information that the system can not save in RAM because it is full, consequently the system slows down considerably because the access times to the disk are much higher than the available memory.

Contact us

Useful links:

Cloud servers

Super Cloud

VPS Metered

Customers

Newsletter