|
Size: 1372
Comment:
|
Size: 1518
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 38: | Line 38: |
| * [[HA-proxy|HA-proxy]] * [[Corosync|Corosync]] |
|
| Line 39: | Line 41: |
| * [[MySQL|MySQL]] | * [[Mariadb|Mariadb]] |
| Line 41: | Line 43: |
| * [[SMTP|SMTP]] * [[IMAP|IMAP]] * [[OwnCloud|OwnCloud]] |
* [[Postfix|Postfix]] * [[Dovecot|Dovecot]] * [[ownCloud|ownCloud]] |
| Line 45: | Line 47: |
| ''This project is based on the GNU/Linux software packaged by Debian, currently the stretch release. The information provided here will most likely work on other GNU/Linux systems as well. Basic knowledge of GNU/Linux commandline tools, file editing etc. is required to use and understand this guide.'' | == Troubleshooting == * [[Troubleshooting Disk IO|Disk IO]] ''This project is based on the GNU/Linux software packaged by Debian, currently the stretch release. The information provided here will most likely work on other GNU/Linux systems as well. Basic knowledge of GNU/Linux commandline tools, file editing, network etc. is required to use and understand this guide.'' |
Its all about uptime!
The main goal is to go as close to no downtime as possible.
These are our worst foes
- Power outage
- Internet access
- Hardware malfunction
- Software updates
To get around this a redundant system has to be built. Realizing that a redundant system consists of many redundant parts, virtualization naturally comes to mind.
Configure your system
Manage Virtual Domains
Network Planning
Configure a Redundant Service
Troubleshooting
This project is based on the GNU/Linux software packaged by Debian, currently the stretch release. The information provided here will most likely work on other GNU/Linux systems as well. Basic knowledge of GNU/Linux commandline tools, file editing, network etc. is required to use and understand this guide.