Back up project data and configuration

The amount of effort that you put into your automatic backups depend on your disaster recovery plan and the amount of acceptable data loss.

Back up the Project configuration file

Backup your project configuration file on a regular basis for disaster recovery purposes. We recommend that you backup your project once a day. You can back up your AVEVA™ Production Management project configuration with a SQL Server Maintenance Plan. For more information, see About SQL Server maintenance.

Back up the AVEVA™ Production Management Management Database

Backing up your data is even more important than backing up your project configuration file. Assess your own business requirements to know how often you want to backup. In the event that you want to restore to your last data backup, how much data can you afford to lose.

Choose a level of backup

The complexity of your automatic backups depend on your disaster recovery plan and the amount of acceptable data loss. These are three suggested levels of backup planning: Minimum, Medium, and Full.

• Minimum backup plan - Backup the Project configuration and AVEVA™ Production Management database

  At the very least, back up these two databases:

  • AVEVA™ Production Management project configuration

  • AVEVA™ Production Management database

    You can automatically scheduled backups for both the Project configuration database and the AVEVA™ Production Management Database through a SQL Server Maintenance Plan.

• Medium backup plan - Backup the streams and queues

  At the next level, it would be possible to write scripts to back up streams and queues.

  • Streams

  • Data Delivery Queue

  • Metrics Queue

• Full backup plan - Backup licenses and dashboards

  For a complete backup and restore, backup each extra item associated with your project.

  • Licenses

  • Dashboards

  • Custom Clients

Related topics

• Monitoring the Server

• Use the Health Management utility

• Monitor SQL Server