Posts by fuzzyduck

fuzzyduck · General matters

Hi,

is there a way to only add a VM to a backup job when it has been changed/used? Like check for vmdk filesize/dates etc?

Now i have included a VM on a daily cron but which has been turned off for quite a while, but i want it scripted just in case. Unfortunately it now keeps pumping gigabytes from disk to disk on a daily basis.

thanks

fuzzyduck · General matters

In MY CASE i removed the VMSD file containing a list of all the snapshots which supposed to exist but didnt, since i only had a Flat VMDK file. I booted and backup appears to be intact.

fuzzyduck · General matters

I removed the VMSD file containing a list of all the snapshots which supposed to exist but didnt, since i only had a Flat VMDK file. I booted and backup appears to be intact.

So why was the VMSD file made in the first place?

fuzzyduck · General matters

To be clear:

1. Flawlessly working U2.
2. Made backup with XSI on U2.
3. Installed another bodged update U3 from the boys over at VMware: see esxi cannot boot after updating to 6.7 u3
4. Rolled back to U2 by reinstalling U2 over failed U3 with option to keep VM's as stated in that topic.
5. Registered that backup made on the running U2.
6. Enumerate error.

But i think i have an update. I removed the VMSD file from the dir and i think the VM booted fine. the VMSD file contains a list of all the snapshots vmdk-files which where not in the dir in the first place(?), indeed just the flat file like you stated.

So maybe problem solved. And yes; With U3 im on my own. But im a tinkering homelab user on non supported hardware

fuzzyduck · General matters

Disk consolidation says:

Disk consolidation for "VM Nextcloud from Backups" has failed: Detected an invalid snapshot configuration

-------------------------------------

Deleting all snapshots says:

Failed to delete all snapshots from virtual machine 'Nextcloud from Backups'

-------------------------------------

My VMSD file has the following:

.encoding = "UTF-8"
snapshot.lastUID = "36"
snapshot.current = "36"
snapshot0.uid = "6"
snapshot0.filename = "Nextcloud V2-Snapshot6.vmsn"
snapshot0.displayName = "pre apt"
snapshot0.type = "1"
snapshot0.createTimeHigh = "362255"
snapshot0.createTimeLow = "-1655509330"
snapshot0.numDisks = "1"
snapshot0.disk0.fileName = "Nextcloud V2.vmdk"
snapshot0.disk0.node = "scsi0:0"
snapshot.numSnapshots = "15"
snapshot1.uid = "7"
snapshot1.filename = "Nextcloud V2-Snapshot7.vmsn"
snapshot1.parent = "6"
snapshot1.displayName = "pre v16 test"
snapshot1.createTimeHigh = "362455"
snapshot1.createTimeLow = "-1143587037"
snapshot1.numDisks = "1"
snapshot1.disk0.fileName = "Nextcloud V2-000001.vmdk"
snapshot1.disk0.node = "scsi0:0"
snapshot2.uid = "9"
snapshot2.filename = "Nextcloud V2-Snapshot9.vmsn"
snapshot2.parent = "7"
snapshot2.displayName = "pre 16 probeer"
snapshot2.createTimeHigh = "362518"
snapshot2.createTimeLow = "460818640"
snapshot2.numDisks = "1"
snapshot2.disk0.fileName = "Nextcloud V2-000003.vmdk"
snapshot2.disk0.node = "scsi0:0"
snapshot3.uid = "10"
snapshot3.filename = "Nextcloud V2-Snapshot10.vmsn"
snapshot3.parent = "9"
snapshot3.displayName = "apt en 16 test 3"
snapshot3.createTimeHigh = "362607"
snapshot3.createTimeLow = "-418619533"
snapshot3.numDisks = "1"
snapshot3.disk0.fileName = "Nextcloud V2-000004.vmdk"
snapshot3.disk0.node = "scsi0:0"
snapshot4.uid = "12"
snapshot4.filename = "Nextcloud V2-Snapshot12.vmsn"
snapshot4.parent = "10"
snapshot4.displayName = "pre 16.0.1 en apt"
snapshot4.type = "1"
snapshot4.createTimeHigh = "362758"
snapshot4.createTimeLow = "1170203190"
snapshot4.numDisks = "1"
snapshot4.disk0.fileName = "Nextcloud V2-000002.vmdk"
snapshot4.disk0.node = "scsi0:0"
snapshot5.uid = "14"
snapshot5.filename = "Nextcloud V2-Snapshot14.vmsn"
snapshot5.parent = "12"
snapshot5.displayName = "pre collabora docker pull"
snapshot5.type = "1"
snapshot5.createTimeHigh = "362829"
snapshot5.createTimeLow = "-1066121014"
snapshot5.numDisks = "1"
snapshot5.disk0.fileName = "Nextcloud V2-000005.vmdk"
snapshot5.disk0.node = "scsi0:0"
snapshot6.uid = "18"
snapshot6.filename = "Nextcloud V2-Snapshot18.vmsn"
snapshot6.parent = "14"
snapshot6.displayName = "pre apt"
snapshot6.createTimeHigh = "363291"
snapshot6.createTimeLow = "-1648858765"
snapshot6.numDisks = "1"
snapshot6.disk0.fileName = "Nextcloud V2-000006.vmdk"
snapshot6.disk0.node = "scsi0:0"
snapshot7.uid = "23"
snapshot7.filename = "Nextcloud V2-Snapshot23.vmsn"
snapshot7.parent = "18"
snapshot7.displayName = "pre apt grote"
snapshot7.createTimeHigh = "363683"
snapshot7.createTimeLow = "-914734759"
snapshot7.numDisks = "1"
snapshot7.disk0.fileName = "Nextcloud V2-000007.vmdk"
snapshot7.disk0.node = "scsi0:0"
snapshot8.uid = "24"
snapshot8.filename = "Nextcloud V2-Snapshot24.vmsn"
snapshot8.parent = "23"
snapshot8.displayName = "pre 16.0.2"
snapshot8.type = "1"
snapshot8.createTimeHigh = "363764"
snapshot8.createTimeLow = "-2145891948"
snapshot8.numDisks = "1"
snapshot8.disk0.fileName = "Nextcloud V2-000008.vmdk"
snapshot8.disk0.node = "scsi0:0"
snapshot9.uid = "26"
snapshot9.filename = "Nextcloud V2-Snapshot26.vmsn"
snapshot9.parent = "24"
snapshot9.displayName = "pre apt en NC update"
snapshot9.type = "1"
snapshot9.createTimeHigh = "363905"
snapshot9.createTimeLow = "-718706524"
snapshot9.numDisks = "1"
snapshot9.disk0.fileName = "Nextcloud V2-000009.vmdk"
snapshot9.disk0.node = "scsi0:0"
snapshot10.uid = "28"
snapshot10.filename = "Nextcloud V2-Snapshot28.vmsn"
snapshot10.parent = "26"
snapshot10.displayName = "pre apt"
snapshot10.createTimeHigh = "364106"
snapshot10.createTimeLow = "-1816108664"
snapshot10.numDisks = "1"
snapshot10.disk0.fileName = "Nextcloud V2-000010.vmdk"
snapshot10.disk0.node = "scsi0:0"
snapshot11.uid = "29"
snapshot11.filename = "Nextcloud V2-Snapshot29.vmsn"
snapshot11.parent = "28"
snapshot11.displayName = "pre apt"
snapshot11.createTimeHigh = "364341"
snapshot11.createTimeLow = "-1705005599"
snapshot11.numDisks = "1"
snapshot11.disk0.fileName = "Nextcloud V2-000011.vmdk"
snapshot11.disk0.node = "scsi0:0"
snapshot12.uid = "30"
snapshot12.filename = "Nextcloud V2-Snapshot30.vmsn"
snapshot12.parent = "29"
snapshot12.displayName = "pre RC update en apt"
snapshot12.createTimeHigh = "364540"
snapshot12.createTimeLow = "-126482367"
snapshot12.numDisks = "1"
snapshot12.disk0.fileName = "Nextcloud V2-000012.vmdk"
snapshot12.disk0.node = "scsi0:0"
snapshot13.uid = "34"
snapshot13.filename = "Nextcloud V2-Snapshot34.vmsn"
snapshot13.parent = "30"
snapshot13.displayName = "pre nieuwe RC en apt"
snapshot13.type = "1"
snapshot13.createTimeHigh = "364903"
snapshot13.createTimeLow = "-409531396"
snapshot13.numDisks = "1"
snapshot13.disk0.fileName = "Nextcloud V2-000013.vmdk"
snapshot13.disk0.node = "scsi0:0"
snapshot14.uid = "36"
snapshot14.filename = "Nextcloud V2-Snapshot36.vmsn"
snapshot14.parent = "34"
snapshot14.displayName = "pre apt"
snapshot14.type = "1"
snapshot14.createTimeHigh = "365430"
snapshot14.createTimeLow = "1338806494"
snapshot14.numDisks = "1"
snapshot14.disk0.fileName = "Nextcloud V2-000014.vmdk"
snapshot14.disk0.node = "scsi0:0"

As you read there i make a snapshot before an "Apt Upgrade", which tend to break Nextcloud sometimes. This time i forgot

So it thinks it has snapshots although i have just on VMDK file? (75Gb-ish which is correct)

Do i have to edit the VMSD to point to the big file? How?

Maybe im talking nonsense

fuzzyduck · General matters

Hi

Im using xsi-backup free and randomly(non-cron) run a backupscript to backup a couple of VM's:

/vmfs/volumes/5b9829e5-1fb54298-75cd-408d5c4a1692/xsi-dir/xsibackup --date-dir=yes --backup-point=/vmfs/volumes/Backups --backup-type=custom --backup-vms="Pihole,TVserver,Nextcloud"

All going well. Untill i tried installing U3 some days ago which failed to boot. I rolled back to U2 by installing it from a USB pendrive. All went well and it booted fine with VM's intact. Even the buildnumber was higer then the installed U2 (must have kept the new vibs, also it didnt took the updates to the point just before U3 and said they where already installed).

Now i screwed up a VM (called nextcloud) and took a backup made by XSI-backup free from BEFORE the crappy rollback to U2, registered it and tried to boot it:

Error - Unable to enumerate all disks

The files I have in the backup are:

Nextcloud V2.nvram
Nextcloud V2.vmdk
Nextcloud V2.vmx
Nextcloud V2.vmxf

I have tried boot it from the backupsource directly and also copy it first to the old location and then try it.

Before the rollback the backups where working fine, so it must be something ESXI related issue and so maybe its not a XSI thing but i hope anyone of you could help me out to run this backup.

Thanks in advance!

fuzzyduck · General matters

Dont worry, Im just a parttime geek with a homebrew esxi server running on a consumer board with non ECC-RAM

fuzzyduck · General matters

i rolled back to U1 and xsi is working again.

thx for the help.

fuzzyduck · General matters

As you dont have a previous build to roll back to, i dont think so. But better let someone answer with more experience than me

fuzzyduck · General matters

i just got in at 6.7. Patched to U1 and U2 now. I have never noticed anything unstable.

I could roll back to U1 though.

fuzzyduck · General matters

Thank you for the reply.

As a terminal novice i give up for now. Ill wait for a bugfix.

thanks

fuzzyduck · General matters

Is busybox used in esxi 6.5 something I can download somewhere?

Busybox binaries download

Rename busybox-x86_64 to busybox?

fuzzyduck · General matters

is it a certain VIB from U2 we can roll-back?

fuzzyduck · General matters

Same error today. Must be ESXI 6.7 U2 i installed. A couple of days ago i was running backups just fine on U1.

Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

#1 General matters » Only backup on change? » 2019-12-27 21:37:03

#2 Re: General matters » Backup completed: Failed - Unable to enumerate all Disks » 2019-11-19 08:22:18

#3 Re: General matters » Unable to enumerate all disks after rollback to ESXI6.7 U2 (solved) » 2019-10-10 09:05:43

#4 Re: General matters » Unable to enumerate all disks after rollback to ESXI6.7 U2 (solved) » 2019-10-07 18:43:18

#5 Re: General matters » Unable to enumerate all disks after rollback to ESXI6.7 U2 (solved) » 2019-10-07 09:35:12

#6 General matters » Unable to enumerate all disks after rollback to ESXI6.7 U2 (solved) » 2019-10-07 09:20:47

#7 Re: General matters » line 490: syntax error: unexpected "&" » 2019-05-02 19:59:56

#8 Re: General matters » line 490: syntax error: unexpected "&" » 2019-05-02 17:57:52

#9 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-30 08:10:39

#10 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-29 19:35:57

#11 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-26 20:05:14

#12 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-26 09:28:26

#13 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-25 20:40:28

#14 Re: General matters » line 490: syntax error: unexpected "&" » 2019-04-25 08:08:17

Board footer