McGregor09
asked on
Veeam doesn't restore individual files with extended ascii characters in their name -
Hello everybody,
I have VMWare VSphere 4 installed on a server. In another computer in the domain, I have correctly installed VMWare client and Veeam.
A virtual machine has been damagen, and while I prepare the server for restoring it, I need to extract some files out from a Veeam backup.
The thing is that, when I try to restore files with extended ascii characters in their name (e.g. Memoria aÑo 2009.doc) the Veeam client answers not restoring it and showing the following error: Object reference not set to an instance of an object
In fact, extended ascii characters are shown with the "diamond" character.
Files without extended ascii characters are restored successfully.
Anybody has an idea how to get it to work?
Thanks in advance!
I have VMWare VSphere 4 installed on a server. In another computer in the domain, I have correctly installed VMWare client and Veeam.
A virtual machine has been damagen, and while I prepare the server for restoring it, I need to extract some files out from a Veeam backup.
The thing is that, when I try to restore files with extended ascii characters in their name (e.g. Memoria aÑo 2009.doc) the Veeam client answers not restoring it and showing the following error: Object reference not set to an instance of an object
In fact, extended ascii characters are shown with the "diamond" character.
Files without extended ascii characters are restored successfully.
Anybody has an idea how to get it to work?
Thanks in advance!
Hi
Can you post any file name examples?
Jail
Can you post any file name examples?
Jail
I think that is proper functionality of Veeam...you need to have standard characters in the VM name for the restore. As that is more of a 'design' issue, I would contact Veeam for verification. I'll continue to do some searching to see if I can find anything further to verify as well.
Regards,
~coolsport00
Regards,
~coolsport00
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
I will try to test this today.
But yes contact the Veeam support. They respond quickly to any issue.
Jail
I will try to test this today.
But yes contact the Veeam support. They respond quickly to any issue.
Jail
ASKER
Hello everybody,
At the end, I just updated to version 5 of Veeam (I was using version 4.1), and this was already fixed, so no problem anymore!
Thanks everybody for your time.
At the end, I just updated to version 5 of Veeam (I was using version 4.1), and this was already fixed, so no problem anymore!
Thanks everybody for your time.
ASKER
Sorry for making you lose your time...
Thanks for posting what you did to solve it. Glad to assist!
~coolsport00
~coolsport00
ASKER
Thanks again!