Changeset 7f6bf79b


Ignore:
Timestamp:
12/04/2021 12:20:27 PM (6 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
11.1, lazarus, trunk, upgradedb, xry111/intltool, xry111/test-20220226
Children:
8986fa9
Parents:
bcdfc53
Message:

Textual changes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • server/databases/upgradedb.xml

    rbcdfc53 r7f6bf79b  
    1313  </sect1info>
    1414
    15   <title>Notes on Database Server Software</title>
     15  <title>Important notes about upgrading Database Server Software</title>
     16
     17    <para>Lets start this chapter a bit dramatic with a screenshot
     18    of an issue that really happened. Don't be scared if you read
     19    this the first time, this issue will not occur if you are going
     20    to install the software the first time:</para>
    1621
    1722<screen>$ sudo systemctl status postgresql
     
    3944  </para>
    4045  <para>
    41     Even if you are installing a DBMS the initial time, read it
    42     anyway, it might give you a guideline on how to set up backup
     46    The root cause of the issue shown above was an upgrade
     47    of the server software to a newer major version but letting the
     48    data files untouched. The admin was able to recover without any
     49    loss of data.
     50  </para>
     51  <para>
     52    Even if you are installing a DBMS the initial time, read this
     53    section too, it might give you a guideline on how to set up backup
    4354    and restore procedures (at least the strategy for building
    4455    them) which are sufficient for your needs and for the safety
     
    171182
    172183    <sect3>
    173       <title>Upgrade by system tools</title>
     184      <title>Upgrade data file by using system tools</title>
    174185
    175186      <para>
Note: See TracChangeset for help on using the changeset viewer.