Availability for the Always-On Enterprise
Post Reply
PrimeNet
Novice
Posts: 3
Liked: 1 time
Joined: Nov 29, 2011 1:20 pm
Full Name: Roger Staerk
Contact:

After Upgrade to B&R 9.5 - broken Synology NAS as Repository

Post by PrimeNet » Nov 27, 2016 12:29 pm

Hi folks

Since we upgraded to the newest B&R 9.5 we cannot use the remote Synology NAS anymore as a Linux-Repository... We tried to remove them and add it from scratch... The add process works fine, but then we cannot use it for e.g. Backup Copy Jobs... Everytime we rescan the Linux Server or the Repository we get an answer "unable to detect IP address"

Before in the v9 this worked like a charm....

Does anybody else has this issue?

Note: Synology NAS on the same subnet works good... We open just port 22 and 2500-5000 TCP in the firewall for the remote NAS.

Thanks for an answer...

PrimNet
Support-ID 00406697

Gostev
Veeam Software
Posts: 22804
Liked: 2801 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by Gostev » Nov 27, 2016 7:30 pm

PrimeNet wrote:Support-ID 00406697
Hello! This is not a valid support case ID, please include the correct one. Thanks!

millardjk
Veeam Vanguard
Posts: 96
Liked: 19 times
Joined: Dec 09, 2012 3:50 am
Full Name: Jim Millard
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by millardjk » Nov 28, 2016 4:20 am

I've got a Synology box (DS2413+ running DSM 6.0.2-8451 Update 4) that I've had to tweak a time or two (http://blog.millard.org/2014/11/use-syn ... itory.html) to keep integrated with Veeam over the versions, but I didn't have to do anything to it after the 9.0->9.5 upgrade. I'd check for the usual network suspects like correct forward/reverse DNS and short/long DNS resolution.

PrimeNet
Novice
Posts: 3
Liked: 1 time
Joined: Nov 29, 2011 1:20 pm
Full Name: Roger Staerk
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by PrimeNet » Nov 28, 2016 11:59 am

@Gostev

Sorry, but this is our only support-ID. Shall I send you a print-screen?

regards
PrimeNet

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by foggy » Nov 28, 2016 12:01 pm

This is probably your company support ID, while we're asking for ID of the case you've opened with Veeam technical support regarding this issue.

PrimeNet
Novice
Posts: 3
Liked: 1 time
Joined: Nov 29, 2011 1:20 pm
Full Name: Roger Staerk
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by PrimeNet » Nov 28, 2016 12:07 pm 1 person likes this post

Hi foggy...

:-) Ok, thanks... Then it is the following ID...
Case # 01982696

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by foggy » Nov 28, 2016 12:16 pm

Thanks, let's see what our engineers could find out from the logs you've provided.

skeezix
Lurker
Posts: 1
Liked: never
Joined: Jan 27, 2017 12:47 am
Full Name: Mike
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by skeezix » Jan 27, 2017 1:13 am

Would love a response on what the problem was with this. Running into the same thing - a remote linux server (synology NAS) worked, but after an upgrade it began having problems. It will connect across the internet to the public IP (forwarding port 22, 2500-5000) and login, but then the logs show it returns the synology's private IPs and tries connecting to those instead of the actual IP in the linux server properties.

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by foggy » Jan 27, 2017 10:43 am

Roger was provided a hotfix that resolved the issue. So I recommend you to install Update 1 (if you haven't yet) and contact technical support if this doesn't help (not sure whether this hotfix was included in the update). Thanks.

millardjk
Veeam Vanguard
Posts: 96
Liked: 19 times
Joined: Dec 09, 2012 3:50 am
Full Name: Jim Millard
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by millardjk » May 09, 2017 3:33 pm

I'm seeing the same behavior (unable to detect IP address) with 9.5.0.823, so it's apparently not in Update 1. The odd piece is that the Util.VolumesHostDiscover_cli.log file on the Synology box shows what appears to be the successful enumeration of IP addresses.

foggy
Veeam Software
Posts: 16691
Liked: 1343 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by foggy » May 15, 2017 4:19 pm

Have you contacted support with this?

vchrizz
Novice
Posts: 4
Liked: never
Joined: Feb 13, 2017 12:27 pm
Full Name: Christoph Loesch
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by vchrizz » Nov 10, 2017 2:06 pm

hi,
i am having same issue using b&r 9.5 with applied update2.
when trying to backup a linux-host, i am getting error "unable to detect ip address".
can the hotfix please be provided like the updates are provided? its cumbersome, to specifically asking for it via support case...
thanks

tdewin
Veeam Software
Posts: 1301
Liked: 426 times
Joined: Mar 02, 2012 1:40 pm
Full Name: Timothy Dewin
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by tdewin » Nov 10, 2017 3:56 pm

Hotfixes are merged in updates. So as long as there is no new update, please work with our support team. You can just refer to this thread and/or existing case by the previous user to speed up the process (01982696)

vchrizz
Novice
Posts: 4
Liked: never
Joined: Feb 13, 2017 12:27 pm
Full Name: Christoph Loesch
Contact:

Re: After Upgrade to B&R 9.5 - broken Synology NAS as Reposi

Post by vchrizz » Nov 10, 2017 5:32 pm

ok, thanks for the explanation!

Post Reply

Who is online

Users browsing this forum: Google [Bot], Majestic-12 [Bot] and 39 guests