Forum Discussion

mlands's avatar
mlands
Level 2
8 years ago

i can´t restore data from a different domain

Hi there,

i would like to backup a server (windows 2016) from a different domain with no trust. I have installed the backup exec agent manually. I can backup files, but we get the message:

backup message:
V-79-57344-38726 - Backup Exec was unable to connect to virtual machine '\(DC)Default(DC)\vm\************\' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup. You must install the Agent for Windows and the virtual machine tools provided by your host software on the virtual machine.

 

-> Agent and VMware Tool was installed!

 

restore message:

Unable to attach to \\************\C:.

V-79-57344-33898 - The resource could not be restored because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.

Make sure that the correct version of the Remote Agent is installed and running on the target computer.

##############

What is the problem? A connection is possible, i can download data from the server in the different domain.

Many thanks in advance.

16
Windows Server 2012 R2

7 Replies

Sort By
  • J_Huggins's avatar
    J_Huggins
    Level 6
    8 years ago

    Is that Backup Server (Windows Server 2016) is running on a Virtual Machine?

    What data are you trying to restore?

     

     

    • mlands's avatar
      mlands
      Level 2
      8 years ago

      Hi J_Huggins,

      my Backup Exec 16 Server is a dedicate Windows Server 2012 R2.

      The Backup Server (other domain) is a virtual Windows Server2016.

      I would like to restore a test-file from a GRT-Backup.

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    8 years ago

    This sounds like a problem talking to the remote agent inside the VM itself - file system GRT backups of a VM do not need to talk to the remote agent inside the VM hence can work successfully.

     

    GRT restores back into the VM itself do need the remote agent to be installed inside the VM and communicating correctly with the BE server. Note we cannot support virtual environments where the virtual network is isolated from the network of the BE server, or where the same hostnames have been used inside different virtual networks (hostnames still have to be unique across all systems involved.)

     

    As such a few tests for you that may help

     

    1) Can you do a traditional agent backups of one file from inside the VM - if you cannnot then you need to fix this backup problem and will probably be able to restore from GRT sets once fixed (you may get a more useful error message by doing this test) - note things like Name resolution, routing into the subnet of the VMs, firewalls blocking NDMP protocol requirements (or aganet publishing) and security logins can all contribute to such problems.

    2) Can you redirect the restore of 1 file to a local disk on the Backup Exec server - this will show that GRT backups are at least operational.

    • mlands's avatar
      mlands
      Level 2
      8 years ago

      Hi 

      • V-79-57344-38730 - Backup Exec was unable to authenticate with virtual machine '\(DC)Default(DC)\vm\den-fs1' and was unable to collect the necessary metadata to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup. You must edit the credentials for the host computer's backup job and then select the proper credentials for the virtual machine.

      • Colin_Weaver's avatar
        Colin_Weaver
        Moderator
        8 years ago

        OK so if the credentials for the VM itself are different from those used to access the host of the VMs then you have to go into the backup job that protects the VMs and set different credentials for the host than the VMs (using the settings available from the left column of the backup job definition)

        However the reason the backup completes and you have GRT selections is that we do not use the remote agent to do file system GRT backups - hence do not actually have to login for the GRT backup to work, however if you still have application GRT enabled in the backup jobs then we will be trying to login to the remote agent even if you do not have any database applications inside the VM (which I suspect is why you have these login errors but still have a GRT backup)