Create a dedicated NFS backup destination for cloud instances, applications and other workloads. You control what gets backed up, when it runs and how long the backup data is retained.
Backup Storage provides the destination. Backup schedules, retention and application-specific backup procedures are configured separately.
↓ backup tool or scheduled job
↓ writes to
↓ retained as
↓ available for
Exp. in Hosting Business
Cloud Deployments
Data Centers
Pay As You Go Pricing
Ticket Response Time
Four steps, and the storage only ever plays one role.
Deploy Backup Storage
Create the Backup Storage resource from the supported marketplace workflow.
Connect Your Workload
Configure the appropriate NFS access between the workload and Backup Storage.
Configure Your Backup Job
Your application, script or backup software determines what, when, retention and format.
Restore When Required
Use the stored backup data according to your application's or tool's restore procedure.
Deploying Backup Storage alone does not start a backup job.
Store backup files generated from Linux workloads.
Send application-generated archives or backup files to the storage destination.
Store database dump files or backups generated using the database's supported backup method.
Compatible hosting/control-panel backup systems can use the storage where NFS destinations are supported.
Use scheduled scripts or automation that writes backup data to the mounted NFS location.
Compatibility depends on the backup method and application. Backup Storage does not automatically make a workload application-consistent.
AccuWeb.Cloud provides the backup destination. Your backup tool or application determines how the backup itself is created.
Select the storage solution that best matches your architecture and workload requirements.
NFS-based destination for backup workflows.
Good for
S3-compatible object storage powered by MinIO Community Edition.
Good for
Self-managed file storage using ownCloud.
Good for
Plan around frequency, retention, recovery requirements, and projected data growth.
How often does the workload need a recoverable copy?
How many historical backups should be retained?
How quickly must the data be restored?
How much backup data will accumulate after retention and growth are considered?
Backup capacity should be planned around backup size × retention × expected data growth.
Understand how dedicated Backup Storage differs from built-in platform backup policies and snapshots.
A separately deployed NFS storage destination that the customer uses with their own backup workflow.
Where available, AccuWeb.Cloud also provides platform-level options such as:
These are separate features. Deploying the Backup Storage product does not automatically enable or replace platform backup policies or snapshots.
Deploy Backup Storage in an available region appropriate for your workload and recovery design.
Cross-region backup architectures require separate networking, replication and recovery planning and can be reviewed as a custom design.
Flexible Pay-As-You-Use Pricing — pay based on the resources you provision, with flexible hourly billing and no long-term contracts.
Backup Storage cost depends on the storage capacity and infrastructure provisioned for the backup destination. Current pricing tiers are shown when you configure Backup Storage in the AccuWeb.Cloud console.
Third-party names and marks belong to their respective owners and are shown for identification only.
Pricing comparison based on equivalent configurations as of 1 August 2026.
Please ask your queries. We are available 24/7
Deploy NFS-based Backup Storage and connect it to the backup workflow that fits your application, retention and recovery requirements.
Backup Storage provides storage capacity. Backup creation, scheduling, retention and restore procedures are configured separately.
All third-party logos and trademarks displayed on AccuWeb Cloud are the property of their respective owners and are used only for identification purposes. Their use does not imply any endorsement or affiliation.
