|
Size: 1471
Comment:
|
Size: 2336
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| The main goal is to go as close to no downtime as possible. | System uptime and availability is being increasingly important. Various services are expected to be accessibly at all times. The challenge is to configure and maintain such a system, with minimal downtime, and preferable no downtime at all. At first this sounds like a very complicated task, but breaking it down to its components makes it possible. Configuring and deploying one component at a time, in a redundant way, allows for added complexity in a simple way, which increasingly builds on a stable redundant platform, keeping the redundancy all the way through the component stack. As the system is comprised of redundant components, it is ensured that any component at any time can be taken down for maintenance, without compromising the uptime and availabilty of the system. |
| Line 7: | Line 7: |
| Deciding the level of importance of the system really depends on the physical environment. As we can see there are | |
| Line 39: | Line 40: |
| * [[Mariadb|Mariadb]] * [[Redis|Redis]] |
|
| Line 40: | Line 43: |
| * [[Mariadb|Mariadb]] | |
| Line 44: | Line 46: |
| * [[ownCloud|ownCloud]] * [[Bacula|Bacula]] |
* [[Nextcloud|Nextcloud]] * [[OPNsense|OPNsense]] |
| Line 47: | Line 49: |
| ''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.'' | ''This project is based on the GNU/Linux software packaged by Debian, currently the buster 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!
System uptime and availability is being increasingly important. Various services are expected to be accessibly at all times. The challenge is to configure and maintain such a system, with minimal downtime, and preferable no downtime at all. At first this sounds like a very complicated task, but breaking it down to its components makes it possible. Configuring and deploying one component at a time, in a redundant way, allows for added complexity in a simple way, which increasingly builds on a stable redundant platform, keeping the redundancy all the way through the component stack. As the system is comprised of redundant components, it is ensured that any component at any time can be taken down for maintenance, without compromising the uptime and availabilty of the system.
These are our worst foes
Deciding the level of importance of the system really depends on the physical environment. As we can see there are
- 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
This project is based on the GNU/Linux software packaged by Debian, currently the buster 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.