rt-importer(8) | Request Tracker Reference | rt-importer(8) |
rt-importer - Import a serialized RT database on top of the current one
rt-importer path/to/export/directory
This script is used to import the contents of a dump created by "rt-serializer". It will create all of the objects in the dump in the current database; this may include users, queues, and tickets.
It is possible to stop the import process with ^C; it can be later resumed by re-running the importer.
Certain records (notably queues and groups) will have their original Organization name prepended to them on import. This is primarily to avoid duplicate names (for example importing a General queue into an RT that already has one would otherwise cause a name collision error). If you are confident you won't have any name collisions in queues or groups, you may suppress this behavior by passing the --exclude-organization flag to "rt-importer".
The importer will pause and ask if you want to ignore the error and continue on or abort (potentially to restart later). Ignoring errors will result in missing records in the database, which may cause database integrity problems later. If you ignored any errors, you should run "rt-validator" after import.
This option can be dangerous and leave you with a broken RT!
Works only in conjunction with "--list".
Some dumps may have been taken as complete clones of the RT system, which are only suitable for inserting into a schema with no data in it. You can setup the required database state for the receiving RT instance by running:
/usr/sbin/rt-setup-database --action create,schema,acl --prompt-for-dba-password
The normal "make initdb" step will not work because it also inserts core system data.
2023-10-25 | perl v5.36.0 |