UNSOLVED

Gecko1507

updated

10 years ago

G

Gecko1507

1 Rookie

32 Posts

0

618

September 27th, 2016 13:00

Image Level Restores

Avamar 7.3.0-233 with vCenter 5.5,

Running image level backups - all working great. When trying to restore from image level backup we get 2 things:

1) Before the restore initiates we are prompted to enter a Username and Password - the only credentials that work are the username and credentials for our dedicated avamar VMware service account.

2) The restores fail after 15secs stating "Failed to create directory to guest"

First question - would you expect to enter credentials when running an image level restore? Ad would the credentials normally be the avamar dedicated VMware user? Can't find anything in the documentation to confirm this.

Second question - is it a permissions issue with VMware not allowing something to be written to the vm!!!!

When we run the same from a guest level backup we can restore fine and does not ask for any credentials.

Once again, any assistance would be appreciated.

Neil

  • dynamox

    11 Legend

    20419 Posts

    87439 Points

    357

    0

    Posted September 27th, 2016 21:00

    sure sounds like the account that you configured to talk to vCenter does not have sufficient privileges in vCenter.  The Avamar VMware guide mentions what permissions the account should have in vCenter.

  • Gecko1507

    1 Rookie

    32 Posts

    357

    0

    Posted September 28th, 2016 00:00

    Hi Dynamox,

    That's what we were thinking last night but am 99.99% sure the customer created the account with the required permissions - I sent them the VMware User Guide with the table of required permissions so..........................

    I was more surprised that it actually asked for a Username and password to be honest - can find absolutely no reference to that in any of the documentation!!

    I have logged an SR now so will let you know the outcome from that.

    Thanks

    Neil

  • Gecko1507

    1 Rookie

    32 Posts

    357

    0

    Posted September 28th, 2016 05:00

    Interesting and I think this is a permissions issue as I can restore the whole vm to a new location with new name etc and that also works fine - it is only when potentially overwriting files to an existing vm that the issue arises.