©XSIBackup-Free: Free Backup Software for ©VMWare ©ESXi

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


Forum menu Menu

You are not logged in.

Pages: 1

#1 Re: Repositories » Repo on VMFS6 and block size related to file system capacity. » 2022-03-09 17:08:48

jybleau

Ok. Thank you for taking the time to provide a more detailed explanation. smile

I understand better now why it really matters not to store the repo directly on a VMFS.

#2 Re: Repositories » Repo on VMFS6 and block size related to file system capacity. » 2022-03-08 16:26:49

jybleau

Damn, I did that for the last 2 years using the classic version cool
It was not a big repo, fortunately.

I'll start using the replica action for storing directly on VMFS!


Ok, so, asking for another advise:
If my backup server is ESXI, with plenty of storage, is it viable to think I can put a deduplicated backup repo within a dedicated linux VM using ext4?

I don't have access to a dedicated NAS for backups, yet.

Thanks

#3 Repositories » Repo on VMFS6 and block size related to file system capacity. » 2022-03-08 05:20:39

jybleau
Replies: 7

Hello,

Regarding the number of files in a repo vs the capacity of a file system.

is it ok to use the default 1MB block size if a repo is stored on a VMFS6 volumes?
The total size of the VMs to backup is arround 300GB.

Or should I set the block size to 50MB like it was XSIBackup-pro-classic?


Second related question:

If I started backing up in a repo with XSIBackup-DC using a file size of 50MB, can I change it to a smaller file size and still backup into this repo without problems?

Thanks

#4 Re: © OneDiff » Error DFUPCID0 » 2019-07-10 22:46:29

jybleau

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.

#5 Re: © OneDiff » Error DFUPCID0 » 2019-07-10 18:27:51

jybleau

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

#6 Re: © OneDiff » Error DFUPCID0 » 2019-07-10 15:27:20

jybleau

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

#7 Re: © OneDiff » Error DFUPCID0 » 2019-07-09 22:49:30

jybleau

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

Pages: 1

Board footer