Maintaining the system

This section will walk you through the basics of regular system maintenance: understanding logs, backing up and restoring the system. For more information on this topic take a look at the Related documents.

The easiest and most safe setup of backup routines is to backup the whole Performance Canvas (default C:\Program files\Performance Canvas\*.* /s)directory with all folders and files below.

Normally it is not needed to have a backup of all program files. To create a more slim backup it is normally enough to backup the following files:

\Performance Canvas\

\Performance Canvas\store\*.* /s

If you have a complete backup of the whole Performance Canvas directory, follow these steps:

  1. Restore the Performance Canvas directory where you want it (default C:\Program Files).
  2. Check the port number (default dsp.port=80) in the file
  3. Check the settings in \Performance Canvas\bin\
  4. Run \Performance Canvas\bin\Install Service.bat to recreate the service.
  5. Start the service from the Control Panel Services.

If you do not have a complete backup (you only have the store-folder), follow these steps:

  1. Run the pc09.exe install package Basic Install
  2. Copy all files from the backuped store folder, except for the \deleted, \properties, \role, \settings, \temp and \tmp folders, into the new “Performance Canvas\store\” folder. To get the old data sources it is also needed to copy \settings\cubes.xml to the new store folder.
  3. Start the service from the Control Panel Services.

The main log file is located in \Performance Canvas\store\logs\dsp.log

There are several log levels possible to choose in the admin console and they corresponds to the property dsp.log in \Performance Canvas\ file with their number (#) in the table below. Choosing high log levels will decrease performance.

Sr.No.Log levelDescription
0FatalLogs only fatal errors. Recommended level for a production environment unless troubleshooting is needed.
1ErrorLogs all errors. Possible level for a production environment unless troubleshooting is needed.
2WarningLogs all errors and warnings.
3InfoLogs all errors and warnings with additional information.
4DebugGives a lot of information. Will have performance implications. Is only to be used if there is an issue that you would like support on, please set log level to debug, perform the actions that you have an issue with, and attach that log file to your support request. That will allow us to respond faster and more accurately since we are able to instantly look at the problem. Remember to change the log level back afterwards.
see also →
Administration console reference documentation
Advanced Administration reference documentation
  • user/maintenance.txt
  • Last modified: 2013/07/16 14:12
  • (external edit)