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

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software


You are not logged in.

#1 Re: General matters » Speed shown in report email is calculated wrong » 2021-08-27 12:20:42

Int

Ok, so that is intentional.
Not what I would have expected from "Speed" but that's ok.
Thank you for the explanation.

#2 Re: General matters » Renamed VMs » 2021-08-27 12:12:20

Int

Thank you for the clarification.

#3 General matters » XSIBackup-DC achievable speed » 2021-08-27 08:08:06

Int
Replies: 1

Hi,

in the post
https://33hops.com/forum/viewtopic.php?id=504
and article
https://33hops.com/xsibackup-faster-dat … ckups.html
you explain in detail how the backup hardware should be designed to achieve a good performance.
Many thanks for that!

What I am missing is some real life examples.

Could you give some examples for some real computer and network hardware configuration used and
the speeds that where achieved with it?

This could give some reference to compare ones own hardware and data rates to.

#4 Re: General matters » Renamed VMs » 2021-08-27 07:58:33

Int

a VM that has been renamed (it is not named the same as the folder that contains it in the datastore)

I recognized a behaviour when a VM has been renamed.  XSIBackup-DC then creates two folders for the VM in the repo. One folder is named like the new VM name, the other is named like the folder.
The folder named like the new VM name is always empty, the actual backup data (map files) are placed the other folder which is named like the VMs folder.

Is this behaviour intentional?
Would it be possible not to create a empty folder named like the new VM name? I think it's just confusing to have two folders.

#5 General matters » Speed shown in report email is calculated wrong » 2021-08-27 07:40:08

Int
Replies: 3

Hi,

I recognized that the speed shown in the report email is calculated wrong.

Num 	VM Name 	Size 	                Diff. 	       State  Time 	Speed 	   Compress 	Errors
1 	[3] _IGMS07 	366.11 GB 	84.36 GB 	1 	01:19:42 	78.40 MB/s 	0 	0

The speed is calculated using the Full Size and the Time, not the actually transferred data (Diff.) and the Time.
So in the example above the real Speed is not 78.40 MB/s but actually 18.06 MB/s

#6 Re: General matters » Backups fail with Error code 1223 or 4574 » 2021-08-23 08:07:47

Int

Regarding the snapshot failures I found out the following:

For the machines that failed with Error code 1223 the vmware.log showed these error messages:

2021-08-14T05:15:01.439Z| vcpu-0| I125: ToolsBackup: changing quiesce state: COMMITTED -> FINISHING
2021-08-14T05:15:02.446Z| vcpu-0| I125: Msg_Post: Warning
2021-08-14T05:15:02.446Z| vcpu-0| I125: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
2021-08-14T05:15:02.446Z| vcpu-0| I125+ The error code was: 3
2021-08-14T05:15:02.446Z| vcpu-0| I125+ The error message was: Quiesce operation aborted
2021-08-14T05:15:02.446Z| vcpu-0| I125: ----------------------------------------
2021-08-14T05:15:02.448Z| vcpu-0| I125: ToolsBackup: changing quiesce state: FINISHING -> ERROR_WAIT

Which makes clear that the issue is within the VMs Windows OS.

Further investigation in the Windows event log showed multiple occurrences of Event ID 8 for Volsnap (a timeout occurred when Windows tried to make a snapshot).
But I could not make out a cause why this happened. There was sufficient free space to create the VSS snapshot and the I/O load was also low during that time.


For the machine that failed with Error code 4574 neither the vmware.log nor the Windows event log showed any helpful messages.


For all machines the "final" solution was to reboot the Windows OS. After the reboot the snapshot was working fine on all of them. Not a satisfying solution but at least it works now ...


I hope this information is helpful to others with the same issues.

#7 Re: General matters » Backups fail with Error code 1223 or 4574 » 2021-08-17 09:46:18

Int

Many thanks for having a second look at my job - I didn't spot that missing "\"

#8 Re: General matters » Backups fail with Error code 1223 or 4574 » 2021-08-17 06:15:22

Int

Can you tell something about these two minor questions I asked?

do you have an idea why the console output redirection in the job is not working?

/scratch/XSI/XSIBackup-DC/var/log/xsibackup.log is always empty.

Finally a minor cosmetic flaw I saw. The email says as summary "error count is: 2 " but in fact the count of errors is 3

#9 Re: General matters » Backups fail with Error code 1223 or 4574 » 2021-08-17 05:52:59

Int

Thank you for clarifying in detail what the problems with quiescing VMs with MS SQL server are.
I will go through your post and see if I can get it working.

I read the chapter about "--quiesce" in the manual
https://33hops.com/xsibackup-dc-full-ma … ml#quiesce
but these possible problems were not mentioned there.

Perhaps you can link to your post "Quiescing Windows OSs" from the manual?
This would help others to find this information and not to run into the same trap as I did, I think.

#10 Re: General matters » Backups fail with Error code 1223 or 4574 » 2021-08-16 15:42:47

Int

It seems that I accidentally posted in the wrong forum - I found out now that the different forums are hard to distinguish because they all are titled "Index» General matters"

If you would have read my post more carefully you would have recognized that I talk about "XSIBackup-DC" several times.

XSIBackup-DC Datacenter is version 1.5.0.13

Could you please move this post to the correct forum and read it again taking into account that it is about "XSIBackup-DC"?

#11 General matters » Backups fail with Error code 1223 or 4574 » 2021-08-16 07:46:49

Int
Replies: 9

Hi,

on this backup job

"/scratch/XSI/XSIBackup-DC/xsibackup" \
--backup \
"VMs(^(IGMS|VPN|XBH))" \
/vmfs/volumes/backup/repo-$(date +%Y) \
--backup-how=hot \
--exclude="vmware-[0-9]{1,6}.log" \
--quiesce \
--timestamp=$(date +%Y%m%d000000) \
--use-smtp=1 \
--mail-to=dummy@dummy.com
>> /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log 2>&1

the backup of three out of 19 VMs fails with these error codes (from the status Email):

· IGMS04: 2021-08-14T05:14:45 | Error code 1223 at file esxi.c, line 1223 | Error description: could not create snapshot in IGMS04, error: KO
· IGMS02: 2021-08-14T05:15:06 | Error code 1223 at file esxi.c, line 1223 | Error description: could not create snapshot in IGMS02, error: KO
· IGMS03: 2021-08-14T10:37:31 | Error code 4574 at file xsibackup.c, line 4574 | Error description: some error/s were raised while backing up: VMs(^(IGMS|VPN|XBH)), error count is: 2 

Unfortunately I don't have more details about the errors because the log file /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log
is empty. Btw. do you have an idea why the console output redirection in the job is not working?

The failing VMs have in common that they are all Windows machines (Windows 10 + Server 2016) and all have MS SQL Server running on them. The other non-failing VMs either don't have MS SQL server or are Linux machines.

Could it be that using option "--quiesce" doesn't play well with MS SQL Server?
I would appreciate any hints to solve this.

Finally a minor cosmetic flaw I saw. The email says as summary "error count is: 2 " but in fact the count of errors is 3

The ESXi server is Version 6.7.0 Update 3, XSIBackup-DC Datacenter is version 1.5.0.13

Best regards

#12 Re: General matters » xsibackup fails to find existing VM (solved) » 2021-07-13 14:50:01

Int

When starting the backup for all running VMs

xsibackup --backup "VMs(RUNNING)"

the VM was included in the list of VMs to backup but the backup itself did not work correctly.

The email report gave this garbled output for the VM

Num 	VM Name 	Size 	Diff. 	State 	Time 	Speed 	Compress 	Errors

16 	[9686dc-ab09e0c8-b200-a0369fd6b900/IGMS101/IGMS101.vmx] b200-a0369fd6b900/IGMS101/IGMS101.vmx 	2.00 MB 	0.00 B 	/vmfs/volumes/5c9686dc-ab09e0c8-b200-a0369fd6b900/IGMS101/IGMS101.vmx 	00:00:00 	inf MB/s 	1626120946 	0

I solved the issue by recreating the VM configuration (.vmx) from scratch and just kept the original virtual hard disks.
With this new VM configuration the xsibackup works fine now.

#13 Re: General matters » Snapshots are deleted when --backup-how=cold used on ESXi 7.0 (solved) » 2021-07-12 11:46:47

Int

Thank you very much.
I tested your bug fix in 1.5.0.10 successfully.

#14 Re: General matters » xsibackup fails to find existing VM (solved) » 2021-06-28 12:18:47

Int

When I remove all spaces, special characters and even capital characters xsibackup still fails with the same error:

2021-06-28T12:12:15 | Error code 2672 at file xsibackup.c, line 2672 | Error description: could not find any VM in list: xbcigms101zabbix, please check that the VM files exist

The datastore path of the VM also does not contain spaces or special characters.

#16 Re: General matters » use regexp for VMs source selection in XSIBackup-DC » 2021-06-26 14:30:06

Int
admin wrote:

Well, we didn't pretend to reach perfection in an ad-hoc written code snippet, just to point you in the right direction.

I didn't assume so and also did not expect perfection. That's why I wrote

Thank you very much for your code snippet - it pointed me in the right direction.

I shared my improved code to help other users of xsibackup.

You shouldn't treat each post which is pointing out a flaw as a criticism.

#17 General matters » Snapshots are deleted when --backup-how=cold used on ESXi 7.0 (solved) » 2021-06-26 14:13:08

Int
Replies: 5

In your post
https://33hops.com/forum/viewtopic.php?id=823
you clarify why snapshots must be deleted on ESXi 7.0, but also state this is only necessary when the VM is on:

deleting all snapshots previous to performing a backup or replica, only if the VM is on.

When xsibackup is started while the VM is off this works fine and the snapshots are preserved.

But when xsibackup is started with option "--backup-how=cold" while the VM is on, the snapshots are deleted:

Powering off VM: test001(21).
-------------------------------------------------------------------------------------------------------------
VM test001(21) is now off.
-------------------------------------------------------------------------------------------------------------
Virtual Machine Name: test001
-------------------------------------------------------------------------------------------------------------
(c)ESXi 7.0 or higher detected, all snapshots were removed for VM test001(21)
-------------------------------------------------------------------------------------------------------------
*** Skipping snapshot, VM is off ***
-------------------------------------------------------------------------------------------------------------

But since the VM is powered down before making the backup, isn't it unnecessary to delete the existing snapshots?

Would it be possible to change the behaviour of xsibackup to keep the snapshots when option "--backup-how=cold" is used?

#18 General matters » xsibackup fails to find existing VM (solved) » 2021-06-25 15:29:26

Int
Replies: 5

This call of xsibackup

xsibackup --backup "VMs(XBC_IGMS101 - Zabbix)"

fails although the VM exists with this name. This is the error produced:

2021-06-25T15:14:23 | Error code 2672 at file xsibackup.c, line 2672 | Error description: could not find any VM in list: xbc_igms101 - zabbix, please check that the VM files exist

"vim-cmd vmsvc/getallvms" shows that this VM really exists with this name:

64     XBC_IGMS101 - Zabbix       [SSD-RAID5] IGMS101/IGMS101.vmx                        centos8_64Guest         vmx-15

A similar backup call

xsibackup --backup "VMs(XBS_DMZ01 - Redmine Test)"

works just fine.

Could the VM hardware version be the cause?
The non-working VM has hardware version "vmx-15", the working VM has hardware version "vmx-14".

The ESXi host is Version:
6.7.0 Update 3 (Build 15160138)

#19 Re: General matters » use regexp for VMs source selection in XSIBackup-DC » 2021-06-25 14:01:48

Int

Thank you very much for your code snippet - it pointed me in the right direction.

Your code has some flaws. It doesn't work properly when the VM name contains spaces or when the VM annotation/description contains newlines.

I modified your code to address these two issues. This is what I came up with:

vim-cmd vmsvc/getallvms | sed -e '1d' -e 's/ \[.*$//' | awk '$1 ~ /^[0-9]+$/ {print substr($0,8,80)}' | grep -E "^W.*0" | sed ':a;N;$!ba;s/ *\n/,/g' | xargs

#20 General matters » use regexp for VMs source selection in XSIBackup-DC » 2021-06-22 06:31:46

Int
Replies: 5

Could you please explain how to use regexp for VMs source selection in XSIBackup-DC?

I tried different variants like --backup "VMs(REGEXP(^PROD))", --backup "REGEXP(^PROD)", ...
none of them works.


I am currently in the process of migrating from XSIBackup-Pro Classic to XSIBackup-DC Datacenter Edition.
I would like to use the regular expression for VM selection that I established in XSIBackup-Pro Classic.
If this does not work I would have to manually create large lists of VMs, which I would like to avoid.


The documentation only explains the optional regexp pattern to exclude disks from the backup.

Could you please add how to use regexp pattern for the source selection to
https://33hops.com/xsibackup-dc-full-ma … tml#source

#21 Re: General matters » Reg Exp and Date functions work in DC? » 2021-06-18 08:21:00

Int

Could you please answer my question about how to use regexp for VMs source selection in XSIBackup-DC?

I am currently in the process of migrating from XSIBackup-Pro Classic to XSIBackup-DC Datacenter Edition.
I would like to use the regular expression for VM selection that I established in XSIBackup-Pro Classic.
If this does not work I would have to manually create large lists of VMs, which I would like to avoid.

#22 Re: General matters » Reg Exp and Date functions work in DC? » 2021-06-17 07:57:24

Int
admin wrote:

Yes, there is a regexp option

could you please explain how to use regexp for VMs source selection in XSIBackup-DC?

I tried different variants like --backup "VMs(REGEXP(^PROD))", --backup "REGEXP(^PROD)", ...
none of them works.

#23 General matters » XSIBackup Edition VM size limit » 2021-06-16 10:59:17

Int
Replies: 1

The comparison of the XSIBackup Editions on https://33hops.com/xsibackup-vmware-esx … #prodchart
mentions "Unlimited VM size" which is not an available option for the free edition.

But I can not find anywhere what this VM size limit for the free edition actually is.

Could you please clarify?

#24 Re: General matters » Reg Exp and Date functions work in DC? » 2021-06-16 10:32:55

Int

The documentation only explains the optional regexp pattern to exclude disks from the backup.

Could you please add how to use regexp pattern for the source selection to
https://33hops.com/xsibackup-dc-full-ma … tml#source

#25 Re: General matters » All Snapshots are deleted » 2021-06-15 13:47:07

Int

Your documentation does not make clear that XSIBackup is silently deleting existing snapshots on ESXi 7.0

at
https://33hops.com/xsibackup-dc-full-ma … on-account
you still say

> We may introduce some code to delete any eventual pre-existing snapshot when ©ESXi 7.0 or above is detected, by now knowing this is left to the Sysadmin: if you want all data to be backed up, do not keep snapshots in production virtual machines. If you backup some VM with previous snapshots in ©ESXi 7.0, you will have to, by now, edit the .vmx file to point it to the base disks before using the restored file set.

Board footer