Updated
Find the actual source of your data
Ask where the POS application and database run: a counter computer, a local server or a cloud server. Record which machine holds the current records and which devices only connect to it. A copy of an application shortcut or installer is not necessarily a copy of the restaurant's data.
Ask the installer which supported backup procedure applies to that deployment. This guide does not claim that DeccanPro includes a particular automatic backup schedule or managed cloud backup service. Confirm the available method and responsibilities during setup.
Assign responsibility and storage
Decide who checks that backups complete and who follows up when they fail. Discuss an appropriate copy outside the primary device, access restrictions and retention with the responsible technical person. Avoid keeping every copy on the same device whose failure you are planning for.
Protect backup files because restaurant records may contain business or customer information. Store access details securely and limit them to the people who need them. Keep a simple dated record of successful checks without putting passwords into the checklist.
Demonstrate a restore away from production
Ask for a controlled restoration into a separate test environment. Confirm that representative menu and order records can be read there. Do not overwrite the live database to find out whether a backup works, and do not test with customer service in progress.
Write down the observed result, the person responsible and the recovery contact. Repeat the review when the server location or backup method changes. A usable plan names the steps and their owner; it does not rely on the assumption that either local or cloud hosting makes recovery automatic.
PUT IT INTO PRACTICE
Your checklist
- Primary data location identified
- Supported backup method and owner confirmed
- Separate storage and access controls discussed
- Restore demonstrated outside the live system