Backup & Business Continuity Policy
What has to be backed up to restore PersivX, how often and where, how recovery is tested, and how long an outage may last.
| Policy owner | Persiv Technology |
|---|---|
| Approved by | Harsh Jain and Ankit Kumar |
| Effective from | 1 November 2026 |
| Reviewed | At least once a year, and after any significant change or incident. Next review: 1 November 2027 |
What Must Be Backed Up
The database alone is not enough to restore PersivX. A complete backup holds:
| Item | Location | Why it matters |
|---|---|---|
| MySQL database | The database named by DB_NAME | Users, reports, visuals, subscriptions, logs, encrypted credentials |
| Datasets | backend-python/rapidBuild/datasets/ | Uploaded files and imported data, per organization |
| Published report versions | backend-python/rapidBuild/visualizations/ | What viewers see; stored as files, not in the database |
| Executive summary files | backend-python/rapidBuild/executivePPT/ | Generated presentations |
| Server settings and licence | .env and the licence folder | Holds the encryption keys. Back it up separately from the data, encrypted: without DATASOURCE_SECRETS_KEY every datasource credential must be re-entered, and a different SECRET_KEY resets everyone's two-step verification. |
Caches (cache_query/, cache_scanDB/) can be rebuilt and need not be backed up.
Schedule and Storage
- The database is backed up every 24 hours and files every 24 hours, by
mysqldumpandrsyncrun from cron. - Backups are encrypted, stored separately from the production servers, and kept for 30 days. Persiv-run servers back up to another cloud server in a different region; on-premises installs back up to the customer's own storage.
- Only Harsh Jain and Ankit Kumar can read or delete backups.
- A failed backup alerts Harsh Jain and Ankit Kumar, who fix it within 1 business day.
- Admins can also download a database backup from inside PersivX. Every download is logged and raises an alert. That feature writes its copies to
datasets/dumps/on the server, which are deleted after 30 days by a daily cron job.
Recovery Targets
| Target | Value |
|---|---|
| Recovery point (most data that may be lost) | 24 hours |
| Recovery time (longest outage) | 8 hours |
Proving Recovery Works
At least every 6 months, a backup is restored to a separate server, PersivX is started on it, and a sample of reports is opened as a viewer to confirm it works. The date, what was restored, how long it took and any problems are recorded.
Keeping the Business Running
- There is no standing alternate site yet. If the hosting region fails, PersivX is rebuilt on a new server from the latest backup, which is already held in a different region, following the restore runbook in Persiv's internal documentation.
- At least two people (Harsh Jain and Ankit Kumar) can carry out a restore, so recovery does not depend on one person.
- Customers are kept informed by email to each customer's admin during an outage.
