Unsolved
This post is more than 5 years old
1 Rookie
•
6 Posts
0
10162
April 18th, 2011 00:00
vmware file-level restore problem
Hi,
We're running Avamar 5.0 SP4 and Vmware 4.1 and I've configured vmware image-level backup & restore according to the documentation (300-010-712). Backups from Windows servers are working fine, and also image-level restore to new virtual machine works nicely. Also all virtual machines are listed properly on administration -> protected -tab. However I cannot get file-level restore working.
I've configure Axionfs according the document (300-009-660), installed special proxy for restores and I can browse the cifs-share from this Windows 2003 SP2 -server fine.
But when trying to restore a single file from image-based backup, it asks for virtual machine credentials, and I cannot get any further from that. I've tried entering several different credentials: domain admin (for the domain where VC and the virtual machine is located in), virtual machine local admin, vc local admin, restore proxy local admin, cifs-user for axionsfs. All of these just gives error: "The virtual machine needs to be powered on". The virtual machine is indeed powered on, just made a fresh backup of that and that worked just fine.
What credentials should be entered while doing file-level restore? And why am I always getting error that the machine should be powered on?
Br,
Arto
Mark_Bellows
240 Posts
0
April 18th, 2011 14:00
Hello Arto!
I found this article on Powerlink that I think will help. This article covers an issue that is permission related, which sounds like your issue:
esg113973
Symptoms :
Avamar VMware File Level Recovery Fails from Image Backup.
Errors in the logs:
avvmagent: VixVMObject:loginToTargetVM: Authentication failure or insufficient permissions in guest operating system
2010-05-26 13:31:48 avvmwfile Error <0000>: avvmagent: VmwAgentClass:RestoreFiles:VixConnections: Authentication failure or insufficient permissions in guest operating system
Cause
Specified user name in restore was in wrong syntax.
Resolution
1. Specify the domain name with the credentials for example: domain\username
2. Ensure that the minimum rights are provided.
The minimum rights required for VMware backups are :
hillhous
1 Rookie
•
6 Posts
0
April 18th, 2011 23:00
Hi Mark,
And thanks for your suggestion. Unfortunately even though the symptoms sounds just correct, I couldn't get any further.
I've tried entering user account on several formats: username, domain\username, computer\username but none of them is accepted. And the user should have enough rights, I've tried with domain admin and also local administrator accounts.
And it doesn't even seem to matter whether I enter correct or incorrect password, the error is always the same. When trying to restore to original location the error is "The virtual machine needs to be powered on", and if I try to restore to different location (whether to the same machine or another windows-machine with image-backup) the error is "Client refused browse request - 536870919 The virtual machine needs to be powered on".
I tried to look for logs but since the computer is backuped up only by image it doesn't have avamar client installed and therefore I don't have logs there on the destination computer. I also checked the file-level restore-proxy's logs, and the only thing I see there are messages like this (not sure if these are related to this):
2011-04-19 09:20:03 avagent Info <6648>: Browse process 596 (C:\Program Files\avs\bin\avvmwfile) started
2011-04-19 09:23:29 avagent Info <6650>: Browse process 2652 (C:\Program Files\avs\bin\avvmwfile) finished (code 536870925: Externally cancelled)
2011-04-19 09:23:29 avagent Warning <6653>: CTL workorder "Browse" non-zero exit status 'code 536870925: Externally cancelled'
And in avamar console -> administration -> event management I don't have any information regarding these restore attemps.
Where should I look these logs at?
hillhous
1 Rookie
•
6 Posts
0
April 26th, 2011 03:00
Hi,
FYI, I opened a case about this and got information that this is a known issue. It has now been solved by upgrading VIX package on proxy server to 1.10. After that also the file level restores works.
Br,
Arto