- Timestamp:
- 01/29/2023 12:51:59 PM (17 months ago)
- Branches:
- 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- cb993ff
- Parents:
- eed39e3
- Location:
- server
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
server/databases/upgradedb.xml
reed39e3 r54d58907 117 117 tools to create backups of your data. Usually the backups created with 118 118 those tools can be read by newer versions of the software (via a 119 restore tool). Using older restore tools with newer backup data is 119 restore tool). Using older restore tools with newer backup data is 120 120 a bad idea; you should <emphasis>never</emphasis> blindly assume that 121 121 it will work. It might, but usually it doesn't. … … 147 147 the amount of data stored in your database (is it a few hundred table 148 148 rows, or is it hundreds of terabytes?). A full backup in the latter case 149 can't be done quickly. To 149 can't be done quickly. To 150 150 fully protect your data, create a backup of the old 151 151 programs (and/or their sources) and save it, along with the data … … 190 190 Some database systems (for instance Postgresql) provide 191 191 a tool which can reformat (upgrade) the existing database 192 files to the new format. 192 files to the new format. 193 193 If you need to restore from a backup (for example, running 194 194 the upgrade tool failed) you will have to reinstall the old software -
server/mail/postfix.xml
reed39e3 r54d58907 12 12 <!ENTITY postfix-md5sum "2442d1e53d58e61842d99fb5978fec4a"> 13 13 <!ENTITY postfix-size "4.6 MB"> 14 <!ENTITY postfix-buildsize "148 MB"> 14 <!ENTITY postfix-buildsize "148 MB"> 15 15 <!ENTITY postfix-time "0.2 SBU (Using parallelism=4)"> 16 16 ]>
Note:
See TracChangeset
for help on using the changeset viewer.