Learn how to restore files from a live VMware VM using Instant Recovery without downtime. A clear, real-world guide with commands and exact steps. Our 24/7 Live Support Team is always here to help you.
Downtime is expensive. Panic is worse. When a critical file vanishes from a production VM, you don’t want theory, you want a fix that works now. That’s exactly why admins rely on Restore files on a live VMware VM using Instant Recovery instead of full restores that burn hours.
This guide is written for real-world recovery. No skipped steps. Just the process that actually gets files back while your VM keeps running.

Overview
Why Instant Recovery in VMware Matters
VMware Instant Recovery lets you boot a VM directly from its backup. In other words, the backup becomes live, immediately. As a result, applications stay accessible, users stay online, and pressure stays low.
More importantly, Restore files on a live VMware VM using Instant Recovery allows you to extract only what you need. Therefore, you avoid restoring entire disks just to recover one file.
Here’s what you gain:
- Business continuity because services stay up
- Lower costs since downtime is minimal
- Operational flexibility as recovery happens in isolation
Prerequisites You Must Check First
Before you begin, stop and verify the basics. Otherwise, the recovery will fail.
- A valid, restorable VMware backup must exist
- VMware vSphere 8.0+: VMs using vVol datastores on ESXi 8.0 are not supported
- CSV recovery is not supported
- If restoring to production networking, the original VM must be powered off
Skipping these checks is the fastest way to break recovery.
The Concept That Makes This Work
You will use three components:
1. The original production VM (keeps running)
2. A restored VM from backup (private network only)
3. An intermediary VM (bridge between private and public networks)
Because of this design, you can safely Restore files on a live VMware VM using Instant Recovery without IP conflicts or outages.
Steps to Restore Individual Files Safely
Create a Private vSphere Standard Switch
First, this switch stays internal to the ESXi host.
vSphere Client (example):
- Select ESXi host
- Configuration → Networking → Add Networking
- Connection type: Virtual Machine
- Create vSphere standard switch
- Name it (example: NB or NetBackup)
This ensures isolated communication.
Configure the Intermediary VM
Next, this VM must already have access to the public network.
- Edit VM settings
- Add Ethernet Adapter
- Connect it to the private switch created earlier
If the IP is not assigned automatically, then configure:
- IP address
- Subnet mask
- Default gateway
At this point, the intermediary VM can talk to both networks. Consequently, file transfer becomes possible.
Restore the VM Using Instant Recovery
Now run the exact command below. Do not skip flags.
nbrestorevm -vmw -ir_activate -C virtual_machine \
-temp_location temporary_datastore \
-R rename_file_path -vmsn
Why -vmsn matters:
It disables networking on boot. Without it, you risk IP conflicts with production.
Rename file example:
change vmname to acme_vm5
This avoids name clashes in vCenter. As expected, isolation remains intact.
Power On and Extract Files
After that:
- Add a NIC to the restored VM
- Connect it to the private switch
- Power it on
Configure IP if required
Then enable file sharing (FTP, NFS, or CIFS). Next, copy files to the intermediary VM. From there, production systems can access them instantly.
This is, without question, the cleanest way to Restore files on a live VMware VM using Instant Recovery without touching the running VM.
Recover Files Instantly, Zero Downtime

Clean Up When Done
Once recovery is complete, list active instant recovery sessions:
nbrestorevm -ir_listvm
Then deactivate the restored VM:
nbrestorevm -ir_deactivate <instant_recovery_ID>
As a result, resources are released cleanly.
Conclusion
Ultimately, when every minute counts, full restores are the wrong tool. Restore files on a live VMware VM using Instant Recovery gives you speed, control, and safety—all at once.
