Every backup through the CCH® ProSystem fx® Engagement or Workpaper Manager Backup Restore Utility should produce a log file on completion. 

To verify the successful execution of the CCH® ProSystem fx® Engagement or Workpaper Manager Backup Restore Utility:

1. Check the directory for the log file.
   • ?:\Pfx Engagement\Admin\Utilities\Backup Restore
     • ? = Drive/Path where the program has been installed.
   • Locate the log file for the time frame in question.
     • Log file name example:
       • "LogFileForBR03272020 - 14 51 30"
       • Notice the timestamp in the file name above.
         • 03 = March
         • 27 = 27th day
         • 2020 = Year
         • 14 = 2PM
         • 51 = 51 Minutes after the hour
         • 30 = 30 seconds of the minute.
       • This should timestamp is when the back  up was started
       • The Windows "Modified Date" should be the time the backup process finished.
     • If the above example backup above had failed, the log file name should be appended with "FAILED"
       • Failed log file name example:
         • "FAILED - LogFileForBR03272020 - 14 51 30"
2. Check the log file contents even if the name does not indicate "FAILED"
   • Open the most recent log file in the directory. Open in Notepad
     • Search the file for the words "error" and "failed"
       • Select some text in the first line of the log file.
       • Edit>Find
       • Type the word "error" w/out the quotes into the find box
       • Leave the direction selected as "down"
         • \
       • If "error" is not found, change the criteria to the word "failed"
         • 
       • If either "error" or "failed" are found in the log files please contact support for further assistance.
         • How do I contact CCH Axcess™, CCH® ProSystem fx®, Sales & Use Tax, and Account Services product support?
3. Check the actual backup location where the SQL backup(.bak) is stored when the CCH® ProSystem fx® Engagement or Workpaper Manager Backup Restore Utility is finished.
   • Visually inspecting the backup files on a regular basis is advised for assurance of continuity measures.
     • Things to verify:
       1. Is there a recent backup file at all?
       2. Is the recent backup file incrementally larger than the last?
          • In most occasions the newer .bak file will be larger than the last due to the day's production getting synchronized into the central databases.
       3. How many files should I be seeing here?
          • In some cases you may be running a batch file to clean up this directory.
            • If you programmatically clean the directory please make sure that you are backing up the directory to another 3rd party prior to deleting the older backups if you want any recovery options of restoring any of the older time frame backups.