[Rt-commit] rt branch, 4.4/docs-migrate-mysql-to-pg, updated. rt-4.4.3-42-g539fcff8a

Gergely Nagy algernon at bestpractical.com
Thu Oct 11 11:53:05 EDT 2018

The branch, 4.4/docs-migrate-mysql-to-pg has been updated
       via  539fcff8a8d9b3d62fdb46e3646a60c6aca3c53a (commit)
      from  a89afbb322f22565bb9387e5822d8785bc2a62cd (commit)

Summary of changes:
 docs/backups.pod | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

- Log -----------------------------------------------------------------
commit 539fcff8a8d9b3d62fdb46e3646a60c6aca3c53a
Author: Gergely Nagy <algernon at bestpractical.com>
Date:   Thu Oct 11 17:51:20 2018 +0200

    Update the rt-serializer arguments in the MySQL->Pg migration docs
    When doing a full database migration, the `--clone` option should be used, both
    to speed up the process (because it doesn't do as much validation then), and to
    do a full export.

diff --git a/docs/backups.pod b/docs/backups.pod
index a18f6bc46..346662f8f 100644
--- a/docs/backups.pod
+++ b/docs/backups.pod
@@ -171,7 +171,7 @@ to run the tool, L<rt-validator>, to make sure there aren't any errors within
 your database:
         /opt/rt4/sbin/rt-validator --check &&
-                /opt/rt4/sbin/rt-serializer --directory ~/path/to/store/serialized/data
+                /opt/rt4/sbin/rt-serializer --clone --directory ~/path/to/store/serialized/data
 =item Setup Database
@@ -261,4 +261,3 @@ Simply saving a tarball should be sufficient, with something like:
     tar czvpf rt-backup-`date +%Y%m%d`.tar.gz /opt/rt4 /etc/aliases /etc/httpd ...
 Be sure to include all the directories and files you enumerated above!


More information about the rt-commit mailing list