Binom Documentation

К навигации

Questions and answers

  • The server choise
    • Which server would you advise?

      We can advise what most of our clients use.
      These tariffs are not must have, they only provide you with good price/performance ratio.
      The server should be selected based on the expected traffic flow:
      Up to 200k clicks per day* - VDS would be enough
      - SSD-K-2 from FastVPS (order without FastPanel panel)
      - 800₽ tariff from (geo - RF/CIS)
      - DigitalOcean - 3GB/1CPU tariff (+10$ if you register via our link)
      200-500k clicks per day*, то можно:
      - SSD-K-3 tariff from FastVPS (order without FastPanel panel)
      - DigitalOcean - 4GB/2CPUs (+10$ if you registering via our link)
      Around 500k-1kk clicks per day*, consider:
      - DEDIBOX® XC 2016 tariff (choose 250 GB SSD)
      If more than 1kk clicks per day*, then we recommend even more powerful servers:
      - (Europe)
      - Dedibox® LT 2017 tariff
      - Dedibox® MD 2017 tariff
      - Hetzner (Germany)
      - EX40-SSD tariff
      - EX41-SSD tariff
      - FastVPS
      - EX-41-SSD tariff
      - BS-64-SSD tariff
      - (USA/Canada/Asia)
      - MC-32 tariff
      - MC-64-OC tariff
      If more than 5k clicks per day*, then:
      - Hetzner (Europe)
      - PX91-SSD tariff
      - (USA/Canada/Asia)
      - MG-128-S tariff (choose 2x480GB SSD SOFT RAID)
      - (Europe)
      - Dedibox® ENT 2016 tariff (choose 3x500 GB SSD)

      It is worth considering your target geo: for Europe you want to buy a server in Europe, and for the US - in the US.
      Also, each server has a dedicated SSD space and the more space there is, the bigger amount of statistics you can store. For example, 1 million clicks take 2-3GB of space.

      Unfortunately, some hosters can’t guarantee quality of their declared characteristics, therefore we do not recommend servers from these companies:
      - - SSD are very slow
      - - performance is much lower than the competitors, many users have repeatedly faced with the drawdown of resources

      * Under this volume is considered uniform traffic. For example, 500k clicks per day - is around 300-360 clicks per minute. If you have bigger number, than look for more powerful server. Traffic peaks in tracker you can see in the Monitor tab

    • Is my server suited to?

      In total, the load calculation is made as per schedule:
      For loading less than clicks 200k per day: 1CPU, 2GB RAM
      For loading less than clicks 500k per day: 2CPU, 4GB RAM
      For loading till clicks 1 Mio per day: 4CPU, 6GB RAM
      For loading over 1 Mio: up 4CPU, up 8GB RAM

      SSD is priority.
      This schedule works for redirects only. Namely, at that traffic your server will be loaded for nearly 100% with the traffic distribution.
      If you intend to load big reports at same time - you better take higher powered server.
      Under this volume we also mean the proportional traffic. So clicks of 500k per day - it is about 5-6 clicks per second. If you get more in the traffic peaks - you need the higher powered server.

    • Where can I find a server for exact Geo? - Canada, USA, Europe, Australia, Singapore (Dedicated / VPS) - Canada, USA, England, Germany, Netherlands, India, Singapore (VPS) - Thailand (VPS) - France, Netherlands (Dedicated / VPS) - Singapore, Australia, Japan (Dedicated / VPS) - Brasil, RSA (VPS) - for small traffic volume only, because not SSD

  • Backup
    • Can I move all the tracker settings with statistics from one to another server?

      You can try it, but it almost does not depend on us, and the result depends on MySQL itself.
      That is why we do not make sure the tracker would run well after such a move.

      In order to transfer the database as correctly as possible, on a new server you need to install the same version of the tracker and with the same database name, as on the old server.

      The method described below transfers all MySQL databases at a time. Move the database to the new server and leave database on the old one will not work.

      • How to transfer

        To simplify the understanding, we implement the following notations:
        server1 - the server from which the transfer is performing;
        server2 - the server to which the transfer is performing;
        folder1 - folder on server1, which you need to create (example mkdir /root/mysql);
        folder2 - folder on server2, which you also need to create (example mkdir /var/lib/mysql_backup).
        Attention! The folders /folder1 and /folder2 must not be the real paths of your current MySQL files!

        1. 1. Install xtrabackup:
        apt-get install percona-xtrabackup-24
        If it did not work, you can check the official installation instructions, briefly:
        wget$(lsb_release -sc)_all.deb
        dpkg -i percona-release_0.1-4.$(lsb_release -sc)_all.deb
        apt-get update
        apt-get install percona-xtrabackup-24

        2. To create a backup, you need at least the same amount of space as all your MySQL databases occupy together. You will also need a place to create an archive, which you will need to transfer to another server.
        In practice, there is usually no extra space, so you can immediately backup to a remote server. To do this, install sshfs on the server from which we will transfer:
        apt-get install sshfs
        To mount a remote folder:
        sshfs username@server:/folder2 /folder1
        where username@server - is the user and IP from server2.
        (example, sshfs root@ /root/mysql)

        3. Make sure that there is no traffic going to the tracker.
        You can just stop nginx:
        service nginx stop

        4. To start the backup process, execute:
        innobackupex --no-timestamp --user=root --password=PASS /folder1
        innobackupex --no-timestamp --user=root --password=PASS --apply-log /folder1

        where PASS is the password from the MySQL root
        (example, innobackupex --no-timestamp --user=root --password=PASS /root/mysql
        innobackupex --no-timestamp --user=root --password=PASS --apply-log /root/mysql

        Depending on the database size, backup time can vary from 5 minutes to several hours.

        5. On a remote server, you need to stop MySQL and replace the database files with the backup files:
        service mysql stop
        mv /var/lib/mysql /var/lib/myslq.old
        mv /folder2 /var/lib/mysql

        (example, mv /var/lib/mysql_backup /var/lib/mysql)
        chown -R mysql:mysql /var/lib/mysql

        6. Now the root MySQL password you have on server2 is the same with one you have on server1, and it needs to be changed in the configuration file of the tracker:
        - Open configuration/system.php file in the tracker folder, by default it is /var/www/binom/configuration/system.php;
        - Find the line with $this->password=;
        - Replace the old MySQL password with a new one;
        - Save changes.

        7. Execute:
        service mysql start
        mysql_upgrade -uroot -p -f

        8. Restart MySQL and check the functionality of the tracker.
        service mysql restart

        9. Unmount the remote folder (execute on the old server):
        fusermount -u /folder2
        (example, fusermount -u /root/mysql)

Want to help us improve this documentation page? Create a pull request