What you’re seeing
- The job progress sits at 99% for hours on a step like removing a snapshot, merging or transforming backups.
- The next scheduled job will not start because the previous one is still running.
- The VM being backed up runs slowly while the snapshot is being removed.
- Cancelling the job leaves a snapshot behind on the VM.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- A large VM snapshot takes a long time to consolidate, especially on slow storage.
- Forever-incremental merges on a slow repository move huge amounts of data in the final step.
- Storage latency spikes during the cleanup phase.
- A locked file or hung VSS writer on the guest keeps the job from finishing.
- Repository disk space is nearly exhausted, slowing the merge to a crawl.
Why it matters
A job that never finishes blocks the next night's backups, so the business quietly loses restore points. Leftover snapshots keep growing and can fill the datastore, which may freeze every VM on it. Staff can also experience slow systems during working hours while the stuck step drags on. What looks like a cosmetic hang can escalate into an outage.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Should we just cancel the job?
Cancelling can leave snapshots behind that need cleaning up, so it is best done with an understanding of what step was stuck.
How do we stop it from happening every night?
Finding the underlying bottleneck, whether storage, snapshot size or a guest issue, is what prevents repeats. Our certified US engineers can investigate in a remote secure session.