What is a Virtual IP (VIP)?
When you create a virtual IP (VIP) address with Liquid Web you will receive both a Public VIP and Private VIP. The public VIP can be configured on a Storm server just as a non-virtual, or standard, IP would be configured. Connecting to a public service, such as HTTP or FTP, on the Public VIP occurs just as it would on a standard IP.
The Private VIP can be configured on a Storm server’s private interface just as a standard private IP would be configured. Connecting to a private service, such as MySQL or Puppet, on the Private VIP also occurs just as it would on a standard private IP.
So why use a VIP? When utilizing multiple servers, having a VIP is beneficial due to its ability to “float” between servers. This allows the VIP to remain highly reachable in circumstances in which a non-virtual (or standard) IP may be otherwise unreachable. It is possible to move both the Public VIP and Private VIP between Storm servers!
Both Public and Private VIPs can be configured on any server on your Storm account so long is that server is in the Zone where the VIPs were created. Typically software, such as the ones listed below, is used to manage on which server a VIP resides.
Use Cases for VIPs
Here are some of the things that you can do with Virtual IP addresses:
- High Availability Databases (MySQL, Percona, MariaDB)
- Non-DNS-based Service Migrations
- High Availability Web Applications (in tandem with or in place of load balancer)
Examples of Software That Can Use VIPs
This is just some of the software that you can use with Virtual IP addresses:
Trying a new server is a breeze, and it’ll be up and running in only a few minutes...
Storm Object Storage delivers a durable, secure, highly available solution for storage needs of virtually any size. With object storage access occurs via API calls to the object storage cluster, which replaces the need to rely on additional servers for dedicated storage.
Here we use the client Cyberduck to interact with Storm Object Storage. Cyberduck is available for download from https://cyberduck.io/?l=en.
- These instructions are intended specifically for configuring Cyberduck for use with Storm Object Storage.
- I’ll be working from a Microsoft Windows 8 desktop with Cyberduck installed.
Continue reading “How to Configure Cyberduck for Use with Storm Object Storage”
- These instructions are intended specifically for resizing a Liquid Web Storm (Cloud) server.
- I’ll be resizing a 2GB Storm VPS instance to an Storm Dedicated server.
Continue reading “How to Resize a Liquid Web Storm (Cloud) Server”
Take a Backup, or Be Sure Backups are Running
We have tutorials on How to Create a Storm Server Backup, and How to Restore a Storm Server Backup.
Check Running Processes
Liquid Web’s Heroic Support team closely monitors the load on your servers with Sonar® proactive monitoring and service restoration. That said, it’s always wise to glance at what processes are running on your server to assure your services are running as expected. Check-out our tutorial on Monitoring Server Processes with Top for Linux.
Verify Services Will Start at Boot
Be sure to verify that all of your necessary services are configured to start when the server boots up. For CentOS users, you can follow this tutorial: chkconfig Command Examples for Red Hat and CentOS.
Save, Save, and Save Some More
Always check whether or not there are any unsaved changes to configuration files, etc. prior to a reboot. Save early and safe often!
Continue reading “Proactive Server Maintenance Checklist, Prior to Reboot”
In order for our Heroic Support® staff to SSH into your server to address issues we’ll need your login details. If we do not have the your login details on file then our monitoring team will not be able to proactively fix any server problems that may arise. Additionally, if you open a ticket to address a specific issue, then the lack of accurate login details may cause a delay in support.
We store the relevant login information in a secure manner, only accessible to our Heroic Support® technicians.
To update and register your login information follow the instructions below once you are logged into the Manage interface at http://manage.liquidweb.com.
Continue reading “Updating Your Root User and SSH Information in Manage”
Before you can host a website on a domain, that domain has to be registered with the proper authorities. Domain registration through Liquid Web is a one-click process in our manage interface, but it may not be immediately obvious just where to do so. Here’s how:
Continue reading “How To: Register a Domain through Manage”
Now that you have an image of a storm server, you can create new servers from that image. Here’s how to do just that:
Continue reading “Restoring a Storm Server from an Image”
While Liquid Web Linux servers always have either APF or CSF firewalls installed, Storm servers can also have an external firewall put in front of them, at no additional charge. A Storm firewall provides an extra layer of protection on an already secure server. Here’s how to set one up:
Continue reading “How To: Configure a Storm Firewall”
Liquid Web’s Account Management System has a robust API that allows for accessing your account from outside of the Manage interface, such as with the Storm WHMCS plugin. In order to access the API, an API user must be created for that account first. Creating an API user is an easy and straightforward process.
Continue reading “Creating an API User in Manage”
Have you ever wanted to check up on the details of your server’s bandwidth usage? Liquid Web’s manage interface provides graphs that give you such information. Here’s how to read them.
Continue reading “Reading Bandwidth Graphs In Manage”