A database problem can feel urgent, especially when people cannot access important records or an application stops working. Before attempting repairs, pause changes that could overwrite data and collect a few key details. Knowing the database type, available backups, and exactly what users are experiencing helps a recovery specialist choose safer next steps. A short, organized handoff can also reduce repeated troubleshooting and help preserve the best available recovery options.
Identify the Database
Write down the database product and version if you know them, such as Microsoft SQL Server, MySQL, PostgreSQL, Oracle, or SQLite. Note the operating system and whether the database runs on a physical server, virtual machine, cloud service, or a local computer. If you are unsure, capture the application name and ask your IT provider to confirm rather than guessing.
Record where the database files are stored and which applications or teams depend on them. Include the server or device name, the affected database name, and whether the system is production, test, or development. Do not send passwords in an ordinary email. Share access details only through a secure method arranged with the recovery provider.
Gather Backup Details
List every backup you know about, including full, incremental, transaction-log, or cloud backups. For each one, note its date and time, storage location, and whether anyone has confirmed that it completed successfully. Check backup software or cloud dashboards for job status, but avoid restoring or overwriting the affected database until a recovery plan is in place.
Keep copies of backup files and related logs unchanged. If possible, note the last time the database was known to work and the most recent backup that was tested. A backup may be incomplete, outdated, or tied to a particular database version, so preserve the original files and explain any uncertainty to the person assessing recovery.
Describe the Symptoms
Write down what happens when someone tries to use the database. Include exact error messages, screenshots, affected features, and whether the issue appears for everyone or only certain users. Note when symptoms first appeared, whether they are constant or intermittent, and what changed just before the problem began.
Record any recent events that might help explain the failure, such as a power outage, system update, application deployment, storage alert, hardware issue, or accidental deletion. Include actions already taken, who performed them, and the results. Avoid repeatedly restarting services, running repair tools, or deleting files; those steps can change evidence or reduce recovery options.
Prepare a Clear Handoff
Put the information in a brief timeline: last known working time, first reported problem, backup dates, and troubleshooting attempts. Identify how urgent the database is, which business processes are affected, and whether the system is still running. Be clear about what must be recovered, such as the full database or a particular table or time period.
Keep the affected system as unchanged as practical while you arrange an assessment. If the database is on a device showing signs of hardware failure, avoid unnecessary use and tell the recovery provider before restarting it. Raleigh Data Recovery can review the information and discuss next steps; share sensitive files or access details only through an agreed secure channel.
A calm, organized handoff starts with the database type, backup history, symptom timeline, and a record of changes already made. Preserve original files and avoid repair attempts until you understand the risks. If you need help assessing the situation, contact a qualified database recovery service and ask how to share information securely.