1RT-IMPORTER(1) User Contributed Perl Documentation RT-IMPORTER(1)
2
6 rt-importer - Import a serialized RT database on top of the current one
7
9 rt-importer path/to/export/directory
10 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 It is possible to stop the import process with ^C; it can be later
16 resumed by re-running the importer.
17 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 OPTIONS
27 --list
28 Print a summary of the data contained in the dump.
29 --quiet
31 Suppresses the display of progress bars during an import. This
32 option is implied when the output isn't going directly to a
33 terminal.
34 --originalid cfname
36 Places the original ticket organization and ID into a global custom
37 field with the given name. If no global ticket custom field with
38 that name is found in the current database, it will create one.
39 --exclude-organization
41 Ordinarily certain records (groups, queues, the --originalid custom
42 field) include the organization name of the original RT instance.
43 Use this option to suppress that behavior and use the original name
44 directly.
45 --ask
47 Prompt for action when an error occurs inserting a record into the
48 database. This can often happen when importing data from very old
49 RTs where some attachments (usually spam) contain invalid UTF-8.
50 The importer will pause and ask if you want to ignore the error and
52 continue on or abort (potentially to restart later). Ignoring
53 errors will result in missing records in the database, which may
54 cause database integrity problems later. If you ignored any
55 errors, you should run "rt-validator" after import.
56 --ignore-errors
58 Ignore all record creation errors and continue on when importing.
59 This is equivalent to running with "--ask" and manually typing
60 "ignore" at every prompt. You should always run "rt-validator"
61 after importing with errors ignored.
62 This option can be dangerous and leave you with a broken RT!
64 --dump class[,class]
66 Prints Data::Dumper representations of the objects of type class in
67 the serialized data. This is mostly useful for debugging.
68 Works only in conjunction with "--list".
70 --no-auto-commit
72 Don't auto commit to database. When this flag is used, it will
73 commit only once for each data file. This could boost performance
74 in some cases.
75 --batch-user-pricipals NUMBER =item --batch-group-pricipals NUMBER
77 The number of user/group principals to create in batch beforehand.
78 Default is 0. This is to improve performance for not-cloned
79 serialized data of big instances, usually you don't need to specify
80 this.
81 --batch-size BATCH_SIZE
83 Create objects in batch. Default is 0, meaning batch processing is
84 not enabled. This is for data serialized with "--clone" or "--all".
85 For cloned serialized data, each batch processing will also take
86 place in a separate child process.
87 --max-processes MAX_PROCESSES
89 The number of max allowed child processes for batch processing.
90 Default is 10. This is for cloned serialized data only.
91
93 Some dumps may have been taken as complete clones of the RT system,
94 which are only suitable for inserting into a schema with no data in it.
95 You can setup the required database state for the receiving RT instance
96 by running:
97 /usr/sbin/rt-setup-database --action create,schema,acl --prompt-for-dba-password
99 The normal "make initdb" step will not work because it also inserts
101 core system data.
102perl v5.38.0 2023-10-22 RT-IMPORTER(1)