Pervasive Backup Agent Is Not Compatible with Creating Work Files

Release Date: 09/12/2017

Q - After PSQL 11 SP2, are both Backup Agent or Volume Shadowing Service (VSS) included for my backup purposes?  Which one should I use?

A - Based on Pervasive's recommendation:

Which Backup Solution Should I Use?
If you are running PSQL on a Windows platform and your backup software is VSS-aware, Pervasive recommends using the PSQL VSS writer as part of the VSS framework. If your backup software is VSS-aware, PSQL is automatically invoked during VSS backups.

If your backup software is not VSS-aware, the best choice is to use Backup Agent with your backup software.

How to Install Backup Agent
You can use PSQL 11 SP2 or after Windows Installation Package to install Backup Agent.  You can also download from the website.

How to Use Backup Agent
Most of the backup software offers pre and post script.  Assuming you are using 64-bits, in the pre-script area, you will add the following line to start Backup Agent:
    pvbackup64 -on
In the post-script area, you will add the following command to end Backup Agent:
    pvbackup64 -off

Backup Agent Precaution
Backup Agent works with backup software to ensure accurate, reliable point-in-time recovery for partial or complete backups. Backup Agent works transparently during a backup session by automatically placing open files into a continuous operations mode while the backup is in process. Any changes to the files that occur during the backup are buffered and applied to the file after the backup is complete.

Through our experience, the main issue we found with Backup Agent is that when a user leaves Backup Agent on after backup finishes, it not only creates large delta files that can slow down performance, but can also compromise the integrity of your data. In addition, we found that any Elliott user will not be able to create any work file while Backup Agent is on.

This is because Backup Agent will try to create a delta file (extension ^^^) for any changes after Backup Agent starts. But the nature of “Work File” is to wipe out the file and start anew, which is incompatible with the Backup Agent delta file concept.

If Backup Agent is started at nighttime, when no users are in the system, then this work file conflict issue won't occur. But if Backup Agent did not complete for some reason, then the next day users will run into the issue when running the process that will require create work files.  Below is an example of what happens when a user tries to run the Elliott Financial Statement, which requires the creation of a GL Statement Work File. If Backup Agent is started, then the user will receive the following error:

    Btrieve Error 025 on GL Statement Work File

Therefore, if you wish to use Backup Agent each night to perform backup, you should make sure that Backup Agent is turned off the next day.  You can do so by using this command line utility:
    pvbackup64 -status
Or you can use the GUI utility, pvbackupgui.exe:

The above example shows that Backup Agent was not started on this machine.


Pervasive PSQL

  1. Btrieve Error Codes 001 - 199
  2. Btrieve Error Codes 3000 - 3099
  3. Btrieve Error Codes 3100 - 3199
  4. PSQL Version Required by Each Elliott Version
  5. Do I Need to Change PSQL Server Engine Default Parameters After Installing It?
  6. New Elliott PSQL Server Processor and RAM Suggestions
  7. Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?
  8. Received "Your Computer Does Not Have PSQL 10 or 11 Client " Even though PSQL Client Is Just Installed
  9. Btrieve Error 161 on Password File When Starting Up Elliott
  10. Problems with Using Pervasive Rebuild Utility on APOPNFIL and AROPNFIL Tables
  11. Security Issue with Installing PSQL Client Remotely on User's Workstation
  12. PSQL and Distributed File System (DFS)
  13. How Do I Turn on PSQL Relational Engine Security?
  14. An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error
  15. Btrieve Error 025 on COP Open Order by Salesman Report
  16. What Is the *.^01 File for My PSQL Btrieve Table?
  17. Suggested Files to be Monitored by Audit Master
  18. Pervasive Backup Agent Is Not Compatible with Creating Work Files
  19. Hardware Recommendations for Your PSQL Database Server
  20. How to Optimize SQL SELECT Statement When Retrieving Data from Invoice History
  21. New User-Defined Functions in Elliott DDF
  22. How to Improve Query Performance When Retrieving Data from Notes & Invoice History
  23. How to Retrieve Tracking Number for an Order from Notes
  24. Actian PSQL Not Started Automatically After Server Reboot
  25. Create a New Database in the PCC for Relational Engine Access
  26. Slow PSQL Relational Engine Performance
  27. IPV6 May Cause Problem for PSQL 11 Relational Query
  28. DDF Files in DATA Folder May Confuse PSQL
  29. What to Do When PSQL 11 License Is Disabled
  30. Quick Installation Guide for Audit Master
  31. Quick User Guide for Audit Master
  32. PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider
  33. Your Firewall Needs to Allow Outbound Traffic to the Netherlands for PSQL Licensing Server Purposes
  34. A Case of Btrieve Error 046 on ARCRCLOG A/R Credit Card Log File
  35. A Support Case of Migrating to Different Version of DDF
  36. How to Clear the Message "Unable to Read your Users record (9/068)"
  37. Setup of the PSQL 13 Report Engine
  38. How to Create CPHSTTRX_VIEW with Left Join to CPINVHDR Due to Invoice Database Archive
  39. How to Access Elliott's Data by Using Query in Microsoft Office Excel 2019
  40. Elliott Database Naming Convention
  41. What Does Btrieve Error 080 Mean?

Feedback and Knowledge Base