Backup & Recovery 11 Adv. Server tape backup + Hyper-V

Userguide 6.3.3.1 ( http://www.acronis.com/support/documentation/ABR11/index.html#14309.html ) it's possible to use autoloader with agent alone. In this case only this agent can backup data to this tape device. However if you need to backup other machines to this autoloader, you need to install Storage Node component on the hyper-v host and use it to operate managed vault organized on the tape.

how does the Agent access the other systems

It depends on what is 'access'. If, in this case, other systems are not Hyper-V VMs on the host, it can read and write to SMB shares on these systems with credentials you specify.

Hello dev-anon,

thanks for your help. The Management Server is now installed on the SBS and an Agent as well as Storage Node were put on the Hyper-V. The Management Console is able to connect to the Agent and even the Autoloader with its tapes is recognised correctly. I've made the decision to use the Agent on the Hyper-V alone to backup files to the Autoloader. All other machines should write their backup to a NAS and let the Agent grab it from there.

After creating a backup task and starting a test backup of files storaged on the NAS, the task stops with several warnings and errors. That's what the log says:

--------------------
Details
--------------------
Typ:            Warnung
Datum und Zeit: 25.06.2012 11:56:35
Backup-Plan:    Backup 25.06.2012 11:29:50
Task:           Einfaches Backup (Vollständig)
Code:           66.606(0x1042E)
Modul:          1
Besitzer:       AdminUser@HYPERVHOST
Nachricht:     
  Aktivieren der Berechtigung 'SeBackupPrivilege' fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 1070
Module: 1
LineInfo: 30b406c3bf94bb35
Felder:  $module : disk_bundle_vs
Nachricht: Aktivieren der Berechtigung 'SeBackupPrivilege' fehlgeschlagen.
--------------------
Fehlercode: 65520
Module: 0
LineInfo: bd28fdbd64edb8e0
Felder:  code : 2147943700, $module : disk_bundle_vs
Nachricht: Dem Aufrufer wurden nicht alle angegebenen Berechtigungen und Gruppen zugewiesen
--------------------
--------------------

I already checked the users "ASN User", "Acronis Agent User" as well as the login user - all of them are members of the groups "Acronis Remote Users", "Backup Operators" and "Administrators". In local security policy, "ASN User" and "Acronis Agent User" have the right to logon as service.

According to the log, there is a problem activating a function called "SeBackupPrivilege".

I have no clue where to look for, do you have any idea?

Best regards,

Meeko

Does AdminUser (I assume it was the user specified in backup plan properties to run the task) has these privileges too? (i.e. member of Backup Operators? )
Run secpol.msc , local policies->user rights assignment , are these users )or their groups) included in list of user having 'backup files and directories" privilege. (and 'restore files and directories too)
Does it fail with the same error for a file backup of local files?

Hello dev-anon,

Does AdminUser (I assume it was the user specified in backup plan properties to run the task) has these privileges too? (i.e. member of Backup Operators? )

Yes, AdminUser has the same privileges.

In secpol.msc, the groups 'Administrators' and 'Backup operators' where already added to the backup and restore privileges. To exclude an error pointing in this direction, I also added the Users to them, with no difference when trying to start the backup task.

I also tried a simple file backup from a local partition to the Autoloader. It fails with almost the same log messages.
Backing up these files to an Image file fails completely during task creation. Also a backup of complete volumes is not possible - they simply do not showing up on the right when selecting the computer.

-------------------------------------------------------------------------------
Fehler
-------------------------------------------------------------------------------
Der von Ihnen gewählte Ordner existiert nicht. Wählen Sie einen anderen Ordner.
-------------------------------------------------------------------------------
Details:
Code: 10.092.549(0x9A0005)
LineInfo: 0x9A79F20828BC7F3;

Modul: disk_bundle_vs
Nachricht: GetFileInfo Aufruf von FileManager fehlgeschlagen.

Code: 10.092.549(0x9A0005)
LineInfo: 0x9A79F20828BCC54;

Modul: disk_bundle_vs
Nachricht: GetFileInfo Aufruf von FileManager fehlgeschlagen.

Code: 262.161(0x40011)
LineInfo: 0xF35F747B3B21FB55;

Modul: mms_vs
Nachricht: Die spezifizierte Datei existiert nicht.

Code: 65.520(0xFFF0)
LineInfo: 0xBD28FDBD64EDB8E0;

Modul: disk_bundle_vs
Nachricht: Das System kann die angegebene Datei nicht finden

-------------------------------------------------------------------------------

There is one thing I haven't mentioned before. When I'm trying to connect to the Agent on the Hyper-V via Management Console on the SBS, a warning window pops up which says there is a difference between the program version of the Agent and the Console. The Agent is recognised as Build 17438 while the installation of the Management Server has Build 17437. This is odd, because I've installed the Agent provided by the web interface of the Management Server itself.

Besides of this confusing fact, is it possible that the different Builds are incompatible?

Best regards,
Meeko

Also a backup of complete volumes is not possible - they simply do not showing up on the right when selecting the computer.

It seems that you haven't installed "Agent for Windows". If you go to add/remove programs in control panel , you'll probably see 'Acronis B&R Agent core' and "Agent for Hyper-V", but not "Agent for Windows". You need it to backup files and local volumes. Agent for Hyper-V can only backup volumes of virtual machines.

Hello dev-anon,

the Agent Core and the Agent itself were installed. In case something went wrong while installing (I've installed the Agent after the Storage Node), I removed every Acronis component installed on the Hyper-V. After finishing, I've started the setup.exe again which was previously provided by the web interface.

After providing information about the License Server, the setup seems to recognize the license correctly. The setup downloads the selected components (Agent Core & Agent ; no Agent for Hyper-V was selected) and hangs for a long time during the installation of the Agent Core.

At the end, the installation is reported as successfully but a warning message comes up after the Agent core was installed:

Acronis Backup & Recovery 11 Agent Core
Code: 013763087
Zeilenkennung: 0x851efe822fcbb3a7
Nachricht: Hinzufügen der Maschine zum Management Server fehlgeschlagen.

Subfehler
Code: 014417960
Zeilenkennung: 0x2a4cf6302dc72c47
Nachricht: Interner Fehler: Befehlsausführung ist fehlgeschlagen.

Subfehler
Code: 014417953
Zeilenkennung: 0x2a4cf6302dc72c7d
Nachricht: Hinzufügen des Acronis Managed Machine Service zum Acronis Management Server fehlgeschlagen.

Subfehler
Code: 014417953
Zeilenkennung: 0x2a4cf6302dc72c8a
Nachricht: Hinzufügen des Acronis Managed Machine Service zum Acronis Management Server fehlgeschlagen.

Subfehler
Code: 020250646
Zeilenkennung: 0x8d165e86fb8195e2
Nachricht: TOL: Failed to execute the command. Diese Aktion registriert die Maschine auf dem Acronis Backup & Recovery 11 Management Server.

Subfehler
Code: 021430291
Zeilenkennung: 0xa76a04993e79384c
Nachricht: Authentifizierung fehlgeschlagen.

Subfehler
Code: 021430290
Zeilenkennung: 0xa76a04993e79385e
Nachricht: Migrieren der Daten zum License Server fehlgeschlagen.

Subfehler
Code: 013238285
Zeilenkennung: 0xec81f6265c058039
Nachricht: Aufbau der Verbindung fehlgeschlagen. Überprüfen Sie die angegebene Adresse der Maschine.

First I thought this could be a Firewall issue so I created rules for ports TCP9876 and TCP25001 manually (on Hyper-V and SBS where Management Server is installed), without any difference.
If this is only an issue of registering the Agent, how can I do it manually to try a bit more without always reinstalling the components?

Best regards,
Meeko

You can manually register agent in Management Server the following way:
Run management console, connect to agent, go to options->machine options, select 'machine management' from the list, specify 'centralized'.