Changeset 8986fa9

Timestamp:

12/04/2021 03:25:28 PM (2 years ago)

Author:

Thomas Trepl (Moody) <thomas@…>

Branches:

11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

d86ea4b

Parents:

7f6bf79b

Message:

Add bdb and sqlite

File:

• server/databases/upgradedb.xml (modified) (8 diffs)

server/databases/upgradedb.xml

@@ -56 +56 @@
     of your data.
   </para>
-  
+
   <sect2>
     <title>Upgrade database server packages</title>
@@ -131 +131 @@
         <listitem>
           <para>Create a full database backup using the old tools.</para>
-          <para>This step creates an offline copy of the database 
+          <para>This step creates an offline copy of the database
           files ready to be used for long term archiving, for desaster
           recovery or just as a preparation for upgrade. This offline
@@ -152 +152 @@
           hundrets of Terabyte. A full backup of the later one isn't done
           quickly (and we assume that the underlaying system of such a DB
-          might not be a home brewed LFS anyhow).</para>
+          might not be a home brewed LFS anyhow).
+          To close the last gap to fully protect your data, create a backup
+          of the corresponding old binaries (and/or their sources) and
+          store it along with the data files to
+          make sure that there is a fallback solution if it comes to
+          the situation that newer software might not be able to read
+          ancient data.</para>
         </listitem>
         <listitem>
           <para>Upgrade the server software</para>
           <para>In this step, instructions to build the database
-          server software are executed just as they are shown in 
+          server software are executed just as they are shown in
           subsequent sections talking about the DBMs like MariaDB or
           Postgresql. This is building the software as
@@ -167 +173 @@
           server software is used. During the restore process, the new
           tools will create and/or upgrade the data files in the
-          format the software expects them to be.</para>
+          format the software expects them to be. At this moment it is
+          assumed that newer software is capable to read old data.</para>
         </listitem>
       </itemizedlist>
@@ -174 +181 @@
         Since you have already a backup procedure in place (and you
         have tested your restore procedure, don't you?), this way might
-        be the easiest way to upgrade as you are going to use well-known
+        be the easiest way to upgrade as you are going to use your wellknown
         processes to upgrade just as you allways do - at least in terms
         of the backup and restore.
@@ -212 +219 @@
   <sect2>
     <title>Notes for specific DBMS</title>
-    
+
     <sect3>
       <title>PostgreSQL</title>
-      
+
       <!-- might add some advanced notes for the DBMS here -->
 
@@ -221 +228 @@
         <ulink url="https://www.postgresql.org/docs/current/backup.html"/>
       </para>
-      
+
     </sect3>
 
     <sect3>
       <title>MariaDB</title>
-      
+
       <!-- might add some advanced notes for the DBMS here -->
 
@@ -232 +239 @@
         <ulink url="https://mariadb.com/kb/en/backup-and-restore-overview/"/>
       </para>
-      
-    </sect3>
-
+
+    </sect3>
+
+    <sect3>
+      <title>Sqlite</title>
+
+      <!-- might add some advanced notes for the DBMS here -->
+
+      <para>Don't underestimate <application>Sqlite</application>, it
+      is a feature rich DBMS. The main difference to the two big
+      players above is that Sqlite does not provide access via a
+      network API. Sqlite databases are files always stored on the
+      same machine as the running program which reads/writes the
+      database. The manipulation of data content is done via API calls
+      to library functions directly within the program.</para>
+
+      <para>In the upstream documentation you may find the
+      following useful:</para>
+
+      <para>Documentation of the sqlite3 command line tool:
+        <ulink url="https://www.sqlite.org/cli.html"/>
+      </para>
+      <para>Documentation of backup API calls:
+        <ulink url="https://www.sqlite.org/backup.html"/>
+      </para>
+
+      <para>Unfortunatly, there is no dedicated chapter in the
+      upstream documentation talking about backup &amp; restore but
+      there are several articles about it somewhere else in the
+      Internet. One example is shown below.</para>
+
+      <para>Documentation for Backup &amp; Restore:
+        <ulink url="https://database.guide/backup-sqlite-database/"/>
+      </para>
+
+    </sect3>
+
+    <sect3>
+      <title>Berkeley DB</title>
+
+      <!-- might add some advanced notes for the DBMS here -->
+
+      <para>Just like <application>Sqlite</application> this
+      software acts on local database files meaning there is no
+      network interface, too.</para>
+
+      <para>The relevant resources for Backup &amp; Restore a Berkeley DB
+      are the man pages for <filename>db_dump</filename> and its
+      counterpart <filename>db_load</filename>.</para>
+
+    </sect3>
   </sect2>
-  
+
 </sect1>