From 91897882d289dd8a45cc15125163f29e632c2a82 Mon Sep 17 00:00:00 2001 From: Badlop Date: Fri, 9 Jan 2009 22:59:37 +0000 Subject: [PATCH] * doc/guide.tex: Improve explanation of backup commands (EJAB-832) * doc/guide.html: Likewise SVN Revision: 1792 --- ChangeLog | 6 ++++++ doc/guide.html | 17 +++++++++++++++-- doc/guide.tex | 17 +++++++++++++++-- 3 files changed, 36 insertions(+), 4 deletions(-) diff --git a/ChangeLog b/ChangeLog index b36261f9f..f30084f06 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,11 @@ 2009-01-09 Badlop + * doc/guide.tex: Improve explanation of backup commands (EJAB-832) + * doc/guide.html: Likewise + + * src/web/ejabberd_web_admin.erl: New appearance of WebAdmin logo, + fixed logo-fill. + * src/mod_configure.erl: Fix access check for vhost configuration 2009-01-08 Mickael Remond diff --git a/doc/guide.html b/doc/guide.html index b7466955e..a75ff4bf9 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -2929,8 +2929,21 @@ The more interesting ones are:
reopen-log
Reopen the log files after they were renamed. If the old files were not renamed before calling this command, they are automatically renamed to "*-old.log". See section 7.1. -
backup, restore, install-fallback, dump, load
You can use these -commands to create and restore backups. +
backup ejabberd.backup
+Store internal Mnesia database to a binary backup file. +
restore ejabberd.backup
+Restore immediately from a binary backup file the internal Mnesia database. +This will comsume quite some memory for big servers. +
install-fallback ejabberd.backup
+The binary backup file is installed as fallback: +it will be used to restore the database at the next ejabberd start. +Similar to restore, but requires less memory. +
dump ejabberd.dump
+Dump internal Mnesia database to a text file dump. +
load ejabberd.dump
+Restore immediately from a text file dump. +This is not recommended for big databases, as it will consume much time, +memory and processor. In that case it’s preferable to use backup and install-fallback.
import-file, import-dir
These options can be used to migrate from other Jabber/XMPP servers. There exist tutorials to migrate from other software to ejabberd. diff --git a/doc/guide.tex b/doc/guide.tex index c3fb6db07..239c9e581 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -3771,8 +3771,21 @@ The more interesting ones are: \titem{reopen-log} Reopen the log files after they were renamed. If the old files were not renamed before calling this command, they are automatically renamed to \term{"*-old.log"}. See section \ref{logfiles}. -\titem {backup, restore, install-fallback, dump, load} You can use these - commands to create and restore backups. +\titem {backup ejabberd.backup} + Store internal Mnesia database to a binary backup file. +\titem {restore ejabberd.backup} + Restore immediately from a binary backup file the internal Mnesia database. + This will comsume quite some memory for big servers. +\titem {install-fallback ejabberd.backup} + The binary backup file is installed as fallback: + it will be used to restore the database at the next ejabberd start. + Similar to \term{restore}, but requires less memory. +\titem {dump ejabberd.dump} + Dump internal Mnesia database to a text file dump. +\titem {load ejabberd.dump} + Restore immediately from a text file dump. + This is not recommended for big databases, as it will consume much time, + memory and processor. In that case it's preferable to use \term{backup} and \term{install-fallback}. %%More information about backuping can %% be found in section~\ref{backup}. \titem{import-file, import-dir} \ind{migration from other software} -- 2.40.0