SYSPRO Embedded Analytics: DR Guidelines

This article provides Disaster Recovery (DR) guidelines in relation to the SYSPRO Embedded Analytics feature.

Best practice advise is provided in the following areas:

  • Backup and restoration of the PostgreSQL database in the event of a disaster

  • Troubleshooting related to PostgreSQL

  • Frequently asked questions

PDF version

Please note that every DR plan is unique as it takes into account custom business needs, recovery objectives, and the system vulnerabilities of a specific organization. Therefore, the information contained within this article is not meant to be a one-size-fits-all solution. Instead, it serves as a starting point that should be adapted based on the unique needs and requirements of your organization's environment.

Overview

Disaster recovery is a vital aspect of any business continuity plan, ensuring that the essential operations of an organization can continue even in the event of a major disruption such as a natural disaster, cyber attack, or system failure. A well-constructed disaster recovery plan has the potential to reduce downtime, minimize the financial impact of an outage and provide a sense of security.

However, it's crucial to understand that every organization is unique, and the specific disaster recovery needs of one company can differ greatly from another. This is why it's imperative to thoroughly evaluate and verify any disaster recovery advice before implementing it in your own environment.

The need for a reliable and practical disaster recovery plan is crucial for any business, as without such a plan, there is limited protection from the impact of significantly disruptive events. This guide provides suggested guidelines and information to help you develop a disaster recovery plan that is suitable for your organization.

PostgreSQL Backup Process

This section provides a guideline for backing up your PostgreSQL databases:

  1. STOP ALL ZOOMDATA SERVICES

    • It is very important for the backup process that all of the zoomdata services are stopped. Otherwise, when attempting to perform a backup, the process will fail to create the required .dump file.

    • It is imperative that you stop the zoomdata_consul service first due to the other zoomdata services that have a dependency on it. Therefore, we recommend stopping the services in the following order:

      1. Zoomdata_consul

      2. Zoomdata_edc_* (i.e. data sources or connectors)

      3. Zoomdata_query_engine

      4. Zoomdata_data_writer_postgresql

      5. Zoomdata_screenshot_service

      6. Zoomdata_service

  2. BACKUP ZOOMDATA DATABASES

    The following provides sample scripts using a command called pg_dump to execute the backups to a file type named .dump.

    See the following link for more information regarding pg_dump and related commands:

    https://www.postgresql.org/docs/current/app-pgdump.html

    You can either save these scripts to file or copy and paste them into Windows PowerShell, and then update as required before running them.

    Ensure to validate and update these scripts accordingly for your environment before using them.

    There are various methods that can be used to connect and authenticate to the pg_dump command:

  3. REVIEW YOUR BACKUP FILES

    Ensure that your backup files have processed correctly.

    Based on the sample scripts and default databases shipped with SYSPRO Embedded Analytics, you should have the following backup files within the SEA folder of your Temp drive:

    • zoomdata.dump

    • zoomdata-keyset.dump

    • zoomdata-qe.dump

    • zoomdata-upload.dump

    • zoomdata-user-auditing.dump

  4. START ALL ZOOMDATA SERVICES

    Ensure that you always start the zoomdata_consul service first, due to the other services' dependency on it.

    Therefore, we recommend that you start the services in the following order:

    1. Zoomdata_consul

    2. Zoomdata_edc_* (i.e. data sources or connectors)

    3. Zoomdata_query_engine

    4. Zoomdata_data_writer_postgresql

    5. Zoomdata_screenshot_service

    6. Zoomdata_service

PostgreSQL Restore Process

This section provides a guideline for restoring your PostgreSQL databases from the backup copy:

  1. STOP ALL ZOOMDATA SERVICES

    • It is very important for the restore process that all of the zoomdata services are stopped. Otherwise, when attempting to perform a restoration, the process will fail to create the required zoomdata database.

    • It is imperative that you stop the zoomdata_consul service first due to the other zoomdata services that have a dependency on it. Therefore, we recommend stopping the services in the following order:

      1. Zoomdata_consul

      2. Zoomdata_edc_* (i.e. data sources or connectors)

      3. Zoomdata_query_engine

      4. Zoomdata_data_writer_postgresql

      5. Zoomdata_screenshot_service

      6. Zoomdata_service

  2. RESTORE ZOOMDATA DATABASES

    The following provides sample scripts using a command called pg_restore to execute restore commands from the .dump files.

    See the following link for more information regarding pg_restore and related commands:

    https://www.postgresql.org/docs/current/app-pgrestore.html

    You can either save these scripts to file or copy and paste them into Windows PowerShell, and then update as required before running them.

    Ensure to validate and update these scripts accordingly for your environment before using them.

    There are various methods that can be used to connect and authenticate to the pg_restore command:

  3. START ALL ZOOMDATA SERVICES

    Ensure that you always start the zoomdata_consul service first, due to the other services' dependency on it.

    Therefore, we recommend that you start the services in the following order:

    1. Zoomdata_consul

    2. Zoomdata_edc_* (i.e. data sources or connectors)

    3. Zoomdata_query_engine

    4. Zoomdata_data_writer_postgresql

    5. Zoomdata_screenshot_service

    6. Zoomdata_service

Potential Error Messages

FAQs