...
Export your current database using the following steps below. This process may take a while to run depending on the size of your database and the hardware configuration of your server. Make sure you have sufficient disk space and available memory for this operation. Note: Before starting the OrientDB console, you should adjust the memory settings and specifically the mx parameter. You can copy the mx setting from the setenv.sh file since it has probable already been tuned to support the size of your database. Since you don't need the OrientDB cache as much during the migration, you can increase the mx parameter a bit higher than its setting in the setenv.sh file. This section in the console script that you need to modify looks like this.
if [ -z "$ORIENTDB_OPTS_MEMORY" ] ; then
ORIENTDB_OPTS_MEMORY="-Xmx1024m "
fi
| Code Block |
|---|
$ cd /sysnet/openempi/openempi-3.5.7/data
$ /tmp/orientdb-3.0.38/bin/console.sh
OrientDB console v.3.0.38 - Veloce (build b636a4c891bc1b0f93df5bb16ec72dedee7a63e7, branch 3.0.x) https://www.orientdb.com
Type 'help' to display all the supported commands.
orientdb> connect plocal:./person-db openempi openempi
Connecting to database [plocal:./person-db] with user 'openempi'...OK
orientdb {db=person-db}> export database person-db
Database export completed in XXXXXXms
orientdb {db=person-db}> quit |
...