Our Backup Policy

Nettescil backup policy is a continuity approach that must be evaluated according to the service type, product scope, technical configuration and the customer’s own data management. A backup does not mean that every system can always be restored exactly as it was. Coverage, creation time, retention, verification and restore conditions may vary by service and plan.

Purpose of backup

Backups can support recovery after accidental deletion, an incorrect configuration, an update problem, data corruption, a hardware failure or a security incident. Backup is not the same as high availability or uninterrupted service. Applications, databases, DNS, server resources, licenses and network connections are also required for a service to work.

Coverage by service

For web hosting, coverage may include account files, databases, mailboxes or the areas supported by the control panel. In reseller hosting, the reseller account and customer accounts may have different scopes. With VPS and VDS, operating system, application files, databases and server settings depend on the selected configuration. Dedicated server plans must consider disks, operating systems, storage and customer-installed services.

Daily, weekly or monthly backup schedules and fixed retention periods should not be assumed without confirmation. Coverage varies by service and plan. If you have a critical restore requirement, ask support to confirm the scope before ordering or making a major change.

Independent customer copies

Independent copies are recommended for critical data. Keep website files, databases, media, mail archives, DNS records, configurations and license information according to the needs of the project. A copy on the same server may not help when the server is inaccessible. Protect backup accounts, encrypt sensitive archives and verify that the files can be read.

Restore and integrity

Before a restore, identify the date, affected files, overwrite behavior and possible service impact. Where possible, test the copy in an isolated environment. Restoring files without the matching database, PHP version, plugins, licenses or DNS settings may not produce a working application. Validate login, content, database connections, uploads, mail and critical flows after the restore.

Retention and deleted data

Retention describes how long copies are kept and how they rotate. It depends on the product, package and operating policy. A deleted file may not exist in a backup if no copy was created before deletion. Data after cancellation is governed by the service and applicable policy. Long-term business, legal and financial records should not be left only to provider backups.

Snapshot is not backup

A snapshot may capture a disk or virtual machine at a point in time, often within the same storage system. It can be useful for quick rollback but may not be an independent copy. High availability helps services continue after some failures; it does not automatically undo deletion, corrupt updates or malicious code. Backup and continuity architecture have different roles.

Responsibilities

Nettescil backup coverage is evaluated by product, plan and technical configuration. Customers remain responsible for content, applications, passwords, plugins, custom settings and independent archives. A restore request should include the service, domain, desired date, affected data and last known working state. Critical data should be backed up independently before major changes.

See Infrastructure, Data Center, Security Infrastructure and Service Status. The scope should be confirmed before a restore is requested.