This material is not an official position of the company and contains only a review and opinion of an employee who places his own web projects with us and his webmasters colleagues.
There comes a time when the most ordinary virtual hosting becomes insufficient for solving a certain kind of tasks. For example, it is not possible to customize and install a specific operating system, or the hosting company administrators themselves will not always allow installing the necessary script for security purposes. And somehow it is not very pleasant to sit on the “needles” due to the fact that another unfriendly virtual hosting neighbor will start sending spam and this, in consequence, can affect all projects that are hosted at this IP address. Technical support naturally blocks such “clever men” right away, but if this problem is repeated with this IP not for the first time, then it usually gets to the bases, and difficulties can begin with website promotion.
The guys and I rented several “pieces” of disk space on the hosting server for quite a long time and, until all issues were resolved, we didn’t even think about moving. To be honest, in principle, most issues can now be resolved. We often go to meet our customers and provide one-time access to install the script or offer to transfer the user to another IP address in the event of the next spammer, which may end up as a regular novice webmaster. All questions can be solved, but for this it is necessary to additionally open a ticket and make extra “gestures” that take time.
And here comes a moment when it becomes just too lazy to do this, because there are more important things. Yes, and every time to jerk administrators somehow bothers, who knows, maybe conscience wakes up, or maybe you just want “freedom”. Freedom in working with your own small, but precisely your own project, and you are restricted and you have to additionally ask about the possibility to step left or right in the ticket, and it’s still far from a fact that this will be well received by technical support. We were tired of all this with the guys and we decided to move to a small virtual server.
')
At the time of our migration, the hosting company has been providing a cloud VPS service for a year. Honestly, these virtual “machines” had both pleasant moments in history and those that I didn’t really want to remember. However, during the operation most of the shortcomings were eliminated and after a rather long period of time no problems were observed anymore.
So, I did a newsletter among several of my webmaster acquaintances who had been posting their projects with us a long time ago, and offered to take the first step towards that “freedom”, which had already been talked about for quite some time. The term of validity of our current virtual hosting packages allowed us not to hurry too much and think things through well. By the way, even at this moment, the material on the review of free hosting control panels was being prepared for publication, and in particular the work on one of them, namely the Vesta panel, made it possible to tip the balance in favor of moving to a small virtual server.
I remember with nostalgia the work on the
article about the “goddess” Vesta, and in general about the collaboration with its development team. I think this is not the last collaboration and the guys will please us more than once with interesting additions and updates to their wonderful panel. But this publication is not about that, so we will not be distracted.
They agreed to carry out the move after the people have moved away a bit from the New Year holidays, there will just be enough time to check everything and figure out some points in administration. The guys entrusted all the organizational issues to me, because I brewed all this “mess” with migration. Well, I think, let's go ...
For a start, here are some weighty arguments in numbers. Do it yourself - at 4 webmasters we rented 2
virtual hosting packages SSD BASIC, and paid for it $ 38 per year, before the price was even higher. When renting the simplest
cloud-based VPS - S in the United States for a year, the price will be about $ 48. What is the point to pay more? - you ask. And let's compare resources and, I think, a similar question will not appear again.
The first point is the disk quota. Both packages hosting SSD BASIC in the amount gave us no more than 20 GB of disk space on the server, against about 40 GB on a virtual machine. However, I want to immediately inform you that after installing the operating system (OS) on your VPS, we “rolled” CentOS 6, 31 GB of disk space left:
[root@SKRS1666 ~]
And since there is nowhere without a convenient graphical management interface, we also installed the Vesta panel, which “consumed” about 1 GB of disk space. As a result of all these simple settings, we and the guys got a guaranteed 30 GB on a solid-state drive of a virtual server:
[root@SKRS1666 ~]
The second point is traffic. If on 2 virtual hosting packages we could consume no more than 200 GB per month, then on the VPS - S the package is already provided in 4 TB (~ 4000 GB). The difference is felt, right? And if you add that each virtual “machine” should have a connection channel of 1 Gbit / s, then I think many of you will want to check it, at least. Well, let's check. Connect to the server via SSH and launch the following command in the console:
wget -O - https://raw.github.com/sivel/speedtest-cli/master/speedtest_cli.py | python
And we look at the result:
Retrieving speedtest.net configuration... Retrieving speedtest.net server list... Testing from XxxxxXxx Netherlands BV (xxx.xxx.xxx.xxx)... Selecting best server based on latency... Hosted by NFOrce Entertainment BV (Amsterdam) [0.00 km]: 3.338 ms Testing download speed........................................ Download: 942.47 Mbit/s Testing upload speed.................................................. Upload: 363.98 Mbit/s
But we want to check the virtual server and locations in the United States:
Retrieving speedtest.net configuration... Retrieving speedtest.net server list... Testing from XxxxxXxx USA (xxx.xxx.xxx.xxx)... Selecting best server based on latency... Hosted by Fast Serv Networks, LLC (Ashburn, VA) [28.16 km]: 2.708 ms Testing download speed........................................ Download: 194.86 Mbit/s Testing upload speed.................................................. Upload: 315.74 Mbit/s
To be honest, I didn’t think that there would be more than 100 Mbit / s, as when loading even such a channel into a shelf, the server can “eat” for 30 TB of traffic for a month. Do you need it? Your margin of 4 TB with a channel of 1 Gbit / s (which is provided on these virtual servers) can “fly” well, a maximum of 12 hours. And then what, sit almost the entire month without a server or spend additional funds to upgrade the traffic? Well, that's true, you need it?
Considering the rather serious bandwidth of the server connection and the very small traffic packages, I advise novice traffic generators to monitor the consumption or not to rent this type of servers at all. They are just not for this kind of task, guys. Yes, you can take a dozen of these machines and in the amount get more resources than on one dedicated server for the same amount, but certainly not in order to distribute the load between all virtual servers.
Such VPS may be of interest to those involved in
email marketing . There are a sufficient number of companies that provide services of this kind, and it is very important for such tasks to have a large number of IP addresses. It’s just that the data center does not always give the opportunity to order to one dedicated server, say, more than 10 ... 15 IP, which, moreover, also cost money. And if for the price of one IP you get not only an address, but a whole virtual server. True, it sounds tempting?
The guys and I do not deal with email distribution, because VPS was rented only for the sake of freedom of action on their “piece” of the server. We also hoped that the problems with krivorukost and love for freebies, which sometimes turned into troubles with spam, already in the distant past. But, in order to make my dreams quieter, I decided to install several additional buns on the server. Not to say that it was a good idea, but first things first.
We had little experience in dealing with spam after we started using, for the CMS of one of the projects, as it turned out, a not entirely “clean” module. Naturally the most correct advice would be - not to use questionable software. But sometimes you want to get a nice feature. But just then the nyashny feature turned into a killer feature was really no time for jokes. Therefore, I went to read the
dock and parallelly install it on the SpamAssassin virtual server along with ClamAV.
Of course, just installing this software is not enough, you need to perform additional configuration. But honestly, it’s good that I didn’t start to do it right away, but first I decided to go to the Vesta control panel in order to activate all
commercial extensions , create users, etc. I remembered that the panel has quite beautiful and informative load charts, for some reason, I wanted to look at them with at least one eye. And just here I am a little bit ofigel. The graph of consumption of RAM was as follows:
I thought it might be a glitch, because I opened the terminal and entered the
free command with the
-m key, and here is the result I got:
[root@lw1666 ~]
Hmmm ... yes, I think that's what I decided to pump over the “machine”, but I completely forgot that there is only 1 GB of RAM on board. I quickly returned to the console and stopped ClamAV using the service
clamd stop command :
[root@lw1669 ~]
SpamAssassin decided not to touch it yet, since it should not “eat” a lot of resources. I waited a bit and went to look at the RAM indicators:
More than 300 MB of free RAM and now the virtual machine has become easier to "breathe", and I somehow let go. I think the SpamAssassin stop will free up at least another 100 MB, but I would still like to sort it out and set up a small but spam protection. I also skipped the idea of ​​launching the same ClamAV on the instructions of cron and then updating the databases, scanning and automatically sending the results to each user's mailbox. After that, the next cron job would stop the process and most of the days the server would work as usual. Theoretically, all these actions can be accommodated in one hour. But, after meeting with the administrators, I decided not to do this. Yes, and loading the RAM into the regiment, even for an hour of time, can have a very detrimental effect on the availability of sites, I thought, and postponed the solution of this issue to better times.
To begin with, it was necessary to transfer projects to a new place, monitor their work, and after that, install additional buns, and, if necessary, optimize the work of the VPS. But I also wanted to do everything here and right now.
Since I didn’t grow together with additional protection, I headed to the
forum in search of a solution for data backup. While studying the information, I remembered that the Vesta control panel allows you to make backups both locally and upload them via FTP to a remote server. To do this, simply create an FTP account on some service, and then enter all the necessary data in the corresponding control panel menu. Yes, our company provides
backup service and for quite reasonable money. But honestly, the guys and I were not ready to increase the hosting budget almost 2 times because of the backup. Therefore, using the search, we found several services on the Internet where you could get FTP access for free. As an example of one of them
Turtobit . There, the free package has a limitation due to the fact that the total size of files uploaded at a time should not exceed 10 GB, but first we decided that it was enough. And in the process of working with VPS, we will look, and who knows, we can even set up backup to YandexDisk. Here everything will depend on the flight of the virtual “typewriter”.
So, having received the FTP access data, go to the Server section of the Vesta control panel. After that we press the Configure button, and going down almost to the bottom, select the BACKUP - Remote backup item, where we enter all the necessary data:
Immediately after this, I advise you to go into the BACKUP menu and create a backup with your hands to make sure that the setting was carried out correctly. Honestly, after I saw the first tar archive on the FTP server, it became so peaceful in my heart. These guys, and mine, too, are now backed up.
Most likely, many more things in the process of VPS will be added, changed or completely reinstalled. This process can be endless if projects develop and require additional changes in the settings of the server itself. Yes, with the creation of a virtual server, which would be almost ready for anything, there were some minor difficulties. But after all, this VPS is a “machine” of the wrong class, and the tasks to pump the Slavik (ZAZ-1103) right up to the Skoda Octavia Tour were not at all.
The guys and I tried to do it cheaply and angrily, and I think we did it. As a result, each of us received our “piece of freedom” on our personal virtual server. Great things start small, and great web projects start their lives on hosting for $ 1 a month. And if at the same time you completely control the flight of your own, and let a little bit of a “pumped-over machine”, then believe it will be long and successful.
PS Since there are still questions on additional protection, I would like to see in the comments all possible opinions on this issue and on setting up such small virtual servers.
PPS Do not think, we do not encourage anyone to rent a service, for example, for almost 4 dollars and share it between 4 users, we just got it, and most webmasters have enough virtual hosting without these tambourine dances)
This material is not an official position of the company and contains only a review and opinion of an employee who posts his own web projects with his webmasters colleagues.