ASTRAPI

Hello 🙂
(This is a community guide on how to setup Backblaze and Cloudflare, as a significantly cheaper replacement for Amazon S3 and Cloudfront.  The author has no affiliate arrangement with any of the companies listed in the guide and offers the guide as a free community resource.  You should consult with your hosting provider and / or server administrator before proceeding with the guide.)
The tutorial is tested with the latest version of Invision 4.5.4 !

Invision Community allows a file storage configuration with Amazon S3 and a content distribution network (CDN) of your choice:
 
WHAT IS BACKBLAZE?
 

 
Backblaze is an infinitely Scalable B2 Cloud Storage. Backblaze B2 is enterprise-grade, S3 compatible storage that companies around the world use to store and serve data. Backblaze's service works with native APIs, CLI, and GUI; you can move and manage data with minimal coding. Their service provides fast access all the time; there is no need to accept delays or pay speed surcharges. It can also support HIPAA compliant storage with their Business Associates Agreement (BAA). B2 is compatible at ¼ the cost of AWS S3 with no hidden fees or minimums.
 
Backblaze is an award winning cloud storage provider for 2020 !
 

 
Pricing:
 

Based on their latest pricing, it is very cheap at around 5$ per 1TB storage per month! There is a cost for direct downloads (bandwidth) at 0.01$ per GB but it will not affect us as we will use Cloudflare and all files will be served from Backblaze to Cloudflare and then to users that is totally free 🙂
Be careful if you have any custom direct downloads that bypass Cloudflare. If you link to custom downloads directly, you will be charged for bandwidth. All default Invision files should go through Cloudflare. I am using Backblaze for a few of my clients and they never charged anything extra as all Invision files are going through Cloudflare as expected. Please monitor your balance after a few days just to be sure!
 
GUIDE:
BEFORE PROCEEDING, PLEASE BACKUP YOUR DATA FIRST!
 
STEP 1: Create a bucket on Backblaze
First we need to sign up at Backblaze Cloud: https://www.backblaze.com/b2/sign-up.html
You will need a phone number to activate your account:

After the activation of the account we will need to create a bucket that will host our files.
 
On the Buckets sections we click on Create a Bucket:

 
Then we add a name for our bucket. Recommendation: avoid dots (.) in the bucket name.
 
On the next screen we type a Bucket name and we select Public and then we click at Create a Bucket.

 
 
After that under the Create a Bucket we should have our Bucket.
 
Now we must keep a note of the ENDPOINT:

 
 
Now we need to get our Bucket access keys from the App Keys menu. At the bottom we click at Add a New Application Key:

 
 
At the new screen we select a anything as a key name and we keep selected the Read and Write access and wee click at Create New Key:

 
 
Then you will see there only once the KeyID and the Application Key that we must keep a note of them as we will need them later !

 
As a last step we need to go to our bucket that we just created and upload an image. From the menu on the left we click on Browse Files and then we click on our bucket:

 
Then we click on upload and we upload a simple file like an image...

 
On the right side of the uploaded image we have to click at the info icon:

 
At the pop up screen we need to keep a note for that part so copy it with the other notes that wee have already:

 
That's it ! We created our bucket and we got the access info that we will need !
 
STEP 2: Create a CNAME dns record at Cloudflare
 
Now you have to login to Cloudflare and go to your DNS tab from the top menu and then click Add record:
 

 
We use as Type the Cname and as Name the cdn and as Target the info that we got from the pop on the previous step in the tutorial above:

 
After saving that DNS record we should have that:

 
Now for security reasons we have to go to the page Rules on the top menu and create two rules:

RULE 1:
Just replace your domain and the bucket name that you create:

 
RULE 2:
Just replace your domain:

 
The final result should be like this:

 
Keep in mind the order of the rules as if you set the second rule as 1 it will not work and your forum images will not work as page rules uses priority. This is important!
That's it for the Cloudflare part!
 
STEP 3: Configure Invision to use the Backblaze Cloud
From Invision Admin Control Panel, go to System -> Files -> Storage Settings

 
Then we click on Configurations:

 
and then on Create New on the right side.
Then we select Amazon S3 and we fill the needed info as:

 
When you click Save if you get any warnings or errors then you have to check again the tutorial as you may forgot something or may have a typo somewhere...
If you save it without any issues then you are ready to use it by going to: System -> Files -> Storage Settings
and select a category with not many images for example Icons & Logos or anything else with a few images and from the drop down options the: Amazon S3:superbucket
 

 
Then wait for the automated task to transfer your files to the Cloud and check if all are ok !
If yes then you can proceed with the rest categories.
 
*Keep only at your server your theme resources:

 
Keep in mind that if you have a lot of GB of files it may take a long time for the transfer !
 
It may help to go to the Dashboard and run manually the process to get the files transferred faster.

*Attachments and Downloads may not work out of the box (don't use them on my test forum and i don't know for sure) and you may need to use the addon S3 Compatible Downloads:
 
I hope that you will benefit from this tutorial and get better performance while saving space on your main server and a lot of money 🙂
Backblaze is much more stable than Wasabi!
It also includes up to 10GB free storage, so you can test it easily !
Credits to: @Joel R and @Martin A.
Enjoy !

Hello 🙂
(This is a community guide on how to setup Backblaze and Cloudflare, as a significantly cheaper replacement for Amazon S3 and Cloudfront.  The author has no affiliate arrangement with any of the companies listed in the guide and offers the guide as a free community resource.  You should consult with your hosting provider and / or server administrator before proceeding with the guide.)
The tutorial is tested with the latest version of Invision 4.5.4 !

Invision Community allows a file storage configuration with Amazon S3 and a content distribution network (CDN) of your choice:
 
WHAT IS BACKBLAZE?
 

 
Backblaze is an infinitely Scalable B2 Cloud Storage. Backblaze B2 is enterprise-grade, S3 compatible storage that companies around the world use to store and serve data. Backblaze's service works with native APIs, CLI, and GUI; you can move and manage data with minimal coding. Their service provides fast access all the time; there is no need to accept delays or pay speed surcharges. It can also support HIPAA compliant storage with their Business Associates Agreement (BAA). B2 is compatible at ¼ the cost of AWS S3 with no hidden fees or minimums.
 
Backblaze is an award winning cloud storage provider for 2020 !
 

 
Pricing:
 

Based on their latest pricing, it is very cheap at around 5$ per 1TB storage per month! There is a cost for direct downloads (bandwidth) at 0.01$ per GB but it will not affect us as we will use Cloudflare and all files will be served from Backblaze to Cloudflare and then to users that is totally free 🙂
Be careful if you have any custom direct downloads that bypass Cloudflare. If you link to custom downloads directly, you will be charged for bandwidth. All default Invision files should go through Cloudflare. I am using Backblaze for a few of my clients and they never charged anything extra as all Invision files are going through Cloudflare as expected. Please monitor your balance after a few days just to be sure!
 
GUIDE:
BEFORE PROCEEDING, PLEASE BACKUP YOUR DATA FIRST!
 
STEP 1: Create a bucket on Backblaze
First we need to sign up at Backblaze Cloud: https://www.backblaze.com/b2/sign-up.html
You will need a phone number to activate your account:

After the activation of the account we will need to create a bucket that will host our files.
 
On the Buckets sections we click on Create a Bucket:

 
Then we add a name for our bucket. Recommendation: avoid dots (.) in the bucket name.
 
On the next screen we type a Bucket name and we select Public and then we click at Create a Bucket.

 
 
After that under the Create a Bucket we should have our Bucket.
 
Now we must keep a note of the ENDPOINT:

 
 
Now we need to get our Bucket access keys from the App Keys menu. At the bottom we click at Add a New Application Key:

 
 
At the new screen we select a anything as a key name and we keep selected the Read and Write access and wee click at Create New Key:

 
 
Then you will see there only once the KeyID and the Application Key that we must keep a note of them as we will need them later !

 
As a last step we need to go to our bucket that we just created and upload an image. From the menu on the left we click on Browse Files and then we click on our bucket:

 
Then we click on upload and we upload a simple file like an image...

 
On the right side of the uploaded image we have to click at the info icon:

 
At the pop up screen we need to keep a note for that part so copy it with the other notes that wee have already:

 
That's it ! We created our bucket and we got the access info that we will need !
 
STEP 2: Create a CNAME dns record at Cloudflare
 
Now you have to login to Cloudflare and go to your DNS tab from the top menu and then click Add record:
 

 
We use as Type the Cname and as Name the cdn and as Target the info that we got from the pop on the previous step in the tutorial above:

 
After saving that DNS record we should have that:

 
Now for security reasons we have to go to the page Rules on the top menu and create two rules:

RULE 1:
Just replace your domain and the bucket name that you create:

 
RULE 2:
Just replace your domain:

 
The final result should be like this:

 
Keep in mind the order of the rules as if you set the second rule as 1 it will not work and your forum images will not work as page rules uses priority. This is important!
That's it for the Cloudflare part!
 
STEP 3: Configure Invision to use the Backblaze Cloud
From Invision Admin Control Panel, go to System -> Files -> Storage Settings

 
Then we click on Configurations:

 
and then on Create New on the right side.
Then we select Amazon S3 and we fill the needed info as:

 
When you click Save if you get any warnings or errors then you have to check again the tutorial as you may forgot something or may have a typo somewhere...
If you save it without any issues then you are ready to use it by going to: System -> Files -> Storage Settings
and select a category with not many images for example Icons & Logos or anything else with a few images and from the drop down options the: Amazon S3:superbucket
 

 
Then wait for the automated task to transfer your files to the Cloud and check if all are ok !
If yes then you can proceed with the rest categories.
 
*Keep only at your server your theme resources:

 
Keep in mind that if you have a lot of GB of files it may take a long time for the transfer !
 
It may help to go to the Dashboard and run manually the process to get the files transferred faster.

*Attachments and Downloads may not work out of the box (don't use them on my test forum and i don't know for sure) and you may need to use the addon S3 Compatible Downloads:
 
I hope that you will benefit from this tutorial and get better performance while saving space on your main server and a lot of money 🙂
Backblaze is much more stable than Wasabi!
It also includes up to 10GB free storage, so you can test it easily !
Credits to: @Joel R and @Martin A.
Enjoy !

You can use Cloudflare that will help a lot your forums as a CDN and has also some nice one click optimizations and they offer a free plan or you can use it only for the DNS records.
Dns records changes are getting active in seconds.

Ips has confirmed a fix for 4.5.4

Great 🙂

Thanks @ASTRAPI! Considering your shared knowledge on MariaDB 10.5, I will wait a little longer to upgrade.

Please keep in mind that MariaDB 10.4/10.5, are not drop-in backwards compatible so choosing any of these would/may be one way upgrade/switches.
Also many users report performance issues (most querying big tables) for the 10.4 that i didn't test yet at 10.5 as it is a bit early for me to do that jump....
A temporary solution for that is to use this parameter at your my.cnf file:
optimizer_use_condition_selectivity=1 Enjoy ! 🙂

Latest Redis version is working fine....

It is faster 🙂

You know that thing where you casually mention something that's relevant to the problem but you are totally oblivious to the fact that you actually didn't account for that thing you just talked about? And then someone comes along and says "why didn't you deal with that thing you just talked about here..."?
That was yesterday.
@Martin A., with the oblivious assist from myself, got a handle on this. This has been cleared by at least two live sites experiencing this problem. A new version will be submitted to the Marketplace asap.
Now, just as a heads up to everyone: we are nudging, but not rushing, towards the end of the usefulness of this derpy thing. 
Amazon S3 is forcing everyone on over to the new styled urls where the bucket name is IN FRONT of the endpoint url. So, my.bucket.s3.awesomes3service.com/.... (this is virtual hosted-style) vs. ye'olde path-style urls, e.g. awesomes3service.com/my.bucket/.... 
The thing with the newer style is you gotta have wildcard support set up for your domain with your DNS settings. You gotta deal with your CDN settings. And naturally, your SSL certificate. Got dots in your bucket names? Shouldn't do that... Dashes are better but now you have some other hitches and so on. In a perfect world you would just have a single non-dotted, non-dashed alphabetic "word" for your bucket names and things work much more smoothly.
The patch here, as it were, is to account for dots in a bucket name and if present, flip things over to http instead of the likely secure SSL https. That stops all the yelling.
The point is, as Amazon S3 standards change, and web/browser security changes, and CDN requirements and changes, and so on, we're going to hit a point where this isn't going to be a viable hack anymore.
We are not there now but in a few years? Who can tell...

These are loading from cloudflare in your case, if they are slow to load, look to the source, in this case cloudflare for speed issues with loading them. 
However, those are all cached in the browser so they are only loaded once per user, once they are loaded they are served from the browser cache.  
Are you seeing actual speed issues with your site or trying to make speed test sites happy?  

Yes.
As long as you follow the steps about Cloudflare, DNS, and naming of the bucket, you can do so free of bandwidth charge. The URL from the guide (cdn.yourdomain.com) points to the root of your bucket. If you upload static content to a folder named "static", the URL to files in that file is cdn.yourdomain.com/static/image.png.

Hello
(This is a community guide on how to setup Wasabi and Cloudflare, as a significantly cheaper replacement for Amazon S3 and Cloudfront.  The author has no affiliate arrangement with any of the companies listed in the guide and offers the guide as a free community resource.  You should consult with your hosting provider and / or server administrator before proceeding with the guide.)
BACKGROUND:
Invision Communities contain rich content, from forum attachments to gallery images to download files.  These resources add up over time. 
Here are real examples of communities that I provide server administration for:
- Website A: 400 GB of total storage and 1.2 TB of total monthly bandwidth 
- Website B: 800 GB of total storage and 14 TB of total bandwidth
Invision Community allows a file storage configuration with Amazon S3 and a content distribution network (CDN) of your choice:
 
WHAT IS WASABI?
Wasabi Cloud  is faster and cheaper than Amazon S3 for object storage, offers unlimited egress for bandwidth, and compatible with Cloudflare.  One of the biggest hidden expenses of using Amazon S3 is not the cost of storage itself, but the bandwidth to deliver objects in and out.  Wasabi does not charge for egress bandwidth, which can save on the majority of the true cost of Amazon S3. It also provides an S3-compliant interface, which means it can be used as a perfect drop-in replacement for Amazon S3 storage and immediately usable on all Invision Communities.   

Wasabi is 80% cheaper and 6x faster than Amazon S3, with 100% data immutability protection, and no data egress fees or API charges. Created by Carbonite co-founders and cloud storage pioneers David Friend and Jeff Flowers, Wasabi is on a mission to commoditize the storage industry. Wasabi is a privately held company based in Boston, MA.
In March of 2018, Wasabi pioneered the cloud storage industry’s first ‘unlimited free egress’ pricing plan. We are excited to join forces with Cloudflare and the Bandwidth Alliance, validating that the early business models of Cloud 1.0 vendors no longer applies in a world that expects unlimited everything.  What this means in practice is that you can use Cloudflare services (including the free plan) like blazing-fast DNS, WAF firewall, performance improvements on the fly, and much more.  Forums users will request a topic, and all static content can be picked up from Cloudflare's optimized services that will connect to Wasabi.

 
At the moment, Wasabi offers three Datacenters:
1)US-WEST
2)US-EAST
3)EU-CENTRAL 

One price. Lightning fast speed. No hidden fees.

You can check and compare the prices above.
 
GUIDE:
BEFORE PROCEEDING, PLEASE BACKUP YOUR DATA FIRST!
YOUR FILES WILL BE IN PRIVATE MODE AND WILL NOT BE ACCESSIBLE ON YOUR FORUM !
YOU MUST GET A PAID PLAN TO BE ABLE TO ACTIVATE THE INVISION FILE PERMISSIONS AND GET YOUR FILES ACCESSIBLE AT YOUR FORUMS.
JUST ADD YOUR CREDIT CARD NOW (AT YOUR PROFILE PAGE) AND THEY WILL CHARGE YOU 5,99$ FOR A MONTH FOR 1TB STORAGE AND UNLIMITED BANDWIDTH.
THE FREE TRIAL WILL NOT WORK FOR INVISION !
 
Step 1: Create a CName at CloudFlare
We start by creating a cname at Cloudflare:
cname -> cdn -> cdn.yourdomain.com.s3.eu-central-1.wasabisys.com  <--For Europe datacenter
or
cname -> cdn -> cdn.yourdomain.com.s3.us-west-1.wasabisys.com  <--For US-WEST datacenter
or
cname -> cdn -> cdn.yourdomain.com.s3.wasabisys.com  <--For US-EAST datacenter
Like this:

 
Step 2: Create a bucket on Wasabi
First we sign up for a free account at Wasabi Cloud: https://wasabi.com/sign-up/
Then we create a bucket:

 
It is important to name it as: cdn.yourdomain.com
 

 
Then keep default suspend Versioning and Suspend Logging:

Then click CREATE BUCKET:
 

 
Step 3: Retrieve your Access Keys
Go to the menu on top left and click Access keys on the left. Click on "Create New Access Key."

 
Copy / save the access key and the secret key:

Step 4: Setting up a new file storage in ACP
Login to Admin Control Panel and navigate to Overview at the Files category and then click at the right side at Storage settings:

 
Then we click at Configurations and at the right side at Create New:
 

We select Amazon s3 and we add the following info:

Save it.
Step 5: Set the new storage at storage settings
Navigate to Storage settings and select from the drop down menu the new Amazon s3 bucket.

 
Keep only at your server your theme resources:

*Attachments and Downloads doesn't work out of the box as it seems there is some hardcoded code at Invision related to S3...
To make them work you just need to install the addon bellow: (tested with Invision 4.4.4).
 
Then wait for any Invision background tasks to finish and check.
I hope that you will benefit from this tutorial and get better performance while saving a lot of money 🙂
Enjoy!
OTHER NOTES:
If you are already using S3 then it is very easy to move straight to Wasabi by following the above tutorial as it is NOT needed to move back your files to server and then to Wasabi.
CREDITS
Credits to @Joel R for giving me the motivation to write this tutorial and providing screenshots from his Wasabi account and for editing the topic.
Thank you

Hello,
I feel we should revisit the platform’s compliance with GDPR, in light of the latest developments and clarifications issued by the EU. Had some discussions, read a lot about this and it's clear to me that the classic Cookie strip with one button (I accept) simply doesn't cut it anymore and would make the website owner liable for not fully following the current regulations.

It's been brought to my attention from the ad network we use, that we should provide a full Consent message to every visitor of our site, and give them the option to choose which cookies, if any, they would want to be used during their visit. There are already many services out there like Cookiebot, Quantcast and OneTrust which can scan one’s site and automate the process by creating this banner. Of course even if they have limited free packages, my main concern is that there are limitations to styling, speed, translation, etc. I feel that such features must be provided from the platform itself, which must integrate the IAB Consent Framework. 
A valid cookie consent banner has to look like the one Cookiebot provides, offering the ability to choose the type of cookies the visitor wants. If you’d like to see a live example, visit this page.

Cookiebot Consent Banner

analytic view
Two links from the Cookiebot site, which I really feel that they offer a full picture of what is the proper way to have a GDPR Consent banner in your site.
GDPR and cookies | GDPR cookie consent | Is my use of cookies compliant? Active consent and the case of Planet49 | CJEU | GDPR & ePR I’d very much like to read your thoughts on this and particularly whether such options are included in the roadmap.

Hi @Ford Focus Owners Club congrats on becoming the new forum owner!  
1.  Do you have IPS Cloud or your own cloud?  If IPS cloud, then send in a support ticket and they can assist.  
2.  You may want to reach out to some users on the Providers page who can help you migrate over.  They're not affiliated with IPS but many of them have years of experience with the software and server migrations.  You can check out users like @ASTRAPI @Makoto or @Spanner who can help you not only move over, but also upgrade to 4.4.  
 

CloudFlare announced there support for HTTP/2 Server Push but Nginx HTTP/2 module doesn't have server push support.
It seems that they use own custom coding and you will have to wait for them to release it as open source so the game will start
Or do you mean to use there implementation? If yes:
 
Enabling Server Push All of our customers using HTTP/2 now have Server Push enabled, but unfortunately, Server Push isn’t one of those features that just works—you’ll need to do a little bit of work to truly leverage the benefits of Server Push. Our implementation follows the guidelines laid out in the W3C’s draft standard on the use of a preload keyword in Link headers1, and we will continue to track that standard as it evolves. So, if you want to push assets for a given request, you simply add a specially formatted Link header to the response: Link: </asset/to/push.js>; rel=preload; Those links can be manually added, but they’re already created automatically by many publishing tools or via plugins for popular content management systems (CMS) such as WordPress. Only relative links will be pushed by our edge servers, which means Server Push won’t work with third-party resources.  

I wanted to provide some feedback for anyone interested in Wasabi since we've been using it for two billing cycles now.
In the beginning I was afraid of the switch because hearing something is not directly supported by Invision with a built-in feature specifically for it is a bit scary.  Before my community switched to self-hosting with this software in 2017, all of my experience was using hosting websites that did most of the work for you, and I was like a fish out of water learning everything about web development on the fly. 
I'm not going to lie and say this was easy as pie to set up for me because I did experience some issues that were not applicable at the time the guide was written, however, it is not hard either and I was able to solve things with quick troubleshooting in Wasabi documentation.  I have a large community, so it took about 3-4 days for the switch to be fully complete working overtime, and we did have some content loss.  I'm still not sure what went wrong, but the attachment folders did not transfer over correctly and a good majority of them were shot into the void somewhere.  It took us about a month to get most important things updated with new attachments, but we still occasionally find ourselves coming across a page or article that has some broken ones.  This is not an issue with Wasabi, this is an issue with either Invision or human error during the transfer.
Regardless, I would do it all over again anyway, because this not only works the same as if you had S3 with Amazon, the amount of money we have saved is so drastic that it's hard to believe Wasabi is capable of providing this service at such a low cost.  The pricing is as advertised at 5.99 per TB of storage.  There are no hidden or surprise fees at the end of the month and so far our bills have never been over $18.  (We store everything except theme based resources on Wasabi.)  The cost breakdown in your control panel is very easy to understand what you're being charged for and what is free.  The same storage for us on Amazon cost roughly $5-7 a day, sometimes more depending on how many requests came in.  The requests are really what dig a hole in your pocket.  We are an art based website, so we were being charged out the hoo-hah for everything no matter where we tried looking for storage, and keeping it on our main server was completely out of the question.
We did experience service failure once a few days ago where requests to pull images from Wasabi were being met with time-out and write permission errors, but I also am aware that Wasabi is growing quite fast right now due to word of mouth and they are trying their best to increase their resources to keep up with the growth.  I'm not worried about having to potentially switch again anytime in the foreseeable future.
We are an established community with a steady income, so I can only imagine how helpful this would be to small communities ran by hobbiest leaders out-of-pocket if you get to a point where you outgrow your server resources.  I imagine that 5.99/m price is what a lot of people will only end up paying for a while.

Wasabi is NOT for hosting a website, it is for files that are part of the website.

Just convert them all to Innodb 🙂

So the first thing I want to say is that it is normal to have some queries not using indexes. For instance, we load all forums up into memory, and when you select all rows from a table no particular index is used (since there is no filtering occurring). You can't solve all of those types of queries.
/*IPS\Patterns\hook543::load:17*/ SELECT * FROM `membersshop_points` WHERE `member_id`=10282; You have a member shop application or plugin installed which needs an index on membershop_points.member_id column.
/*IPS\Http\Url\cms_hook_FriendlyUrl::createFriendlyUrlFromComponents:55*/ SELECT store_current_id FROM `cms_url_store` WHERE store_type='page' and store_path='fbclid=IwAR16ELYSJqeQ0TjcQoAaPOQFNEZDw6C2zfGHKAtHwPCToBE5SILpAsvUtWI'; This has already been addressed for 4.5, though it's unlikely to be slow for most communities regardless.
/*IPS\Theme\Cache\class_membersshop_front_widgets::mostpoints:61*/ SELECT * FROM `core_members` ORDER BY core_members.shop_points DESC LIMIT 6; Again, your member shop application. You may get some performance by adding an index on core_members.shop_points and/or the query may need to be adjusted.
/*IPS\featuredcontent\_Slider::fromCustom:638*/ SELECT * FROM `featuredcontent_contents` WHERE fcc_slider=70 ORDER BY RAND() LIMIT 0,20; Order by RAND() is always going to be horrible. This should be changed by the plugin author. We have a pseudo-random approach when we order "randomly".

Hello
The best thing that you can do is to convert all tables to Innodb .
You will benefit a lot.

Hello @Gauravk
You should plan an upgrade to Centos 7 to get the new compilers and try to use phpfpm + Nginx + tuning everything on the system....
Not something that you can solve easily on a topic...

Hello
To get an idea you can get 2X your cpu:
Chassis model: dell R730
Processor: 2X Intel® Xeon E5 2640v4 CPU - 16C/32T - 2.6 GHz
Storage: 3 × 500 GB SSD
Memory: 192 GB DDR4 ECC
215 Euro
Then you can get the administration support in different prices that you must agree on what you want and how much you want to pay....
You can get something from 50 Euro up to 150 Euro easily...

@Hugo_S4 I would suggest that you contact @ASTRAPI, he's the server expert.

There should be instructions for cpanel that you can find on how to save a backup.  
If you need managed assistance, there are several competent third party providers in the community like @Makoto @ASTRAPI @DawPi and @Spanner who can help not just make a backup, but also run test conversions to prep your board for upgrade.