Temporary up- or downgrade your hypernode plan

in Usage

It is possible to temporary up- or downgrade your hypernode. This way you can alway be ahead of a traffic increase by upgrading to a bigger plan with more resources.

Up- and downgrades

Temporary upgrading your hypernode is fairly easy: Just log-in on our Service Panel and select Administratief -> Pakketbeheer -> Pakkettype.

From there choose the new specs you prefer in the comparison table and select the check mark at the bottom of the page to agree and start the up- or downgrade with Pakket aanpassen.

Pay per day

Need a bigger hypernode for a few days? Upgrade and downgrade to your original plan as soon as the bigger node is no longer needed.

If you upgrade your hypernode to a bigger plan for a single day, only 1 day will be billed. This way you can upgrade for an event, mailing or sales action without being bound to a monthly plan for the rest of the month.

Just upgrade your node, run your event or sales action and the next day you downgrade it again, and you will be billed accordingly.

If you upgrade your node and change it back within 2 hours, no additional cost involved in the up and or downgrade.
This way if you up or downgraded by mistake your hypernode, you can always undo your action.

If you want to do a quick test or ensure yourself the bigger node is big enough for your expected traffic increase, this can be done during the 2 hour reflection time.

Change of IP Address

Because we first create a second node and then remove the old one, every down- and upgrade will cause a change of IP for your hypernode.
Right before the migration is finished, we email the technical contact the new IP address.

Make sure to keep a list of payment providers, firewalls local dns servers and other services that depend on the IP address of the hypernode, so you can quickly change the ip in case of an up- or downgrade.

How an up- or downgrade is managed

Up- and downgrades are a fully automated process. When you order an up- or downgrade, a new server is started at the cloud provider and then configured.

When the node is configured the databases and file content on your current hypernode will be copied to the new server.

To finish the migration we test if everything is working. If this is the case, we change the appname.hypernode.io DNS records (And the ones for your domain if you linked it to your hypernode) and decommission the old node.

This way the downtime is as small as possible, depending on the TTL of your DNS.

Downtime during upgrades

If you have a very large database or a highly utilized hypernode, upgrades can cause some errors due to deadlock errors on your database or long running php processes reaching timeout values.

Make sure you don’t schedule up- or downgrades during peak hours and always check Magereport Premium or the command line to ensure yourself no product exports and long running crons are currently active.

Ensure yourself no mailings, TV commercials, social media advertisement and other traffic generating events are started. Always upgrade in advance!

SSH Access during up- and downgrades

During the up- or downgrade we disable SSH and FTP access to avoid new file changes that are not copied to the new server.
Make sure not to add product changes, upload images, or change settings in the magento admin backend while a migration is executed.