Before the change. Local support.
Before the change.
Keep a restore point.
Capture a point-in-time disk image before upgrades or configuration changes. Plan capture and recovery with HostGet.
Point-in-time image
Capture a supported disk state.
Change preparation
Prepare before an update.
Restore planning
Know your recovery steps.
Local support
Talk to our team in Dhaka.
Built for planned changes
Make changes with a recovery plan.
Capture before upgrades
Prepare a restore point before a software upgrade or configuration change.
Plan a rollback
Confirm what is captured and how restoration affects existing data.
Reuse an image where supported
Discuss creating a compatible server from an image where the platform supports it.
How it works
Capture. Change. Verify.
Capture
Prepare the application and confirm the snapshot completed.
Change
Make your planned upgrade or configuration change.
Verify
Test the service and decide whether recovery is needed.
Restore if required
Confirm the recovery target and protect any newer data before restoring. Timing and impact depend on the platform.
Snapshots and backups
Different jobs. A stronger recovery plan.
Change checkpoints
Snapshots capture supported disk state at a point in time. Use them around planned changes, with a defined retention and restore process.
Scheduled protection
Backups follow a planned schedule and retention policy. Confirm independent storage, recovery history and restore testing for your setup.
A snapshot alone is not an independent backup strategy. Check capture scope and test recovery.
Retention planned
around your changes.
Image size and retention affect pricing. Confirm capture scope, supported features and costs with our team.
Discuss your requirementsDefine the change
Identify the disks and services involved in your planned change.
Plan capture
Review application consistency, capture scope and maintenance requirements.
Confirm recovery
Agree restoration steps, retention and an independent backup plan.
FAQ
A few things you might ask.
How long does taking a snapshot take?
Timing depends on disk size, platform and workload. Confirm maintenance needs and whether the capture is crash-consistent or application-consistent; active databases may need quiescing or application-aware preparation.
Does restoring lose anything?
Restoring an earlier image can overwrite changes made after capture. Confirm the target and preserve required newer data before proceeding.
Can I restore to a different server?
Creating or restoring a compatible server may be supported. Confirm provider, region, image format, disk and licensing constraints first.
How many snapshots should I keep?
Choose retention based on change frequency, recovery needs and cost. Remove unneeded snapshots only after validation, while maintaining independent backups.
Related products
Explore related services.
Plan the change. Prepare the way back.
Image size and retention affect pricing. Confirm scope and costs with our team.