Backup from NAS to Tape fails with "No connection to Remote-Computer"

...you're got a remote agent licensed and installed on the media server, correct?

Backing up to tape would probably be slower due to the stop/start nature of backing up files of different sizes, where B2D would be faster.

THanks!

Of course we've got a remote agent licensed, but not installed on the remote server, because there is no remote agent for Synology NAS.

Well, I tested it with a 123 GB File. The job to disk (12x 1TB SATA HDD 7.200 RPM in RAID6) run with round about ~3 GB where the job to tape (LTO6) run with round about ~7,5 GB - 8 GB. Of course, that was an idealistic scenario with one single large file. However, that was quite impressive. But let's wait for the productive environment, especially with tapes ... ;-)

It won't install on the NAS unless it runs Windows Storage Server.

Is the remote agent installed on the media server?

Don't get me wrong - I already know that it won't install on the NAS, because there is no working / existing Agent for the Synology NAS, which is running with an (from Synology) self build Linux. Because of this, I have to backup over Network Share via SMB (without an Agent)

I guess with "Media Server" you mean the "Backup Server", on which Backup Exec is installed, don't you?

Well, I thought an agent is already installed on the "Backup Server" together with Backup Exec, especially because the "Backup Server" was / is already listed in Backup Exec.

So, because of your reply, I tried to add the "Backup Server" (on which Backup Exec is already installed and which is already listed in Backup Exec Software) in Backup Exec again, choose it as "Windows Server", and as a result of this, the Backup Exec Software installed an agent on the "Backup Server" (or it seemed so). After that I did a reboot of the "Backup Server" and tried a backup from the NAS directely to tape again.

And it failed again. Btw. Failure-Code E0000F02

I'm still wondering, because Backup from the NAS to Disk (on the Backup Server) already works, also the Backup from local files on the Backup Server to Tape.

Would you post the complete failed job log ? Thanks.

Of course. But i'm sorry, it's a german Backup Exec ;-)

Der Backup Exec-Server konnte keine Verbindung zur Remote-Maschine XYZ mit dem Protokoll IPv4 aufbauen.

Laufwerk und Laden von Medium angefordert: 03.07.2015 09:14:19

Laufwerks- und Medieninformationen von Medienladevorgang: 03.07.2015 09:15:29
Wechslername : Wechsler01 an XYZ
Laufwerkname: Bandlaufwerke01 in Wechsler01
Medienschacht: 1
Medienkennung: HZ9620L6
Medien-GUID: {23f2a4ab-ec94-4c37-89f6-4e7b1333304c}
Überschreibschutz bis: 02.07.2015 18:27:32
Anhängbar bis: 31.12.9999 01:00:00
Name des Ziel-Mediensatzes: Mediensatz 0001
Aufbewahren für: 1 Stunde(n)


Alle verwendeten Medien
 HZ9620L6

Medienvorgang - An Medium anhängen oder überschreiben, falls kein anhängbares Medium verfügbar ist.

Komprimierungstyp: Software

Verschlüsselungstyp: Keine

Der Backup Exec-Server konnte keine Verbindung zur Remote-Maschine XYZ mit dem Protokoll IPv4 aufbauen.

Auftrag beendet am Freitag, 3. Juli 2015 um 09:15:31
Abschlussstatus: Fehlgeschlagen
Endgültiger Fehler: 0xe0000f02 - Vom Backup Exec-Server konnte keine Verbindung mit dem Remote-Computer hergestellt werden. Möglicherweise befindet sich der Remote-Computer nicht im ausgewählten Subnetz. Versuchen Sie eine andere Netzwerkschnittstelle oder lassen Sie Backup Exec eine beliebige verfügbare Netzwerkschnittstelle wählen.
Endgültige Fehlerkategorie: Ressourcenfehler

Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-3842

Der Backup Exec-Server konnte keine Verbindung zur Remote-Maschine XYZ mit dem Protokoll IPv4 aufbauen.

Satztyp                  : Sichern
Satzstatus             : Fehlgeschlagen
Satzbeschreibung         : 

Ressourcenname           : XYZ
Anmeldekonto             : 
Verwendete Verschlüsselung        : Keine

Fehler                   : e0000f02 - Vom Backup Exec-Server konnte keine Verbindung mit dem Remote-Computer hergestellt werden. Möglicherweise befindet sich der Remote-Computer nicht im ausgewählten Subnetz. Versuchen Sie eine andere Netzwerkschnittstelle oder lassen Sie Backup Exec eine bel

Benutzter Agent                   : Ja
Benutzte Advanced Open File Option: Nein

And to confirm, no settings have been set under the Network & Security options of the backup job ? Ideally, it should be set to use any available interface or subnet.

Thanks for your fast reply!

I tried every possible combination with same result. Actually it's set to Any Netzworkinterface and Protocol to IPv4.

Well, I configured a LACP in Windows Server 2012 R2 - but that shouldn't be the problem, because the connection to the NAS and the backup from the NAS to Disk (in Backup Server) works successfully. Only the Backup from the NAS to Tape fails.