©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 General matters » Increase disk size of a vm machine » 2019-09-14 21:01:28

Rasmus
Replies: 1

Hi.
I need to increase the size of a disk in one of my VM's, and I am running XSIBackup.
I am not allowed to change disk size as long as there are any snapshots. After running XSIBackup, there are snapshots.
How would I go about this?

#2 Re: General matters » Link » 2019-08-29 12:40:47

Rasmus

Great. Got it working right away by pointing to the xsibackup_id_rsa file with the -i switch.

Thank you.

#3 General matters » Link » 2019-08-28 08:43:35

Rasmus
Replies: 2

Hi.
I have created a link between my two esxi hosts, and it seems to works as intended, however , if I try to manually SSH or SCP between the same two hosts, I get a password promt. I am trying to make an automated file transfer between these two hosts, but the transfer stops at the password promt.
Do I need to create a seperate RSA pair? Will the new Pair overwrite the old pair? Is it possible to have to separate RSA pairs?

Thank you.

#4 Re: General matters » Unable to enumerate all disks » 2019-08-26 11:01:30

Rasmus

Hi.
I had a look at the disk controllers on the severs, and you were (of course) right about the controller cache set to off.
I turned it on, and there is a substantional increase in performance and speed. Thank you.

Sincerely
Rasmus Børresen

#5 © OneDiff » Takes forever to remove snapshots » 2019-08-23 08:23:35

Rasmus
Replies: 1

Hello again.
I have been struggeling with OneDiff for some time now.
I am backing up 4 VM`s, 3 server 2012R2 and one Ubuntu.
Ubuntu and two of the 2012R2 servers are a breeze to copy. They are fairly small (40Gb), but our main server, also a 2012R2 is 120Gb with a second disk og 400Gb.
The smaller ones takes about 4-5 minutes each to mirror with OneDiff, while the large VM takes roughly 15 hours to mirror. it takes about 10 hours just to remove snapshots, and the 00001.vmdk files that are created by onediff are almost 100Gb. I have enabled less secure ciphers, but it appears to make no difference in speed. Transfer speed is about 4,5 - 5Mb/s. The system on both sides are esxi 6,7, so it wont accept blowfish ciphers.
So my main question is why the delta files are so huge, even when running onediff subsequently as soon as the first run is done? There should only be small changes to the VM during this time sequence.
The original VM is cluttered with logfiles and other xsi-backup related files from previous backups, both failed and successfull. Are these files in anyway hampering OneDiff?

Sincerely
Rasmus Børresen

#6 Re: General matters » Unable to enumerate all disks » 2019-08-15 21:24:23

Rasmus

I am still trying to figure out what to do here.
My backup scenario is like this:
4 vm`s on server A (HP Proliant ml350g9 ) with esxi 6.7
I am using onediff to mirror these vm`s over to server B (also a HP Proliant ml350g9 ) with esxi 6.7
On server A, I am also using vmkfstools to make historical backups to a local folder twice a week.
I am now unable to start any of the local backups on server A, due to snapshots in use by another disk, unable to enumerate all disks.
I just discovered that onediff creates a new snapshot for every run it does to mirror over to server B, and the original VM`s seems to run on these snapshots. Making a backup with vmkfstools to a local data store may not be a good idea after all, because the snapshots are preventing the backups to start. Is this a correct assumption? Is it not possible to use onediff and vmkfstools to backup the same VM`s to different locations, and if so, what would be the best way to back up vm`s to different locations?

#7 General matters » Unable to enumerate all disks » 2019-08-14 22:09:53

Rasmus
Replies: 4

Hi.
After struggling with xsibackup for a while, it finally appears to be running ok even when using cronservice to schedule my backups.
During quite a few failed attemps, xsibackup created several snapshots and files that I dont know what to do with. The backups I am creating are a combination of mirroring with onediff to a backup exsi server, and local backups using vmkfstools to create historical backups.
I just attempted to start up one of the local backup copies, and it will not start. The error is unable to enumerate all disks. One of the disks in this virtual machine is already in use by a virtual machine or by a snapshot. When I look at the snapshot manager, I see a snapshot called xsibackupdiff.
I dont know what to do with the snapshots, and I am really afraid to mess up the original VM`s. Also the backups that are created are only about half the size of the original VM.
What do I need do about this?

#8 Re: © OneDiff » Error DFUPCID0 » 2019-07-10 19:29:52

Rasmus

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?

#9 Re: © OneDiff » Error DFUPCID0 » 2019-07-10 13:18:27

Rasmus

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
----------------------------------------------------------------------------------------------------------------------------

#10 Re: © OneDiff » Error DFUPCID0 » 2019-07-09 21:16:14

Rasmus

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

#11 © OneDiff » Error DFUPCID0 » 2019-07-08 10:24:44

Rasmus
Replies: 16

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

Pages: 1

Board footer