SEQTA Cloud Database Backup Service

Modified on Tue, 25 Aug at 6:09 AM

Overview

The SEQTA Cloud Database Backup Service provides cloud-hosted SEQTA schools with secure access to their SEQTA data without requiring direct database connectivity.

This service has been introduced to replace direct database access, reducing security risks while continuing to support schools' reporting, analytics, and integration requirements.

Using this service, authorised school administrators can enable automated daily database backups and retrieve backup files for use in their own reporting platforms, data warehouses, business intelligence tools, and custom integrations.


Benefits

The Database Backup Service enables schools to:

  • Access their SEQTA data outside of SEQTA and SEQTA Analyse.
  • Continue performing advanced reporting and analytics.
  • Support existing data-driven decision-making processes.
  • Build or maintain custom integrations using exported data.
  • Access a secure alternative to direct database connections.
  • Receive automated daily backups with minimal administration.


How It Works

Once enabled:

  1. SEQTA generates a database backup once per day.
  2. The backup is automatically sanitised to remove excluded system and security-related data.
  3. Authorised school administrators can retrieve the backup file.
  4. Older backups are automatically removed according to the retention policy.

The backup schedule and frequency are managed by SEQTA and cannot be customised.


Included Data

Database backups contain school data required for reporting, analytics, and integration scenarios, including information related to:

  • Student records
  • Attendance
  • Wellbeing
  • Academic results
  • Marks and grades
  • Timetable-related data
  • Other operational data stored within SEQTA


Excluded Data

To protect the security and integrity of the SEQTA platform, certain tables and data sets are excluded from backups.

Excluded data includes:

  • User credential information
  • Authentication-related data
  • SEQTA system configuration tables
  • Internal platform management data
  • SEQTA user interface-specific data
  • Other security-sensitive information determined by TES

These exclusions ensure schools receive access to relevant operational data while protecting platform security.


Enabling the Service

Prerequisites

  • The school must be hosted on SEQTA Cloud.
  • The administrator must have the required permissions within SEQTA.
  • The school needs to contact Tes for us to enable the feature so the options are available for the school admin.

To Enable Database Backups

  1. Navigate to Administration Settings.
  2. Open Database Backup Settings.
  3. Enable Database Backups.
  4. Save the configuration.

Once enabled, the first backup will be generated during the next scheduled daily backup cycle.


Retrieving a Backup

Authorised administrators can:

  1. Use an API to initiate the backup download.
  2. Restore or import the backup into their own reporting or integration environment.

Note: Schools are responsible for downloading, storing, restoring, and managing backup files within their own infrastructure.


Backup Characteristics

FeatureDetails
FrequencyDaily
ScheduleManaged by SEQTA
CompressionApplied where supported
EncryptionAlways applied
RetentionBackups automatically deleted after the retention period
Custom SchedulingNot available
Real-Time AccessNot available

Common Use Cases

Reporting and Analytics

Schools can load backup data into:

  • Microsoft Power BI
  • Tableau
  • SQL Server
  • Data warehouses
  • Custom reporting platforms

Custom Integrations

Schools that currently use or previously used direct database access can refactor integrations to consume data from the daily backup instead.

Examples include:

  • Student wellbeing reporting
  • Attendance analytics
  • Executive dashboards
  • Academic performance reporting
  • Custom school applications


Important Considerations

Not a Real-Time Data Feed

The Database Backup Service is designed for daily data extraction and reporting.

It is not intended for use cases that require near real-time access to information such as student attendance status throughout the school day.

School Responsibilities

Schools remain responsible for:

  • Downloading backup files
  • Restoring data into local databases or reporting platforms
  • Managing backup security once downloaded
  • Maintaining any custom integrations that consume the backup data

Security Recommendations

To protect student and school data:

  • Store backups in secure environments.
  • Restrict access to authorised personnel only.
  • Avoid storing backups on personal devices where possible.
  • Follow your school's data governance and privacy policies.


Frequently Asked Questions

Does this replace direct database access?

Yes. The Database Backup Service is the strategic replacement for direct database access for cloud-hosted SEQTA schools.

Will SEQTA Analyse be affected?

No. SEQTA Analyse remains available and continues to operate independently of the Database Backup Service.

What if we have custom integrations?

Most integrations can be adapted with only minor changes to consume data from the backup rather than connecting directly to a live database.

Can we change the backup time or frequency?

No. Backups are generated once per day on a managed schedule.

Can we access historical backups?

Backups are retained according to the configured retention policy. Older backups are automatically deleted.

Is all database data included?

No. Security-sensitive, system, authentication, and platform-specific tables are excluded from the backup.


Support

If you require assistance with enabling the Database Backup Service, accessing backups, or understanding included and excluded data sets, please contact the SEQTA Support Team through the standard support channels.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article