Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

herrep

Member

From: Munich

Registered: 2019-07-08

Posts: 106

XSIBackup-DC 1.5.1.4: Information or warning treated as error

Hi,

Once it happened that the available space in the remote FS could not be determined:

2021-11-28T21:26:33 | Error code 1547 at file common.c, line 1547 | Error description: could not get remote FS available space at /vmfs/volumes/nas-holzkirchen-backup/hpdl380p/replica-hot, details: Interrupted system call
-------------------------------------------------------------------------------------------------------------
Available space in backup volume:           -1 (17179.87 PB)

The result was that the report email reported an error for replicating the respective VM:

2021-11-28T21:32:58 | Error code 4701 at file xsibackup.c, line 4701 | Error description: some error/s were raised while backing up: VMs(server.herre.at), error count is: 1

However, as long as the backup can be successfully performed, there is no need to raise an error. WOuld it be more appropriate to raise a warning or info message?

Best regards,
Peter

admin

Administrator

Registered: 2017-04-21

Posts: 2,057

Re: XSIBackup-DC 1.5.1.4: Information or warning treated as error

(c)XSIBackup is backup software as its name reflects. It's conservative software by design.

No, we are not going to go over such an error with a warning, it is indeed a gross error that deserves immediate action from part of the sys admin.

cuchillo

Member

Registered: 2019-01-03

Posts: 50

Re: XSIBackup-DC 1.5.1.4: Information or warning treated as error

I get Error code 1547 too. The target of backup is XSI-NAS... It seems like XSI-Backup-DC can not get free space from XSINAS. How to solve this?

herrep

Member

From: Munich

Registered: 2019-07-08

Posts: 106

Re: XSIBackup-DC 1.5.1.4: Information or warning treated as error

At present, XSIBackup-DC has two major issues in conjunction with estimating whether a backup can be stored at the requested destination.

The first issue is that XSIBackup-DC cannot reliably calculate the required amount of space for a backup. For example, if you exclude files from backup, the size of the excluded files is not deducted from the required amount of space. Therefore, XSIBackup-DC reports a WARNING like this:

Not enough space to backup server: avail 12.46 TB | required 40.69 TB

However, XSIBackup-DC ignores this warning, does not raise any error and successfully completes the backup without any further issues.

Unfortunately, this behavior is not kept the same way for the second issue: Sometimes, the destination system does not correctly report back the amount of available space. This second issue, while resulting in the same situation of not being capable of predicting whether the backup will fail or not, is treated differently:

2021-11-28T21:26:33 | Error code 1547 at file common.c, line 1547 | Error description: could not get remote FS available space at ..., details: Interrupted system call
-------------------------------------------------------------------------------------------------------------
Available space in backup volume:           -1 (17179.87 PB)

The result is: If XSIBackup-DC determines that the required backup space does not fit into the available backup space although it does, no error is raised. If the destination system does not report back any available space so that XSIBackup-DC does not know whether the required backup space fits into the available backup space, an error is raised although the backup has successfully completed.

I do not know what design constraints are behind this decision, but from a user experience the same result is treated differently.

admin

Administrator

Registered: 2017-04-21

Posts: 2,057

Re: XSIBackup-DC 1.5.1.4: Information or warning treated as error

However, XSIBackup-DC ignores this warning, does not raise any error and successfully completes the backup without any further issues.

As said, conservative by design.

Unfortunately, this behavior is not kept the same way for the second issue: Sometimes, the destination system does not correctly report back the amount of available space. This second issue, while resulting in the same situation of not being capable of predicting whether the backup will fail or not, is treated differently:

Of course it's treated differently, it has nothing to do with lack of space. This error is telling you the remote command to retrieve the available space failed.

I do not know what design constraints are behind this decision, but from a user experience the same result is treated differently.

You are comparing two different situations that have nothing to do between them.