VSS - Guest OS Credential problem

[hkanthony]

I selected some VMs to back up and enabled the application aware option in the backup job, but it requires to provide Guest OS credentials and from the product manual, the user name must be supplied as DOMAIN\username.
Howerver all my VMs are running as WORKGROUP (no domain joined) and Each VM has individual administrator account . Therefore I want to know how to enter the Guest OS Credential field of this job.

In addition, I want to know if Veeam V6 for Hyper-V supports Universal Application-Item Backup and Recovery (VSS). (no this topic found in the product manual.)

Thanks

[Vitaliy S.]

Hi Anthony,

You can use any account that belongs to local administrator's group on your VMs, please use the following format to HOSTNAME\USER_ACCOUNT to backup these VMs with application aware image processing enabled.

U-AIR functionality as well as other vPower-based functionality is not available for Hyper-V with this first release.

Thanks!

[darryl.crossley]

Morning guys,
Is there a way to pass a wildcard local admin account to Veeam? A customer has a local admin account on all servers named 'l0caladmin', they would prefer to use this rather than creating a domain account with local admin access.

I obviously don't want to create hundreds of accounts with the credentials 'SERVERNAME\l0caladmin', is there any way around this?

I have tried:
l0caladmin
.\l0caladmin

Both fail to connect to the admin share, have I missed an easy option here?

Darryl (BEarena)

[Gostev]

Hi Darryl,

What you are describing should definitely work in my opinion. I would approach it the same way using the .\account for the account name. Can you try to connect to the \\server\admin$ share with Windows Explorer from the backup server machine by specifying the credentials in the same way to the Windows Explorer?

I also suggest that you run this test against some of your own internal VMs, because may be there is some configuration issue that is specific to this customer's VMs?

Please, let us know the results of the above tests.

Thank!

[darryl.crossley]

Absolutely spot on Gostev, looks like FW rules.

They've pre-provisioned all the network ACL's as per my design, obviously not.

Never trust the customer!

[darryl.crossley]

Does application aware image processing require TCP 445? The admin guide specifies:
TCP 1025 to 5000 (for Windows 2003)
TCP 49152-65535 (for Windows 2008)

[darryl.crossley]

Looks like TCP/UDP 135, 137-139, 445 are all required. These are classed as Backup Server to Windows Server ports.
I'll get these opened up.

[foggy]

Generally, network connection to the guest is not a requirement. If these ports are closed, the job will fail over to VIX to deploy Veeam runtime agent into VM to perform application-aware processing.

[mats.jansson]

We have simular problem, "Generally, network connection to the guest is not a requirement. If these ports are closed, the job will fail over to VIX to deploy Veeam runtime agent into VM to perform application-aware processing."

Our jobs never fail over to VIX, any ideas?

[Vitaliy S.]

Do you have VMware Tools up & running on these VMs? If yes, then please contact our technical team for further logs review.

[tsightler]

Also, remember that VIX will not work unless you either a) disable UAC on the servers being backed up, or b) use the "real" Administrator or Domain Admin account (i.e. the one with the well-known UID 500) as these accounts are exempt from UAC by default.