This article details how to perform maintenance on GhostPractice databases and prepare them for disaster recovery.
DBCC CheckDB SQL Command
Use the DBCC CHECKDB SQL Command on the GhostPractice databases
Any Database Consistency errors will be displayed on the last 2 lines of the results panel. If there are any allocations on consistency errors, please advise us immediately.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'Mustang'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
This will identify any potential problems before backing up the databases
Recovery from Backup
- A new environment (Hardware and Windows Operating system) needs to be set up and made available.
- The save or new version of SQL and SQL Database management studio needs to be set up.
- Databases need to be retrieved from off-site storage to the new environment and restored in SQL.
- GhostPractice can then be installed and configured.
Disaster Recovery Testing
- Recovery testing must be scheduled and carried out at least once every six months.
- The IT Service Provider should inform and request assistance from GhostPractice if required.
- The IT Service Provider must set up a testing environment on a separate server or appropriate machine.
- The IT Service Provider must obtain the backup data from remote storage and provide the backup files to GhostPractice if they are to conduct the restore.
- GhostPractice can be requested to perform a database restore and get the system ready for end-user testing.
-
Testing Backups Restored
- The Client Manager must elect the appropriate user(s) that will participate in the testing
-
Elected users must select the following, at a minimum:
- Random invoices/credit notes that were produced
- Random matters to perform work on
- Attach and update documents and reports
This will test the ability to restore and access all 3 GhostPractice databases.