Changeset 7f6bf79b for server/databases/upgradedb.xml
- Timestamp:
- 12/04/2021 12:20:27 PM (3 years ago)
- Branches:
- 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, gimp3, 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/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 8986fa9
- Parents:
- bcdfc53
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
server/databases/upgradedb.xml
rbcdfc53 r7f6bf79b 13 13 </sect1info> 14 14 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> 16 21 17 22 <screen>$ sudo systemctl status postgresql … … 39 44 </para> 40 45 <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 43 54 and restore procedures (at least the strategy for building 44 55 them) which are sufficient for your needs and for the safety … … 171 182 172 183 <sect3> 173 <title>Upgrade bysystem tools</title>184 <title>Upgrade data file by using system tools</title> 174 185 175 186 <para>
Note:
See TracChangeset
for help on using the changeset viewer.