https://mwiki.costasano.club/index.php?action=history&feed=atom&title=ICT%3ASurvivability_-_Future_PlansICT:Survivability - Future Plans - Revision history2026-07-23T01:07:21ZRevision history for this page on the wikiMediaWiki 1.45.1https://mwiki.costasano.club/index.php?title=ICT:Survivability_-_Future_Plans&diff=392&oldid=prevMngr: Created page with "= Costa Sano MediaWiki – Survivability and Continuity Plan = __TOC__ == Purpose == This document explains how the system remains operational for many years with: * limited budget * volunteer maintenance * hardware replacement * possible administrator change The focus is continuity, not features. ---- == Historical background == Experience has shown that data loss can be catastrophic. In the past, insufficient backups caused: * equipment loss * weeks of redevelop..."2026-02-04T18:04:27Z<p>Created page with "= Costa Sano MediaWiki – Survivability and Continuity Plan = __TOC__ == Purpose == This document explains how the system remains operational for many years with: * limited budget * volunteer maintenance * hardware replacement * possible administrator change The focus is continuity, not features. ---- == Historical background == Experience has shown that data loss can be catastrophic. In the past, insufficient backups caused: * equipment loss * weeks of redevelop..."</p>
<p><b>New page</b></p><div>= Costa Sano MediaWiki – Survivability and Continuity Plan =<br />
__TOC__<br />
<br />
== Purpose ==<br />
This document explains how the system remains operational for many years with:<br />
<br />
* limited budget<br />
* volunteer maintenance<br />
* hardware replacement<br />
* possible administrator change<br />
<br />
The focus is continuity, not features.<br />
<br />
----<br />
<br />
== Historical background ==<br />
Experience has shown that data loss can be catastrophic.<br />
<br />
In the past, insufficient backups caused:<br />
<br />
* equipment loss<br />
* weeks of redevelopment work<br />
* high financial cost<br />
<br />
Therefore survivability is a primary design requirement.<br />
<br />
Backups and portability are not optional.<br />
<br />
----<br />
<br />
== Core strategy ==<br />
<br />
The system must be:<br />
<br />
* rebuildable<br />
* portable<br />
* independent<br />
* well documented<br />
<br />
No single component should be irreplaceable.<br />
<br />
----<br />
<br />
== 3-2-1 Backup Strategy ==<br />
<br />
Always maintain:<br />
<br />
* 3 copies of data<br />
* 2 different media types<br />
* 1 off-site copy<br />
<br />
This policy has been used successfully for decades and must continue.<br />
<br />
Backups include:<br />
<br />
* VM images<br />
* database dumps<br />
* uploaded files<br />
* configuration files<br />
<br />
----<br />
<br />
== Virtual Machines ==<br />
<br />
All services run inside VMs.<br />
<br />
Benefits:<br />
<br />
* hardware independence<br />
* easy migration<br />
* snapshot capability<br />
* fast recovery<br />
* simple replication<br />
<br />
If hardware fails:<br />
→ copy VM → boot → continue<br />
<br />
No reinstall required.<br />
<br />
----<br />
<br />
== Hardware Independence ==<br />
<br />
The system must run on:<br />
<br />
* old PCs<br />
* small servers<br />
* consumer hardware<br />
<br />
No specialised hardware required.<br />
<br />
This reduces cost and ensures availability of replacement parts.<br />
<br />
----<br />
<br />
== Software Independence ==<br />
<br />
Avoid:<br />
<br />
* paid licenses<br />
* proprietary platforms<br />
* cloud lock-in<br />
* subscriptions<br />
<br />
Use:<br />
<br />
* Linux<br />
* MediaWiki<br />
* MariaDB<br />
* Apache<br />
* WordPress<br />
<br />
All are free and long-term stable.<br />
<br />
----<br />
<br />
== Migration Plan (future) ==<br />
<br />
=== Today ===<br />
Hyper-V + Windows Server<br />
<br />
=== Possible future ===<br />
Proxmox or Linux hypervisor<br />
<br />
Because:<br />
* no licenses<br />
* lower cost<br />
* simpler maintenance<br />
<br />
Migration is easy due to VM architecture.<br />
<br />
----<br />
<br />
== Disaster Recovery Procedure (summary) ==<br />
<br />
If total failure occurs:<br />
<br />
# Install hypervisor<br />
# Restore VM images<br />
# Start database<br />
# Start web server<br />
# Test access<br />
<br />
Target:<br />
System operational within one day.<br />
<br />
----<br />
<br />
== Knowledge Transfer ==<br />
Survivability also depends on people.<br />
<br />
Therefore:<br />
<br />
* document everything in ICT:<br />
* avoid complex tricks<br />
* keep configuration readable<br />
* follow consistent patterns<br />
<br />
A successor should understand the system quickly.<br />
<br />
----<br />
<br />
== Golden Rules for Future Maintainers ==<br />
<br />
Do:<br />
* keep backups running<br />
* keep documentation updated<br />
* keep architecture simple<br />
* reuse existing patterns<br />
<br />
Do NOT:<br />
* introduce unnecessary complexity<br />
* depend on paid software<br />
* mix many new technologies<br />
* redesign without strong reason<br />
<br />
----<br />
<br />
== Final Philosophy ==<br />
The goal is not the newest technology.<br />
<br />
The goal is:<br />
<br />
''A system that quietly works for the next 10 years.''<br />
<br />
Boring, simple systems survive.<br />
<br />
That is success.</div>Mngr