-
- VP, Product Management
- Posts: 7167
- Liked: 1537 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Synology/Veeam Problem. Does someone have one in the Lab?
Hi Team,
we have a customer that uses a Synology
Synology RS3412RPxs with DSM Firmware auf DSM 4.2.
Some LUNs mapped by iSCSI to VMware ESXi Server and to the Veeam Server for Direct SAN based backups.
Additionaly the customer added a LUN for data (Repository) to the Veeam Server only.
The Problem is if Veeam searches for the right volume to read data out of the SAN, the Synology dropes the Connection of the Veeam only LUN and the disk isn´t accessible anymore.
Hard reboot needed at Synology to get it back online.
Synology reports that there is a known Performance issue with Veeam, that they do not know why this exists and that it has a low prority for fix.
They say that with other VMware backup solutions it works well.
I think this problem does not match to a performance problem, because there are only metadata transfered (LUN identifier).
Does someone have a Synology, too and can counter check this bug? Thanks in advance ... Andy
we have a customer that uses a Synology
Synology RS3412RPxs with DSM Firmware auf DSM 4.2.
Some LUNs mapped by iSCSI to VMware ESXi Server and to the Veeam Server for Direct SAN based backups.
Additionaly the customer added a LUN for data (Repository) to the Veeam Server only.
The Problem is if Veeam searches for the right volume to read data out of the SAN, the Synology dropes the Connection of the Veeam only LUN and the disk isn´t accessible anymore.
Hard reboot needed at Synology to get it back online.
Synology reports that there is a known Performance issue with Veeam, that they do not know why this exists and that it has a low prority for fix.
They say that with other VMware backup solutions it works well.
I think this problem does not match to a performance problem, because there are only metadata transfered (LUN identifier).
Does someone have a Synology, too and can counter check this bug? Thanks in advance ... Andy
-
- Veeam Software
- Posts: 768
- Liked: 162 times
- Joined: Feb 01, 2013 8:15 am
- Full Name: Pieter Vereecken
- Location: The Netherlands
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
What I've had with a customer is that when he backed up to the Synology (repository) it had the same behavior and we solved it by limiting the combined data ingestion rate to a fixed amount. I don't know if that can help you in this case, but I thought I'd share.
Pieter Vereecken
Solutions Architect Team Leader, EMEA
Solutions Architect Team Leader, EMEA
-
- VP, Product Management
- Posts: 7167
- Liked: 1537 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
Will check with customer. Thank you very much.
-
- VP, Product Management
- Posts: 7167
- Liked: 1537 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hi Team,
customer finally had a webex with some developers from Synology.
They created a custom script that checks the metadata of the Synology of specific LUNs.
With this script they identified nearly 850MB of corrupt volume metadata.
Customer deleted the volume and created a new one. Backups run without Problems now.
customer finally had a webex with some developers from Synology.
They created a custom script that checks the metadata of the Synology of specific LUNs.
With this script they identified nearly 850MB of corrupt volume metadata.
Customer deleted the volume and created a new one. Backups run without Problems now.
-
- Veeam Software
- Posts: 712
- Liked: 168 times
- Joined: Nov 30, 2010 3:19 pm
- Full Name: Rick Vanover
- Location: Columbus, Ohio USA
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
New issue.
This came up a while ago, and just now on Twitter. But here is the Twitter conversation: https://twitter.com/RER_iTinker/status/ ... 3387130884
Short answer is that user found that DSM 6.0-7321 broke his Linux connection, he ended up "adding a non-root account to sudoers file on @Synology device + elevate to root for it @veeam works."
This came up a while ago, and just now on Twitter. But here is the Twitter conversation: https://twitter.com/RER_iTinker/status/ ... 3387130884
Short answer is that user found that DSM 6.0-7321 broke his Linux connection, he ended up "adding a non-root account to sudoers file on @Synology device + elevate to root for it @veeam works."
-
- Influencer
- Posts: 24
- Liked: 4 times
- Joined: Aug 09, 2012 8:16 am
- Full Name: Stan
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
I had no success with this method
Root is now available only via certificat
SO what I suggest is to:
Launch puttygen.exe
Type of key to generate “SSH-2 RSA”
copy the generated key on the uper windows
save pub and priv key on the desktop
then:
putty login as admin
then sudo su (you're root now)
then:
vi /etc/ssh/sshd_config
change:
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
cd /root/.ssh
vi .ssh/authorized_keys
copy your pub key from puttygen.exe (in the uper windows of puttykeygen)
:wq! (to exit save vi)
change the permissions on the authorized_keys file
chmod 700 /root/.ssh
chmod 644 /root/.ssh/authorized_keys
then in Veeam
go to backup infrastructure
linux
edit server
ssh connection
add linux private key (the one saved on the desktop)
no passphrase
use as credential
finish
You're done
veeam is root again and can rescan storage

Root is now available only via certificat
SO what I suggest is to:
Launch puttygen.exe
Type of key to generate “SSH-2 RSA”
copy the generated key on the uper windows
save pub and priv key on the desktop
then:
putty login as admin
then sudo su (you're root now)
then:
vi /etc/ssh/sshd_config
change:
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
cd /root/.ssh
vi .ssh/authorized_keys
copy your pub key from puttygen.exe (in the uper windows of puttykeygen)
:wq! (to exit save vi)
change the permissions on the authorized_keys file
chmod 700 /root/.ssh
chmod 644 /root/.ssh/authorized_keys
then in Veeam
go to backup infrastructure
linux
edit server
ssh connection
add linux private key (the one saved on the desktop)
no passphrase
use as credential
finish
You're done
veeam is root again and can rescan storage

-
- Service Provider
- Posts: 129
- Liked: 27 times
- Joined: Apr 01, 2016 5:36 pm
- Full Name: Olivier
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
What version of Veeam do you use?
I get always an "invalid private key" message from my v9 while with a regular ssh it works
Oli
I get always an "invalid private key" message from my v9 while with a regular ssh it works
Oli
-
- Influencer
- Posts: 24
- Liked: 4 times
- Joined: Aug 09, 2012 8:16 am
- Full Name: Stan
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
V9
did you follow my tuto ?
It works on 2 environment
did you follow my tuto ?
It works on 2 environment
-
- Service Provider
- Posts: 129
- Liked: 27 times
- Joined: Apr 01, 2016 5:36 pm
- Full Name: Olivier
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
I didn't get time to get on the problem again, but I suspect it is the type of ssh encryption veeam support is the problem. I need to check the sshd config on the Synology.
Oli
Oli
-
- Novice
- Posts: 6
- Liked: 2 times
- Joined: May 25, 2015 11:08 am
- Full Name: Manfred Lang
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hello All,
after a long time of Troubleshooting, Veeam Synology Linux Agent Integration to Synology NAS (Veeam Datamover inside of Synology) works again now.
There was not only the problem with the new sudo behavior, there was also a problem with the /tmp SFTP Access and with the Veeam "Renci SSH" implementation. Veeam is using "Renci SSH" instead of "Granados SSH" if diffie-hellman-group1-sha1 is not enabled on Synology. "Renci SSH" is running in a "Message type 80" Problem in most installations (not all, some work with "Renci SSH").
I wrote a Synology Installation documentation for successful Veeam Data Mover (Linux Repository) on Synology Systems.
Feel free to download my full Synology documentation (but in german language) from http://langs-world.spdns.de/Downloads/S ... sitory.pdf
PS: I don't know, if this is working on Non-Intel Synologys, I only tested Synologys with Intel CPU.
Best regards,
Manfred
after a long time of Troubleshooting, Veeam Synology Linux Agent Integration to Synology NAS (Veeam Datamover inside of Synology) works again now.
There was not only the problem with the new sudo behavior, there was also a problem with the /tmp SFTP Access and with the Veeam "Renci SSH" implementation. Veeam is using "Renci SSH" instead of "Granados SSH" if diffie-hellman-group1-sha1 is not enabled on Synology. "Renci SSH" is running in a "Message type 80" Problem in most installations (not all, some work with "Renci SSH").
I wrote a Synology Installation documentation for successful Veeam Data Mover (Linux Repository) on Synology Systems.
Feel free to download my full Synology documentation (but in german language) from http://langs-world.spdns.de/Downloads/S ... sitory.pdf
PS: I don't know, if this is working on Non-Intel Synologys, I only tested Synologys with Intel CPU.
Best regards,
Manfred
-
- VP, Product Management
- Posts: 7167
- Liked: 1537 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hi Manfred,
thanks for sharing this.
Non Intel x86 compatible CPU will not work as there are only datamover that can work on x86 and x86-64 CPUs.
All other systems can be integrated as CIFS repositories. Other options are to use iSCSI from a Windows or Linux Repository Server or NFS together with a Linux repository Server.
thanks for sharing this.
Non Intel x86 compatible CPU will not work as there are only datamover that can work on x86 and x86-64 CPUs.
All other systems can be integrated as CIFS repositories. Other options are to use iSCSI from a Windows or Linux Repository Server or NFS together with a Linux repository Server.
-
- Technology Partner
- Posts: 22
- Liked: 6 times
- Joined: Jun 18, 2013 9:05 am
- Full Name: Hendrik Bardowicks
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hi Manfred,
just tested your documentation with a DS216+ , DSM 6 and Veeam B&R v9.
NFS connection works. Thank you.
just tested your documentation with a DS216+ , DSM 6 and Veeam B&R v9.
NFS connection works. Thank you.
-
- Novice
- Posts: 6
- Liked: 2 times
- Joined: May 25, 2015 11:08 am
- Full Name: Manfred Lang
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hi Hendrik,
thank you for your response. But please note, it's not a NFS Connection, it's the proprietary Veeam connection going to the Veeam Linux Agent (= Veeam Perl Data Mover) running inside of the Synology.
This is the fastest and safest way to use Synology with Veeam. Safest because the repository won't be damaged if the network connection breaks while a backup job is working, fastest because the network connection is compressed and the repository maintenance tasks are working inside the Synology with local disk access.
The only disadvantages are: The Synology must have an Intel CPU and should have at least 2GB RAM, better 4GB RAM or more.
PS: If someone is interested: I also successfully added QNAPs to Veeam, but the preparation of QNAPs is much more complex (including compilation of additional perl modules with cpan) and not 100% functioning (Veeam can't see freespace on QNAP storage).
Regards, Manfred
thank you for your response. But please note, it's not a NFS Connection, it's the proprietary Veeam connection going to the Veeam Linux Agent (= Veeam Perl Data Mover) running inside of the Synology.
This is the fastest and safest way to use Synology with Veeam. Safest because the repository won't be damaged if the network connection breaks while a backup job is working, fastest because the network connection is compressed and the repository maintenance tasks are working inside the Synology with local disk access.
The only disadvantages are: The Synology must have an Intel CPU and should have at least 2GB RAM, better 4GB RAM or more.
PS: If someone is interested: I also successfully added QNAPs to Veeam, but the preparation of QNAPs is much more complex (including compilation of additional perl modules with cpan) and not 100% functioning (Veeam can't see freespace on QNAP storage).
Regards, Manfred
-
- Expert
- Posts: 114
- Liked: 25 times
- Joined: Dec 09, 2012 3:50 am
- Full Name: Jim Millard
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
I know people are doing various workarounds, but my solution was possibly the simplest of all: I used the CLI to reset the root password to something I know--in this case, the same root password I used prior to updating to DSM6, so I didn't have to update the credentials in Veeam--and everything is working as it did under DSM5.
Updating the root password:
1) login via SSH using the same credentials used for admin login using the web client
2) issue the following to get an elevated prompt: sudo su -
3) issue the following to reset the password: synouser –setpwd root password_same_as_admin_or_not
Updating the root password:
1) login via SSH using the same credentials used for admin login using the web client
2) issue the following to get an elevated prompt: sudo su -
3) issue the following to reset the password: synouser –setpwd root password_same_as_admin_or_not
-
- Novice
- Posts: 6
- Liked: 2 times
- Joined: May 25, 2015 11:08 am
- Full Name: Manfred Lang
Re: Synology/Veeam Problem. Does someone have one in the Lab
Hello,
The root elevation isn't any problem with Veeam and your solution is just affecting the root elevation.
Regards, Manfred
Don't only think about upgraded Synologys, also think about new installations starting with DSM 6. New DSM 6 installations are diferent from upgraged ones, the upgrade process don't touch a lot of the old DSM 5 system settings.millardjk wrote:I know people are doing various workarounds, but my solution was possibly the simplest of all: I used the CLI to reset the root password to something I know--in this case, the same root password I used prior to updating to DSM6, so I didn't have to update the credentials in Veeam--and everything is working as it did under DSM5.
The root elevation isn't any problem with Veeam and your solution is just affecting the root elevation.
Regards, Manfred
-
- Expert
- Posts: 114
- Liked: 25 times
- Joined: Dec 09, 2012 3:50 am
- Full Name: Jim Millard
- Contact:
Re: Synology/Veeam Problem. Does someone have one in the Lab
Good point; there can also be some "interesting" changes when doing upgrades starting as DSM 4.Don't only think about upgraded Synologys, also think about new installations starting with DSM 6. New DSM 6 installations are diferent from upgraged ones, the upgrade process don't touch a lot of the old DSM 5 system settings.
Who is online
Users browsing this forum: Amazon [Bot], Fippu, Google [Bot] and 163 guests