mO SharemO Share

We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!

How to do POS DB Restoration

We have noticed ongoing problems with POS Restoration. Being familiar with the appropriate steps for different situations and POS versions is essential.

Prerequisites:

  1. Backup must be generated by the POS Application

  2. Manually taking backups using SQL Server Management Studio or attaching database files are not covered in this article.

Different Scenarios for Restoration of POS DB

Scenario 1: Restoring in the same application environment

Important pre-requisites to ensure:

  • The POS program files were there and the POS was working fine before it crashed. This means we have the latest files from when the POS was last used.

  • If it exists then the POS Database should be dropped before proceeding to Restore.

After copying files, use our POS Restore utility for restoration.

 Scenario 2: Restoring in a fresh machine

In this scenario, users typically choose between two options: Restore or Copy the application folder from a customer-managed backup location and Fresh installation.

In either case, the first step is to determine the POS version that was in use before the crash.

Important Considerations -

Does POS Application File set Backup Exist

 

If POS Application Files Backup Does Not Exist (Fresh Installation):

 

Make sure to download and copy the correct patch. Using the wrong patch can cause errors due to the tight integration of the backup logic with the Restore application. Accurately identifying the POS version prior to the crash is critical to follow these guidelines effectively.

Need Help?

Should you face any issues after implementing these steps, please reach out to Ginesys support for further assistance.

Your attention to this critical process is greatly appreciated.