KB ID : 104059
Products :
Published : Jan. 3, 2019
Created : Jan. 3, 2019
Last Modified : Jan. 20, 2020

Cause 1

This alert usually throws when the credentials provided for the guest machine(s) are incorrect.

Solution

  • Check whether the credentials provided for the guest machine(s) are correct or not. You can ensure the given credentials by navigating to the Edit Backup page.

Cause 2

For appaware enabled backups Vembu Backup Agent will try to push an appaware-guest-tool into the guest machine to ensure application consistency. By default, the tool will use installation location as "C:\Windows". So, If the given user account does not have enough permission to create a folder in the location “C:\Windows” in Guest Machine then the backup will fail with the given error.

Solution

  • It is necessary to give administrator account for the appaware process during backup configuration if not edit the backup job and provide the administrator account credentials.

  • Make sure the given user account is having privileges (without elevated permissions) to create a folder inside “C:\Windows” in the guest machine.

Cause 3

A) When added target host is not reachable [ UNC validation path validation [ admin$] ]

B) When there is an issue in accessing Windows Management Instrumentation [ WMI ] of your target host.

C) If guest machines windows firewall enabled, then we have to add windows firewall exception in Group policy object editor.

Solution

Please follow the steps provided below:

For Cause A: When added target host is not reachable - UNC Validation

Target host Remote share [ Admin$ ] is required for copying the VIS installer to the target machine.

You can confirm UNC validation by verifying the admin$ share access manually from your Machine where “VembuBDR” or “VembuVMBackup" had been installed.

        Open 'Run' and type the following  \\IP\admin$
        In place of IP provide the “Hostname\IP“ of the target machine 
        Example: \\192.168.100.100\admin$

Make sure the target host is reachable. If reachable and still you face the above error, then proceed with the following verification:

Case 1: Make sure your firewall does not block following remote connections, if so please add the below rule into your Inbound firewall rules in your target machine

   Step 1: Open control panel 
   Step 2: Navigate to System and security >Windows Firewall >Advanced Setting
   Step 3: In Windows firewall with advanced security, click Inbound Rules.
   Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
   Step 5: In predefined dropdown > select “Remote service Management “ rule and proceed with the default option to enable it and click finish.

Case 2: Make sure Following services are running in your target machine

   Server Service 
   Windows Remote Management (WS -management)

For Cause B: When there is an issue in accessing Windows Management instrumentation [ WMI ] of your target host

Case 1: Make sure your firewall does not block any Windows Management Instrumentation function, if so please add the below rule into your Inbound firewall rules in your target machine

  Step 1: Open control panel 
  Step 2: Navigate to System and security >Windows Firewall >Advanced Setting
  Step 3: In Windows firewall with advanced security, click Inbound Rules.
  Step 4: Inbound rules > click new rule and proceed to opt for Predefined option
  Step 5: In predefined dropdown > select “Windows Management instrumentation “ rule and proceed with the default option to enable it and click finish.

Case 2: Make sure Following services are running in your target machine

    Window Management Instrumentation

For Cause C: If guest machines windows firewall enabled, then we have to add windows firewall exception in Group policy object editor

Configure Windows Firewall service to allow inbound remote administration connections:

  • Launch the Group Policy Object Editor snap-in (gpedit.msc) to edit the Group Policy object (GPO) that is used to manage the Windows Firewall settings in your organization.
  • Navigate to Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall, and then open either Domain Profile or Standard Profile, depending on the profile which you want to configure.
  • Enable the following exception: "Allow inbound remote administration exception".

Enabling the exception: "Allow inbound remote administration exception"

If the issue still persists, please contact Vembu Support.

Cause 4

For appaware enabled backups, Vembu Backup Agent will try to push an appaware-guest-tool into the guest machine to ensure application consistency. By default, the tool will use the installation location as "C:\Windows". So, If the given user account does not have enough permission to create a folder in the location “C:\Windows” in Guest Machine then the backup will fail with the given error.

Solution

1) Change the VembuIntegration service logon user to an admin user in services.msc (By default, VIS service will run in local system account).

2) Restart the VembuIntegrationService once the logon user is changed.

3) Now try to trigger the backup again.

edit retag flag offensive close merge delete