It is highly recommended to implement a Backup & Restoration Process Plan for Production Instances. The following things should be included in the Backup & Restoration process:
pack.sh and install.sh files are available in parent folder of $TRINITI_HOME to take care of backup and restoration process.
Backup process:
One-time Cold Backup and Hot Backup (Hourly Index Backup) of Application Implementation database which contains transactional data.
Daily Backup in the compressed format of TrinitiApps folder which is assigned to $TRINITI_HOME environment variable.
Log files folders and Cache files folders (For example: $TRINITI_HOME/glassfish4/glassfish/domains/domain1/osgi-cache) should be excluded in the backup process.
One-time Cold Backup and Hot Backup (Daily Index Backup) of TrinitiApps Configuration database.
Keep a copy of backup files in another storage.
Restoration process:
Backup should be tested by cloning PROD to TEST for at least a month.
Post-Cloning (Post-Restoration) activity should be done if the restoration is not done on PROD instance. Post-Cloning activity takes care of changing the deployment paths and URLs for the target instance.