Skip to main content

When i tried to restore my database using veeam explorer for oracle from a backup created using application aware processing i got :

Failed to resolve path : /h01/oracle/agent/agent_13.4.0.0.0.

 

 

Hi ​@istm,

 

This error typically occurs when the original Oracle Agent path /h01/oracle/agent/agent_13.4.0.0.0 used during backup no longer exists on the target machine.

 

Please check if that exact path exists if not, you can recreate it.


Alternatively, try restoring the database to another location or use the Export option in Veeam Explorer for Oracle.

 

Also, make sure your Oracle environment variables and plug-ins are properly configured.

 

Hope this helps!


Hi ​@istm,

 

This error typically occurs when the original Oracle Agent path /h01/oracle/agent/agent_13.4.0.0.0 used during backup no longer exists on the target machine.

 

Please check if that exact path exists if not, you can recreate it.


Alternatively, try restoring the database to another location or use the Export option in Veeam Explorer for Oracle.

 

Also, make sure your Oracle environment variables and plug-ins are properly configured.

 

Hope this helps!


Why i’m not able to see the Original Host Here, is it an error from my part, or i missed something in the configuration.
 

 


Hi ​@istm -

I assume you’re using Veeam Backup here? Or, are you using Veeam Agent for Linux? I assume Veeam with your screenshots. What version of Veeam? Is your virtual infrastructure VMware or Hyper-V?

As Waqas stated...it appears the path in your originally backed up Oracle Linux VM no longer exists. Can you log on to the VM (ssh or console) and check the path? I assume your VM is still in your virtual infrastructure? Did you remove it from inventory by chance, then re-add it? That would cause the VM to get a new ref-ID and thus cause it to be like a newly backed up VM.

Check those things and let us know.

Best.


Another thing to try to verify your source VM is still ok on the virtual infrastructure side...in the Backup Job..Edit the settings > and go to the Virtual Machines section. Click the Recalculate button and verify all VMs listed have a VM size. If any have a 0MB, then something was done on the virtual infrastructure side to cause them to have a different ref-iD. Simply re-add the VM to your Job and remove the 0MB VM in the list. And this is assuming you’re backing up individual VMs. If you’re using a ‘container’ (Cluster or Datastore), you won’t have VMs shown in a list.


Hi. We have a similar issue and opened a ticket with veeam on this. unfortunately the root cause is unclear and no solution as of now. Have you been able to resolve your issue? If yes, what was the cause and what was the solution? Thanks in advance!

Paul


Comment