1RT-IMPORTER(1)        User Contributed Perl Documentation       RT-IMPORTER(1)
2
3
4

NAME

6       rt-importer - Import a serialized RT database on top of the current one
7

SYNOPSIS

9           rt-importer path/to/export/directory
10
11       This script is used to import the contents of a dump created by
12       "rt-serializer".  It will create all of the objects in the dump in the
13       current database; this may include users, queues, and tickets.
14
15       It is possible to stop the import process with ^C; it can be later
16       resumed by re-running the importer.
17
18       Certain records (notably queues and groups) will have their original
19       Organization name prepended to them on import. This is primarily to
20       avoid duplicate names (for example importing a General queue into an RT
21       that already has one would otherwise cause a name collision error). If
22       you are confident you won't have any name collisions in queues or
23       groups, you may suppress this behavior by passing the
24       --exclude-organization flag to "rt-importer".
25
26   OPTIONS
27       --list
28           Print a summary of the data contained in the dump.
29
30       --originalid cfname
31           Places the original ticket organization and ID into a global custom
32           field with the given name.  If no global ticket custom field with
33           that name is found in the current database, it will create one.
34
35       --exclude-organization
36           Ordinarily certain records (groups, queues, the --originalid custom
37           field) include the organization name of the original RT instance.
38           Use this option to suppress that behavior and use the original name
39           directly.
40
41       --ask
42           Prompt for action when an error occurs inserting a record into the
43           database.  This can often happen when importing data from very old
44           RTs where some attachments (usually spam) contain invalid UTF-8.
45
46           The importer will pause and ask if you want to ignore the error and
47           continue on or abort (potentially to restart later).  Ignoring
48           errors will result in missing records in the database, which may
49           cause database integrity problems later.  If you ignored any
50           errors, you should run "rt-validator" after import.
51
52       --ignore-errors
53           Ignore all record creation errors and continue on when importing.
54           This is equivalent to running with "--ask" and manually typing
55           "ignore" at every prompt.  You should always run "rt-validator"
56           after importing with errors ignored.
57
58           This option can be dangerous and leave you with a broken RT!
59
60       --dump class[,class]
61           Prints Data::Dumper representations of the objects of type class in
62           the serialized data.  This is mostly useful for debugging.
63
64           Works only in conjunction with "--list".
65

CLONED DATA

67       Some dumps may have been taken as complete clones of the RT system,
68       which are only suitable for inserting into a schema with no data in it.
69       You can setup the required database state for the receiving RT instance
70       by running:
71
72           /usr/sbin/rt-setup-database --action create,schema,acl --prompt-for-dba-password
73
74       The normal "make initdb" step will not work because it also inserts
75       core system data.
76
77
78
79perl v5.30.1                      2020-03-09                    RT-IMPORTER(1)