Warning! 
When restoring a binder all users must be out of Engagement or logged in using field mode.

• Restoring information with this utility will interrupt synchronization and prevent users from logging into the application. 
• This activity should not be performed while users are synchronizing and or actively logged into Engagement or Workpaper Manager on Terminal server, Citrix server or environments where the users local databases are on the SQL Server/Application Server. 
• If running any of the environments previously mentioned then all users will need to log out of Engagement or Workpaper Manager before continuing.

Note: Currently supported versions of Engagement and Workpaper Manager (v2021, v2020, v2019) may restore single binders using a backup generated on a prior year version of the application. Refer to step 10 for further details.

When using v2018 or older Engagement or Workpaper Manager and attempting to restore binders created on a prior year release, please instead follow this article:

• How can I restore a single binder from prior version of CCH® ProSystem fx® Engagement or Workpaper Manager?

If the current backup was created on the same version of Engagement or Workpaper Manager, or is otherwise outlined in step 10, please proceed with the steps below: 

1. Verify "Disable LFR to CFR synchronization," has been checked under Central File Room Properties within Engagement or Workpaper Manager Administrator Module
   1. Log into the Administrator module. 
   2. Right-click on the central file room(s), and click Properties.
   3. Put a check in the box next to Disable LFR to CFR Synchronization.
   4. Click OK.
   5. Repeat the process for any additional CFRs.
   6. Close out of Administrator. Module.
      • Note:  After restoring the binder from backup the checkbox will need to be unchecked before users can be allowed to sync again.
2. Stop and then start the Pfx and SQL services.
   • For instructions, please review our article How do I start, stop, or restart the CCH® ProSystem fx® Engagement or Workpaper Manager services?
   • Do not use the restart option for this purpose as there is the possibility it will not disconnect all users and processes.
3. Prevent the problem binder from being synchronized after the procedure has been completed in order to prevent the recovered binder from reverting to the problematic state.  
   • If possible, delete the binder in question from all Local File Rooms.
     • For data preservation purposes of the existing copy, a binder package may need to be created of the existing binder before deleting it locally from a local file room.
       • How do I create a binder package in CCH® ProSystem fx® Engagement?
   • Ensure that all users with a copy of the binder have been instructed to avoid synchronizing the binder until further notice.
4. On the server that hosts Engagement Administrator or Workpaper Manager Administrator database, use Windows File Explorer to browse out to ?:\Pfx Engagement\Admin\Utilities\Backup Restore, where "?" is the drive where Engagement or Workpaper Manager is installed.
   • If you are using Engagement or Workpaper Manager v2017 or older, double-click on BackupRestoreUtil.exe.
   • OR
   • If you are using Engagement or Workpaper Manager v2018 or newer, right-click on BackupRestoreUtil.exe and select "Run as Administrator" from the menu.
5. Click Next on the Welcome dialog.
6. After you have read and understand the information regarding backup, check the box and click Next.
7. Select Restore and check the box Binders only.
   • This will restore the binder's database-resident data.
8. Click the Browse button.
9. Select the database backup file (.bak) created and open the file. 
   • Below there will be displayed report of the databases stored in the backup and It will list at least seven databases. 
10. Select the database backup file (.bak) created and open the file.  
    • Currently supported versions of Engagement and Workpaper Manager may restore a binder from a SQL backup created in the two prior major versions of Engagement.  
      • The v2021 Backup & Restore utility can perform single binder restoration using a SQL backup created in v2020 or v2019. 
      • The v2020 Backup & Restore utility can perform single binder restoration using a SQL backup created in v2019 or v2018. 
      • The v2019 Backup & Restore utility can perform single binder restoration using a SQL backup created in v2018 or v2017. 
    • When selecting a .bak file created on a prior year release of Engagement or Workpaper Manager, a “Database Mismatch” prompt will occur. Click OK to proceed with the restore process.
11. Select the binder(s) you wish to individually restore. 
    • To make the binder(s) easier to locate, sort the list by any column you prefer. 
    • To sort by a particular column, click the box to the right of its column heading.
12. Once you have selected the binder(s) to restore, click Next
13. Click Restore.
14. Click Finish.
15. Restore the binder's workpapers using the firm's file backup for the server. 
    • First, determine the binder's workpaper path, then restore that folder.
    • To locate the workpaper path:
      1. Right-click the binder in the Administrator Module.
      2. Click Properties and then click on the Information tab.
16. Restore the path that was listed in the previous step.
    • Note: If a binder is restored to a client folder that no longer exists, the created client folder may display the identifying client GUID as the client name in the Central File Room. This can be manually corrected in the client properties after the restore process is completed.