Are there any side effects of clearing ArtifactHit and ArtifactHitBin?
They are about 85% of the data on a client install (or at least, when excluding them from the entity snapshot, the resultant zip file is reduced by about that).
Are there any side effects of clearing ArtifactHit and ArtifactHitBin?
They are about 85% of the data on a client install (or at least, when excluding them from the entity snapshot, the resultant zip file is reduced by about that).
Just following up, there don’t seem to be any repercussions, and depending on your traffic, particularly if you use find as you type kind of drop-downs, omitting ArtifactHit and ArtifactHitBin from the snapshot exports greatly reduce the size.
And, also, FWIW, if it helps anyone, we create snapshots from client machines and then locally do:
Client Machine:
Local Machine
Where backupH2.sh is:
#!/usr/bin/env bash
if [ -z "$MOQUI_HOME" ]; then
MOQUI_HOME=~/src/moqui
fi
backup_root=~/src/MoquiBackup/MoquiH2Backup
rm -rf ${backup_root}/backup$1
mkdir -p ${backup_root}/backup$1/db
cp -R $MOQUI_HOME/runtime/db/derby ${backup_root}/backup$1/db
cp -R $MOQUI_HOME/runtime/db/h2 ${backup_root}/backup$1/db
cp -R $MOQUI_HOME/runtime/db/orientdb ${backup_root}/backup$1/db
cp -R $MOQUI_HOME/runtime/elasticsearch ${backup_root}/backup$1
Where restoreH2.sh is:
#!/usr/bin/env bash
if [ -z "$MOQUI_HOME" ]; then
MOQUI_HOME=~/src/moqui
fi
backup_root=~/src/MoquiBackup/MoquiH2Backup
gradle cleanDb
cp -R ${backup_root}/backup$1/db/derby ${MOQUI_HOME}/runtime/db/
cp -R ${backup_root}/backup$1/db/h2 ${MOQUI_HOME}/runtime/db/
cp -R ${backup_root}/backup$1/db/orientdb ${MOQUI_HOME}/runtime/db/
cp -R ${backup_root}/backup$1/elasticsearch ${MOQUI_HOME}/runtime/
It makes testing and retesting on client machine data much easier.