We've upgraded our hypervisors to the latest version, which comes with a newer platform and kernel underneath. It delivers major improvements.
Patching is critical in our business. Many avoid it, while we're advocates for it!
💅 Polish
https://github.com/The-Network-Crew/BackBork-KISS-Plugin-for-WHM
We've built a WHM Plugin which wraps existing cPanel-shipped tooling to deliver what JetBackup did. This frees us of proprietary data encapsulation!
This has been done in association with Velocity Host Pty Ltd, who provide TrueNAS Storage (not to us… yet). After intensive development, the first beta release v1.3.0 has been published and is undergoing testing now.
https://github.com/The-Network-Crew/BackBork-KISS-Plugin-for-WHM
Due to a problem with how cPanel/WHM implements IPv6, we have changed from using /128 addresses per-website capable of individual PTR (Reverse DNS) etc, to instead using SNI (Server Name Indication) over the Shared IPv6.
This means that outbound routing does not misinterpret its path and instead choose an arbitrary assigned /128 instead of the server-assigned IPv6 /96. We could instead add a route script to replace the default route, however it also adds loading having more addresses, so for a few reasons, we've gone SNI.
Work continues on the Backup Platform overhaul that was triggered by an ACL problem. We are close to having this finalised and functionality restored.
As part of this project, we have decided to also overhaul our retentions:
As part of trouble-shooting a problem that came about while modifying the off-site DR syncing from NEXTDC, we have engaged with specialist engineers and decided to take the opportunity to overhaul our primary backup storage.
To do this thoroughly, we need to rebuild the data-sets in-use to store client data. While doing this, we are transitioning from flexible limits to Dedicated Backup Storage per-client that gives you more security & flexibility. We should be able to retain the data that was stored prior so that JetBackup "carries on".
While working through this, it has highlighted that we have over-committed storage on the basis of low usage across 10+ years of data. That is not a problem as our usage is low (around 30%), however with the new system build we need to allocate space specifically, so have overhauled inclusions:
| Plan | VPS Capacity | Old Backup Quota | New Backup Quota |
|---|---|---|---|
| DEV | 300GB (Unchanged) | 1TB (Flexible) | 500GB (Dedicated) |
| FM-1 | 600GB (Unchanged) | 2TB (Flexible) | 1TB (Dedicated) |
| FM-2 | 900GB (Unchanged) | 3TB (Flexible) | 2TB (Dedicated) |
| FM-3 | 1.2TB (Unchanged) | 5TB (Flexible) | 3TB (Dedicated) |
| FM-4 | 2TB (Unchanged) | 7TB (Flexible) | 5TB (Dedicated) |
| FM-5 | 3TB (Unchanged) | 10TB (Flexible) | 8TB (Dedicated) |
This work is on-going and we will continue to share updates as we progress. We will also be adjusting our retention periods, introducing hourly backups!
