What Should I Agree On Regarding Backups for Your Application?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
My PHP maintenance, from €60/month + VAT*, includes daily backups of the entire database and all files, retained for 7 days on my server. Before intervening, I agree on the scope with you; the restoration procedure must be specified for your application and does not imply a promised recovery time.
Criteria: describe what you need to be able to recover
I propose starting with the use of your application, not by choosing a backup tool. What information does your company enter? What documents does it need to consult? Which part of the operations worries you if it stops being available? You do not need to answer with folder names. An understandable description of the work you want to preserve allows technical questions to be prepared without assuming that any backup contains everything necessary.
In my PHP maintenance offering, I include backups, alongside security updates and bug fixes. I make daily backups of the entire database and all files, retained for 7 days on my server. The restoration procedure and verifications must be specified for your application; I do not publish a recovery time.
Proposed outline for backup scope
- MySQL database
- Operational tables and records that the application needs to reconstruct business state.
- Files and attachments
- Deployed code, configuration outside the repository, and documents or PDFs generated or uploaded by users.
- Retention policy
- Daily backups of the entire database and all files, retained for 7 days on my server. Restoration procedure to be specified for the project.
- Restoration testing
- Ability of the backup to bring up the application and allow consultation of its data in a controlled environment.
- Responsibilities and permissions
- Demarcation between automatic hosting provider backups and backups managed within PHP maintenance.
This outline is a proposal, not contracted coverage.
I would not ask you to fill in superficial answers just to close the document. If you do not know what information the application stores beyond what you see on screen, we would mark it as pending review. In the same way, I would prefer to leave a recovery condition unapproved rather than write «all included» without knowing what it means for your business. The scope must help make decisions, not hide open questions beneath a technical label.
What my offering proves and what it does not
I maintain existing PHP applications, including those I did not develop myself. Published maintenance has a starting price from €60/month + VAT* and includes the categories described on the homepage. That does not prove that your application's current backups are usable, nor does it constitute an audit of what your provider does. I would not assess their work without knowing the agreement and the evidence you can provide.
Reviewing your application requires analysing its specific situation. I make daily backups of the entire database and all files, and retain them for 7 days on my server. This coverage does not prove a verified restoration or establish a procedure or recovery timeframe.
How I would propose verifying a restoration
As a proposal to agree upon, I would describe a recovery situation and the outcome you need to review. Would seeing data be sufficient, or would an operation also need to be checked? What documents would need to be available? How would we identify the information that should correspond to the recovered point in time? These are preparation questions, not a test already conducted or a promise about what can be recovered today.
I would also propose agreeing on who authorises the review, on what environment it is carried out, and who validates the outcome. I would not use live data or alter production merely to prepare this conversation. The specific procedure requires a subsequent agreement. If shared recovery evidence does not yet exist, I would describe it as pending rather than as a passed check simply because a backup file exists.
To evaluate that evidence, I would propose keeping a readable description of what was checked and what was not included in the review. That way, we could distinguish the scope of the exercise from the general maintenance terms. I do not claim that this record already exists or follows a fixed format: it is a recommendation we would need to adapt and approve before using it as a procedure.
When you should NOT consider backups settled
I would not propose settling the matter if the only available information is «there is a backup» and you still do not know which application or content it refers to. Nor would I consider it settled if you need to recover documents that no one has included in the scope. This is not a conclusion about your installation; it is the clarity criterion I propose to avoid confusing a business expectation with an agreed deliverable.
From a technical standpoint, it is advisable to distinguish between general server snapshots provided by a hosting provider and specific backups of your PHP application's database and files. I would not describe either option as sufficient or superior by default. The trade-off I would review in each case is what it covers, what evidence it provides, and what responsibility falls to each party. Your provider's terms are information you must confirm, not facts deducible from this article.
How I would prepare it with you
My published process starts with a written diagnosis and defines deliverables, budget, and timeframe before development. To guide an inquiry about backups, I would propose explaining what tool you use and what you need to preserve. If you already have documentation about backups, you could describe what it states without attaching secrets or taking an intervention as authorised. The technical review and access credentials would be agreed upon afterwards.
To prepare your inquiry, indicate what PHP/MySQL application you have running, who currently manages the hosting, what data and documents are critical to your operations, and whether you also want a quote for any new feature. You can use that information to prepare the questions you need answered, without taking their answers as verification of a backup. If you also request a new feature, it is best to describe it separately, as my published offering distinguishes.
What question to bring to the review
I propose choosing a business task and completing this sentence: «If I needed to recover the application, I would want to verify that I can return to…». Then I would note down what information and documents are involved in that task, without yet asserting where they are or how they are backed up. That description can serve to prepare the scope of a verification. It does not guarantee that the outcome is possible with current backups: that is precisely a question we would need to review and agree upon, not a conclusion I can anticipate in this article.
What I would separate in a backup's technical inventory
To prepare a specific review, what components would need to be identified? The following questions do not claim that your installation has all of them, or that your hosting already backs them up.
- Relational database: MySQL dumps, tables, character sets, transaction handling, and consistency of recovered records.
- File system: Code, uploaded attachments, generated PDFs, and environment configuration.
- Server snapshots: Scope of server snapshots relative to the application backup and the inventory of data and documents.
Then I would connect each component to a task you need to recover. If a document appears without its record, or a record without the file it references, an issue would remain to be reviewed before describing recovery as verified.
Frequently asked questions
What data and files do I cover?
I back up the entire database and files of your application daily, and retain the copies for 7 days on my server. To prepare for recovery, I review with you what information and documents are involved in its use. That coverage does not equate to a verified restoration or a resolution deadline.
How do I verify recovery?
I back up the entire database and files daily and retain each copy for 7 days on my server; that does not equate to a verified restoration or a guaranteed recovery time. To prepare a potential check, what database and files would need to be restored, who would authorise the test, and what operations would need to be reviewed?