You are not logged in.
OK. FWIW it is not a question of having the time, but rather the necessary knowledge
But Filr4 uses PostgreSQL. What should I look for in the logs?
This VM is an appliance so upgrading is basically spinning up a new VM and migrating the data. It is a Linux VM. I could also take this up with the vendor. I have not had any problem with any other VM.
I will schedule a reboot next weekend. One difference I can see is that this VM does not have VMWare native tools but: open-vm-tools 10.3.10 build 12406962
Log:
2020-11-26T12:43:29.683Z info hostd[2099430] [Originator@6876 sub=Vimsvc.TaskManager opID=esxui-c329-c5d3 user=root] Task Created : haTask--vim.FileManager.makeDirectory-112209
2020-11-26T12:43:29.684Z info hostd[2099430] [Originator@6876 sub=Nfcsvc opID=esxui-c329-c5d3 user=root] Create requested for /vmfs/volumes/5e945a5b-865e687e-cfc0-b02628fba814/Filr4
2020-11-26T12:43:29.707Z info hostd[2099430] [Originator@6876 sub=Nfcsvc opID=esxui-c329-c5d3 user=root] file mkdir (/vmfs/volumes/5e945a5b-865e687e-cfc0-b02628fba814/Filr4) by 'root'
2020-11-26T12:43:29.707Z info hostd[2099430] [Originator@6876 sub=Vimsvc.TaskManager opID=esxui-c329-c5d3 user=root] Task Completed : haTask--vim.FileManager.makeDirectory-112209 Status success
2020-11-26T12:43:29.888Z info hostd[2099446] [Originator@6876 sub=DatastoreBrowser opID=esxui-9824-c5e6 user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] recursive:false
2020-11-26T12:43:33.300Z info hostd[2098919] [Originator@6876 sub=DatastoreBrowser opID=esxui-5060-c5f3 user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] Filr-3.0 recursive:false
2020-11-26T12:43:35.093Z info hostd[2099455] [Originator@6876 sub=DatastoreBrowser opID=esxui-9add-c5fa user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] Filr-3.0 recursive:false
2020-11-26T12:43:38.179Z info hostd[2098919] [Originator@6876 sub=DatastoreBrowser opID=esxui-747-c600 user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] recursive:false
2020-11-26T12:43:39.767Z info hostd[2099451] [Originator@6876 sub=DatastoreBrowser opID=esxui-fe88-c605 user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] Filr4 recursive:false
2020-11-26T12:43:41.719Z info hostd[2099447] [Originator@6876 sub=DatastoreBrowser opID=esxui-e581-c612 user=root] DatastoreBrowserImpl::SearchInt MoId:5e945a5b-865e687e-cfc0-b02628fba814-datastorebrowser dsPath:[datastore1] Filr-3.0 recursive:false
2020-11-26T12:43:41.774Z info hostd[2099444] [Originator@6876 sub=Vimsvc.TaskManager opID=esxui-590c-c616 user=root] Task Created : haTask--vim.VirtualDiskManager.copyVirtualDisk-112224
2020-11-26T12:43:41.776Z info hostd[2099436] [Originator@6876 sub=DiskLib opID=esxui-590c-c616 user=root] DISKLIB-LIB_CLONE : Failed to clone disk using Object Cloning
2020-11-26T12:43:41.898Z info hostd[2099436] [Originator@6876 sub=Libs opID=esxui-590c-c616 user=root] DDB: "adapterType" = "lsilogic" (was "buslogic")
2020-11-26T12:43:41.898Z info hostd[2099436] [Originator@6876 sub=Libs opID=esxui-590c-c616 user=root] DDB: "longContentID" = "cb04ad82ddf414bb7a409a538e3da8a0" (was "cd376258d9a7c6da085cfdbefffffffe")
2020-11-26T12:43:41.898Z info hostd[2099436] [Originator@6876 sub=Libs opID=esxui-590c-c616 user=root] DDB: "virtualHWVersion" = "7" (was "14")
2020-11-26T12:43:41.899Z info hostd[2099436] [Originator@6876 sub=DiskLib opID=esxui-590c-c616 user=root] DISKLIB-LINK : DiskLinkNativeVmfsCloneExisting: Failed to create native clone. (24).
2020-11-26T12:43:41.899Z info hostd[2099436] [Originator@6876 sub=DiskLib opID=esxui-590c-c616 user=root] DISKLIB-LIB_CLONE : Failed to create native clone on destination handle : The specified feature is not supported by this version (24).
2020-11-26T12:43:43.063Z info hostd[2098835] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5e945a5b-865e687e-cfc0-b02628fba814/Filr-3.0/Filr-3.0.vmx] State Transition (VM_STATE_OFF -> VM_STATE_CREATE_SCREENSHOT)
2020-11-26T12:43:43.064Z info hostd[2098835] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5e945a5b-865e687e-cfc0-b02628fba814/Filr-3.0/Filr-3.0.vmx] State Transition (VM_STATE_CREATE_SCREENSHOT -> VM_STATE_OFF)
2020-11-26T12:43:43.064Z info hostd[2099434] [Originator@6876 sub=Solo.ScreenHandler] Requested screenshot was zero bytes. Failing operation.
2020-11-26T12:43:46.963Z info hostd[2098919] [Originator@6876 sub=Default] IPMI SEL sync took 0 seconds 0 sel records, last 4
edit: Found this: [url=https://communities.vmware.com/t5/vSphere-Command-Line-Interface/ESXi-6-free-backup-via-vmkfstools-overriding-default-config/m-p/2672360](c)ESXi Free backup via vmkfstools[/url]
OK. I had this error in the past every other day with the Filr3 appliance. I upgraded this appliance to Filr4 a week ago and the upgraded appliance VM now emits this error on backup, every other day. The server is a brand new server with a RAID array.
• [ Tue Dec 1 05:11:08 UTC 2020 ] ERROR (DIFDELAL), details [Filr4] error: error deleting all snapshots VM [Filr4_XSIBAK] Id 12, error: Remove All Snapshots:• [ Tue Dec 1 05:11:16 UTC 2020 ] ERROR (DIFQMSH4), details [Filr4] error: first 500M mistmatch [Filr4-flat.vmdk]
• [ Tue Dec 1 05:11:24 UTC 2020 ] ERROR (DIFQMSH4), details [Filr4] error: first 500M mistmatch [Novell Filr-2_1-flat.vmdk]
• [ Tue Dec 1 05:11:32 UTC 2020 ] ERROR (DIFQMSH4), details [Filr4] error: first 500M mistmatch [Filr4_1-flat.vmdk]
• Remove all snapshots failed Command: vim-cmd vmsvc/snapshot.removeall 12 2>&1 • [ Tue Dec 1 05:11:32 UTC 2020 ] WARNING (DIFRMVMX), details [Filr4] measure DIFRMVMX: took measure, renamed remote .vmx file to reinitialize OneDiff
The log does not say why it cannot delete the snapshot:
---------------------------------------------------------------------------------------------------------------------------------
2020-12-01T05:11:07| [Filr4] info: deleting snapshot at [Filr4_XSIBAK] Id 12...
2020-12-01T05:11:08| [Filr4] error DIFDELAL: error deleting all snapshots VM [Filr4_XSIBAK] Id 12, details: Remove All Snapshots:
2020-12-01T05:11:08| Remove all snapshots failed
----------------------------------------------------------------------------------------------------------------------------
XSIBACKUP-PRO 11.2.19
VMware ESXi 6.7.0 build-14320388
OK. It is a raidset, but I will read that document you linked to and see what can be done. I will change the datastore to VMFS6 anyway an incoming weekend. The target server is the old server and it will just be used for backup and archival purposes.
This popped up as I am adding VMs to the backup job. It is always the same VM and the error ocurrs every other day:
Last error raised for the above VM:ERROR DIFQMSH4, details: [Filr-3.0] error: first 500M mistmatch [Filr-3.0_1-flat.vmdk]
• [ Mon Oct 12 05:11:14 UTC 2020 ] ERROR (DIFDELAL), details [Filr-3.0] error: error deleting all snapshots VM [Filr-3.0_XSIBAK] Id 15, error: Remove All Snapshots:• [ Mon Oct 12 05:11:22 UTC 2020 ] ERROR (DIFQMSH4), details [Filr-3.0] error: first 500M mistmatch [Filr-3.0-flat.vmdk]
• [ Mon Oct 12 05:11:30 UTC 2020 ] ERROR (DIFQMSH4), details [Filr-3.0] error: first 500M mistmatch [Novell Filr-2_1-flat.vmdk]
• [ Mon Oct 12 05:11:38 UTC 2020 ] ERROR (DIFQMSH4), details [Filr-3.0] error: first 500M mistmatch [Filr-3.0_1-flat.vmdk]
• Remove all snapshots failed Command: vim-cmd vmsvc/snapshot.removeall 15 2>&1 • [ Mon Oct 12 05:11:38 UTC 2020 ] WARNING (DIFRMVMX), details [Filr-3.0] measure DIFRMVMX: took measure, renamed remote .vmx file to reinitialize OneDiff
Any idea what may cause this?
XSIBACKUP-PRO 11.2.19
ESXi 6.7.0 build-14320388
I saw a post with a similar error and I checked that both machines run the same version of VMWare but the source has VMFS6 and the target VMFS5, could that be the issue?
Yes. You are right. I cannot make the error show up again. I tried running the installer four times. I guess the problem resolved itself and yes, as everything else works, then it must be able to find writeout.
Any news here? XSIBackup appears to run fine. I have created and scheduled jobs and the logs are fine, but those errors when installing are worrying me.
Yes. I had no difficulty installing the free version in the past on another server and yes, I have wiped everything and reinstalled. I have tried to provide as much info as possible.
When I installed, I did this:
Copied the files to /tmp
Ran the installer: chmod 0700 install && ./install
Answered the questions
From what I see, writeout is defined in src/functions. I have this:
[root@ESXI34:~] ls -l /scratch/XSI/XSIBackup-Pro/
total 1449
-rwx------ 1 root root 4617 Sep 15 13:39 EULA
-rwx------ 1 root root 6713 Sep 15 13:39 README.txt
drwxr-xr-x 1 root root 8 Sep 15 13:48 bin
drwxr-xr-x 1 root root 8 Sep 15 13:39 conf
drwxr-xr-x 1 root root 8 Sep 15 13:39 jobs
-rwx------ 1 root root 288 Sep 15 13:39 request.key
drwxr-xr-x 1 root root 8 Sep 15 13:39 src
drwxr-xr-x 1 root root 8 Sep 15 13:39 var
-rwx------ 1 root root 157596 Sep 15 13:39 xsibackup
-rwx------ 1 root root 1831 Sep 15 13:39 xsibackup_id_rsa
-rwx------ 1 root root 403 Sep 15 13:39 xsibackup_id_rsa.pub
[root@ESXI34:~]
[root@ESXI34:~] ls -l /scratch/XSI/XSIBackup-Pro/src
total 413
-rwx------ 1 root root 367 Sep 15 13:39 api
-rwx------ 1 root root 1171 Sep 15 13:39 cron-init
-rwx------ 1 root root 40321 Sep 15 13:39 functions
-rwx------ 1 root root 4131 Sep 15 13:39 instcron
-rwx------ 1 root root 2044 Sep 15 13:39 mapblocks
-rwx------ 1 root root 47530 Sep 15 13:39 onediff
drwxr-xr-x 1 root root 8 Sep 15 13:39 pro
-rwx------ 1 root root 13515 Sep 15 13:39 sendmail
-rwx------ 1 root root 171 Sep 15 13:39 version
-rwx------ 1 root root 48690 Sep 15 13:39 xsitools
[root@ESXI34:~]
May I emphasize that this server has never had any other version of XSIBackup installed!
Could it be a PATH issue?
ESXi 6.7.0 #1 SMP Release build-14320388 Aug 5 2019
OK. The offending lines are:
"$PWD"/bin/xsidiff --request-license
writeout "A request.key file has been generated in the root of the installation dir"
writeout "You can use this request.key file to get a license for your (c) XSIDiff binary"
writeout "Login here with your registered e-mail address: \e[1mhttps://33hops.com/user-login.html\033[0m"
Not that I understand why, but it does not seem to be fatal?
OK. So, tried again, still see the same errors??
[root@ESXI34:/tmp] chmod 0700 install && ./install
------------------------------
-> XSIBackup Installation <-
------------------------------
This will install XSIBackup to the desired directory
It is recommended that you use the root user for the
installation process, to avoid problems derived from
the lack of privileges.
Just provide the base path, the installation process
will create the XSIBackup-Pro root folder under it.
Where do you want to install XSIBackup to? (/scratch/XSI):
-----------------------------------------------------
XSIBackup will be installed to the following directory:
-----------------------------------------------------
Install dir: /scratch/XSI/XSIBackup-Pro
-----------------------------------------------------
Confirm that you want to install to the directory above (yes/no): yes
-----------------------------------------------------
Archive: /scratch/XSI/XSIBackup-Pro/XSIBACKUP-PRO.zip
creating: src/
inflating: src/api
inflating: src/cron-init
inflating: src/functions
inflating: src/instcron
inflating: src/mapblocks
inflating: src/onediff
creating: src/pro/
inflating: src/pro/borg
inflating: src/pro/certify
inflating: src/pro/custimgs
inflating: src/pro/esxbackup
inflating: src/pro/events
inflating: src/pro/host
creating: src/pro/menu/
inflating: src/pro/menu/common
inflating: src/pro/menu/config
inflating: src/pro/menu/crond
creating: src/pro/menu/help/
inflating: src/pro/menu/help/addLink.hlp
inflating: src/pro/menu/help/backupHow.hlp
inflating: src/pro/menu/help/backupPoint.hlp
inflating: src/pro/menu/help/backupProg.hlp
inflating: src/pro/menu/help/backupType.hlp
inflating: src/pro/menu/help/backupVMs.hlp
inflating: src/pro/menu/help/crondMain.hlp
inflating: src/pro/menu/help/editJobs.hlp
inflating: src/pro/menu/help/excludeDisks.hlp
inflating: src/pro/menu/help/jobsMain.hlp
inflating: src/pro/menu/help/listLinked.hlp
inflating: src/pro/menu/help/progOptions.hlp
inflating: src/pro/menu/help/regexpVMs.hlp
inflating: src/pro/menu/help/remotePoint.hlp
inflating: src/pro/menu/help/runJobs.hlp
inflating: src/pro/menu/help/schedJobs.hlp
inflating: src/pro/menu/help/setHost.hlp
inflating: src/pro/menu/help/watchJobs.hlp
inflating: src/pro/menu/help/xsiopts.hlp
inflating: src/pro/menu/jobs
inflating: src/pro/menu/link
inflating: src/pro/menu/main
inflating: src/pro/menu/restore
inflating: src/pro/menu/smtp
inflating: src/pro/menu/tools
inflating: src/pro/onediff
inflating: src/pro/onediffcert
inflating: src/pro/restore
inflating: src/pro/smartinfo
inflating: src/pro/vmsregexp
inflating: src/pro/xsitoolschk
inflating: src/pro/xsitprune
inflating: src/sendmail
inflating: src/version
inflating: src/xsitools
inflating: EULA
inflating: xsibackup
creating: bin/
inflating: bin/dd
inflating: bin/dialog
inflating: bin/lzop
inflating: bin/pv
inflating: bin/xsibackup-rsync
inflating: bin/xsidiff
creating: conf/
inflating: conf/dialogrc
inflating: conf/err-imsgs
inflating: conf/smtpsrvs
inflating: conf/xsiopts
-----------------------------------------------------
Applying permissions to files...
-----------------------------------------------------
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 71: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 72: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 73: writeout: not found
###########################################################################
# XSIBACKUP-PRO: END-USER LICENSE AGREEMENT #
###########################################################################
LAST UPDATED: 2018-02-08 (ISO FORMAT YYYY-MM-DD)
PLEASE READ THIS END-USER LICENSE AGREEMENT CAREFULLY BEFORE ACCEPTING IT,
DOWNLOADING OR USING XSIBACKUP-PRO ("APPLICATION"). BY ACCEPTING THE LICENSE
AGREEMENT, DOWNLOADING OR USING THE APPLICATION, YOU ARE AGREEING TO BE BOUND
BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS
OF THIS AGREEMENT, DO NOT CLICK ON THE "I AGREE" BUTTON AND DO NOT DOWNLOAD
OR USE XSIBACKUP-PRO.
LICENSE
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. GRANTS YOU A REVOCABLE,
NON-EXCLUSIVE, NON-TRANSFERABLE, LIMITED LICENSE TO DOWNLOAD, INSTALL AND USE
XSIBACKUP-PRO SOLELY FOR YOUR PERSONAL, COMMERCIAL OR NON▒COMMERCIAL PURPOSES
STRICTLY IN ACCORDANCE WITH THE TERMS OF THIS AGREEMENT.
RESTRICTIONS:
A) YOU AGREE NOT TO, AND YOU WILL NOT PERMIT OTHERS TO: LICENSE, SELL, RENT,
LEASE, DISTRIBUTE, TRANSMIT, OUTSOURCE, DISCLOSE OR OTHERWISE COMMERCIALLY
EXPLOIT XSIBACKUP-PRO OR MAKE XSIBACKUP-PRO AVAILABLE TO ANY THIRD PARTY.
B) YOU ARE ALLOWED TO MODIFY THE SOURCECODE TO TWEAK THE APPLICATION BEHAVIOUR
TO YOUR NEEDS, WITH THE EXCEPTION OF THE EULA AND LICENSE FILES AND ANY CODE
THAT MAY PRINT ON SCREEN. MODIFYING THE CODE TO REMOVE LIMITATIONS OF ANY FREE
OR TRIAL VERSION IS EXPRESSLY FORBIDDEN TOO.
C) YOU CAN USE XSIBACKUP-PRO TO GIVE SERVICE TO YOUR CUSTOMERS, JUST AS LONG
AS THIS SERVICE IS GIVEN EXCLUSIVELY UNDER YOUR OWN FACILITIES AND IS INSTALLED
ON DEVICES OF YOUR EXCLUSIVE PROPERTY.
D) XSIBACKUP-PRO HAS BEEN DESIGNED TO READ DATA FROM ONE PRIMARY LOCATION AND
WRITE THIS SAME DATA TO A SECONDARY LOCATION. THE APPLICATION DOES NOT MODIFY
THE CONTENTS OF THE DATA ON THE PRIMARY LOCATION. THUS THE APPLICATION CREATORS
SHALL NEVER BE RESPONSIBLE FOR ANY PRIMARY DATA LOSS AND YOU IMPLICITLY RECOGNIZE
YOUR RESPONSABILITY TO VERIFY THAT THE SECONDARY DATA HAS BEEN CORRECLTY WRITTEN
INTO THE DESIRED SECONDARY LOCATION.
E) 33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. WILL NOT ATTEND REQUESTS
REPORTING BUGS ON COPIES OF THE APPLICATION WHICH MD5 HASH IS NOT EXACTLY THE
SAME AS THE ORIGINALLY TRANSMITED UPON THE PURCHASE.
F) ANY SUPPORT REQUESTED FOR A COPY OF THE APPLICATION WICH MD5 CHECKSUM IS NOT
EXACTLY THE SAME AS THE ORIGINAL WILL BE CONSIDERED A SERVICE REQUEST AND WILL
BE SUBJECT TO CHARGE ACCORDING TO THE LAST PUBLISHED TARIFFS.
G) YOU ARE ALLOWED TO USE XSIBACKUP-PRO TO BACKUP UP TO 20 DIFFERENT HOSTS
BELONGING TO A SINGLE ORGANIZATION, IDENTIFIED BY A SINGLE TAX ID NUMBER, FROM
A SINGLE CRONTAB. IF YOU INSTALL THE CRONTAB TO ADDITIONAL SERVERS, YOU MUST BUY
ADDITIONAL LICENSES. THERE IS NOT ANY LIMITATION IN THE NUMBER OF GUESTS YOU MAY
BACKUP UP PER HOST,
MODIFICATIONS:
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. RESERVES THE RIGHT TO MODIFY,
SUSPEND OR DISCONTINUE, TEMPORARILY OR PERMANENTLY, XSIBACKUP-PRO OR ANY SERVICE
TO WHICH IT CONNECTS, WITH OR WITHOUT NOTICE AND WITHOUT LIABILITY TO YOU.
TERM AND TERMINATION:
THIS AGREEMENT SHALL REMAIN IN EFFECT UNTIL TERMINATED BY YOU OR 33HOPS, SISTEMAS
DE INFORMACION Y REDES, S.L.
THIS AGREEMENT WILL TERMINATE IMMEDIATELY, WITHOUT PRIOR NOTICE FROM 33HOPS,
SISTEMAS DE INFORMACION Y REDES, S.L., IN THE EVENT THAT YOU FAIL TO COMPLY WITH
ANY PROVISION OF THIS AGREEMENT. YOU MAY ALSO TERMINATE THIS AGREEMENT BY DELETING
XSIBACKUP-PRO AND ALL COPIES THEREOF FROM THE DEVICES IT MIGHT BE INSTALLED TO.
UPON TERMINATION OF THIS AGREEMENT, YOU SHALL CEASE ALL USE OF XSIBACKUP-PRO AND
DELETE ALL COPIES OF XSIBACKUP-PRO FROM YOUR MOBILE DEVICE OR FROM YOUR DESKTOP.
SEVERABILITY:
IF ANY PROVISION OF THIS AGREEMENT IS HELD TO BE UNENFORCEABLE OR INVALID, SUCH
PROVISION WILL BE CHANGED AND INTERPRETED TO ACCOMPLISH THE OBJECTIVES OF SUCH
PROVISION TO THE GREATEST EXTENT POSSIBLE UNDER APPLICABLE LAW AND THE REMAINING
PROVISIONS WILL CONTINUE IN FULL FORCE AND EFFECT.
AMENDMENTS TO THIS AGREEMENT:
33HOPS, SISTEMAS DE INFORMACION Y REDES, S.L. RESERVES THE RIGHT, AT ITS SOLE
DISCRETION, TO MODIFY OR REPLACE THIS AGREEMENT AT ANY TIME.
CONTACT INFORMATION:
IF YOU HAVE ANY QUESTIONS ABOUT THIS AGREEMENT, PLEASE CONTACT US AT 33HOPS.COM
-------------------------------------------------------------------------------
I ACCEPT THE LICENSE AGREEMENT (yes/no) yes
------------------------------------------------------------------------------------------------------------------
You can start now using XSIBACKUP-PRO 11.2.19
------------------------------------------------------------------------------------------------------------------
[root@ESXI34:/tmp]
Yes, but I was stupid and removed the symlink to scratch... Can I just recreate it?
Edit: Ah. It is recreated on boot
OK. I tried the uninstall under Tools in the GUI and got this:
/scratch/XSI/XSIBackup-Pro/src/pro/menu/main: line 181: /scratch/XSI/XSIBackup-Pro/bin/dialog: not found
/scratch/XSI/XSIBackup-Pro/src/pro/menu/main: line 171: /scratch/XSI/XSIBackup-Pro/bin/dialog: not found
/scratch/XSI/XSIBackup-Pro/src/pro/menu/main: exec: line 176: /scratch/XSI/XSIBackup-Pro/src/pro/menu/main: not found
[root@ESXI34:/tmp]
So I used the manual method and deleted the scratch dir. Crap! I should not have done so..
OK. The link you provided in your reply is broken. Should I use the GUI remove under tools? So I should just install in the new VMWare server, right?
Edit: You mean this link?
[url=https://33hops.com/xsibackup-uninstall-procedure.html](c)XSIBackup Uninstall Procedure[/url]
Saludos!
I have finally gotten around to installing the Pro version we bought in March. This was on our new VMWare server (v6.7) that has never had XSI installed. I also installed to the old server that had the free version before. The idea is to copy vital VMs from the nex to the old each night.
I have a few questions so far:
The installer said this:
Applying permissions to files...
-----------------------------------------------------
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 71: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 72: writeout: not found
/scratch/XSI/XSIBackup-Pro/xsibackup: line 73: writeout: not found
###########################################################################
# XSIBACKUP-PRO: END-USER LICENSE AGREEMENT #
###########################################################################
Can I ignore the three "not found" lines? Got this on both servers
When I start it with /scratch/XSI/XSIBackup-Pro/xsibackup
It says XSIBACKUP-FREE 11.2.19?
On our old server, the installation seems to have added it to the path automatically, ie I could just type "xsibackup", now I have to use the full path
When I try running a backup from the new server to the old, ie:
[root@ESXI34:/tmp] /scratch/XSI/XSIBackup-Pro/xsibackup --backup-point="10.0.20.36:22:/vmfs/volumes/Storage2TB/back
up" --backup-type=custom --backup-vms="DEV01" --backup-prog=Onediff
The copy errors out with:
Info: transfering file | /vmfs/volumes/datastore1/DEV01/DEV01_1-flat.vmdk
------------------------------------------------------------------------------------------------------------------
Info: activate your (c)XSIDiff license to boost transfer speed
------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------
[DEV01] CLXSIDF1 error: file transfer error: sh: /vmfs/volumes/5f5f1892-652aa386-61e5-74867aed9da0/XSI/XSIBackup-Pro/xsibackup/vmfs/volumes/5d8f4d7a-e9c21ba4-8ad7-74867aed9da0/xsi-dir/xsibackup/vmfs/volumes/datastore1/xsi-dir/xsibackup/scratch/XSI/XSIBackup-Pro/bin/xsibackup-rsync: not foundrsync: connection unexpectedly closed (0 bytes received so far) [sender]rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.0]
------------------------------------------------------------------------------------------------------------------
Excluded disks removed from backup .vmx file
Any ideas?
Edit:
Adding --remote-xsipath="/scratch/XSI/XSIBackup-Pro" fixed the file transfer error.
You are absolutely right and the intention is to upgrade the old server as soon as I have all VMs moved to the new. I was just checking in case the HW will not allow it, but In that case I will try the most recent that runs.
Just checking.. Have been running XSI free, but bought the pro version for the new server that I am installing. The new server is running ESXi 6.7 and the old is running 5.5. The idea was to keep the old server as backup and run all production VMs on the new and then copy them nightly to the old, to serve as hot backups.
If possible, I will upgrade the old server to 6.7 also, but if this is not possible, can I run different versions of ESXi, provided i keep the virtual machine versions at a level, supported by both?
Hmm.. Still trying to figure out how XSIBackup uses snapshots.. Am I right in assuming that if I leave out "backup-prog" entirely, then it uses the built in VMWare tools? I was under the impression that it would strip all snapshots when doing so? It does not appear to do that now though? Ie in the log:
2020-03-07T21:27:27| Removing snapshots, please wait...
But when I check the VM, snapshots are still there?
Anyway. Server is upgraded now so I can delete that snapshot. Should I also delete the snapshot OneDiff created, before changing my backup-prog back from none to OneDiff?
Also, with XSitools it now creates a full backup in a new folder, named "20200306200006" for every new backup.
OK. When I do so, it does not remove the "xsibackupdiff 1" snapshot. Is that to be expected? Should I leave it there or remove all snapshots before I turn back to OneDiff after the upgrade?
OK. Note that I will need this extra snapshot just for a while, until I have verified that the patch install went OK.
Naturally would one option be to change the backups to use XSItools, create the snapshot, do the upgrade and then change back when I have verified that all is OK.
OK. The current installation is in: /vmfs/volumes/datastore1/xsi-dir
I will make a backup of the job files and uninstall, following the instructions above this weekend.
Currently running XSIBACKUP-FREE 11.2.8. Have bought the pro version. I have not set up any connections to other servers yet. Do I just run the script that was generated for me? It will retain my current jobs?
Hi!
We run XSIBackup nightly to create OneDiff copies of VMs to a separate disk:
/vmfs/volumes/datastore1/xsi-dir/xsibackup --backup-prog=Onediff --backup-point=/vmfs/volumes/Storage2TB/backup --backup-type=custom --backup-vms="nod1"
The backup creates a snapshot named "xsibackupdiff"
Question is: I want to install updates to one VM, but would like to do a snapshot beforhand. This snapshot will be created after "xsibackupdiff", right? Will this interfere with the onediff snapshot?
Anything else I need to think of? I just like to have a snapshot in case the install of updates causes problems.
It ran just fine during the night. Time to add a few more VMs to the job.
Thanks (Muchas Gracias) again for providing this excellent piece of software!