Scheduled copies. Local support.
Keep the history.
Plan the recovery.
Schedule copies of your important data, agree how long to keep them and test the way back with HostGet.
Scheduled copies
Agree a backup schedule.
Retention history
Keep the history you need.
Separate storage
Plan independent copies.
Restore testing
Test the path to recovery.
Built for recovery planning
A copy is only the beginning.
Plan what is protected
Identify application files, databases and attached volumes that need coverage.
Keep useful history
Agree a schedule and retention policy around your recovery needs.
Test your recovery
Verify supported restore procedures before you need them in an incident.
How it works
Define. Schedule. Verify.
Scope data
Agree which files, databases and volumes are included.
Set the policy
Plan schedule, retention and separate storage for the copies.
Test restores
Check recoverability and document the time and steps involved.
Monitor the result
Confirm how failed jobs are reported and who follows up. A scheduled job must complete successfully to create a usable recovery point.
Recovery and availability
Different needs. Complementary plans.
Backup for recovery
Retain copies and history to recover from deletion, corruption or loss. Recovery takes time and depends on the available recovery points.
Redundancy for availability
Use a suitable redundant application architecture to reduce interruptions. Backups remain necessary underneath that design.
Agree recovery point and recovery time goals, then test the plan. A backup alone does not keep a service online.
A backup plan shaped
around your data.
Storage volume and retention affect cost. Confirm your scope, schedule and supported restore options with our team.
Discuss your requirementsDefine coverage
List the data, databases and volumes that must be protected.
Agree the policy
Confirm schedule, retention, storage separation and access controls.
Test recovery
Test the restore process and document responsibilities and recovery goals.
FAQ
A few things you might ask.
How often should backups run?
Choose a schedule based on how much recent data you can afford to lose and how quickly it changes. Confirm the supported schedule, job duration and monitoring with our team.
How long should I keep backups?
Retention should reflect your operational, recovery and applicable record-keeping needs. Confirm storage costs and supported retention options; do not assume unlimited history.
Can I restore just one file?
File-level, database or full-server recovery depends on the backup method and configuration. Confirm supported restore granularity and test it before relying on it.
Do I still need snapshots?
Snapshots can help around planned changes, while scheduled backups provide recovery history under an agreed policy. Use both where appropriate and verify their scope and independence.
Related products
Explore related services.
Know what you can recover.
Talk to our team and plan backups around your data.