#1 2019-07-08 10:24:44

Rasmus
Member
Registered: 2019-06-24
Posts: 4

Error DFUPCID0

Hi.
I just updated to 11.2.5, and now I get error messages relating to unknown cipher type.
CLRSYNC4: Unknown cipher type 'chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc'

When I reverted to 11.2.3 it appeared to work again.
Does anyone have an idea  what could cause this problem?

Best regards

Last edited by Rasmus (2019-07-08 12:15:27)

Offline

#2 2019-07-09 12:15:00

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

Yes, when we detect that OpenSSH version is 6.5 or above, we prepend chacha20-poly1305@openssh.com to the list of ciphers to use in SSH transfers. The reason is that that cipher created by Prof. Daniel Berstein, is far lighter than regular AES, while still keeping a high level of security, thus tranfer speeds boost up when using it.

We can be pretty sure that OpenSSH includes it, nevertheless, there could always be some bug at detecting it when combining different ESXi versions. What ESXi versions are you using?

UPDATE:

The change log reflects this change in version 11.2.5. Please contact us if you are still getting this error, it can be easily fixed.

https://33hops.com/xsibackup-change-log.html

Offline

#3 2019-07-09 21:16:14

Rasmus
Member
Registered: 2019-06-24
Posts: 4

Re: Error DFUPCID0

Hello again. I am running 6.7 update 1 on both hosts. I am aware of the change log, but I am not able to understand why this should give me problems, and actually render onediff unusable. If you have a fix for this, it would be highly appreciated.

Sincerely
Rasmus

Offline

#4 2019-07-09 22:49:30

jybleau
Member
Registered: 2019-07-08
Posts: 4

Re: Error DFUPCID0

Hello, I'm having the same error on a newly setup ESXi 6.5u2 using 11.2.5. I run using "xsitools" backup prog.

error: cannot copy VMX file, details: Unknown cipher type 'chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-
cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc'


Source OS is: 6.5.0 Update 2 (Build 13635690) (Dell ISO)
Destination OS is: ESXi 6.5.0 Update 2 (Build 13004031) (Dell ISO)
ssh -V gives: OpenSSH_7.7p1, OpenSSL 1.0.2p-fips  14 Aug 2018

I don't have the error between 2 other ESXi 6.5u2 servers that are using version 11.2.3.

How do I contact you so "it can be easily fixed" ?

Thanks

Last edited by jybleau (2019-07-09 22:53:01)

Offline

#5 2019-07-09 22:53:40

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

Our fault, the chacha20-poly1305@openssh.com cipher was removed from the list of OpenSSH vSphere drivers, most probably cause its not FIPS compliant. We'll fix this issue tomorrow, or should I say today :-)

Offline

#6 2019-07-10 12:23:37

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

We have published a fix as XSIBackup-Pro 11.2.6
We will be actively improving this branch, so any eventual new issue will be fixed rapidly.

Offline

#7 2019-07-10 13:18:27

Rasmus
Member
Registered: 2019-06-24
Posts: 4

Re: Error DFUPCID0

Ok, so I installed 11.2.6, and no joy. Actually even worse. Now I also receive the UTF 8 error mesage that a different user also complained about. I am not very experienced with VM Ware, and I am really afraid of messing up the original VM machines. They seem to be littered with snapshots an logfiles from countelss of failed backups.
Here is a parts of my latest logfile. And just to make it clear, I have not manualy modified any .vmx file. I dont even know how to.

2019-07-10T13:03:51|  Removing snapshots, please wait...
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:53|  Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] error: cannot copy VMX file, details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] error: cannot copy VMSD file, details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] info: no .vmxf file found
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] info: no .nvram file found
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-000001-sesparse.vmdk
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-000001.vmdk
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-Snapshot31.vmsn
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-Snapshot88.vmsn
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Disk [/vmfs/volumes/datastore1/Frontend/Frontend-000001-sesparse.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Disk [/vmfs/volumes/datastore1/Frontend/Frontend-000001.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend-Snapshot31.vmsn
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend-Snapshot31.vmsn
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend-Snapshot88.vmsn
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend-Snapshot88.vmsn
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend.vmdk
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend.vmdk
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Info: transfering file | /vmfs/volumes/datastore1/Frontend/Frontend-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:08|  [Frontend] CLXSIDF1 error: file transfer error: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:08|  Excluded disks removed from backup .vmx file
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:10|  [Frontend] error OVMXCHK2: VMX file check 2 fail, details: first line in .vmx file is not [.encoding = "UTF-8"], has this file been manually modified/edited?
2019-07-10T13:04:11|  [Frontend] error CPVMXCNT: could not update VMX file in [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] error DIFDVMSD: could not delete VMSD file in [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] info: Updating CID at [192.168.148.3:22:/vmfs/volumes/datastore2/Frontend/Frontend.vmdk]
2019-07-10T13:04:11|  [Frontend] error DIFUPCID: cannot update CID at VM [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] info: backup complete
2019-07-10T13:04:11|  [Frontend] info: finished doing a first copy in a diff scope, subsequent backups will be differential
2019-07-10T13:04:11|  [Frontend] info: should you need to use the mirror VM, register it manually at the backup ESXi host
----------------------------------------------------------------------------------------------------------------------------

Last edited by Rasmus (2019-07-10 16:59:00)

Offline

#8 2019-07-10 15:27:20

jybleau
Member
Registered: 2019-07-08
Posts: 4

Re: Error DFUPCID0

Hello,

I got it fixed using 11.2.6 but with the new --ssh-ciphers option.

My ESXi version is: 6.5.0 build-13635690 (from the Dell maintained ISO).
It still tried with the chacha20-poly1305@openssh.com, etc. ciphers and failed.

It still failed with: --ssh-ciphers=aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc

But it finally worked by using the "exact" ciphers list found in /etc/ssh/sshd_config file, which is like this:
--ssh-ciphers=aes128-ctr,aes192-ctr,aes256-ctr,3des-cbc


Very restrictive indeed... I don't know if you could/should base your default cipher list on the sshd_config file (?)

Thanks

Last edited by jybleau (2019-07-10 15:47:27)

Offline

#9 2019-07-10 16:24:18

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

It should work just as long as one of the ciphers offered by the client exists in the server.
This is the output from one of our 6.5.0 test servers:

[root@esxi21:/vmfs/volumes/57e961ea-90e2ba-2d89c4/xsi-dir] vmware -v
VMware ESXi 6.5.0 build-4564106
[root@esxi21:/vmfs/volumes/57e961ea-90e2ba-2d89c4/xsi-dir] ssh -Q cipher
3des-cbc
blowfish-cbc
cast128-cbc
arcfour
arcfour128
arcfour256
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-cbc@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
aes256-gcm@openssh.com
chacha20-poly1305@openssh.com

The client offers these ciphers, but then the sshd_config file has these:

blowfish-cbc,aes128-ctr,aes192-ctr,aes256-ctr,3des-cbc

Which is clearly inconsistent.

I believe VMWare has been extremely concerned about the multiple security issues that have affected OpenSSH in the last years and how that could affect them as a brand. They have probably became progressively paranoid, cause they have removed a number of useful ciphers and they seem to be narrowing everything down to FIPS compliant stuff.

The thing is that SSH is much more than a way to tunnel shell commands. Some of these ciphers are so inneficcient, in terms of speed, that they limit SSH/SCP speed by 50-60% when compared to unencrypted data transfers with NetCat (nc). Then users start spreading urban legends about ESXi Shell network throughput being limited..., it's not the shell network speed that's limited, it's the fact that it uses one core and SSH uses extremely heavy ciphers.

chacha20-poly1305@openssh.com is a beam of light in regards to this, as it offers a high level of security but due to its nature it is extremely efficient.

Offline

#10 2019-07-10 17:48:13

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

Your problem is with the cipher, which is in turn causing the other error.
Please, contact support with all details:

- ESXi version.
- Full backup job.
- Full output log.

Rasmus wrote:

Ok, so I installed 11.2.6, and no joy. Actually even worse. Now I also receive the UTF 8 error mesage that a different user also complained about. I am not very experienced with VM Ware, and I am really afraid of messing up the original VM machines. They seem to be littered with snapshots an logfiles from countelss of failed backups.
Here is a parts of my latest logfile. And just to make it clear, I have not manualy modified any .vmx file. I dont even know how to.

2019-07-10T13:03:51|  Removing snapshots, please wait...
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:53|  Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] error: cannot copy VMX file, details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] error: cannot copy VMSD file, details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] info: no .vmxf file found
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:03:56|  [Frontend] info: no .nvram file found
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-000001-sesparse.vmdk
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-000001.vmdk
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-Snapshot31.vmsn
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend-Snapshot88.vmsn
2019-07-10T13:04:07|  DISK=/vmfs/volumes/datastore1/Frontend/Frontend.vmdk
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Disk [/vmfs/volumes/datastore1/Frontend/Frontend-000001-sesparse.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Disk [/vmfs/volumes/datastore1/Frontend/Frontend-000001.vmdk] excluded
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend-Snapshot31.vmsn
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend-Snapshot31.vmsn
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend-Snapshot88.vmsn
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend-Snapshot88.vmsn
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Rsync file transfer (1st)
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  From: /vmfs/volumes/datastore1/Frontend/Frontend.vmdk
2019-07-10T13:04:07|  To: /vmfs/volumes/datastore2/Frontend/Frontend.vmdk
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  [Frontend] error CLRSYNC4: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:07|  rsync: connection unexpectedly closed (0 bytes received so far) [sender]
2019-07-10T13:04:07|  rsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:07|  Info: transfering file | /vmfs/volumes/datastore1/Frontend/Frontend-flat.vmdk
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:08|  [Frontend] CLXSIDF1 error: file transfer error: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:08|  Excluded disks removed from backup .vmx file
---------------------------------------------------------------------------------------------------------------------------------
2019-07-10T13:04:10|  [Frontend] error OVMXCHK2: VMX file check 2 fail, details: first line in .vmx file is not [.encoding = "UTF-8"], has this file been manually modified/edited?
2019-07-10T13:04:11|  [Frontend] error CPVMXCNT: could not update VMX file in [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] error DIFDVMSD: could not delete VMSD file in [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] info: Updating CID at [192.168.148.3:22:/vmfs/volumes/datastore2/Frontend/Frontend.vmdk]
2019-07-10T13:04:11|  [Frontend] error DIFUPCID: cannot update CID at VM [Frontend_XSIBAK], details: Unknown cipher type 'arcfour,blowfish-cbc,aes128-ctr'
2019-07-10T13:04:11|  [Frontend] info: backup complete
2019-07-10T13:04:11|  [Frontend] info: finished doing a first copy in a diff scope, subsequent backups will be differential
2019-07-10T13:04:11|  [Frontend] info: should you need to use the mirror VM, register it manually at the backup ESXi host
----------------------------------------------------------------------------------------------------------------------------

Offline

#11 2019-07-10 18:27:51

jybleau
Member
Registered: 2019-07-08
Posts: 4

Re: Error DFUPCID0

In reply to #9

I get this output from
  VMware ESXi 6.5.0 build-13004031 and
  VMware ESXi 6.5.0 build-13635690:

[root@vm2:~] ssh -Q cipher
3des-cbc
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-cbc@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
aes256-gcm@openssh.com
chacha20-poly1305@openssh.com
[root@vm2:~] cat /etc/ssh/sshd_config | grep Ciphers
Ciphers aes128-ctr,aes192-ctr,aes256-ctr,3des-cbc

My list of ssh client ciphers is shorter than the one you get.

I also just tried a backup that successfully completed by adding the chacha20-poly1305@openssh.com like this in the backup command:

xsibackup --backup-point=aServerPath --backup-type=custom 
--backup-vms=aVM --backup-prog=xsitools 
--ssh-ciphers=chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,3des-cbc

I still got the negociated ciphers as:

Negotiated Cipher (server->client): aes128-ctr
Negotiated Cipher (client->server): aes128-ctr

It seems like... if one of the ciphers I specify in the --ssh-ciphers option is not in the ssh -Q cipher list, I get the error. (but I still have to re-test a backup command with a cipher not known to the client)

Thanks

Last edited by jybleau (2019-07-10 18:29:00)

Offline

#12 2019-07-10 19:29:52

Rasmus
Member
Registered: 2019-06-24
Posts: 4

Re: Error DFUPCID0

So, I installed xsi-pro 11.2.6 on my backup esxi server (I dont even know if I am allowed to), and inserted the switch that user jybleau sugested and now it works.
In my own oppinion, xsi-backup seems a little unstable and difficult to use, at least for a novice user as my self. I have spent countless hours on all sorts of problems that have arised, espesialy when using onediff. My company even bought a new server to use as a backup for the main esxi, just to be able to do a quick recovery in case of hardware failure. I am still not able to get a reliable run using cron. Onediff crashes and messes up the remote copy, and I have to reset the counter, and it takes more than 24 hours to start over again, just like today when the upgrade failed. It is a bit frustrating, and the cost of labour outruns the cost of a prooven backup system by far. Now I have invested so much time into this, and I feel that there is no way back. I need this to be reliable and to work as intended without the constant need of nursing the system. Is this at all possible?

Offline

#13 2019-07-10 22:04:33

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

To Rasmus:

We already asked you to contact support. You have pasted only part of the output, we don't know what is your job syntax, we don't know what are your case details cause you ommited the header where all general variables and versions appear. You need personalized help, we are sorry that you feel frustrated but we never said that this was for novices. Believe us, it's a lot simpler that you think it is.

On the other hand, if version 11.2.3 was working for you, why did you update to a newer one?

If you don't know what the support e-mail address is, just send us a form and we'll get back to you: https://33hops.com/formulario-de-contacto.asp

As general information: we do not support other ESXi "versions" than the official builds from VMWare.
Manufacturer builds are arbitrary modifications of the original software, we cannot support anything under the sun.

We have thoroughly tested latest XSIBackup versions on the official VMWare builds.

Offline

#14 2019-07-10 22:13:05

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

To jybleau:

Same as above, you said that you are using DELL builds. This manufacturer builds are not among the worse, DELL is a serious enterprise and they do a good job, but still, they incorporate arbitrary changes, so you might need to deal with them.

Offline

#15 2019-07-10 22:46:29

jybleau
Member
Registered: 2019-07-08
Posts: 4

Re: Error DFUPCID0

To admin:

I tested a backup command adding a cipher that is not found in my ssh -Q cipher output, and I got the error as I expected.
If it might be useful for you to know...

You don't need to say that you "[unfortunately] can't support anything under the sun"... I'm here to try to fix an issue and hopefully help build a tougher software. This kind of problem sometimes falls in the grey zone (at the beginning of the analyse at least).

I thought it was recommended to use the Dell build for my server model for the drivers, etc. Ya aye! Should have sticked to the official VMWare!

Thanks for your time and for the great piece of software; the pro version works very well for me; not necessarily easy for novices, I have read the manual more than once, watched the tutorials; there is a learning curve, my cronjob did not work at first attempt... But very satisfied overall.

Offline

#16 2019-07-10 23:35:19

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

Thank you very much for your feedback, that will help a lot. We probably entered a minefield when fine tweaking the ciphers depending on the ESXi/OpenSSH version, but the difference in performance is worth the time, as that, so many times named, chacha20-poly1305@openssh.com or some older or deprecated Less Secure Ciphers can boost throughput up to 30%

As stated DELL builds are not bad at all, especially when you compare them to some other manufacturers that I will not mention and whose ESXi builds in the past contained critical bugs and arbitrary modifications that even broke some base design principles of ESXi.

As a rule of thumb: VMWare certifies hardware on its own, you don't need a manufacturer build to be sure your hardware is supported. Manufacturers will usually claim that if you use their version, everything will run smoother and bla, bla, bla. I will leave the matter to your own thoughts and will just place a question the other way around: If you were a manufacturer, why would you invest a lot of money and resources to create a custom build when your hardware has already been certified by VMWare?...

I can sympathize with some users like Rasmus. XSIBackup has evolved through the years always adding more options. Of course there's always a default bahaviour, so you don't need to set too many arguments, but when it comes to use it over IP, especially when mixing ESXi versions, you need to at least take on account a number of things: ESXi version, VMFS version, OpenSSH version, etc...

The key is to always take it as easy as possible and use the same ESXi version, same VMFS version, share datastores when operating in a LAN, etc... If you can't use the same ESXi version you will need to at least use a common denominator Hardware Version.

©XSIBackup Datacenter is a total rethink of the same concept. It performs two actions: --backup and --replica, it does it really fast and simplifies usage greatly. You have a totally working trial version that copies VMs up to 40 GB.

Offline

#17 2019-07-11 18:04:35

admin
Administrator
Registered: 2017-04-21
Posts: 858

Re: Error DFUPCID0

We have been testing XSIBACKUP-PRO 11.2.6 all day with special focus on ESXi 6.5.0 and we have not been able to reproduce any cipher issue, OpenSSH versions seem to be perfectly able to negotiate a cipher with default options.

Of course we are referring to VMWare official builds. Should somebody encounter a similar issue, please contact support and we'll try to help you find a common cipher denominator and set it via the --ssh-ciphers argument.

Offline

Board footer