Fusion Arc Hosting – Backup, Recovery & Disaster Recovery Policy

Fusion Arc Hosting – A Fusion Arc Telecom LLC Company

Effective Date: September 18, 2026
Last Updated: September 18, 2026


1. Purpose and Scope

This Backup, Recovery & Disaster Recovery Policy (“Backup Policy”) explains the backup, restoration, disaster-recovery, and business-continuity protections provided with applicable Fusion Arc Hosting Services.

This Policy addresses:

  • included backup protection;
  • incremental backup processing;
  • recovery-point retention;
  • current-day and previous-day disaster-recovery states;
  • restoration requests;
  • healthy-node recovery;
  • backup availability;
  • backup exclusions;
  • data-loss limitations;
  • Customer backup responsibilities;
  • VPS/VDS backup coverage;
  • optional and future backup products; and
  • other backup and recovery matters.

This Policy forms part of the Fusion Arc Hosting Agreement and operates together with the applicable:

  • Terms of Service (“TOS”);
  • Acceptable Use Policy (“AUP”);
  • Fair Usage Policy (“FUP”);
  • Privacy Policy;
  • Refund & Payment Policy;
  • Support Scope, Fully Managed Services & Best-Effort Assistance Policy (“Support Policy”);
  • Service Level Agreement (“SLA”);
  • product descriptions;
  • checkout terms;
  • service-specific terms;
  • order forms; and
  • other applicable written agreements.

The order-of-precedence provisions in the TOS govern any direct conflict between contractual documents.

For matters specifically concerning backups, recovery points, restoration, backup retention, disaster recovery, and backup availability, this Policy is the primary subject-matter policy unless an applicable written agreement expressly provides otherwise.


2. General Backup Principle

Backup systems are intended to provide an additional recovery layer.

They do not constitute a guarantee against:

  • data loss;
  • hardware failure;
  • software failure;
  • corruption;
  • malware;
  • accidental deletion;
  • incomplete backups;
  • backup-job failure;
  • infrastructure failure;
  • third-party failure;
  • Customer error; or
  • other events affecting Customer data.

No backup system can guarantee that every file, database, mailbox, account, configuration, or recovery point will always be successfully created or restored.

Customers remain responsible for maintaining independent copies of critical or irreplaceable information.


3. RAID and Storage Redundancy

Applicable Fusion Arc Hosting infrastructure may use storage redundancy such as:

  • RAID 1;
  • RAID 10; or
  • another redundant storage architecture.

RAID and similar storage technologies provide live production-storage redundancy.

RAID is not a backup.

Storage redundancy may protect against certain individual storage-device failures, but it does not preserve historical versions of Customer data.

For example, if a Customer:

  • deletes a file;
  • overwrites a database;
  • modifies an application;
  • corrupts data; or
  • introduces malicious code,

the live redundant storage system may faithfully reproduce that change across its storage devices.

Historical recovery is provided through separate backup systems where included.


4. Applicable Managed Hosting Services

Unless a product description expressly states otherwise, the standard managed backup model described in this Policy generally applies to qualifying Fusion Arc Hosting managed cPanel or cPanel/WHM environments, including applicable:

  • Web Hosting;
  • WordPress Hosting;
  • CMS Hosting;
  • Reseller Hosting;
  • Agency Hosting;
  • Enterprise Hosting;
  • Semi-Dedicated Hosting;
  • managed cPanel hosting; and
  • other qualifying Fully Managed cPanel/cPanel-WHM Services.

The exact backup coverage available to a particular Service depends upon:

  • the Service purchased;
  • Service configuration;
  • backup-system configuration;
  • applicable product terms;
  • infrastructure availability; and
  • any separately purchased backup product or add-on.

5. Standard Included Incremental Backup Model

Applicable managed hosting Services generally include multiple incremental recovery states.

Under the standard included model, Fusion Arc Hosting intends to maintain:

  1. the two most recent successful hourly incremental recovery points;
  2. a current-day incremental disaster-recovery state; and
  3. a previous-day incremental disaster-recovery state.

These recovery states serve different recovery purposes.

The existence of a scheduled backup job does not guarantee that the corresponding recovery point was successfully created.

Only successfully completed and retained recovery points are available for restoration.


6. Hourly Incremental Recovery Points

Fusion Arc Hosting processes applicable managed hosting backup data on an hourly incremental schedule.

Under the standard included backup model, Fusion Arc Hosting generally retains the two most recent successfully completed hourly incremental recovery points.

These recovery points are intended primarily for rapid recovery from recent events such as:

  • accidental file deletion;
  • recent configuration changes;
  • failed application updates;
  • plugin failures;
  • theme failures;
  • recent application errors;
  • failed deployments;
  • recently corrupted files;
  • recent database problems; or
  • other recent Customer-data changes.

Where technically supported, hourly incremental recovery may allow restoration of:

  • individual files;
  • directories;
  • databases;
  • email data;
  • account data; or
  • other supported components

without necessarily restoring the entire hosting account.


7. Two-Point Hourly Retention

The standard included Service does not represent that every hourly recovery point is preserved indefinitely.

Under the standard model, hourly backup retention is generally limited to the two most recent successful hourly recovery points.

As newer successful hourly recovery points are created, older hourly recovery points may:

  • expire;
  • be consolidated;
  • be removed;
  • be overwritten; or
  • otherwise cease to be available.

A Customer should not assume that an hourly recovery point older than the two most recently retained successful points remains available.


8. Current-Day Incremental Disaster Recovery

Applicable managed hosting Services also maintain a current-day incremental disaster-recovery state.

This recovery state is intended to provide an additional recovery layer beyond the two most recent hourly recovery points.

The current-day recovery state may be used where:

  • a broader account recovery is required;
  • the newest hourly point is unsuitable;
  • multiple parts of an account require recovery;
  • infrastructure recovery is being performed; or
  • another recovery condition makes the daily disaster-recovery state more appropriate.

The current-day recovery state remains subject to successful backup processing and applicable retention.


9. Previous-Day Incremental Disaster Recovery

Applicable managed hosting Services also maintain a previous-day incremental disaster-recovery state.

This recovery state provides an additional historical recovery option when returning Customer data to an earlier state is more appropriate than using the current-day or most recent hourly recovery point.

The previous-day recovery state may be particularly useful for:

  • larger account corruption;
  • delayed discovery of an application problem;
  • broader account rollback;
  • infrastructure recovery;
  • failed deployments discovered after several hours;
  • security incidents; or
  • other circumstances requiring an earlier recovery state.

The previous-day recovery state remains subject to successful backup processing and applicable retention.


10. Incremental Backup Architecture

Incremental backup systems generally avoid creating an entirely independent full copy of every Customer account for every scheduled recovery point.

Instead, backup systems may:

  • track changed data;
  • maintain deduplicated information;
  • reference previous backup data;
  • maintain backup chains;
  • consolidate recovery information; or
  • otherwise use incremental storage technologies.

A recovery point may therefore depend upon additional backup data maintained by the backup platform.

Customers should not interpret the term “incremental” to mean that only changed files can be restored.

Where supported by the backup system, an incremental recovery point may represent a recoverable state of the applicable account at the time associated with that recovery point.


11. Offsite Backup Infrastructure

Applicable disaster-recovery data may be transmitted to or maintained on backup infrastructure separate from the applicable production hosting node.

Offsite backup infrastructure is intended to reduce dependence upon the physical production server hosting the Customer’s active Service.

Offsite does not necessarily mean:

  • a particular geographic distance;
  • a particular city;
  • a particular state;
  • a particular datacenter provider;
  • a particular cloud provider; or
  • a guaranteed separate disaster region

unless expressly stated in the applicable product terms.

Fusion Arc Hosting may change:

  • backup providers;
  • storage infrastructure;
  • backup locations;
  • backup technologies;
  • backup architecture; or
  • backup vendors

as operational requirements change.


12. Backup Scheduling Is Not a Recovery Guarantee

A backup being scheduled for a particular time does not mean that a valid recovery point necessarily exists for that exact time.

Backup jobs may:

  • start later than scheduled;
  • require extended processing time;
  • fail;
  • partially fail;
  • be interrupted;
  • encounter storage errors;
  • encounter network errors;
  • encounter filesystem errors;
  • encounter database errors;
  • encounter Customer-account errors;
  • be delayed by infrastructure conditions; or
  • otherwise fail to produce the expected recovery point.

The most recent available recovery point is therefore the most recent successfully completed and retained recovery point, not necessarily the most recently scheduled backup job.


13. No Guaranteed Recovery Point Objective

Unless expressly stated in a separately applicable written SLA or Service agreement, Fusion Arc Hosting does not guarantee a specific Recovery Point Objective (“RPO”).

Although hourly incremental backup processing may ordinarily occur, a technical failure could result in the newest available recovery point being older than expected.

The existence of hourly scheduling therefore does not constitute a guarantee that no more than one hour of data can ever be lost.


14. No Guaranteed Recovery Time Objective

Unless expressly stated in a separately applicable written SLA or Service agreement, Fusion Arc Hosting does not guarantee a specific Recovery Time Objective (“RTO”).

Restoration time may depend upon factors including:

  • account size;
  • file count;
  • inode count;
  • database size;
  • mailbox size;
  • backup location;
  • backup-system performance;
  • backup integrity;
  • network conditions;
  • server conditions;
  • replacement infrastructure;
  • restoration queue;
  • DNS changes;
  • nameserver changes;
  • security review;
  • Customer cooperation; and
  • other technical circumstances.

Published or communicated restoration times are operational estimates unless expressly identified as guaranteed SLA commitments.


15. Restoration Requests

Customers may request restoration through the appropriate Fusion Arc Hosting Technical Support, recovery, or migration-ticket process.

Fusion Arc Hosting may require the Customer to identify:

  • the affected Service;
  • the desired recovery point;
  • the affected file or data;
  • the desired restore scope;
  • the reason for restoration;
  • whether a full-account restore is requested; or
  • other information reasonably required to perform recovery.

Fusion Arc Hosting may recommend a different available recovery point or restoration method where technically appropriate.


16. Granular Restoration

Where supported by the applicable backup platform and recovery point, Fusion Arc Hosting may restore individual:

  • files;
  • folders;
  • databases;
  • email data;
  • website components; or
  • other supported account data.

Granular restoration depends upon:

  • available backup data;
  • the applicable backup platform;
  • backup integrity;
  • the type of data;
  • account configuration; and
  • the requested recovery point.

Granular recovery is not guaranteed for every Service, recovery point, or data type.


17. Full-Account Restoration

Where appropriate, Fusion Arc Hosting may restore an entire hosting account from an available recovery point.

A full-account restoration may replace or overwrite current Service data with data contained in the selected recovery state.

This may affect:

  • files;
  • databases;
  • email;
  • DNS-related configuration;
  • account configuration;
  • application settings;
  • users;
  • permissions; and
  • other account information.

Customers should understand that restoring an entire account to an earlier recovery state may remove changes made after that recovery point.


18. Restoration Can Overwrite Current Data

A restoration is not necessarily additive.

Depending upon the restore operation, existing Customer data may be:

  • replaced;
  • overwritten;
  • removed;
  • reverted; or
  • otherwise changed.

Customers requesting restoration are responsible for understanding that data created or modified after the selected recovery point may be lost.

Where practical, Fusion Arc Hosting may explain the likely effect of a requested restore before performing it.


19. Customer Authorization for Restoration

By requesting a restoration, the Customer authorizes Fusion Arc Hosting to perform reasonably necessary actions to complete the requested recovery.

This may include:

  • overwriting files;
  • replacing databases;
  • restoring email;
  • modifying permissions;
  • modifying account configuration;
  • changing server assignments;
  • changing IP assignments;
  • modifying DNS;
  • changing nameservers;
  • restarting Services; or
  • performing other technically necessary recovery actions.

Fusion Arc Hosting is not responsible for the loss of newer Customer data that is an expected consequence of restoring an older recovery point, subject to applicable law.


20. Healthy-Node Restoration

For qualifying managed cPanel Services experiencing an extended infrastructure incident, Fusion Arc Hosting may offer restoration onto another healthy Fusion Arc Hosting node.

Healthy-node restoration may be appropriate where:

  • the original server is experiencing an extended repair;
  • an appropriate recovery point exists;
  • compatible replacement infrastructure is available;
  • sufficient capacity exists;
  • recovery is technically feasible; and
  • Fusion Arc Hosting determines that alternate-node recovery is operationally appropriate.

Healthy-node recovery is an assisted recovery process, not automatic failover.


21. Healthy-Node Recovery Requires a Request

Healthy-node restoration is generally performed after a Customer requests recovery through an appropriate Technical Support, migration, or recovery ticket.

Fusion Arc Hosting does not guarantee automatic migration to another node merely because:

  • a server becomes unavailable;
  • hardware fails;
  • network connectivity fails; or
  • an outage exceeds a particular period.

Fusion Arc Hosting may independently perform infrastructure migration where necessary, but the availability of Customer-requested healthy-node restoration remains subject to technical and operational conditions.


22. Healthy-Node Recovery Process

Where healthy-node restoration is accepted, Fusion Arc Hosting may:

  1. identify an available successful recovery point;
  2. identify compatible healthy infrastructure;
  3. restore the applicable Customer account;
  4. assign or modify applicable IP information;
  5. update server-side configuration;
  6. identify required DNS or nameserver changes;
  7. assist with routing changes; and
  8. verify the restored hosting environment where reasonably practical.

The exact procedure depends upon the affected Service and infrastructure.


23. DNS and IP Changes During Recovery

Recovery to another server may require changes to:

  • IP addresses;
  • DNS records;
  • nameservers;
  • mail-routing information;
  • reverse DNS;
  • SSL/TLS configuration; or
  • other network-related settings.

Fusion Arc Hosting may assist with required changes where they fall within our control.

DNS propagation may depend on:

  • external resolver caches;
  • TTL values;
  • third-party DNS providers;
  • registrars;
  • Customer-controlled DNS;
  • internet providers; and
  • other systems outside Fusion Arc Hosting’s direct control.

Fusion Arc Hosting does not guarantee immediate worldwide DNS propagation.


24. Restoration Does Not Guarantee Application Functionality

Successful restoration of files or account data does not guarantee that the Customer’s application will function correctly.

Application operation may still depend upon:

  • application code;
  • database consistency;
  • external APIs;
  • third-party software;
  • credentials;
  • licenses;
  • plugins;
  • themes;
  • dependencies;
  • application configuration;
  • external DNS;
  • external databases;
  • third-party SaaS Services; or
  • other systems outside the restored backup.

Application troubleshooting after restoration remains subject to the Support Policy.


25. Backup Integrity

Fusion Arc Hosting uses backup technologies intended to maintain recoverable data, but no backup system is immune from:

  • corruption;
  • incomplete files;
  • missing data;
  • metadata errors;
  • filesystem problems;
  • database consistency issues;
  • interrupted jobs;
  • software bugs;
  • storage failure;
  • network failure;
  • hardware failure; or
  • other technical problems.

A recovery point appearing in a backup system does not create an absolute guarantee that every component within that recovery point can be successfully restored.


26. Database Consistency

A database backup or restoration may reflect the state of the database at the time the applicable backup information was captured.

Highly active applications may continue modifying data while backup operations occur.

Fusion Arc Hosting does not guarantee transactional or application-level consistency for every application unless expressly stated otherwise.

Customers operating applications requiring specialized transactional backup procedures should maintain independent application-aware backup systems appropriate for those requirements.


27. Malware and Compromised Backups

A backup is not automatically a clean backup.

If:

  • malware;
  • malicious code;
  • compromised credentials;
  • vulnerable software;
  • corrupted files; or
  • unauthorized modifications

were present when a recovery point was created, the backup may contain the same condition.

Restoring a backup does not guarantee:

  • malware removal;
  • vulnerability remediation;
  • credential security;
  • application security; or
  • elimination of the original cause of compromise.

Additional remediation may require:

  • malware scanning;
  • software updates;
  • credential changes;
  • vulnerability remediation;
  • plugin replacement;
  • application repair; or
  • Customer/developer action.

28. Backup Exclusions

Fusion Arc Hosting may exclude or temporarily remove an account or data from normal backup processing where reasonably necessary because of:

  • prohibited storage use;
  • excessive backup files;
  • unusual filesystem conditions;
  • technical incompatibility;
  • backup-platform limitations;
  • severe inode conditions;
  • corrupted account data;
  • malicious data;
  • infrastructure instability;
  • account suspension;
  • abuse;
  • security incidents;
  • Customer configuration;
  • unsupported data;
  • Service-specific restrictions; or
  • other technical circumstances preventing normal backup processing.

Where practical, Fusion Arc Hosting may restore backup eligibility once the underlying condition is corrected.


29. Storage Abuse and Backup Eligibility

Managed hosting storage is primarily intended for legitimate hosted:

  • website data;
  • application data;
  • databases;
  • email;
  • account configuration; and
  • related Customer Service information.

Hosting accounts are not unrestricted backup repositories or archival-storage systems unless the applicable product expressly provides such use.

Accounts using hosting storage in violation of:

  • the TOS;
  • AUP;
  • FUP;
  • product terms; or
  • applicable storage restrictions

may be excluded from some or all backup processing where the usage interferes with normal backup operations or infrastructure.


30. Customer-Generated Backups

Customers may create reasonable Customer-controlled backups where allowed by the applicable Service and Fair Usage Policy.

Customer-created backup archives remain Customer data.

Fusion Arc Hosting does not guarantee or assume responsibility for:

  • Customer-created backup integrity;
  • third-party backup plugins;
  • external backup destinations;
  • Customer-controlled cloud storage;
  • backup software selected by the Customer; or
  • restoration from unsupported Customer-generated backup formats.

Technical assistance with Customer-generated backups may be provided according to the Support Policy.


31. Customer Responsibility for Independent Backups

Customers should maintain independent backups of information that is:

  • irreplaceable;
  • mission critical;
  • legally required;
  • subject to regulatory retention;
  • subject to long-term archival requirements;
  • financially material; or
  • otherwise important to the Customer.

Independent backup copies should ideally be maintained outside the same hosting account and under the Customer’s control.

Fusion Arc Hosting backup Services provide additional continuity and recovery protection but are not intended to be the Customer’s only permanent copy of irreplaceable data.


32. Regulated and Long-Term Archival Data

Unless expressly agreed otherwise in writing, standard Fusion Arc Hosting backup Services are not designed to satisfy specialized regulatory, evidentiary, legal-hold, or archival-retention requirements.

Customers requiring:

  • immutable backups;
  • permanent archives;
  • multi-year retention;
  • regulatory retention;
  • legal-hold storage;
  • specialized encryption;
  • compliance-certified backup infrastructure; or
  • another specialized retention standard

must independently determine and maintain the systems necessary to satisfy those requirements.


33. VPS and VDS Services

Standard VPS and VDS Services do not automatically include the managed cPanel incremental backup and healthy-node recovery model described in this Policy unless expressly stated otherwise.

VPS/VDS backup and recovery protection depends upon:

  • the Service purchased;
  • an applicable backup add-on;
  • a management product;
  • a specific backup configuration; or
  • another written Service term.

A VPS/VDS Customer should not assume that provider-side backups exist unless backup coverage is expressly included or purchased.


34. Self-Managed VPS/VDS

For Self-Managed VPS/VDS Services, the Customer is generally responsible for maintaining their own backup strategy unless a separate backup product has been purchased and provisioned.

This responsibility may include:

  • operating-system backups;
  • application backups;
  • database backups;
  • configuration backups;
  • file backups;
  • offsite copies;
  • backup monitoring; and
  • restoration testing.

Fusion Arc Hosting is not responsible for the absence of Customer-managed backups on a Self-Managed Service where provider backup coverage was not included or purchased.


35. Managed VPS/VDS

Fully Managed status does not automatically mean that a VPS/VDS includes the same backup retention model as applicable managed shared/cPanel hosting.

Backup coverage remains determined by the:

  • purchased product;
  • applicable backup add-on;
  • product description;
  • checkout selection;
  • quotation;
  • order form; or
  • written Service agreement.

36. Dedicated and Bare-Metal Services

Backup coverage for Dedicated and Bare-Metal Services is determined by the applicable:

  • product description;
  • backup add-on;
  • management package;
  • Service configuration;
  • order form;
  • quotation; or
  • written agreement.

A Dedicated or Bare-Metal Service does not automatically include provider-managed backups solely because the physical server is Fully Managed.


37. Future Extended Incremental Retention Add-Ons

Fusion Arc Hosting may introduce optional paid backup products providing additional incremental recovery history.

Possible future capabilities may include:

  • additional hourly recovery points;
  • multi-day incremental history;
  • longer retention periods;
  • additional disaster-recovery copies;
  • expanded granular restoration; or
  • other backup features.

These additional products are not included unless and until Fusion Arc Hosting expressly makes the applicable add-on available and the Customer purchases or otherwise receives it.

Mention of planned, contemplated, beta, future, or proposed backup functionality does not:

  • guarantee that the feature will launch;
  • guarantee a particular launch date;
  • create entitlement to the feature;
  • modify existing backup retention; or
  • create an obligation for Fusion Arc Hosting to provide it.

38. Purchased Backup Add-Ons

Where Fusion Arc Hosting offers and the Customer purchases an additional backup product, the applicable:

  • product description;
  • checkout terms;
  • stated retention;
  • order;
  • quotation; and
  • service-specific terms

determine the additional coverage.

Purchased extended retention supplements, rather than automatically replaces, the standard backup model unless expressly stated otherwise.


39. Backup Retention May Change by Product

Different Services may have different:

  • backup frequencies;
  • recovery-point counts;
  • retention periods;
  • backup locations;
  • restoration options;
  • granular-recovery capabilities; and
  • disaster-recovery procedures.

The product-specific backup description controls the technical coverage of the applicable Service.

Fusion Arc Hosting may modify backup architecture prospectively as infrastructure or products evolve, subject to the TOS and applicable law.


40. Backup System Maintenance

Fusion Arc Hosting may perform:

  • backup-system maintenance;
  • storage maintenance;
  • software upgrades;
  • repository maintenance;
  • backup pruning;
  • backup verification;
  • backup migration;
  • storage migration;
  • platform changes; or
  • other administrative work

required to operate backup infrastructure.

Such maintenance may temporarily affect:

  • backup scheduling;
  • backup creation;
  • restoration;
  • backup visibility; or
  • recovery-point availability.

41. Backup Verification and Monitoring

Fusion Arc Hosting may monitor backup systems and investigate backup failures.

Monitoring may include:

  • backup-job status;
  • storage capacity;
  • job errors;
  • repository status;
  • account backup status;
  • data-transfer errors;
  • backup-system health; and
  • other technical indicators.

Monitoring does not guarantee that every failed, incomplete, corrupt, or unavailable recovery point will be detected immediately.


42. Backup Failure

A failed backup job does not automatically mean the underlying hosting Service has failed.

Where a scheduled backup fails, Fusion Arc Hosting may:

  • retry the backup;
  • investigate the failure;
  • repair backup configuration;
  • move backup data;
  • adjust scheduling;
  • use another available recovery point; or
  • take other reasonable corrective action.

Backup failure does not automatically create entitlement to:

  • a monetary refund;
  • damages;
  • compensation;
  • Service cancellation;
  • consequential damages; or
  • another remedy

except where expressly provided by the TOS, SLA, applicable product terms, or applicable law.


43. Restoration Failure

Fusion Arc Hosting does not guarantee that every restoration attempt will succeed.

A restoration may fail because of:

  • backup corruption;
  • missing backup components;
  • application inconsistency;
  • software incompatibility;
  • unsupported data;
  • filesystem damage;
  • database damage;
  • insufficient replacement infrastructure;
  • technical errors;
  • third-party issues; or
  • other conditions outside reasonable control.

Where appropriate, Fusion Arc Hosting may attempt another available recovery point or recovery method.


44. Restoration Fees

Restoration from the standard included backup Service may be included where provided by the applicable Service.

Fusion Arc Hosting may charge for restoration where:

  • the applicable product does not include restoration assistance;
  • repeated or unusually complex restores are requested;
  • specialized recovery work is required;
  • Customer-generated backup data must be reconstructed;
  • professional Services are required;
  • data must be recovered from unsupported systems; or
  • the applicable product terms provide for a restoration fee.

Any applicable charge will ordinarily be disclosed or quoted before billable recovery work is performed.


45. Restoration and Beyond Scope Assistance

Standard restoration of supported backup data may fall within normal Technical Support scope.

Additional work may become Beyond Scope where restoration requires:

  • application redevelopment;
  • custom coding;
  • database reconstruction;
  • unsupported software repair;
  • third-party vendor work;
  • application-specific repair;
  • manual recreation of missing data; or
  • other work outside the supported hosting platform.

Beyond Scope Assistance is governed by the Support Policy.


46. Service Suspension

A suspended Service may continue to have existing backup recovery points for a period of time, but Fusion Arc Hosting does not guarantee that:

  • new backups will continue during suspension;
  • every existing recovery point will remain available;
  • normal retention will be extended; or
  • backup expiration will pause.

Customers should resolve suspension conditions promptly if retained backup data is important.


47. Service Termination

When a Service is terminated, associated backup recovery points may:

  • become unavailable;
  • expire;
  • be pruned;
  • be deleted;
  • be overwritten; or
  • otherwise cease to exist.

Fusion Arc Hosting does not guarantee any period of backup availability following Service termination unless expressly stated otherwise.

Customers must retrieve or independently preserve required data before termination.


48. Cancellation

A pending or completed cancellation does not create any special backup-retention obligation.

If a Customer schedules a Service for termination, the Customer is responsible for obtaining any required independent copy of their data before the termination becomes effective.

Cancellation procedures and deadlines are governed by the Refund & Payment Policy.


49. Account Deletion

Deletion of an active hosting Service or Customer account may remove access to associated backups.

Some backup data may remain temporarily until expiration or overwrite according to backup rotation.

The possible existence of residual backup data does not mean that the data remains:

  • Customer-accessible;
  • restorable;
  • searchable; or
  • available upon request.

Privacy-related residual retention is governed by the Privacy Policy.


50. Backup Data and Privacy

Backup data may contain Customer Content and Personal Information.

Backup data is processed in accordance with the Privacy Policy and applicable Service terms.

Deletion of information from an active system may not immediately delete the same information from an existing backup.

Backup copies may remain until they:

  • expire;
  • are rotated;
  • are overwritten;
  • are pruned; or
  • are otherwise deleted according to applicable backup procedures.

51. Third-Party Backup Technology

Fusion Arc Hosting may use third-party backup, storage, datacenter, network, or infrastructure technologies to provide backup Services.

Third-party technologies may:

  • change;
  • fail;
  • experience outages;
  • introduce software defects;
  • change licensing;
  • change compatibility;
  • discontinue products; or
  • require infrastructure migration.

Fusion Arc Hosting may replace or modify backup technologies where reasonably necessary.


52. Infrastructure Failure

Fusion Arc Hosting backup architecture is intended to reduce, but cannot eliminate, risks arising from:

  • storage-device failure;
  • server failure;
  • filesystem failure;
  • software failure;
  • network failure;
  • datacenter events;
  • infrastructure outages;
  • disasters; or
  • other technical events.

No backup architecture can guarantee recovery from every possible failure scenario.


53. Catastrophic or Correlated Failure

Multiple protection layers may still be affected by the same or related event.

For example, a sufficiently severe:

  • datacenter event;
  • security event;
  • software defect;
  • account corruption;
  • backup-system failure;
  • provider failure;
  • malicious act; or
  • disaster

could affect more than one recovery mechanism.

Fusion Arc Hosting does not guarantee that the existence of multiple recovery points makes complete data loss impossible.


54. Disaster Recovery

Disaster recovery refers to technical efforts intended to restore Service or Customer data following a significant infrastructure event.

Depending upon the event, disaster recovery may involve:

  • restoring backup data;
  • replacing hardware;
  • rebuilding servers;
  • restoring Customer accounts;
  • relocating Services;
  • assigning new IP addresses;
  • modifying DNS;
  • migrating to healthy infrastructure;
  • restoring databases;
  • reconstructing configuration; or
  • other technically necessary actions.

Disaster-recovery procedures depend upon the circumstances of the incident and available recovery data.


55. Business Continuity

Fusion Arc Hosting may use multiple continuity measures including applicable:

  • redundant storage;
  • security systems;
  • backup systems;
  • incremental recovery points;
  • offsite backup infrastructure;
  • network redundancy;
  • replacement infrastructure; and
  • assisted restoration.

These measures are intended to improve resilience.

They do not create a guarantee of uninterrupted Service or zero data loss.

Availability and uptime obligations remain governed by the applicable SLA and TOS.


56. No Automatic Failover Promise

Unless a product expressly includes automatic failover, Fusion Arc Hosting backup and recovery Services should not be interpreted as an automatic high-availability or failover Service.

Backup restoration generally requires:

  • detection;
  • evaluation;
  • recovery-point selection;
  • restoration;
  • configuration;
  • routing; and
  • verification.

Healthy-node restoration is therefore a disaster-recovery procedure, not an instantaneous failover guarantee.


57. Customer Cooperation

Customers requesting restoration must reasonably cooperate with Fusion Arc Hosting.

Cooperation may include:

  • confirming the intended recovery point;
  • identifying affected data;
  • providing authorization;
  • testing restored applications;
  • updating external DNS;
  • updating third-party integrations;
  • confirming application functionality;
  • changing credentials following compromise; or
  • providing other information reasonably necessary for recovery.

Failure to cooperate may delay or prevent restoration.


58. Customer Verification After Restore

Customers are responsible for reviewing restored Services after recovery.

Customers should verify applicable:

  • websites;
  • applications;
  • databases;
  • email;
  • files;
  • DNS;
  • integrations;
  • payment systems;
  • scheduled tasks;
  • user accounts; and
  • other business-critical functionality.

Fusion Arc Hosting may assist with supported hosting-environment verification, but the Customer remains responsible for confirming application and business-data accuracy.


59. Recovery of Deleted Customer Data

Fusion Arc Hosting cannot guarantee recovery of data deleted by a Customer.

Recovery is possible only where an appropriate retained recovery point:

  • successfully exists;
  • predates the deletion;
  • contains the requested data;
  • remains available; and
  • can be successfully restored.

The sooner a Customer reports accidental deletion, the greater the possibility that an appropriate retained recovery point may still exist.


60. No Permanent Historical Archive

The standard backup Service is a rotating disaster-recovery and operational-recovery system.

It is not a permanent historical archive.

Recovery points are expected to expire as part of normal rotation.

Customers requiring permanent or long-term history must maintain an appropriate independent archival system or purchase an applicable extended-retention product when such a product is available.


61. No Guarantee Against Customer Error

Fusion Arc Hosting is not responsible for preventing every Customer action that may affect data.

Customers may have technical ability to:

  • delete files;
  • overwrite databases;
  • alter permissions;
  • uninstall applications;
  • delete email;
  • modify DNS;
  • change configuration;
  • delete accounts;
  • deploy defective code; or
  • otherwise alter Customer Content.

Backup Services may provide a recovery option where a suitable recovery point exists, but they do not guarantee reversal of every Customer action.


62. Recovery Following Security Incidents

Where a security incident affects Customer data, Fusion Arc Hosting may recommend restoring from an earlier recovery point.

A restoration alone may not correct the cause of the compromise.

Recovery may also require:

  • credential rotation;
  • malware remediation;
  • software updates;
  • vulnerability remediation;
  • application changes;
  • firewall changes;
  • removal of unauthorized users; or
  • other security work.

Security assistance remains governed by the Support Policy and applicable Service scope.


63. SLA Relationship

Backup scheduling and restoration availability are separate from ordinary uptime measurements unless expressly included in the applicable SLA.

A:

  • failed backup;
  • unavailable recovery point;
  • delayed restore; or
  • unsuccessful restoration

does not automatically constitute qualifying SLA downtime.

Any applicable SLA credit remains governed solely by the SLA and TOS.


64. Limitation of Liability

All backup, restoration, disaster-recovery, and data-loss matters remain subject to the disclaimers, exclusions, remedies, and limitations of liability contained in the TOS.

To the maximum extent permitted by applicable law, Fusion Arc Hosting does not assume unlimited liability merely because:

  • backup Services were provided;
  • a recovery point existed;
  • a restoration was requested;
  • a restoration was attempted;
  • a backup failed;
  • data was unavailable;
  • data was corrupted; or
  • disaster-recovery assistance was performed.

Nothing in this Policy excludes liability that cannot legally be excluded.


65. No Expansion Through Support Communications

A Live Chat response, Technical Support ticket, ordinary email, troubleshooting statement, restoration estimate, or other informal communication does not modify the backup coverage, retention, guarantees, or liability provisions of the written Fusion Arc Hosting Agreement unless expressly confirmed through an authorized contractual process.

A technician’s good-faith statement concerning:

  • backup availability;
  • expected restore time;
  • expected retention;
  • recovery likelihood; or
  • technical condition

is an operational assessment and does not create a contractual guarantee inconsistent with this Policy or the TOS.


66. Courtesy or Exceptional Recovery

Fusion Arc Hosting may occasionally retain or locate backup data beyond the normal expected retention period.

The availability of such data in one situation:

  • does not create a continuing obligation;
  • does not modify normal retention;
  • does not guarantee similar recovery in the future; and
  • does not create a Customer entitlement to expired recovery points.

Likewise, voluntarily performing extraordinary recovery work does not permanently expand the included backup Service.


67. Product Changes

Fusion Arc Hosting may change:

  • backup software;
  • backup providers;
  • storage providers;
  • backup infrastructure;
  • scheduling architecture;
  • retention architecture;
  • disaster-recovery processes;
  • restoration tools; or
  • related technologies

as products and infrastructure evolve.

Material contractual changes will be handled according to the TOS and applicable law.


68. Policy Updates

Fusion Arc Hosting may update this Policy as:

  • backup technology changes;
  • infrastructure changes;
  • products change;
  • backup providers change;
  • storage architecture changes;
  • recovery methods improve;
  • new backup add-ons become available; or
  • operational requirements evolve.

Material changes will be handled in accordance with the TOS and applicable law.


69. Contact and Recovery Requests

Backup and restoration requests should generally be submitted through an appropriate Technical Support, migration, or recovery ticket in the Fusion Arc Hosting Client Area.

Urgent technical issues may initially be reported through Live Chat, but extended or destructive restoration operations may require a Technical Support ticket for:

  • authorization;
  • recovery-point selection;
  • auditability;
  • extended processing; and
  • Customer confirmation.

Questions concerning paid backup products, backup add-ons, or future extended-retention products should be directed to Sales & Billing when such products are available.


70. Backup Coverage Summary

For clarity, the standard applicable managed-hosting backup model generally provides:

Included Managed cPanel/cPanel-WHM Recovery

  • incremental backup architecture;
  • two most recent successful hourly incremental recovery points;
  • a current-day incremental disaster-recovery state;
  • a previous-day incremental disaster-recovery state;
  • applicable offsite disaster-recovery storage;
  • granular file/folder/data restoration where supported;
  • full-account restoration where appropriate; and
  • assisted healthy-node restoration during qualifying infrastructure incidents where technically appropriate.

Not Guaranteed

Fusion Arc Hosting does not guarantee:

  • that every scheduled backup succeeds;
  • that every recovery point exists;
  • that every file is recoverable;
  • that every database is internally consistent;
  • that every mailbox is recoverable;
  • that every restore succeeds;
  • that restored applications function correctly;
  • that backups are malware-free;
  • a particular RPO;
  • a particular RTO;
  • uninterrupted availability; or
  • zero data loss.

VPS/VDS

Standard VPS/VDS Services do not include the managed cPanel backup model by default unless expressly stated or an applicable backup product has been purchased.

Future Extended Retention

Additional incremental retention products may be introduced in the future but are not presently included or promised unless expressly offered and purchased.

Customer Responsibility

Customers should maintain independent backups of important, irreplaceable, regulated, or long-term archival data.