Backups and recovery

1. Agreed protection

These terms apply only when incorporated into a service Order. The backup schedule must identify each protected service, disk or data set; exclusions; the backup type and frequency; retention and expiry; destination, supplier and jurisdictions; access and key control; failure detection and handling; restore method; customer responsibilities; and any charges. It must distinguish VM-level backup from application-consistent recovery.

No backup frequency, retention period, recovery point or recovery time is promised by this page. A successful job is not proof that a particular application can be restored. Backup protection must be confirmed for the actual service and backed by an appropriate restore check.

2. Novasean’s and the customer’s duties

Novasean must perform the backup tasks it agrees, handle known failures within the agreed process and tell the customer about material loss of the agreed protection. The customer must perform its assigned application exports, consistency checks, retention decisions and independent continuity measures. An independent customer copy does not release Novasean from a backup duty it has accepted.

Where personal data are included, the DPA controls processing, location, suppliers, transfers and deletion. The existing Canadian backup arrangement for the account portal described in the location notice must not be assumed to be the arrangement for a new VPS.

3. Requesting a restore

Use the service’s agreed support route and identify the affected service, desired restore point and incident impact. The parties must assess available copies, expected loss of later changes, security and application-consistency risks, and authorisation before destructive restoration. Any additional charge must be agreed before work outside the contracted scope begins.

Novasean must verify the restore tasks assigned to it; the customer must validate its application and reconcile later data where assigned. Do not treat a restored VM as proof that all business records are correct. The support terms distinguish first response, workaround and restoration.

4. Retention and service exit

The schedule must explain expiry of live and backup copies, legal holds, access during justified residual retention, and how completed deletions are reapplied after restoration. A backup exception must have a defined purpose and limit. The DPA and switching terms determine applicable return, retrieval and deletion rights; ending a subscription must not trigger premature erasure contrary to those rights.