You are not logged in.
Pages: 1
Thanks very much. I will try it soon and let you know.
Hi,
I am not missing the src/functions file and it and the src directory are executable. I have installed it on 4 different 5.1 servers, all with the same result. I have tried copying the directories from a working 6.0 server but with the same result.
ls -ld src/vmfs/volumes/54a9c48e-14faed07-0e64-00215e5232d0/XSI/XSIBackup-Pro # ls -ld src
drwxr-xr-x 1 root root 8 Jan 5 21:49 src
/vmfs/volumes/54a9c48e-14faed07-0e64-00215e5232d0/XSI/XSIBackup-Pro # ls -l src
-rwx------ 1 root root 367 Jan 5 21:49 api
-rwx------ 1 root root 1171 Jan 5 21:49 cron-init
-rwx------ 1 root root 39965 Jan 5 21:49 functions
-rwx------ 1 root root 4131 Jan 5 21:49 instcron
-rwx------ 1 root root 2044 Jan 5 21:49 mapblocks
-rwx------ 1 root root 48818 Jan 5 21:49 onediff
drwxr-xr-x 1 root root 8 Jan 5 21:49 pro
-rwx------ 1 root root 13515 Jan 5 21:49 sendmail
-rwx------ 1 root root 171 Jan 5 21:49 version
-rwx------ 1 root root 48690 Jan 5 21:49 xsitools
Thanks,
Kelly.
Hi,
I am successfully running xsibackup 11.2.2 on ESXi 5.1.0 but I am trying to upgrade to 11.2.14 or 11.2.15 to install a fix you released for me in 11.2.14. But under ESXi 5.1, I get the errors shown below when I try to run xsibackup either straight after install or later from the command line. Please note that it runs fine on my other cluster running ESXi 6.0.0.
The software has been installed and permissions were applied
-----------------------------------------------------
Do you want to execute (c)XSIBackup now (yes/no): yes
-----------------------------------------------------
/scratch/XSI/XSIBackup-Pro/xsibackup: line 10: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 10: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 10: writeout: not found
touch: /scratch/XSI/XSIBackup-Pro/.ERR-: No such file or directory
touch: /scratch/XSI/XSIBackup-Pro/.ERR-: No such file or directory
touch: /scratch/XSI/XSIBackup-Pro/.ERR-: No such file or directory
touch: /scratch/XSI/XSIBackup-Pro/.ERR-: No such file or directory
I end up with a heap of files with names like shown below.
/vmfs/volumes/54a9c48e-14faed07-0e64-00215e5232d0/XSI/XSIBackup-Pro # ls
ERR-~1 ERR-~133 ERR-~168 ERR-~44 ERR-~79
ERR-~10 ERR-~134 ERR-~169 ERR-~45 ERR-~8
ERR-~100 ERR-~135 ERR-~17 ERR-~46 ERR-~80
ERR-~101 ERR-~136 ERR-~170 ERR-~47 ERR-~81
ERR-~102 ERR-~137 ERR-~171 ERR-~48 ERR-~82
ERR-~103
Thank you,
Kelly.
Thanks very much. I have tested this and it works correctly. It does not delete the backups that it successfully completed prior to the error and the error message is more meaningful when a VM has been migrated / vmotioned before its turn at being backed up.
Thank you. That is much appreciated.
I did read somewhere that the backup ID should be numeric but it was in this format when I started and seemed to work so I didn’t change it. As long as I don’t over 5 characters it seems to be OK. Is there something that won’t work if it is not numeric? I will change it - just curious. Does the name of the file that the job is stored in have to match the backup id?
Please see the details of my job included and you will see that —date-dir=yes. Every new backup when it starts will go to a different date-dir directory. I have no problem with vmfsktools deleting files at the START of a backup because it is a new directory every time. What I have a problem with it doing is deleting any backups that same single job has just created half way through the backup when it encounters an error. I can 100% tell you that this is what happens as I have watched it do it. The error I made in my first description that may have led you to misunderstand me is that I said it deleted everything from the —backup-point when I should have said —backup-point/date-dir.
So, if it backs up /vmfs/volumes/backup/2019121200000059/vm01 and then the next one is /vmfs/volumes/backup/2019121200000059/vm02 and then it hits the described error due to DRS as vm03 has migrated to another host, it then DELETES vm01 and vm02 from the date-dir directory and then continues to backup vm04.
I also have no problem with it continuing to backup vm04 but I have a massive problem with it deleting vm01 and vm02 which were successful backups. It deletes them NOT at the start of a new backup but part way through the one backup.
My backup window is so large that I would need to disable DRS permanently to fix this issue. I do not mind so much if it simply missed the migrated ones but It is unacceptable that the others are deleted.
I cannot confirm it for sure but I think it only happens with vmkfstools and not onediff or xsidiff. I certainly didn’t notice it with the others.
I would appreciate it if you tested it and check your code. Maybe when it errors in this instance the code is starting again from the beginning where it does actually delete everything in the directory. Or maybe some variables are incorrectly initialised or set and it loops back around and executes the deletion code. Or maybe it is in something in vmkfstools itself.
You have misunderstood me. The one backup backs up say 20 vms using a single job. It may have backed up 10 out of 20. It then hits the migrated vm that is no longer there. It then removes all files for the 10 vms it has only just backed up and continues to backup the remaining 9. At the end of the backup I may only have 9 out of 20 backups remaining. But more likely it comes across another migrated machine and the whole thing happens again and I might only be left with 3 backed up machines or even none.
This has occurred not just once but every day for a week on each of the 4 hosts.
This is happening on all 4 hosts in a cluster. The exact same job is running on a different cluster with no problems but I don’t see the migration problems on that cluster.
This seems like a big bug to me. I take your point about disabling DRS which I already did today after I finally worked out that this was the cause. It has been a very frustrating process.
I have just determined that the machines in question were vMotioned from one host to another between when xsibackup started and when it tried to back them up. It should not result in all backup files being deleted, however!
I am running xsibackup with --backup-prog=Vmkfstools and --backup-type=All. It may successfully backup many of my virtual machines until it thinks it has to backup a vm with no name. At this point it produces some errors saying that it is skipping that vm but then it DELETES ALL of the vm backups that it has already done up until this point (that is everything on my --backup-point). It then continues to backup the remaining vms. It might even happen again in the same backup and I am left with only a few backed up machines or none at all.
This happens on all 4 hosts in the cluster but works OK on other clusters.
I initially thought that something weird was happening with the --backup-room and --del-dirs options but I removed these with no improvement. I have watched the backup run and monitored the backup point and have witnessed it delete all of the files at the time when the errors occurred.
Please note that the VM ID it references does NOT show up when I run "vim-cmd vmsvc/getallvms includeConfigNotAvailable" and does not exist in /etc/vmware/hostd/vmInventory.xml. I do not know where xsibackup is getting it from.
Other relevant history:
- I was recently using --backup-prog=OneDiff and then --backup-prog=XSIdiff but changed to Vmkfstools as I was getting too many errors. I was also getting similar errors with those backup progs but it did not DELETE the other backups when the error occurred.
- XSIbackup version 11.2.2
- VSphere version 6.0
Backup Job:
"/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup" \
--backup-prog=Vmkfstools \
--date-dir=yes \
--backup-point=/vmfs/volumes/backup \
--backup-type=All \
--backup-how=Hot \
--backup-room=25000 \
--use-smtp=2 \
--mail-to=xxx@xxx.com.au \
--del-dirs=+3d \
--backup-id=esx6f \
--description="esx6 All Full" \
--exec=yes >> "/vmfs/volumes/esx6-local-1/xsi-dir/var/logs/xsibackup.log"
Errors in log file at time of file deletion:
-------------------------------------------------
2019-12-11T22:27:23| [] Starting backup (size is 40485M on 40962M file)
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:23| XSIBackup will backup your VMs while they are running, so that users can continue to use the VM
2019-12-11T22:27:23| while the backup is taking place. You can also run cold and warm --backup-how
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:23| Hot backup selected for VM: [], will not be switched off
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:25| [] error: the .vmx file was not found, this VM cannot be backed up
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:25| [] info: boot partition is MBR
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:26| Removing snapshots, please wait...
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:29| Error CLDELSN1: cannot delete snapshot VM Id: 705, details: (vim.fault.NotFound) {
2019-12-11T22:27:29| faultCause = (vmodl.MethodFault) null,
2019-12-11T22:27:29| msg = "Unable to find a VM corresponding to "705""
2019-12-11T22:27:29| }
2019-12-11T22:27:29| (vim.fault.NotFound) {
2019-12-11T22:27:29| faultCause = (vmodl.MethodFault) null,
2019-12-11T22:27:29| msg = "Unable to find a VM corresponding to "705""
2019-12-11T22:27:29| }
2019-12-11T22:27:29| cat: can't open '/vmfs/*.vmsd': No such file or directory
2019-12-11T22:27:30| Syncronizing config files
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:31| [] error: the .vmx file was not found, this VM cannot be backed up
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:31| [](705) warning: no .vmsd file found
2019-12-11T22:27:35| [] error DIFFEXUP: no VMDK disks present, skipping VM, nothing to backup
2019-12-11T22:27:36| [] info: VMWare tools were not detected, the system will not be quiesced
---------------------------------------------------------------------------------------------------------------------------------
2019-12-11T22:27:39| Backing up virtual disks...
---------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
Errors to Standard out for entire job (note it deleted all existing backups twice once at 699 and once at 705):
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
cat: can't open '': No such file or directory
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 9: to: not found
cat: can't open '': No such file or directory
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
cat: can't open '': No such file or directory
grep: : No such file or directory
cat: can't open '': No such file or directory
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 4: to: not found
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
cat: can't open '/vmfs/*.vmsd': No such file or directory
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 9: to: not found
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "699""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
cat: can't open '': No such file or directory
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 9: to: not found
cat: can't open '': No such file or directory
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
cat: can't open '': No such file or directory
grep: : No such file or directory
cat: can't open '': No such file or directory
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 4: to: not found
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
}
cat: can't open '/vmfs/*.vmsd': No such file or directory
/vmfs/volumes/esx6-local-1/xsi-dir/xsibackup: eval: line 9: to: not found
(vim.fault.NotFound) {
faultCause = (vmodl.MethodFault) null,
msg = "Unable to find a VM corresponding to "705""
Hi,
I would like to use --backup-prog=xsidiff for my xsibackups. My understanding is that I need a license key to backup using xsidiff if the vm is > 10gb. Can you please tell me how I go about doing this as I can't find the instructions anywhere on the website? From reading other people's questions, I know that I need to put the request.key somewhere and get back a license.key that I should put in the xsi directory but I cannot find where I need to upload request.key too.
We have licenses for xsibackup pro. Do I need a separate license.key for each host that I am backing up?
Thanks,
Kelly.
Pages: 1