From 3b2433b664bafc1d1db9c90ce5242fbed5c8b1ef Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Tue, 20 Feb 2024 12:42:18 +0100
Subject: Started on fallback

---
 topics/systems/mariadb/mariadb.gmi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'topics/systems/mariadb')

diff --git a/topics/systems/mariadb/mariadb.gmi b/topics/systems/mariadb/mariadb.gmi
index 4000482..ae0ab19 100644
--- a/topics/systems/mariadb/mariadb.gmi
+++ b/topics/systems/mariadb/mariadb.gmi
@@ -2,9 +2,9 @@
 
 Here we capture some common actions
 
-To install Mariadb (as a container) see
+To install Mariadb (as a container) see below and
 
-=> setting-up-local-development-database.gmi
+=> topics/deploy/installation
 
 # Tags
 
@@ -39,9 +39,9 @@ To get a log with some stuff filtered out try
 mysql -p -u webqtlout db_webqtl -e "SHOW BINLOG EVENTS IN 'gn0-binary-log.000014';" -r -s |grep -v -e "Access\|GTID\|INSERT_ID\|COMMIT\|Temp\|lastlogin\|LITERA\|flush\|ROLLBACK"
 ```
 
-# Update MariaDB on penguin2 to the latest production database
+# Update MariaDB to the latest production database using borg recovery
 
-The MariaDB instance running on penguin2 needs to be periodically updated to the latest version of the database running on production. We do this by restoring backups of the production database stored on penguin2 into the penguin2 MariaDB database directory. Here's how.
+The MariaDB instance needs to be periodically updated to the latest version of the database running on production. We do this by restoring backups of the production database into MariaDB database directory. Here's how.
 
 Backups are managed using Borg as the ibackup user. First, become the ibackup user.
 ```
-- 
cgit v1.2.3