Complete Application Backup

This requires accessing files on your server.

This requires accessing one or more database applications on your server(s).

An iDashboards administrator account isn't required but may be helpful.

Question:

What would be the best method to back up iDashboards in the event of a server crash?

Answer:

Responsible IT planning always includes a solid backup strategy for recovering from small to catastrophic failures. Because this topic can evolve into an enormous undertaking, here are some stages of how to backup the iDashboards application

Option #1 (Best): Image Backup

A System Image is always the best backup. A system image prevents the need of any recovery configuration steps that may occur due to setting changes. For example, Tomcat, Java and SQL Server. If these settings change the application will need to be manually reconfigured so that it can function properly on a new/restored system.

Option #2 (Good): Application Specific Backup

It is good to know the various components of our application and have a little knowledge on how they work together. Framework components (Tomcat, Java and your database server) are all required to use iDashboards. For properly restoring these components, locate each system and each of the related configuration files. In addition to the framework components, include the application directory (explained below).

Option #3 (Good Enough): Minimum Backup:

Only backing up the minimum may cause difficulty in restoring to a new server in the event of a catastrophic failure. There may be costly reconfigurations but the core system can be functional.

1. Database

For more information, go here (🔗link) to the article "SQL Server: Backing Up Your Databases".

1. The iDashboards Repository Database Repository
   1. This is where all of our application data is stored (chart/dashboard/user/groups...etc.)
   2. You can check the db.url property of the ivizgroup.properties file in the <install directory>\ivizgroup\config folder for the location of the repository. The iDashboards Installation directory is referred to as the ivizgroup directory.
   3. The database is likely called "idashboards"
2. Workbook Database
   1. This is where your Excel or CSV files get uploaded
   2. This database might be called something like "idashboards_workbooks"
3. Data Store
   1. These are Data Sources which iDashboards can use for creating data, like when using Forms.
   2. The primary database might be called something like "idashboards_datastore"
4. Data Hub 
   1. Same as a "Data Store" (above), these are Data Sources which the Data Hub can use for ETL purposes.

2. Application Directory

1. Often called "ivizgroup", or "Home Directory" within the documentation, this is where critical and essential files are saved. While some of these files might have options to be replaced (like your logo file or a dashboard thumbnail), there are files here which can never be replaced (API files, etc.). 
   1. Application configuration files
      • Connection information to the repository database (ivizgroup.properties)
      • All application images (content, graphics, previews)
      • The iDashboards license file (config)
      • The iDashboards log files (logs)
      • JDBC drivers to data sources (drivers)
      • Critical API files
   2. Location options might include:
      • C:\Documents and Settings\tomcat\ivizgroup
      • C:\ivizgroup\idashboards

Restoring

How to restore iDashboards is based on the backup strategy used (above). If a System Image is not restored, then there will be manual tasks to get each component installed and configured. This type of restoration process will include copying files/directories as well as configuring an application through the offered interface.

For a Application Specific Backup or Minimum Backup, restore the repository database and the ivizgroup directory and point the application server to the ivizgroup folder. This will get the application up and running in a short amount of time. Please contact iDashboards Support for further assistance.