dtietze wrote:
Dave wrote:
only real complication I can think of is the filestore (if you use filesystem as the store rather than the DB))
And even for that there's a "nikuadmin" command (nikuadmin filestore migrate) that you can use to internalize the filestore into the database before you create the backup for the migration, and then dump it all out again, also using nikuadmin, on the target machine.
Daniel
v13:
$NIKU_HOME/bin/serviceant -f $NIKU_HOME/.setup/scripts/search.xml -projecthelp
v8 / v12:
$NIKU_HOME/bin/nikuant -f $NIKU_HOME/.setup/scripts/search.xml -projecthelp
Buildfile: C:\Clarity\13.0.1\.setup\scripts\search.xml
Main targets:
...
migrate Migrate documents from filesystem to database
...
Default target: usage
Please use this command ("[niku]admin search migrate") if, and only if, the intention/requirement is to permanently change from storing files directly on the disk, into the database. It is not a bi-directional command or action, there are no supported ways to undo it again aside from rolling back your system and data to a consistent point prior to running this command. In at least v12.1 and above, the command also first requires you to specifically set (and save) in the CSA the setting "Store files in database" as a safeguard, else it will assume you invoked the command by accident and will not run if the setting is still on "Store files on disk" instead (as per $NIKU_HOME/.setup/scripts/dmsblob.xml).